Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Samuli Suominen <ssuominen@g.o>
Subject: Re: Re: newsitem: unmasking udev-181
Date: Sun, 11 Mar 2012 19:35:36 +0200
On 03/11/2012 07:33 PM, William Hubbs wrote:
> On Sat, Mar 10, 2012 at 07:28:41PM -0800, Luca Barbato wrote:
>> On 3/10/12 6:53 PM, Rich Freeman wrote:
>>> neither the genkernel nor dracut docs have specific instructions about
>>
>> I guess we could pour more effort in getting dracut more easy to use
>> and/or try to figure out which are the items that should be moved to /
>> and fix the remaining ones...
>
> I highly discourage moving more things to /.  If you google for things
> like, "case for usr merge", "understanding bin split", etc, you will
> find much information that is very enlightening about the /usr merge and
> the reasons for the /bin, /lib, /sbin ->  /usr/* split.

Indeed. I thought we got past this already and started moving things to 
/usr [1][2]

http://bugs.gentoo.org/398081
http://bugs.gentoo.org/403073

More to follow...


Replies:
Re: Re: newsitem: unmasking udev-181
-- Michał Górny
References:
newsitem: unmasking udev-181
-- William Hubbs
Re: newsitem: unmasking udev-181
-- Rich Freeman
Re: Re: newsitem: unmasking udev-181
-- Luca Barbato
Re: Re: newsitem: unmasking udev-181
-- William Hubbs
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: newsitem: unmasking udev-181
Next by thread:
Re: Re: newsitem: unmasking udev-181
Previous by date:
Re: Re: newsitem: unmasking udev-181
Next by date:
Re: Re: newsitem: unmasking udev-181


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.