So I can better understand TSL, would someone kindly explain the philosophy or reason of using some variations from the typical (I think) FHS or at least de facto standards regarding some of tsl dir scheme? For instance, in my experience, php, apache and mysql typically reside down /usr/local, rather than /usr/share or /usr/lib.
You have probably worked only with systems were the packages were installed from sources.
The tradition is that people install software that they add on themselves (especially when building from sources) in '/usr/local/*' to keep it separate from the distribution. This makes it easier to tell what's been changed or added locally; for example you can do "ls /usr/local/bin" to see locally added binaries.
Another common tactic is to install add-on software in /opt/* especially when it comes only as a binary, for example Oracle or Borland; commercial stuff. (In my experience, this is more common on Solaris than Linux. Mostly things on Linux go into /usr or /usr/local.)
Apache, Mysql, perl, python, gcc, and so on are all part of most Linux distributions now so they are packaged by the distributor and so they really are part of the distributions and they install that way. (Hey TSL guys, where's emacs? :-)
/usr/*/lib is for libraries /usr/*/share is for non-executable files like docs and man pages
If you build mysql or php yourself from sources you downloaded then you would probably install them in /usr/local. If you build RPM's to be used in a distro, you would install in /usr.
Re: mysql, you probably see only text files (docs, man pages, language files). The rest of mysql is in normal places -- /usr/sbin for the daemon, /usr/bin for binaries, /usr/lib for libraries, /var/lib/mysql for databases.
My comments here apply to pretty much every UN*X variant I have used not TSL specific.
-- Brian Wilson Corvallis, Oregon 541-368-4120
_______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
