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 ) id 1R4Uka-0003bJ-3U for garchives@archives.gentoo.org; Fri, 16 Sep 2011 09:30:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B080F21C234; Fri, 16 Sep 2011 09:30:10 +0000 (UTC) Received: from svr-us4.tirtonadi.com (unknown [69.65.43.212]) by pigeon.gentoo.org (Postfix) with ESMTP id 33B2921C032 for ; Fri, 16 Sep 2011 09:29:09 +0000 (UTC) Received: from mail-fx0-f53.google.com ([209.85.161.53]) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.69) (envelope-from ) id 1R4UjO-001rqn-64 for gentoo-user@lists.gentoo.org; Fri, 16 Sep 2011 16:29:10 +0700 Received: by fxh2 with SMTP id 2so1686861fxh.40 for ; Fri, 16 Sep 2011 02:29:04 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.223.8.81 with SMTP id g17mr191695fag.74.1316165344782; Fri, 16 Sep 2011 02:29:04 -0700 (PDT) Received: by 10.223.95.207 with HTTP; Fri, 16 Sep 2011 02:29:04 -0700 (PDT) Received: by 10.223.95.207 with HTTP; Fri, 16 Sep 2011 02:29:04 -0700 (PDT) In-Reply-To: <2584650.Gi816EnIAc@eve> References: <20110912150248.GB3599@acm.acm> <73132955.y04H0sY5km@eve> <2584650.Gi816EnIAc@eve> Date: Fri, 16 Sep 2011 16:29:04 +0700 Message-ID: Subject: Re: [gentoo-user] udev + /usr From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=0015174480e2d769ea04ad0b9fbc X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Archives-Salt: X-Archives-Hash: 40f3a10b06c9c82659366379891c3137 --0015174480e2d769ea04ad0b9fbc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sep 16, 2011 4:03 PM, "Joost Roeleveld" wrote: > > On Thursday, September 15, 2011 05:38:41 PM Canek Pel=C3=A1ez Vald=C3=A9s= wrote: > > [--major snippage--] > > I see it the other way around: you ensure that your initramfs is in > > sync with your system. In other words: the initramfs contains a subset > > of your normal installation. That is why it makes redundant /lib, > > /sbin and /bin. > > The reason I ditched lilo when grub came out was because I always would forget > to run the lilo-command. (Another was that lilo wouldn't work on a new > machine, but that's not important) > The same will be true for dracut. And probably not just for me. > > The on-disk-format may stay the same and the tools (am thinking LVM here) > should always be able to find my filesystems. But, what if the initramfs does > the fsck with older tools? > > Currently, the fsck runs before actually mounting the filesystems. If the > filesystems end up being pre-mounted, when will fsck run and which version? > Speaking of fsck, didn't someone lamented the fact that fsck can no longer be statically linked, thus making initr* 'blew up' in size? When more and more utilities go the non-statically-linked way... congratulations! You now have an initr* that's practically a cpio-ized version of / Rgds, --0015174480e2d769ea04ad0b9fbc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sep 16, 2011 4:03 PM, "Joost Roeleveld" <joost@antarean.org> wrote:
>
> On Thursday, September 15, 2011 05:38:41 PM Canek Pel=C3=A1ez Vald=C3= =A9s wrote:
> >
[--major snippage--]
> > I see it the other way around: you ensure that your initramfs is = in
> > sync with your system. In other words: the initramfs contains a s= ubset
> > of your normal installation. That is why it makes redundant /lib,=
> > /sbin and /bin.
>
> The reason I ditched lilo when grub came out was because I always woul= d forget
> to run the lilo-command. (Another was that lilo wouldn't work on a= new
> machine, but that's not important)
> The same will be true for dracut. And probably not just for me.
>
> The on-disk-format may stay the same and the tools (am thinking LVM he= re)
> should always be able to find my filesystems. But, what if the initram= fs does
> the fsck with older tools?
>
> Currently, the fsck runs before actually mounting the filesystems. If = the
> filesystems end up being pre-mounted, when will fsck run and which ver= sion?
>

Speaking of fsck, didn't someone lamented the fact that fsck can no = longer be statically linked, thus making initr* 'blew up' in size?<= /p>

When more and more utilities go the non-statically-linked way... congrat= ulations! You now have an initr* that's practically a cpio-ized version= of /

Rgds,

--0015174480e2d769ea04ad0b9fbc--