From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: separate /usr preparation vote
Date: Mon, 19 Aug 2013 06:19:24 +0000 [thread overview]
Message-ID: <20130819061924.GA15036@gentoo.org> (raw)
In-Reply-To: <20130819024809.GA9962@linux1>
On Sun, Aug 18, 2013 at 09:48:09PM -0500, William Hubbs wrote:
> > I just don't see any reason for waiting, at least not right now. If
> > the argument is that we should give users some period of time to
> > prepare, then we should be sending out some kind of specific news item
> > telling them what preparations to make and THEN waiting.
>
> The vote is to make sure all of the necessary documentation is in place,
> so this isn't really part of it. But, yes, once this vote passes,
> communication to users as the changes happen will be important.
Documentation can always be improved, but I do feel it is up to the task
already. We document how to create an initramfs using genkernel (which is
dead easy) and mention several times that a separate /usr (or root on LVM)
requires an initramfs.
All our examples use the initramfs as well.
> > Finally, I could see the /usr merge as a POSSIBLE reason to move
> > things sooner. If somebody wants to propose some plan to make that
> > happen they should do so, and we can debate it on this list and so on.
> > However, I don't see any value in moving a bunch of stuff around
> > purely for the sake of a /usr merge when there isn't any plan to
> > finish the work. If anybody is thinking about that being the driver
> > they need to have a plan that actually gets us to the end goal, and of
> > course we need to agree that this is even a goal we want to have.
>
> The /usr merge is a totally separate issue that I really don't want to
> bring into this discussion. There are people who are fine with us
> cleaning up the separate /usr issue, but opposed to the /usr merge, so
> that needs to be a separate item imo.
Yes please; merging / <-> /usr has impact beyond just documentation and
initramfs. For SELinux for instance, that means our policies will need to be
adjusted so all /bin/* contexts also get assigned to /usr/bin (and /sbin to
/usr/sbin) and symlinks are "accepted" where they are currently not.
I think for such a merger, we'll need to know what will be the goal, and set
steps in that direction that make it so a transition is not full-park,
big-bang, but rather gradually with little to no end user involvement
(step-wise).
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2013-08-19 6:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 22:20 [gentoo-project] rfc: separate /usr preparation vote William Hubbs
2013-08-18 6:32 ` Ulrich Mueller
2013-08-18 11:37 ` Rich Freeman
2013-08-19 2:48 ` William Hubbs
2013-08-19 3:10 ` Rich Freeman
2013-08-19 3:48 ` Rick "Zero_Chaos" Farina
2013-08-19 11:31 ` Rich Freeman
2013-08-19 6:19 ` Sven Vermeulen [this message]
2013-08-19 6:30 ` Ulrich Mueller
2013-08-19 13:35 ` Ian Stakenvicius
2013-08-18 13:08 ` Anthony G. Basile
2013-08-18 13:46 ` Rich Freeman
2013-08-19 0:18 ` Denis Dupeyron
2013-08-19 0:29 ` Rick "Zero_Chaos" Farina
2013-08-19 1:40 ` Anthony G. Basile
2013-08-19 1:57 ` Rich Freeman
2013-08-27 19:11 ` Roy Bamford
2013-08-27 19:30 ` Ian Stakenvicius
2013-08-28 0:46 ` Rich Freeman
2013-08-27 19:30 ` Rick "Zero_Chaos" Farina
2013-08-28 1:25 ` William Hubbs
2013-08-28 15:04 ` Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130819061924.GA15036@gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox