From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] bug in exportfs
Date: Mon, 15 Feb 2016 12:55:40 +0200 [thread overview]
Message-ID: <1bf0a76063ce59910453b8007eb36d7f@proxima.alt.za> (raw)
In-Reply-To: <CAOw7k5iKUN627cKY8NUpoCWaFM_wcNTHK6LEvNyVtewiKdxb+Q@mail.gmail.com>
> Yes, although that convention isn't in Plan 9, and it might be
> worthwhile reconsidering how and why it is used. If for configuration
> files, perhaps they should be stored elsewhere; if for access control
> (eg, .htaccess), perhaps groups would be better, with dynamic group
> membership providing the effect of an access control list.
Charles, I think Kenji has a point and you are diverting the
discussion <grin>.
Whereas I agree that the leading-dot convention ought to be buried, in
reality (a) it is not going to just go away and (b) if it was so
readily accepted, it must have fulfilled a need.
But that's history. When exporting a file system, as Kenji points
out, things may break if we remove features. At the same time,
documenting and, if necessary, implementing a different approach based
on a custom namespace seems like a great idea and may at least stop
further abuse of the filtering that, it seems to me, we cannot
eliminate without risk of possible pain.
I do doubt very much that retrofitting will take place, but one can hope.
Lucio.
next prev parent reply other threads:[~2016-02-15 10:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 23:31 arisawa
2015-12-17 11:40 ` Peter Hull
2015-12-17 13:05 ` arisawa
2015-12-22 9:25 ` Peter Hull
2015-12-22 10:02 ` arisawa
2016-02-13 14:26 ` Charles Forsyth
2016-02-14 2:00 ` Prof Brucee
2016-02-14 10:27 ` hiro
2016-02-14 12:21 ` Charles Forsyth
2016-02-14 12:33 ` Charles Forsyth
2016-02-14 16:38 ` cinap_lenrek
2016-02-14 22:57 ` Charles Forsyth
2016-02-15 1:05 ` arisawa
2016-02-15 6:12 ` Bruce Ellis
2016-02-15 10:34 ` Charles Forsyth
2016-02-15 10:55 ` lucio [this message]
2016-02-15 12:08 ` Charles Forsyth
2016-02-15 12:13 ` Brantley Coile
2016-02-15 15:05 ` lucio
2016-02-15 15:24 ` erik quanstrom
2016-02-15 12:44 ` lucio
2016-02-15 12:48 ` Charles Forsyth
2016-02-15 14:03 ` lucio
2016-02-15 15:38 ` erik quanstrom
2016-02-15 15:56 ` Skip Tavakkolian
2016-02-15 12:18 ` Charles Forsyth
2016-02-15 15:30 ` erik quanstrom
2016-02-15 23:32 ` Charles Forsyth
2016-02-19 14:12 ` Charles Forsyth
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=1bf0a76063ce59910453b8007eb36d7f@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.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 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).