Linked by Thom Holwerda on Mon 23rd Feb 2009 17:29 UTC
General Unix UNIX's method of handling file systems and volumes provides you with an opportunity to improve your systems' security and performance. This article addresses the issue of why you should split up your disk data into multiple volumes for optimized performance and security.
Thread beginning with comment 350352
To view parent comment, click here.
To read all comments associated with this story, please click here.
darknexus
Member since:
2008-07-15

/opt is one of those directories that really doesn't have a set use. Some systems, i.e. Slackware, install large packages such as KDE into /opt, others don't. Some, such as Crux Linux, use /opt the way others use /usr/local (/usr/local is nonexistent on Crux).
On Linux, I use /opt like /usr/local, but for software that is to have its own structure. Managed packages don't go there, /opt is for self-compiled software that for whatever reason would need to be kept under its own folder. For instance, Mysql goes into /opt/mysql if I compile it from source. Same with GNOME, if I wish to be on the bleeding edge, it goes under /opt/gnome if I've compiled it. I do not put other structures under /usr/local, that is reserved for self-compiled software that fits the standard folder structure.
For *BSD, I use /opt like /usr/local on Linux, as /usr/local is reserved for installed ports and packages, not for locally compiled software not under control of the ports tree.
Naturally there are no set rules involving these directories. That's just the way I do it. Ah, the wonderful world of the fhs, eh? Some parts of it are not standard at all.

Reply Parent Score: 2