public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-project@lists.gentoo.org, council@gentoo.org
Subject: Re: [gentoo-project] Council meeting: Tuesday 8th May 2012, 19:00 UTC
Date: Fri, 4 May 2012 22:25:00 -0500	[thread overview]
Message-ID: <20120505032500.GA4720@linux1> (raw)
In-Reply-To: <20120505024134.GA4666@linux1>

[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]

Hi Mike,

On Fri, May 04, 2012 at 09:41:34PM -0500, William Hubbs wrote:
> On Fri, May 04, 2012 at 08:46:21PM -0400, Mike Frysinger wrote:
> > On Friday 04 May 2012 19:06:37 William Hubbs wrote:
> > > If you use an initramfs to pre-mount /usr, all of these issues are moot
> > > and things just work (tm). Mike's sep-usr use flag option on busybox
> > > may do this, but see below.
> > > 
> > > - Separate /usr without initramfs blocks the /usr merge.
> > >   In my original request to have your vote reviewed, I pointed out the
> > >   document which asserts that the /usr merge is a good thing and pointed
> > >   out the thread in which we discussed it on -dev. The arguments
> > >   supporting it are strong, and I haven't seen any technical argument
> > >   against it that would not be addressed by using an initramfs with
> > >   separate /usr. If you are using an initramfs, you will never know
> > >   when the /usr merge happens, but if you are using something like
> > >   Mike's option your system is not compatible with the merge.
> > 
> > why exactly do you say that ?  i already explained that busybox[sep-usr] works 
> > perfectly fine in a /usr-merged world.  the /ginit static ELF literally needs 
> > nothing else in the system to work.  you could boot a rootfs where the only 
> > thing in / was ginit and it wouldn't be a problem.
> 
> Ah ok, maybe this is the answer then. That's why I said above that I
> wasn't sure.
> 
> If you are installing the ginit binary directly in /, we may be good
> to go. :-)

This is pretty slick. I'm running with an initramfs, but I may test your
code here in  a few.

Also, I think I found something I'm going to send you a patch for. I'll
handle that in private email though.

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-05-05  6:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  2:02 [gentoo-project] Council meeting: Tuesday 8th May 2012, 19:00 UTC Jorge Manuel B. S. Vicetto
2012-05-04 23:06 ` William Hubbs
2012-05-05  0:46   ` Mike Frysinger
2012-05-05  2:41     ` William Hubbs
2012-05-05  3:25       ` William Hubbs [this message]
2012-05-05  5:32         ` William Hubbs
2012-05-05  8:32           ` Fabian Groffen
2012-05-05 15:56             ` William Hubbs
2012-05-07 17:48               ` Donnie Berkholz

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=20120505032500.GA4720@linux1 \
    --to=williamh@gentoo.org \
    --cc=council@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=vapier@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