linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Dodge <dododge@dododge.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Passing information from initramfs to real rootfs
Date: Fri, 14 Nov 2003 17:42:50 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106883182701954@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106880306401848@msgid-missing>

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

  parent reply	other threads:[~2003-11-14 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14  9:43 Passing information from initramfs to real rootfs Hannes Reinecke
2003-11-14  9:47 ` Olaf Hering
2003-11-14 17:42 ` Dave Dodge [this message]
2003-11-14 18:44 ` Olaf Hering
2003-11-20  0:01 ` Greg KH
2003-11-20  6:41 ` Olaf Hering

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=marc-linux-hotplug-106883182701954@msgid-missing \
    --to=dododge@dododge.net \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).