From: "Harald Dunkel" <harald.dunkel@t-online.de>
To: Mathieu Segaud <matt@minas-morgul.org>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: udev: what's up with old /dev ?
Date: Wed, 13 Oct 2004 16:13:34 +0200 [thread overview]
Message-ID: <416D380E.4080202@t-online.de> (raw)
In-Reply-To: <87vfde3gvs.fsf@barad-dur.crans.org>
Mathieu Segaud wrote:
>
> huh, well initrd is / that is mounted over the so-called _rootfs_
> initramfs is here to _be_ that rootfs. So no pivot_root needed and the run-it
> program included in klibc tarballs takes care of wiping-out everything that
> could waste memory into the initramfs before mounting the real /.
> If it was to compiled out of the kernel, it would just be an initrd....
>
> rootfs is _needed_ for mounting the real root, so is initramfs.
>
So the kernel boots, activates the initramfs somehow to
become the first /, and then starts /sbin/init (e.g. kinit
from the klibc package).
And then?
The sources of kinit show that its job is parse the kernel
command line arguments, configure the NIC, mount the root
filesystem via NFS, etc. Other configurations might require
a different init to start hotplug and udev, or to handle the
LVM and crypto magic, for example. My point is that if there
is no one-for-all init process to handle _every_ possible
startup procedure, then it might be necessary to rebuild the
initramfs. This would be easier (and easier to test) if
initramfs is not compiled into the kernel, but a separate
image to be loaded at boot time "somehow".
Or did I miss something?
Regards
Harri
next prev parent reply other threads:[~2004-10-13 14:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:08 udev: what's up with old /dev ? J.A. Magallon
2004-10-10 22:51 ` Zack Weinberg
2004-10-10 23:15 ` Hacksaw
2004-10-10 23:25 ` J.A. Magallon
2004-10-11 0:06 ` Hacksaw
2004-10-11 19:13 ` Denis Vlasenko
2004-10-11 9:14 ` Felipe Alfaro Solana
2004-10-11 10:29 ` Arkadiusz Miskiewicz
2004-10-11 12:02 ` Felipe Alfaro Solana
2004-10-11 11:11 ` Hacksaw
2004-10-11 12:04 ` Felipe Alfaro Solana
2004-10-11 20:06 ` Hacksaw
2004-10-11 20:51 ` Bartlomiej Zolnierkiewicz
2004-10-11 21:28 ` Hacksaw
2004-10-12 0:19 ` Greg KH
2004-10-12 8:11 ` Harald Dunkel
2004-10-12 16:58 ` Greg KH
[not found] ` <416C26B4.6040408@t-online.de>
[not found] ` <20041012185733.GA31222@kroah.com>
[not found] ` <416C3BB6.4040200@t-online.de>
[not found] ` <20041012203022.GB32139@kroah.com>
2004-10-12 21:35 ` Harald Dunkel
2004-10-13 13:08 ` Mathieu Segaud
2004-10-13 14:13 ` Harald Dunkel [this message]
2004-10-13 14:33 ` Mathieu Segaud
-- strict thread matches above, loose matches on Subject: below --
2004-10-10 22:41 Michael Thonke
2004-10-11 7:19 Zack Weinberg
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=416D380E.4080202@t-online.de \
--to=harald.dunkel@t-online.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@minas-morgul.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