linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: aer-list@mailandnews.com (Anders Eriksson)
Cc: linux-kernel@vger.kernel.org
Subject: Re: / on ramfs, possible?
Date: Mon, 30 Oct 2000 12:42:56 +0000 (GMT)	[thread overview]
Message-ID: <E13qEHB-0006po-00@the-village.bc.nu> (raw)
In-Reply-To: <200010300727.IAA12250@hell.wii.ericsson.net> from "Anders Eriksson" at Oct 30, 2000 08:27:31 AM

> 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?

Firstly make sure you get the patches that make ramfs work if they arent all
yet applied, then build your initrd that populates it on boot. Now you can
make use of the pivot_root() syscall (you may need to generate your own 
syscall wrapper for that one as its very new). That lets you flip your root
and initrd around

-
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/

  parent reply	other threads:[~2000-10-30 12:42 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
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 [this message]
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=E13qEHB-0006po-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=aer-list@mailandnews.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).