From: "H. Peter Anvin" <hpa@zytor.com>
To: Mike Waychison <Michael.Waychison@Sun.COM>
Cc: autofs mailing list <autofs@linux.kernel.org>,
viro@parcelfarce.linux.theplanet.co.uk, "Ogden,
Aaron A." <aogden@unocal.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ian Kent <raven@themaw.net>
Subject: Re: [RFC] Towards a Modern Autofs
Date: Fri, 09 Jan 2004 13:36:04 -0800 [thread overview]
Message-ID: <3FFF1EC4.7080406@zytor.com> (raw)
In-Reply-To: <3FFF1DA7.8060005@sun.com>
Mike Waychison wrote:
>
> Unless I'm missing something, implementing this as a seperate filesystem
> type still has the appropriate atomicity guarantees as long as the VFS
> support complex expiry, whereby userspace would tag submounts as being
> part of the overall expiry for a base mountpoint.
>
It would, but it seems like a vastly more invasive change to the VFS
than ought to be necessary.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Mike Waychison <Michael.Waychison@Sun.COM>
Cc: viro@parcelfarce.linux.theplanet.co.uk,
Ian Kent <raven@themaw.net>,
autofs mailing list <autofs@linux.kernel.org>,
"Ogden, Aaron A." <aogden@unocal.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [autofs] [RFC] Towards a Modern Autofs
Date: Fri, 09 Jan 2004 13:36:04 -0800 [thread overview]
Message-ID: <3FFF1EC4.7080406@zytor.com> (raw)
In-Reply-To: <3FFF1DA7.8060005@sun.com>
Mike Waychison wrote:
>
> Unless I'm missing something, implementing this as a seperate filesystem
> type still has the appropriate atomicity guarantees as long as the VFS
> support complex expiry, whereby userspace would tag submounts as being
> part of the overall expiry for a base mountpoint.
>
It would, but it seems like a vastly more invasive change to the VFS
than ought to be necessary.
-hpa
next prev parent reply other threads:[~2004-01-09 21:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 22:28 [RFC] Towards a Modern Autofs Ogden, Aaron A.
2004-01-06 22:28 ` [autofs] " Ogden, Aaron A.
2004-01-06 22:41 ` Mike Fedyk
2004-01-06 22:47 ` Tim Hockin
2004-01-06 22:53 ` Paul Raines
2004-01-06 22:53 ` [autofs] " Paul Raines
2004-01-07 14:05 ` Greg Wooledge
2004-01-07 23:14 ` Jim Carter
2004-01-07 23:14 ` [autofs] " Jim Carter
2004-01-07 23:32 ` H. Peter Anvin
2004-01-07 23:32 ` [autofs] " H. Peter Anvin
2004-01-08 12:52 ` Ian Kent
2004-01-08 12:52 ` Ian Kent
2004-01-08 18:31 ` viro
2004-01-09 18:43 ` Ian Kent
2004-01-09 18:43 ` [autofs] " Ian Kent
2004-01-09 19:41 ` Mike Waychison
2004-01-09 19:41 ` [autofs] " Mike Waychison
2004-01-09 19:57 ` H. Peter Anvin
2004-01-09 19:57 ` [autofs] " H. Peter Anvin
2004-01-09 21:31 ` Mike Waychison
2004-01-09 21:31 ` [autofs] " Mike Waychison
2004-01-09 21:36 ` H. Peter Anvin [this message]
2004-01-09 21:36 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 22:50 Tim Hockin
2004-01-13 1:30 ` Ian Kent
2004-01-12 16:58 [autofs] " Mike Waychison
2004-01-13 1:54 ` Ian Kent
2004-01-13 19:01 ` Mike Waychison
2004-01-10 5:43 [autofs] " Ian Kent
2004-01-12 13:07 ` Mike Waychison
2004-01-12 16:01 ` raven
2004-01-13 18:46 ` Mike Waychison
2004-01-08 15:39 [autofs] " Mike Waychison
2004-01-09 18:20 ` Ian Kent
2004-01-09 20:06 ` Mike Waychison
2004-01-09 20:51 ` Jim Carter
2004-01-06 23:34 Ogden, Aaron A.
2004-01-06 23:26 Ogden, Aaron A.
2004-01-06 19:55 Mike Waychison
2004-01-06 19:55 ` Mike Waychison
2004-01-06 21:01 ` H. Peter Anvin
2004-01-06 21:44 ` Mike Waychison
2004-01-06 21:50 ` Tim Hockin
2004-01-06 22:06 ` H. Peter Anvin
[not found] ` <20040106221502.GA7398@hockin.org>
2004-01-06 22:20 ` H. Peter Anvin
2004-01-07 16:19 ` Mike Waychison
2004-01-07 21:14 ` Jim Carter
2004-01-07 22:55 ` Mike Waychison
2004-01-08 12:00 ` Ian Kent
2004-01-08 17:34 ` [autofs] " H. Peter Anvin
2004-01-08 23:42 ` Michael Clark
2004-01-09 20:28 ` Mike Waychison
2004-01-09 20:54 ` H. Peter Anvin
2004-01-09 21:43 ` Mike Waychison
2004-01-09 18:32 ` Ian Kent
2004-01-09 20:52 ` Mike Waychison
2004-01-08 0:48 ` Ian Kent
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=3FFF1EC4.7080406@zytor.com \
--to=hpa@zytor.com \
--cc=Michael.Waychison@Sun.COM \
--cc=aogden@unocal.com \
--cc=autofs@linux.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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.