From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1bf0a76063ce59910453b8007eb36d7f@proxima.alt.za> To: 9fans@9fans.net Date: Mon, 15 Feb 2016 12:55:40 +0200 From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] bug in exportfs Topicbox-Message-UUID: 8445c73c-ead9-11e9-9d60-3106f5b1d025 > 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 . 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.