On Fri, May 3, 2019 at 9:13 PM jaltman <jaltman(a)auristor.com> wrote:
> Say they're not, and need some other distinct setup. If it's
> standardized, as is seeming more apparent from the existing SELinux
> hooks, OK. Perhaps it's worth adding to the FSH, if it's such a
> standard usage?
The use of /afs as the default location to mount a cell's root volume
"root.afs" dates back at least as far as 1989. Throughout the 90s /afs became
the root of the public global AFS file namespace. Organizations that deployed AFS for
private namespaces did use other top-level mounts but all of the worldwide public
namespace paths are rooted at /afs regardless of operating system; even AFS on Windows
uses the \\AFS UNC path that is canonically equivalent to /afs.
I believe that /afs should be added to the FHS as the standard mount for the public AFS
and AuriStorFS file namespace. All recent AFS-family clients will interpret the path
component below /afs/ as a cell name and search for the cell's location servers in DNS
using SRV or AFSDB records. This permits any individual or organization that controls a
domain to standup storage that can be accessed from any internet connected device with
close to zero configuration provided the required access requirements are met.
Then I think you want the fhs-discuss mailing list, to help this get
through, at
https://lists.linux-foundation.org/mailman/listinfo/fhs-discuss.
It's a pretty quiet list, so there may be a more active relevant chat
channel. Does anyone else know of a more active list or channel to
update the FHS ?