From: "H. Peter Anvin" <hpa@transmeta.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rootfs (part 1)
Date: Wed, 16 May 2001 16:24:01 -0700 [thread overview]
Message-ID: <3B030C11.3270CFA7@transmeta.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0105161850200.26191-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>
> In full variant of patch I don't _have_ mount_root(9). It's done by
> mount(2). Period. Initrd or not. Notice that rootfs stays absolute root
> forever - it's much more convenient for fs/super.c, since you can get rid
> of many kludges that way. So I'm not too happy about populating rootfs with
> tons of files. BTW, loading initrd is done by open(2), read(2) and write(2) -
> none of this fake struct file business anymore.
>
OK, I see what you're doing now. However, I'm confused what you mean
with "rootfs stays absolute root forever" -- does that mean that you
mount the new root on top of /, and so the rootfs remains in the system
never to be reclaimed, as opposed to pivot_root-ing it?
-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
next prev parent reply other threads:[~2001-05-16 23:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 12:12 [PATCH] rootfs (part 1) Alexander Viro
2001-05-16 14:43 ` Christoph Rohland
2001-05-16 18:23 ` Alexander Viro
2001-05-16 19:47 ` Christoph Rohland
2001-05-16 23:37 ` Alan Cox
2001-05-16 17:11 ` Linus Torvalds
2001-05-16 17:45 ` Christoph Rohland
2001-05-16 17:55 ` Jeff Garzik
2001-05-16 18:00 ` Linus Torvalds
2001-05-16 18:23 ` David L. Parsley
2001-05-16 18:46 ` Christoph Rohland
2001-05-16 18:33 ` Alexander Viro
2001-05-16 23:49 ` Alan Cox
2001-05-17 6:46 ` Christoph Rohland
2001-05-16 18:48 ` Alexander Viro
2001-05-16 22:21 ` H. Peter Anvin
2001-05-16 23:06 ` Alexander Viro
2001-05-16 23:24 ` H. Peter Anvin [this message]
2001-05-16 23:31 ` Alexander Viro
2001-05-16 23:33 ` Alan Cox
2001-05-17 0:10 ` Alexander Viro
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=3B030C11.3270CFA7@transmeta.com \
--to=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.