On 04/03/2012 07:28 PM, Ruslan Nabioullin wrote: > What are optimal schemes for establishing directories containing data to > be shared amongst several users, with no conceptual individual owner? > (confined to the host and/or exported over a network by, e.g., NFS) > > FHS does not explicitly state a convention, but it suggests an alternate > subdivision of /home (e.g., /home/staff), which appears to be an elegant > way of adding, in addition to users' home dirs, e.g., > /home/staff/shared, in contrast to, e.g., /home/shared. > > Although not stated by FHS, it should be noted that some distros provide > by default a /home/<USER>/shared dir (granting rx to g or go). However, > this scheme would be only appropriate for shared data conceptually owned > by an individual, versus shared data conceptually owned by a group. > > FHS also mentions one possible methodology for naming within /srv, > namely administrative context, which would elegantly allow for, e.g., > /srv/physics/shared. > > Various sources (e.g., NFS's exports(5)) suggest schemes which create > dirs within /, e.g., /pub, but this appears inelegant and violates FHS.
For distributions and third-party software distributors, yes. The FHS is intended to guide those groups more than end users or sysadmins. If you're concerned about this from the point of view of an end user or sysadmin, do whatever you think best. Personally, I've used /var for that purpose before, but /home and new toplevel dirs have also been used. If you're coming from the perspective of a distribution or third-party software developer, it's hard to say what the right thing would be without more information about your specific use case. -- Jeff Licquia The Linux Foundation +1 (317) 915-7441 [email protected] Linux Foundation Events Schedule: events.linuxfoundation.org Linux Foundation Training Schedule: training.linuxfoundation.org _______________________________________________ fhs-discuss mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/fhs-discuss
