From: "H. Peter Anvin" <hpa@transmeta.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: / on ramfs, possible?
Date: Mon, 30 Oct 2000 15:26:42 -0800 [thread overview]
Message-ID: <39FE03B2.E3E12A23@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0010302323490.16101-100000@imladris.demon.co.uk>
David Woodhouse wrote:
>
> On 29 Oct 2000, H. Peter Anvin wrote:
>
> > > I want my / to be a ramfs filesystem. I intend to populate it from an
> > > initrd image, and then remount / as the ramfs filesystem. Is that at
> > > all possible? The way I see it the kernel requires / on a device
> > > (major,minor) or nfs.
> > >
> > > Am I out of luck using ramfs as /? If it's easy to fix, how do I fix it?
> > >
> >
> > Use pivot_root instead of the initrd stuff in /proc/sys.
>
> Urgh. Then you're still using an initrd, and you still have to include all
> the crap necessary to support those horrid block-device thingies.
>
> Why not just use a ramdisk?
>
Pardon?! This doesn't make any sense...
The question was: how do switch from the initrd to using the ramfs as /?
Using pivot_root should do it (after the pivot, you can of course nuke
the initrd ramdisk.)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-30 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 7:27 / on ramfs, possible? Anders Eriksson
2000-10-30 7:34 ` H. Peter Anvin
2000-10-30 23:24 ` David Woodhouse
2000-10-30 23:26 ` H. Peter Anvin [this message]
2000-10-30 23:32 ` David Woodhouse
2000-10-30 23:37 ` H. Peter Anvin
2000-10-30 23:39 ` Jeff Garzik
2000-11-01 9:16 ` aer-list
2000-10-30 12:42 ` Alan Cox
2000-10-30 20:09 ` Stuart Lynne
2000-10-30 8:39 Adam J. Richter
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=39FE03B2.E3E12A23@transmeta.com \
--to=hpa@transmeta.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@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).