News for hackers. Stuff that matters.
Re:Skipping fsck during boot with systemd? by userbinator on Sunday December 21, 2014 @08:08AM (#8779656)
The way I interpreted his "solution" of "add a kernel boot parameter" was if you want to interrupt the fsck, you should hard-reset the machine to add it on the next boot, making it even more likely your filesystem will need fsck'ing. fsck itself is AFAIK safe with ctrl+c (i.e. it won't corrupt the filesystem further to interrupt it) so this change means users who really want to cancel a fsck have to take the route of possibly causing filesystem corruption themselves. Absolutely fscking insane.
Re:Skipping fsck during boot with systemd? by asveikau on Sunday December 21, 2014 @11:00AM (#8779997)
Is anyone else grossed out with the fact that systemd is parsing the kernel's command line? This is like if some program started reading unrelated crap from another program's command line, just because.

Edit: I guess downvoters don't care about code smell. This is literally like an unrelated process pulling out someone else's argv and using it as their own. Ick.

Re:Skipping fsck during boot with systemd? by the_why_of_y on Sunday December 21, 2014 @01:40PM (#8780492)
Linus Torvalds thinks it's perfectly fine and exactly how /proc/cmdline was intended to be used, but what does he know anyway? If systemd is doing it, it must be wrong.

http://lwn.net/Articles/593677/

Re:Skipping fsck during boot with systemd? by asveikau on Sunday December 21, 2014 @02:17PM (#8780586)
There is a lot of strong criticism of systemd in that thread. I was actually considering posting it as sympathetic to my point. It simultaneously expresses what both of us are saying. (You can read the command line, but don't do it for stupid shit.) From your link:

> But the problem appears when system services seem to think that they own those flags, and nothing else matters, and they don't do something "sane" any more.

Then later:

> It does become a problem when you have a system service developer who thinks the universe revolves around him, and nobody else matters, and people sending him bug-reports are annoyances that should be ignored rather than acknowledged and fixed. At that point, it's a problem.

Next paragraph indicates the rant is directed at Kay Sievers, udev and systemd developer, and his "continued bad behavior".

It does ring true for me as a user, I have noticed systemd-based systems spam a lot of things that used to be "for the kernel" and a bit more sacred, like dmesg and command line.

Re:Skipping fsck during boot with systemd? by Jasper_ on Sunday December 21, 2014 @01:19PM (#8780419)
The kernel command line has widely been considered an API to userspace. That's why the kernel exports it in /proc/cmdline.
Re:Skipping fsck during boot with systemd? by asveikau on Sunday December 21, 2014 @02:20PM (#8780595)
By this logic I might as well say everything in /proc is an API that I can use for any purpose, rotten or not. "It's ok because I read it from /proc/1276/mem". No sir, nothing bad about that design!
Re:Skipping fsck during boot with systemd? by darklajid on Sunday December 21, 2014 @10:55AM (#8779987)
No, the discussion was mostly about the parameter as a way to suppress fsck if you know you're in a hurry at boot time.

That argument was followed with other 'bad luck, if you want tonchange your choice' examples, like rm-ing a file. The argument sucks, but at no point a hard reset was part of the suggestion, really. More a "Yeah, so why didn't you pass the parameter and why do you complain about that afterwards"

That said, both sides of the discussion became immature rather quickly (my favorite is the "I killed a Windows 8 laptop because only that stopped the updates") and the issue isn't all that big in the first place, because systemd might support fsck interruption in the future/it seems to be on the todo list and therefor accepted as a missing feature.

Re:Skipping fsck during boot with systemd? by lclarkmichalek on Sunday December 21, 2014 @08:33AM (#8779714)
It's really not hard to add a kernel book param if you're booting via grub
Re:Skipping fsck during boot with systemd? by foxhill on Sunday December 21, 2014 @08:38AM (#8779722)
sigh i don't even.