From: aer-list@mailandnews.com
To: David Woodhouse <dwmw2@infradead.org>
Cc: "H. Peter Anvin" <hpa@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: / on ramfs, possible?
Date: Wed, 01 Nov 2000 10:16:16 +0100 [thread overview]
Message-ID: <200011010916.KAA19911@hell.wii.ericsson.net> (raw)
In-Reply-To: Message from David Woodhouse <dwmw2@infradead.org> of "Mon, 30 Oct 2000 23:32:23 GMT." <Pine.LNX.4.21.0010302329140.16675-100000@imladris.demon.co.uk>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
> On Mon, 30 Oct 2000, H. Peter Anvin wrote:
>
> > 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.)
>
> My question is: What do you want to do that for? You can nuke the initrd
> ramdisk, but you can't drop the rd.c code, or ll_rw_blk.c code, etc. So
> why not just keep your root filesystem in the initrd where it started off?
>
Because the stuff on the initrd is not at all what I want in the resultant filesystem. The machine(s) in question are some disk-based some disk-less. I have a system for remote installation/removal of packages (--> the "partition" _has_ to be able to grove/shrink).
The package builder should not have to worry about these details, so the directory hierarcy cannot contain any traces of _how_ the packges got there in the first place.
/Anders
[-- Attachment #2: Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2000-11-01 9:18 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 [this message]
2000-10-30 12:42 ` Alan Cox
2000-10-30 20:09 ` Stuart Lynne
-- strict thread matches above, loose matches on Subject: below --
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=200011010916.KAA19911@hell.wii.ericsson.net \
--to=aer-list@mailandnews.com \
--cc=dwmw2@infradead.org \
--cc=hpa@transmeta.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