From: "H. Peter Anvin" <hpa@zytor.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: making the mountpoints visible all the time (fwd)
Date: Wed, 19 Nov 2003 08:45:22 -0800 [thread overview]
Message-ID: <3FBB9E22.8090309@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0311191612420.24336-100000@wombat.indigo.net.au>
Ian Kent wrote:
>
> That sounds good a good idea for inclusion in 4.1.1 (I have quite a list
> already).
>
> Move the decision on what the map contains to the program map implementer.
> That would be fairly straight forward to implement given that I have a
> placeholder function in each map module.
>
Well, it's pretty much the only thing that makes sense, since a program
map can inherently do "anything".
Pretty much ghosting implies that there are now two operations required
of a map: key->data lookup (old), and enumerate all keys (new).
And of course autofs needs to deal with the consequences of the map
changing underneath it.
-hpa
next prev parent reply other threads:[~2003-11-19 16:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 8:13 making the mountpoints visible all the time (fwd) Ian Kent
2003-11-19 16:45 ` H. Peter Anvin [this message]
2003-11-21 0:51 ` Ian Kent
2003-11-21 1:43 ` H. Peter Anvin
2003-11-21 6:59 ` Ian Kent
2003-11-21 8:49 ` Ruslan U. Zakirov
2003-11-22 7:14 ` Ian Kent
2003-11-21 19:52 ` H. Peter Anvin
2003-11-21 19:56 ` H. Peter Anvin
2003-11-22 7:19 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 5:05 Chris Croswhite
2003-11-17 5:32 ` Ian Kent
2003-12-02 13:49 ` Ian Kent
2003-11-16 16:05 Ian Kent
2003-11-16 19:58 ` Alexander Macdonald
2003-11-17 2:53 ` 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=3FBB9E22.8090309@zytor.com \
--to=hpa@zytor.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/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.