From: Christoph Hellwig <hch@infradead.org>
To: nscott@aconex.com
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, RFC] - remove mounpoint UUID code
Date: Wed, 12 Mar 2008 03:22:59 -0400 [thread overview]
Message-ID: <20080312072259.GA26148@infradead.org> (raw)
In-Reply-To: <34665.192.168.3.1.1205266196.squirrel@mail.aconex.com>
On Wed, Mar 12, 2008 at 07:09:56AM +1100, nscott@aconex.com wrote:
> I don't have any immediate plans. I can imagine it could be used to
> stitch parts of the namespace together in a filesystem that supports
> multiple devices (in a chunkfs kinda way) ... or maybe more simply
> just an in-filesystem auto-mounter. *shrug*. But its there, the tools
> support it (once again, I didn't see a userspace patch - hohum), so I
> would vote for leaving it in its current form so some enterprising,
> constructive young coder can try to make something useful from it
> at some point. :)
That kind of automounter really doesn't belong into the low-level
filesystem. If we really wanted it it would go into the VFS, storing
the uuid or other identifier for the mountpoint in an xattr. This is
really just dead junk that should go away.
next prev parent reply other threads:[~2008-03-12 7:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 4:00 [PATCH, RFC] - remove mounpoint UUID code Eric Sandeen
2008-03-08 4:31 ` Ian Costello
2008-03-08 4:33 ` Eric Sandeen
2008-03-08 4:40 ` Ian Costello
2008-03-08 4:59 ` Eric Sandeen
2008-03-08 11:54 ` Christoph Hellwig
2008-03-11 0:44 ` Nathan Scott
2008-03-11 1:19 ` Eric Sandeen
2008-03-11 20:09 ` nscott
2008-03-12 7:22 ` Christoph Hellwig [this message]
2008-07-08 3:09 ` [PATCH, RFC] - remove mountpoint " Eric Sandeen
2008-07-25 2:22 ` [PATCH, RFC] - remove mounpoint " Niv Sardi
2008-07-25 3:11 ` Eric Sandeen
2008-07-25 5:12 ` Niv Sardi
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=20080312072259.GA26148@infradead.org \
--to=hch@infradead.org \
--cc=nscott@aconex.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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