@[email protected] to [email protected] • 24 days agoWhat's your favourite OS that does not use systemd?discuss.tchncs.deimagemessage-square233fedilinkarrow-up1707
arrow-up1707imageWhat's your favourite OS that does not use systemd?discuss.tchncs.de@[email protected] to [email protected] • 24 days agomessage-square233fedilink
minus-squareParade du Grotesquelinkfedilink10•24 days agoIt’s either Slackware (Linux, no systemd), OpenBSD or NetBSD. True story: I install a Red Hat server with a disk shelf with about 12 SAS disk in it. Red Hat has systemd. Everything works fine for a month. One (1) disk out of the 12 fails. No biggie. Shutdown the server cleanly. Replace disk. Flip power back on. Rebuild disk config. Simple, right? Wrong. You see, systemd is unhappy. It detects a new disk. It has lost a previous disk. And so, it refuses to boot. Period. Yes, there are ways out of this. But that was the day I decided systemd was the down of the devil.
minus-square@[email protected]linkfedilink11•24 days agoThis has never happened to me on a systemd server before. Methinks you left out some details
minus-square@[email protected]linkfedilink4•24 days agoProbably systemd panicked because disk id has changed. Not a reason to stop booting but that is why people hate it. Tries to handle everything, badly.
minus-squareThe_DecryptorlinkfedilinkEnglish3•23 days agoI mean, the point of the init process is to bring up the filesystem and disks, if the configuration is wrong that’ll be the process to complain about it.
minus-squarePossibly linuxlinkfedilinkEnglish1•22 days agoI once hit my head on a metal pipe From then forward I stopped using indoor plumbing
It’s either Slackware (Linux, no systemd), OpenBSD or NetBSD.
True story: I install a Red Hat server with a disk shelf with about 12 SAS disk in it. Red Hat has systemd. Everything works fine for a month.
One (1) disk out of the 12 fails. No biggie. Shutdown the server cleanly. Replace disk. Flip power back on. Rebuild disk config. Simple, right?
Wrong. You see, systemd is unhappy. It detects a new disk. It has lost a previous disk. And so, it refuses to boot. Period.
Yes, there are ways out of this. But that was the day I decided systemd was the down of the devil.
This has never happened to me on a systemd server before. Methinks you left out some details
Probably systemd panicked because disk id has changed. Not a reason to stop booting but that is why people hate it. Tries to handle everything, badly.
I mean, the point of the init process is to bring up the filesystem and disks, if the configuration is wrong that’ll be the process to complain about it.
I once hit my head on a metal pipe
From then forward I stopped using indoor plumbing