From: Hans Reiser <reiser@namesys.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Rob Landley <landley@trommello.org>,
Nick LeRoy <nleroy@cs.wisc.edu>,
"Martin J. Bligh" <mbligh@aracnet.com>,
linux-kernel@vger.kernel.org
Subject: Re: The reason to call it 3.0 is the desktop (was Re: [OT] 2.6 not 3.0 - (NUMA)) (fwd)
Date: Mon, 14 Oct 2002 06:42:01 +0400 [thread overview]
Message-ID: <3DAA2EF9.2090408@namesys.com> (raw)
In-Reply-To: Pine.GSO.4.21.0210132107020.9247-100000@steklov.math.psu.edu
Alexander Viro wrote:
>
>
>>Logically, the second /var mount should be "mount --move /initrd/var /var",
>>followed by "umount /initrd" to free up the initrd memory. Right now it's
>>doing "mount -n --bind /initrd/var /var", because /etc is a symlink into /var
>>(has to remain editable, you see), and this way the information about which
>>partition var actually is can be kept in one place. (This is an
>>implementation detail: I could have used volume labels instead.)
>>
>>The point is, right now I can't free the initial ramdisk because it has an
>>active mount point under it..
>>
>>
>
>umount -l
>mount --move
>
>
>
>
>
>
It seems Linux evolves faster than I can track. These are nice features.:)
Hans
next prev parent reply other threads:[~2002-10-14 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.21.0210132106460.9247-100000@steklov.math.psu.edu>
2002-10-14 1:09 ` The reason to call it 3.0 is the desktop (was Re: [OT] 2.6 not 3.0 - (NUMA)) (fwd) Alexander Viro
2002-10-14 2:42 ` Hans Reiser [this message]
2002-10-14 2:48 ` Alexander Viro
2002-10-14 16:41 ` Rob Landley
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=3DAA2EF9.2090408@namesys.com \
--to=reiser@namesys.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=nleroy@cs.wisc.edu \
--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 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).