From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-47630-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1R4Iyj-0001FJ-Nr
	for garchives@archives.gentoo.org; Thu, 15 Sep 2011 20:56:14 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 4E8F321C329;
	Thu, 15 Sep 2011 20:55:45 +0000 (UTC)
Received: from mail-bw0-f53.google.com (mail-bw0-f53.google.com [209.85.214.53])
	by pigeon.gentoo.org (Postfix) with ESMTP id 94D6021C2C2
	for <gentoo-dev@lists.gentoo.org>; Thu, 15 Sep 2011 20:54:39 +0000 (UTC)
Received: by bkbzt12 with SMTP id zt12so3902820bkb.40
        for <gentoo-dev@lists.gentoo.org>; Thu, 15 Sep 2011 13:54:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        bh=DFa4idTcnkTcsq4txQaAwUWbkgxNq15qtXjejiJihZA=;
        b=U35zYaJN4Ym0Ffd9FKRQNZtlOn0nNrzZFVENXQY2RudlDqB9WzT3LNPN7aMUgmVE2S
         hd4T5aSreOtZRZPiigGPi6CZZXdgbgPq2f8CBr7zYFiLEVDzrI4DrlqIfsA0P8lgHdZw
         nLQfW/HhfdAhMsUBfixEXRAMqxmh4v0zzj4ec=
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.204.135.145 with SMTP id n17mr1087669bkt.39.1316120078711;
 Thu, 15 Sep 2011 13:54:38 -0700 (PDT)
Sender: freemanrich@gmail.com
Received: by 10.204.143.67 with HTTP; Thu, 15 Sep 2011 13:54:38 -0700 (PDT)
In-Reply-To: <8673732.aDYRJ5yb2i@eve>
References: <1740055.XA9oyAS8HQ@eve>
	<4E7214B7.9010406@gentoo.org>
	<CAGfcS_=kA7WDG21knY1z6h9zdZU670niBivsOXiDS2jwVC6xLg@mail.gmail.com>
	<8673732.aDYRJ5yb2i@eve>
Date: Thu, 15 Sep 2011 16:54:38 -0400
X-Google-Sender-Auth: okw5D4nzcAel01JVh-X0FU2M26Y
Message-ID: <CAGfcS_mV9QS5xLEPOR5G_vEmWNw4iFbMxf=+dBmyWaGVWX+MMQ@mail.gmail.com>
Subject: Re: [gentoo-dev] udev and /usr
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Content-Type: multipart/alternative; boundary=0015174c402cc5fd7104ad011551
X-Archives-Salt: 
X-Archives-Hash: 53eeafebb39956f6ddbbe7910b5deccd

--0015174c402cc5fd7104ad011551
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Sep 15, 2011 at 4:40 PM, Joost Roeleveld <joost@antarean.org> wrote:

>
> It is my understanding all the options need to be specified every time
> dracut
> is run to create an initramfs. If this becomes mandatory, will this be
> added
> to the "make" script of the kernel-sources and as such, make this more
> specific?
>

There are no plans to make dracut mandatory, unless you're putting root on
lvm or luks or something, and a good initramfs is already needed for that.

I think /etc/dracut.conf already has just about anything you'd want to be
persistent across runs.


>
> Another issue arrises where some of the tools are updated that are also in
> the
> initramfs. Will we then still need to remember to also update the initramfs
> if
> these are needed?
>
>
Potentially - if the tools in the initramfs won't work.  That seems unlikely
though - on-disk formats don't really change much and all stuff like mdadm
and lvm tools do is find stuff and pass it along to the kernel which does
the real work.  If you migrate your root from raid1 to raid17 and the old
initramfs doesn't understand raid17 then you'll have a problem.  I imagine
that if you migrate to raid17, however, you'd have put some thought into
this.



> My server currently uses mdadm raid1 for /, /boot and swap and raid1+lvm
> for
> the rest. This works without the need of an initramfs.
>
> Will this still work? Or will I need to be using dracut instead?
>
>
I suspect that if /usr is on raid1+lvm that you might need dracut.  I'm not
100% sure on that, since in theory the initramfs can find all it needs on
root in this case.  However, the goal was to keep it simple. I'd defer to
somebody actually involved with the simple image.

Rich

--0015174c402cc5fd7104ad011551
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 15, 2011 at 4:40 PM, Joost Roeleveld <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:joost@antarean.org">joost@antarean.org</a>&gt;</span> wrote:<=
br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br></div>It is my understanding all the options need to =
be specified every time dracut<br>
is run to create an initramfs. If this becomes mandatory, will this be adde=
d<br>
to the &quot;make&quot; script of the kernel-sources and as such, make this=
 more<br>
specific?<br></blockquote><div><br></div><div>There are no plans to make dr=
acut mandatory, unless you&#39;re putting root on lvm or luks or something,=
 and a good initramfs is already needed for that.</div><div><br></div>
<div>I think /etc/dracut.conf already has just about anything you&#39;d wan=
t to be persistent across runs.</div><div>=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex;">

<br>
Another issue arrises where some of the tools are updated that are also in =
the<br>
initramfs. Will we then still need to remember to also update the initramfs=
 if<br>
these are needed?<br>
<br></blockquote><div><br></div><div>Potentially - if the tools in the init=
ramfs won&#39;t work. =A0That seems unlikely though - on-disk formats don&#=
39;t really change much and all stuff like mdadm and lvm tools do is find s=
tuff and pass it along to the kernel which does the real work. =A0If you mi=
grate your root from raid1 to raid17 and the old initramfs doesn&#39;t unde=
rstand raid17 then you&#39;ll have a problem. =A0I imagine that if you migr=
ate to raid17, however, you&#39;d have put some thought into this.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
My server currently uses mdadm raid1 for /, /boot and swap and raid1+lvm fo=
r<br>
the rest. This works without the need of an initramfs.<br>
<br>
Will this still work? Or will I need to be using dracut instead?<br><br></b=
lockquote><div><br></div><div>I suspect that if /usr is on raid1+lvm that y=
ou might need dracut. =A0I&#39;m not 100% sure on that, since in theory the=
 initramfs can find all it needs on root in this case. =A0However, the goal=
 was to keep it simple. I&#39;d defer to somebody actually involved with th=
e simple image.</div>
</div><br><div>Rich</div>

--0015174c402cc5fd7104ad011551--