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: 0) by Anonymous Coward on Sunday December 21 2014, @08:58AM
No, it doesn't work! Suspend on laptops, even older ones, is one thing you expect NOT to work with Linux.
> So in summary, in order to find yourself dealing with this problem as described, you have to have made 3 big mistakes - single > slice partitioning, shutting your laptop down instead of suspending work, AND using systemd. Three strikes and you are out.
You should remove BACKSPACE key in your keyboard, since you never need to correct yourself.
(Score: -1, Flamebait) by Anonymous Coward on Sunday December 21 2014, @09:57AM
You should remove BACKSPACE key in your keyboard, since you never need to correct yourself.
He can't -- the dumb-ass appears to be using a fucking typewriter.
What a twat; would ya look at that font choice?
(Score: 1) by Wrong Turn Ahead on Sunday December 21 2014, @10:07AM
Like!
(Score: 1) by dweezil-n0xad on Sunday December 21 2014, @01:58PM
No, it doesn't work! Suspend on laptops, even older ones, is one thing you expect NOT to work with Linux.
Suspend in Linux works fine in my experience.
(Score: 0) by Anonymous Coward on Sunday December 21 2014, @03:16PM
You must have that one specific early-2000s-era Thinkbook model where suspend isn't a total disaster. The rest of us happen to use other laptops and desktops that aren't that one specific early-2000s-era Thinkbook model where suspend isn't a total disaster. So for us, suspend is a total disaster!
(Score: 1) by dweezil-n0xad on Monday December 22 2014, @11:52AM
I remember having hangs after a resume when I was using Ubuntu on a cheap Lenovo laptop in 2010. Those problems disappeared when I switched that laptop to Arch Linux. Ubuntu is known for problems with suspend.
(Score: 2) by Arik on Sunday December 21 2014, @04:15PM
1996 called, they would like their FUD back.
If laughter is the best medicine, who are the best doctors?
(Score: 0) by Anonymous Coward on Sunday December 21 2014, @04:49PM
I don't think it's FUD. I've never had suspend or hibernate work out-of-the-box on any Linux system I've ever used, regardless of the distro, regardless of whether it was a desktop a laptop, and regardless of who manufactured the hardware. I've gotten it to work, but only after doing lots of reading online, lots of fiddling, and ultimately wasting far too much of my time.