On Fri, 27 Jul 2007, Greg Freemyer wrote:
A) create there own directory / partition / mount point in the root if there is going to be a lot of data. This is particularly true if it is gone to be a main function of the computer.
"A" above is not considered good practice, at least not from what I've seen.
/data, /GIS-info, /source-code-for-our-teams-mega-application etc.
However, one can create application-specific directories in /opt, and in fact the LSB spec requires it. I work on an open-source app that normally installs to /usr/local/* directories, including it's system-wide configs in /usr/local/share/<app-name>/*. In it's LSB form it installs to /opt/<app-name>/* instead.
B) if there is not going to be enough data to justify that, I believe most Linux apps are using /var/lib/<appname>
Depends. If they're distributed with the OS they sometimes do that.
If they're not part of the OS, they usually install into
/usr/local/* instead so that they're separate from any OS files.
If you're creating your own application, separate from any OS
distribution, consider putting it in /usr/local or /opt. As an
example, the app I spoke of installs into one or the other of these
heirarchies. The first is the default, the 2nd is if you compile it
as a Linux Standard Base package (LSB):
/usr/local/bin/ (executables)
/usr/local/lib/<app-name>/ (scripts)
/usr/local/share/<app-name>/ (configs, maps, sound files, etc)
/usr/local/share/doc/<app-name>/ (README's, INSTALL's, FAQ, LICENSE)
/usr/local/man/man1/ (man pages)
-or-
/opt/<app-name>/bin/ (executables)
/opt/<app-name>/lib/<app-name>/ (scripts)
/opt/<app-name>/share/<app-name>/ (configs, maps, sound files, etc)
/opt/<app-name>/doc/<app-name>/ (README's, INSTALL's, FAQ, LICENSE)
/opt/<app-name>/man/man1/ (man pages)
--
Curt, WE7U: