| |||||||||||||
Quotes of the weekQuotes of the weekPosted Mar 3, 2011 8:02 UTC (Thu) by Wummel (subscriber, #7591)Parent article: Quotes of the week
The /usr warning has no information in it whatsoever.
(Log in to post comments)
Quotes of the week Posted Mar 3, 2011 19:48 UTC (Thu) by mezcalero (subscriber, #45103) [Link]
Amazing, this ignorance!
systemd doesn't change anything here. There's no reason to avoid it. systemd itself will work fine if /usr is separate. However, a lot of stuff that we ship by default on most Linux distributions these days won't. We just warn about that *fact*.
So, let me repeat this and make this clear:
A) systemd itself works fine with seperate /usr
B) if you want to fix this, then fix the specific programs, which are not systemd
C) this is a statement of fact, on the status quo. It is not a change in any way. It isn't news in any way.
D) this is just a warning. You may ignore it if you wish.
Quotes of the week Posted Mar 4, 2011 11:19 UTC (Fri) by jospoortvliet (subscriber, #33164) [Link]
You know, Lennart, I love you ;-)
Of course in a very platonic way as my girlfriend would probably kill you if things were otherwise.
You combine a lovely straightforward (should I say German?) communication style with being annoyingly (to many) right at least most of the time...
Oh and the page on FD.o http://freedesktop.org/wiki/Software/systemd/separate-usr... is awesome in this regard :D
As far as I am concerned, you can keep this up. It amuses me to see ppl get railed up over nothing all the time and you telling them (rightly so) what idiots they are, hehe...
Quotes of the week Posted Mar 4, 2011 12:45 UTC (Fri) by nix (subscriber, #2304) [Link]
"I upgraded to systemd and now my system is throwing disturbing warnings" is hardly "nothing". The wiki link fixes everything: now we can see what the real problem is, and determine whether it applies to us.
Quotes of the week Posted Mar 4, 2011 15:22 UTC (Fri) by Wummel (subscriber, #7591) [Link] Yes, the Wiki link clarifies the warning message. The misleading warning text was the reason for the misunderstanding that most people (including me) had.So the real problem occurs when a) systemd queries udev information which executes a script in /usr and b) /usr is not yet mounted. One suggested solution is to move scripts from /usr/bin to /bin, another solution is to wait until /usr is mounted. Hopefully, there will soon be concrete bug reports with the offending udev rules so that those problems can be fixed.
Quotes of the week Posted Mar 4, 2011 19:32 UTC (Fri) by nix (subscriber, #2304) [Link]
No, systemd is executing a program in /lib/udev. The problem is that a few programs in /lib/udev depend on glib (which is often in /usr/lib) and a few depend on the USB or PCI databases under /usr/share. Without /usr, those databases are inaccessible, so everything which needs them will fail during coldplugging.
Quotes of the week Posted Mar 4, 2011 14:38 UTC (Fri) by mezcalero (subscriber, #45103) [Link]
I never publicly called anybody an idiot.
Quotes of the week Posted Mar 4, 2011 15:28 UTC (Fri) by Wummel (subscriber, #7591) [Link] And I agree. You explained the warning message and the misunderstanding is cleared up.Let's move on to fixing the technical problems that lead to the warning message.
Quotes of the week Posted Mar 4, 2011 15:51 UTC (Fri) by nix (subscriber, #2304) [Link]
No, that was me!
Moral: never post after four hours of commuting. (Of course, if I'd followed that advice for the last four years I'd never have posted at all.)
Quotes of the week Posted Mar 10, 2011 17:59 UTC (Thu) by welinder (guest, #4699) [Link]
> I never publicly called anybody an idiot.
That statement is not true. It's true for this thread, but not
For example:
http://www.mail-archive.com/pulseaudio-discuss@mail.0poin...
Quotes of the week Posted Mar 4, 2011 12:31 UTC (Fri) by NAR (subscriber, #1313) [Link] this is just a warning. You may ignore it if you wish.That is a bad user interface design. Shove some stuff to the user's face that he can (and in most cases should) ignore. This leads to users ignoring all warnings in the future. If it's not relevant - don't show it. If systemd itself works fine, but the interaction with udev leads to an error - produce a meaningful error message then.
Quotes of the week Posted Mar 4, 2011 12:36 UTC (Fri) by Darkmere (subscriber, #53695) [Link]
The issue is rather that the failure mode is hard to decipher and debug. Due to fallback and "robustness" of the stack, rather than breaking horribly when things are not where expected, much of this software will shut up and move on, doing it's best to avoid your system being unusable.
However, when you end up with a net result that mostly does not function, you have to get your warning from somewhere, and getting it from the init process is as good as any.
Also, remember that the kind of user who'd put /usr on it's own partition is not likely the user who'd ignore the errors or click through them. It's a user who's technically savvy, has enough knowhow of the oldschool things to commit to such a task, and as such, are well served by this warning.
|
|||||||||||||