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 Sunday December 21 2014, @06:33AM
Ok, I have to take issue with this. Partially because I like slackware, but also partially because you don't seem to think through your own argument.
You want, apparently, debian exactly. Except no systemd. So... Use devuan?
Also, wanting "debian exactly" but not systemd gets more contradictory every year. Debian has been riddled with poorly thought-out crapware like gnome3 and pulse for the last several years, and that's EXACTLY why systemd is now their init system. They follow popularity over quality. Every new release of debian has been measurably worse in code quality, well, at least since five.
So now you still want that, except this latest action is just over the line. Well, that's the direction they are headed. Towards worse code. So if you lose systemd, then the next thing they do probably sucks even more (not sure how that's possible, but they'll swing it somehow), and you have the same problem all over again.
And then you look at one distro that doesn't force crap on users, instead choosing to use whatever Patrick feels is actually best in stead of blindly "welp, the redhat PR team says it's great, so we'll go with it." And you dismiss that distro as a relic. Guess what: It might not seem "modern" to you but it's actually standing up for what users want, which seems to be exactly your problem with debian. I'm sorry you had to lose your distro, but maybe it's time to stand with people who will stand with you, instead of hoping to latch on to the easiest to use software like a remora.
There are more distros out there without systemd than slackware, find one you like and make it work.
novak
(Score: 0) by Anonymous Coward on Sunday December 21 2014, @10:12AM
> There are more distros out there without systemd than slackware,
please list them. a grateful public awaits your reply.
(Score: 1, Interesting) by Anonymous Coward on Sunday December 21 2014, @02:38PM
We can't actually use Devuan until a release is actually available. So you can fuck off with that suggestion.
And systemd infects Debian these days. In the past, I could install and run my Debian systems completely without using Lennart's or GNOME's shitty software. That's no longer the case. Now it is forced up me.
Yeah, we want Debian without systemd back. It worked fine for us. We don't need this systemd bullshit.
The only reason Slackware is "immune" to systemd is because Slackware is still stuck in 1998, for crying out loud! By your reasoning, the shitty HP-UX workstation I used in the early 1990s is "modern", too!
(Score: 2) by janrinok on Sunday December 21 2014, @07:38PM
Debian Wheezy does NOT use systemd - and will be supported for quite a while yet. Use Debian - it is simple, and you can stop complaining about the quality of a release that hasn't yet happened. Oh, you mean that you have already switched to Jessie and forgot that it hasn't even finished its development cycle yet? Well, perhaps you ought to think long and hard about what you want from your system and then choose the appropriate release.
Furthermore, even Jessie allows you to remove systemd and continue to use initd. Nobody is forcing you to use systemd!
(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