Ask yourself: "Would it make sense to eventually share those files through SMB/NFS/AFS/GIT/.?" If so, then you can reasonably consider that your directory is a local file sharing service, and thus store these inside a subdirectory of /srv, even though there is not a daemon actually serving those files to other systems. However you structure it, the /srv is perfectly acceptable to store files to be shared among several users if you can reasonably consider that sharing these files constitute a service by itself. From my personal experience, most administrators that exploit the /srv directory goes on with a per-client, per-site or per-project subdirectory, and then put data directories at that level. The FHS then goes on explaining that the methodology used to name subdirectories of /srv is unspecified. srv/ or /srv//: According to the FHS, /srv contains site-specific data which is served by this system. Both are fine and both are FHS complient, really. I know that some administrators prefer to have these somewhat isolated from the rest of the filesystem, so they mount a distinct volume (ie. You could for example create a directory /groups or /shared and organize files in these as you see fit. CAN I PUT FILES IN EXCHANGE PUBLIC FOLDER FREEor /media//: I honestly don't know why this option has a bad reputation in the Linux world, but let's make this clear: this is really your system, and the FHS says that you are free from creating new directories at the root level as long as you do not conflict with anything for which there is well-established semantics. Still, your question was about the most appropriate place, so let's consider a few common answers (ordered from by most preferred to my less preferred, given your specific use case): Therefore, you may technically put your movies directory anywhere, as long as it doesn't go against FHS conventions. It is important to remember that the FHS addresses issues where file placements need to be coordinated between multiple parties such as local sites, distributions, applications, documentation, etc the FHS doesn't try to set rules for every single situation you may have: local placement of local files is a local issue ( FHS 3.0, section 1.1). Important configuration detains need to be noted (eg group memberships, permission sets, fs tunables for performance, and anything else that is not a default) It needs to become part of system recovery, daily checks, backups, etc. Oh, one thing: Whatever you do, do document it. If you want to make one user the custodian and give the rest access to this project space, feel free to host it in the user's home directory. Questions to consider: Are you going to dedicate a mount-point for this purpose? If there are other similar "groups", I may or may not prefer to host them together, eg /data/movies-entusiast Particularly if this is the primary purpose of this system, I would just create There is nothing wrong with creating a new mount point or directory for this purpose from the root. See the hier(7) man page ( man hier) for more information of the purpose of each directory described by the FHS. I generally use this directory for group-shared files for the reason mentioned in Chris Down's answer I see group file sharing as being a service that the server provides. /srv is an acceptable and often-preferred location for group files.Subdivision may be accomplished by using subdirectories such as /home/staff, /home/guests, /home/students, etc." The FHS actually notes that, "on large systems (especially when the /home directories are shared amongst many hosts using NFS) it is useful to subdivide user home directories. Some see this directory as being an area for group files as well. /var is for "files whose content is expected to continually change during normal operation of the system-such as logs, spool files, and temporary e-mail files." I like to think of it like this: if your data wouldn't look right summarized in a list, it generally doesn't belong in /var (though, there are exceptions to this.)./opt is generally for programs that are self-contained or need to be isolated from the rest of the system for some reason (low and medium interaction honeypot programs, for example). Data here should only change for administrative reasons (e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |