(*).    ROCK Linux and standards

(*).1.    Does ROCK Linux obey the FHS standard?

Sort of. With ROCK Linux I try to follow the FHS (Filesystem Hierarchy
Standard). The homepage of the FHS is <http://www.pathname.com/fhs/>. The
ASCII version of the FHS can be found in this directory as 'fhs.txt'.

However - ROCK Linux isn't fully complient with the standard:

 *) A few applications don't support the FHS yet - so I can't guarantee
    that everything is in the right place.

 *) I only take care that all man pages goes to /usr/share/man - to put
    the manual page in the right subdirectory here is up to the package
    makefile.

 *) To guide the user to the new locations and make sure that the packages
    place their files in the right directories I've created a few symlinks:

       /usr/doc           -> /usr/share/doc
       /usr/man           -> /usr/share/man
       /usr/info          -> /usr/share/info
       /usr/opt           -> /opt
       /usr/spool         -> /var/spool
       /usr/tmp           -> /tmp
       /var/spool/locks   -> /var/lock
       /var/spool/mail    -> /var/mail

*) Since a few packages need a /usr/libexec directory, I've created one. The
   FHS does not explicitly forbid such a directory - but from the FHS
   philosophy this stuff should go to /usr/lib/<something>.

*) Most of the FHS implementation is up to the packages - not to the ROCK
   build scripts. But I've tried to do the most importand stuff ...


(*).2.    Why isn't there a real package management system? Or is there?

RPM is installed. However, it is not recommended to use RPM to install
software directly on a ROCK Linux distribution. Most RPMs will install stuff
somewhere in /usr, while software which is not part of the distribution
*should* go into /opt.

A simple package management system *is* installed. Please see the appropriate
section of the FAQ, which also explains how to make use of RPMs if you cannot
compile the software yourself.




