From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 13-11-2012
Date: Tue, 30 Oct 2012 11:38:20 -0500 [thread overview]
Message-ID: <20121030163820.GA7141@linux1> (raw)
In-Reply-To: <508FFE6C.4070200@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2741 bytes --]
On Tue, Oct 30, 2012 at 12:21:00PM -0400, Ian Stakenvicius wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 30/10/12 11:36 AM, William Hubbs wrote:
> > Fellow Council Members:
> >
> > We now have two methods of handling separate /usr configurations
> > on Linux in the tree.
> >
> > The first, and by far, the most flexable method is to use an
> > initramfs. This method is now documented in the initramfs guide [1]
> > and the handbooks. It would need to be used if a user needs
> > specialized drivers running or modules loaded before the / or /usr
> > file systems can be accessed. A non-inclusive list of these
> > situations would be RAID, LVM2, ZFS, and software for encrypted
> > file systems.
> >
> > The second method can be used if the flexability of the first
> > method is not needed. It involves re-emerging
> > >=sys-apps/busybox-1.20.0 with the sep-usr use flag active and
> > following the instructions in the elog messages. This is the way to
> > support separate /usr without an initramfs if someone wants this.
> >
> > The goal of separate /usr support is to insure that /usr is always
> > available when / is, and both of these methods meet this goal. If
> > users switch to one of these methods, there is no further work
> > required by us to support separate /usr configurations.
> >
> > I have gone over this with Diego in QA, and he agrees that these
> > are the methods we should use. That is why he is on the cc:
> > specifically for this email.
> >
> > I believe the only remaining step is for the council to approve
> > this plan, so I would like it to be added to the agenda.
> >
> > If this is approved, my plan will be to release a news item then
> > give a time window for users to read the news item and make their
> > decision [2]. Once the time window expires, we could assume that
> > users with separate /usr have switched to using one of these two
> > methods of supporting it.
> >
>
> The end result of this assumption is that the use of
> gen_usr_ldscript() and the move of libs from /usr/lib to /lib will
> become deprecated, correct? I think it's pertinent to note this (or
> whatever other changes will then be requested/required for Council to
> decide on) within this discussion, if not also within the "plan"..
On Linux, yes, you are correct. I wouldn't propose touching it for the
*bsd platforms.
Also, once everyone switches over, this deprecation would be
transparent. The calls to gen_usr_ldscript would be removed from
ebuilds where possible, and the function itself could be disabled on
linux. Once this is done, when packages are rebuilt, the libraries would
migrate back to /usr/lib.
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-10-30 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 15:00 [gentoo-project] Call for agenda items -- Council meeting 13-11-2012 Fabian Groffen
2012-10-30 15:36 ` William Hubbs
2012-10-30 16:21 ` Ian Stakenvicius
2012-10-30 16:38 ` William Hubbs [this message]
2012-11-02 17:22 ` William Hubbs
2012-11-08 17:07 ` Alexis Ballier
2012-11-08 17:38 ` William Hubbs
2012-10-30 22:06 ` Chí-Thanh Christopher Nguyễn
2012-10-30 22:09 ` Ciaran McCreesh
2012-10-30 22:11 ` Chí-Thanh Christopher Nguyễn
2012-10-30 22:34 ` Zac Medico
2012-10-31 6:41 ` Pacho Ramos
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=20121030163820.GA7141@linux1 \
--to=williamh@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