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: 2) by novak on Monday December 22 2014, @06:19AM
We can't actually use Devuan until a release is actually available. So you can fuck off with that suggestion.
Yeah, I guess they don't plan to release until around the time a new debian stable comes out, in the mean time you can use debian 7, which has no systemd.
Yeah, we want Debian without systemd back. It worked fine for us. We don't need this systemd bullshit.
As do more than a few others. My point is that debian started dying years ago but no one could be bothered to notice then. It's only after the devs have delivered the final, killing blow to debian that people are starting to realize what happened.
Slackware is still stuck in 1998
No, it's not. At all, in any way. I assume you're either an idiot or haven't tried it if you say that. Slackware is a quality modern system, incorporating essentially all the same software as debian.
By your reasoning, the shitty HP-UX workstation I used in the early 1990s is "modern", too!
Ok, so, first, you're comparing hardware and software, which means you're either too angry or too stupid to think logically. Breathe. Second, slackware 14.1 is more up to date than debian stable. Just because you haven't bothered to try to understand something doesn't make it antiquated. Stop waving your lower jaw around like that and dissing the few good systems left.
novak