From: Matthew Wilcox <matthew@wil.cx>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Alexander Viro <viro@math.psu.edu>,
Linux kernel development list <linux-kernel@vger.kernel.org>,
Linux FS development list <linux-fsdevel@vger.kernel.org>
Subject: Re: (struct dentry *)->vfsmnt;
Date: Wed, 14 Mar 2001 17:40:31 +0000 [thread overview]
Message-ID: <20010314174031.A12200@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0103140146590.2506-100000@weyl.math.psu.edu> <200103141726.f2EHQoj09856@webber.adilger.int>
In-Reply-To: <200103141726.f2EHQoj09856@webber.adilger.int>; from adilger@turbolinux.com on Wed, Mar 14, 2001 at 10:26:50AM -0700
On Wed, Mar 14, 2001 at 10:26:50AM -0700, Andreas Dilger wrote:
> > Let me put it that way: I don't understand why (if it is useful at all)
> > it is done in the fs. Looks like a wrong level...
>
> For the same reason that the UUID and LABEL are stored in the superblock:
> you want this infomation kept with the filesystem and not anywhere else,
> otherwise it will quickly get out-of-date. Wherever you mounted the
> filesystem last is where it would be mounted if you import the VG on
> another system. You can obviously edit /etc/fstab afterwards if it is
> wrong, and then remount the filesystem(s), and this will store the
> correct mountpoint into the filesystem for the next vgimport.
Al is saying `why not do this in mount(8) instead of mount(2)?' I haven't
seen you answer that yet.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-03-14 17:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 23:20 LA Walsh
2001-03-10 1:00 ` Alexander Viro
2001-03-10 1:56 ` LA Walsh
2001-03-10 2:42 ` Alexander Viro
2001-03-14 1:28 ` Andreas Dilger
2001-03-14 2:32 ` Alexander Viro
2001-03-14 4:27 ` Andreas Dilger
2001-03-14 5:11 ` Alexander Viro
2001-03-14 5:19 ` Andreas Dilger
2001-03-14 5:49 ` Alexander Viro
2001-03-14 6:05 ` Andreas Dilger
2001-03-14 6:50 ` Alexander Viro
2001-03-14 17:26 ` Andreas Dilger
2001-03-14 17:40 ` Matthew Wilcox [this message]
2001-03-14 18:06 ` Andreas Dilger
2001-03-14 18:11 ` Alexander Viro
2001-03-14 19:14 ` Andreas Dilger
2001-03-14 19:32 ` Alexander Viro
2001-03-14 20:21 ` Ragnar Kjørstad
2001-03-14 19:31 ` Dave Kleikamp
2001-03-14 19:45 ` Andreas Dilger
2001-03-14 19:51 ` Alexander Viro
2001-03-14 19:57 ` Dave Kleikamp
2001-03-14 21:07 ` Andreas Dilger
2001-03-15 12:21 bsuparna
2001-03-15 12:59 bsuparna
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=20010314174031.A12200@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=adilger@turbolinux.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 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®