From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Passing information from initramfs to real rootfs
Date: Thu, 20 Nov 2003 00:01:08 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106928668820025@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106880306401848@msgid-missing>
On Fri, Nov 14, 2003 at 07:44:09PM +0100, Olaf Hering wrote:
> On Fri, Nov 14, Olaf Hering wrote:
>
> > On Fri, Nov 14, Hannes Reinecke wrote:
> >
> > > Hi all,
> > >
> > > is it possible to get information out of initramfs to be passed to the
> > > real root fs?
> >
> > mkdir /foo
> > mkfs.minix /dev/ram42
> > mount -nt minix /dev/ram42 /foo
> > echo my content > /foo/backup.txt
> > umount /foo
> >
> > ...
> >
> > mount -n /dev/ram42 /oldinitramfscontent
> >
> >
> > might work.
>
> Doesnt work, the ramdisk content disappears during umount. Does anyone
> know what it disappears in the initramfs context, but not in the running
> system?
Why umount it then?
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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
next prev parent reply other threads:[~2003-11-20 0:01 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
2003-11-14 18:44 ` Olaf Hering
2003-11-20 0:01 ` Greg KH [this message]
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-106928668820025@msgid-missing \
--to=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.