From: Rob Landley <landley@trommello.org>
To: Alexander Viro <viro@math.psu.edu>
Cc: Nick LeRoy <nleroy@cs.wisc.edu>, Hans Reiser <reiser@namesys.com>,
"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 12:41:28 -0400 [thread overview]
Message-ID: <200210142151.g9ELpiLG101376@pimout1-ext.prodigy.net> (raw)
In-Reply-To: <Pine.GSO.4.21.0210132107020.9247-100000@steklov.math.psu.edu>
On Sunday 13 October 2002 09:09 pm, 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
Cool. Thanks.
Rob
(Serves me right for still having Red Hat 7.2 on my laptop. Old man pages.
Now I've got to find a new project to force myelf to learn VFS internals. Oh
well... :)
(Nit-pick: the man page description of umount -l doesn't look like it'd help
with the removable media problem, I.E. "umount --gimme_my_cd_back_NOW", but
the code may disagree, and the discussion's already turned up a 2.4 patch
from Tirgran via Hugh Dickens, so I'll shut up now. :)
prev parent reply other threads:[~2002-10-14 21:46 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 ` Alexander Viro
2002-10-14 2:42 ` Hans Reiser
2002-10-14 2:48 ` Alexander Viro
2002-10-14 16:41 ` Rob Landley [this message]
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=200210142151.g9ELpiLG101376@pimout1-ext.prodigy.net \
--to=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=nleroy@cs.wisc.edu \
--cc=reiser@namesys.com \
--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
all inboxes | Powered by JetHome®