[mdlug] Looking for info regarding Linux server FSH standard practices when sharing files

[Aaron Kulkis]

Jeff Hanson wrote:
> I'm in the middle of setting up a new server and I need to create
> network shares of several large archives of add-ons and updates to
> various OSes and applications.  What is the standard practice for the
> location of files that will be accessed by many users on a network but
> not belonging to a specific user?  Something like "/home/public" or
> should it be somewhere in /var?

remember...the computer and the environment of it's data
is all a MAN-MADE UNIVERSE...therefore...DO WHAT MAKES SENSE.



/data
/local/public

/home is for home directories (although I have put other
things in the /home filesystem, I would never advocate
that a path beginning with /home be used for public
access...if you do that, make a symbolic link, like this:

ln -s /home/public /public

So that it appears under /public.)

/local/public would be a good choice.

Publicizing a path name that begins with /home/ for
public data violates the "do what makes sense" rule.

what DOES make sense is a path name that implies
what it's used for.

[Use the magic of symbolic links to make the
data PHYSICALLY reside on whatever file system
makes the most sense for you... /local and /home
are good for being left alone when you decide
to install a new version of the OS (i.e. clean
install instead of "upgrade")