[systemd-devel] /usr on separate file system

[Lennart Poettering]

On Thu, 03.03.11 17:02, Matthew Miller (mattdm at mattdm.org) wrote:

> 
> On Thu, Mar 03, 2011 at 09:51:52PM +0100, Lennart Poettering wrote:
> > Why? systemd just warns you. systemd itself works fine with sperate
> > /usr. It's just a statement on the general ecosystem, a statement of
> > fact on the status quo.
> > 
> > systemd is just the messenger. Don't shoot the messenger.
> 
> If systemd works fine and you'll continue to commit to making it not be part
> of the problem, I don't see why it *should* be the messenger. There's plenty
> of ways in which I can seriously misconfigure my system that I don't expect
> systemd to warn me about. Basically all you are doing is asking for people
> to yell at you. :)

Well, we already get all those bugs about issues related to broken
separate /usr support all the time. It's a choice between bubonic plague
and cholera: either we get all those bugs and need to help folks track
them down each and every time, or we just educate folks what's going on
but we'll be yelled at while doing so.

It's a bit the same logic the kernel folks used when they introduced the
"tainted" flag for closed source modules.

I think it's better informing people what is going on instead of just
standing back and closing their bugs WONTFIX as they run into them.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.