SoylentNews is people
SoylentNews
A Debian user has recently discovered that systemd prevents the skipping of fsck while booting:
With init, skipping a scheduled fsck during boot was easy, you just pressed Ctrl+c, it was obvious! Today I was late for an online conference. I got home, turned on my computer, and systemd decided it was time to run fsck on my 1TB hard drive. Ok, I just skip it, right? Well, Ctrl+c does not work, ESC does not work, nothing seems to work. I Googled for an answer on my phone but nothing. So, is there a mysterious set of commands they came up with to skip an fsck or is it yet another flaw?
One user chimed in with a hack to work around the flaw, but it involved specifying an argument on the kernel command line. Another user described this so-called "fix" as being "Pretty damn inconvenient and un-discoverable", while yet another pointed out that the "fix" merely prevents "systemd from running fsck in the first place", and it "does not let you cancel a systemd-initiated boot-time fsck which is already in progress."
Further investigation showed that this is a known bug with systemd that was first reported in mid-2011, and remains unfixed as of late December 2014. At least one other user has also fallen victim to this bug.
How could a severe bug of this nature even happen in the first place? How can it remain unfixed over three years after it was first reported?
(Score: 3, Insightful) by VLM on Sunday December 21 2014, @12:41PM
Running the check on a modern HDD may be an hour-long distraction
The "linux people" have moved on to freebsd, where "zpool scrub zroot" runs in the background. Also on my SSD desktop with only a couple gigs of stuff, a scrub only takes a minute or so. We'll call it 20 seconds per gig. "Modern HDD" is an oxymoron other than multi-terabyte beasts that live in a fileserver at home or the NAS at work. I would have to check but I think I'm down to 4 spinning rust drives at home, 3 multi-terabyte beasts in the fileserver and one in the kids xbox.
The "enterprise java windows developers" have all taken over linux now and they're spreading their views over linux rather than merging into the community. So you get folks who think the design of systemd is a great idea, etc. We're stuck with windows ME edition thinking, running on a otherwise decent linux kernel.