From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] autofs
Date: Tue, 16 Jul 2002 13:23:58 +0100 [thread overview]
Message-ID: <152377f48470da984ce494ebe56ed076@vitanuova.com> (raw)
it's better, i think, if the directories are refcounted and disappear
when not referenced, otherwise the directory tends to fill up with
garbage.
(e.g. try:
autofs
cd /n
sdfvgsdf
ls -l
)
that was the most tricky thing about the original implementation
(remember to account for walk to "..")
i *think* i preferred autodir as a name (after all, it only
automatically creates directories, not files) but that's just a matter
of taste. maybe "autodirfs"...?
the other thing is perhaps it should by default bind itself *after*
the usual contents of /n. this means it doesn't obscure any currently
mounted stuff; also, there's a potential performance hit from using it
(an additional interaction with a user-level program when walking to
directories through /n), so perhaps one should continue to allow the
old statically created /n directories too where that might be an
issue.
cheers,
rog.
next reply other threads:[~2002-07-16 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 12:23 rog [this message]
2002-07-16 11:42 ` Sam
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 8:58 Fco.J.Ballesteros
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=152377f48470da984ce494ebe56ed076@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.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;
as well as URLs for NNTP newsgroup(s).