Re: Passing information from initramfs to real rootfs

[Dave Dodge <dododge@dododge.net>]

On Fri, 14 Nov 2003, Hannes Reinecke wrote:
> I'm thinking especially on udev and friends; udev could handle
> hotplug-events during boot-up from initramfs, but the devices generated
> cannot be passed to the real root-device, so essentially we have to
> re-scan sysfs to find and generate all events which might have been
> generated during boot and pass them to udev _again_.
[...]
> Easiest solution would be to have it moved initrd-style to /initramfs or
> somesuch, then we could easily access it und umount it (i.e. free the
> memory) as soon as we're done with the processing.

That's what I was planning to do for my test system. With the current
kernel I basically have to eliminate mount_root anyway in order to
use initramfs at all, so I was going to do the "real" root mount in
userspace and pivot_root to it explicitly.

As far as the initramfs /dev, my plan is to try symlinking or bind
mounting it into the new root, and continue to use the same /dev as
initramfs. If you want to umount and free the initramfs memory then I
guess you'd have to copy the dev contents somehow (unless or until
someone has a way to create a dedicated ramfs for /dev during
initramfs and then remount that at /dev after a pivot_root).

                                                  -Dave Dodge



-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel