On Thu, Oct 12, 2000 at 03:59:02PM -0500, Steve Borho wrote:
| > My first question is when should you use /opt vs. /usr/local? The
| > standard defines both, but with my lack of experience they sound
| > equivalent to one another, but they must be for different purposes,
| > but what I did not understand.
|
| Historically, /usr/local is for locally compiled and/or written
| software. /opt is for commercially packaged/bundled software.
|
| Treat /usr/local as an extension of /usr for storing things you
| installed by hand that weren't included with the OS.
I would add that I tend to feel that RPMs (or whatever your packaging
tool is - anything which writes to a per-machine db of installed
software) generally shouldn't install into /usr/local either, because
of the below...
| /usr/local is
| sometimes nfs mounted between systems, but not usually.
Except at middle-sized and upwards sites, where it's often NFS mounted.
For this reason I prefer not to deal with RPMs with try to install in
/usr/local, because the data there are not per-machine, but site-wide.
| If you go out and by some boxed set 'FooWorks', it usually gets
| installed in /opt. /opt is often nfs mounted between systems.
| Each subdir in /opt is typically arranged just like /usr/local (ie, it's
| own bin/ lib/ doc/ man/ sub-directories).
Yep. I actually do this rather agressively here, and co-work with /usr/local.
See:
http://www.zip.com.au/~cs/syncopt/
This makes /opt largely a forest of symlinks pointing to a central
/usr/local/opt, with flexibility to make anything local for speed or
robustness. It also means I can install _once_ and all the machines
keep in sync, and install multiple versions of things at once for
testing (or a mix for different users).
| > CVS - Am I correct in my understanding that the CVSROOT should be
| > under /var since it is variable data and not /usr/local which is for
| > applications and their respective files.
|
| Theoretically, the cvs repository should be on it's own partition mounted
| off of the root directory somewhere like /cvs or /cvsroot
|
| Barring that, it should probably go in /var
Or do what we do - make a user called "cvs" (well, "archive" here for
historic reasons) and put it in there. That way you can talk about ~cvs
and have less need to have explicit knowledge of the location.
| > Groups - If you have a group working on a project where do you put
| > the groups information. I am assuming you would put it in /home and
| > make the directory the default home directory of the group.
|
| /home shouldn't be used for anything other than home directories. This
| is because the autofs tool (which automatically mounts your home
| directory onto whichever machine you happen to log in on) get's annoyed
| with anything in in /home. RH7 was the first version of RH Linux which
| obeys this rule.
|
| Again, these kinds of files would optimally be on their own partition,
| but otherwise they should probably go on the same filesystem as /home so
| the data gets included in whatever backup scheme you use.
Or, again, in a project driven system (like the software development
env here), most projects have a user associated with them. So
~projectname is where the files live. There's a "projectname" group to
match which has the staff logins in it. ~projectname lives in /home
just like any other user. Staff use a 002 or 007 umask when working on
the project, and the project direct are group owner by the project
group, with the setgid bit turned on so that new files therein acquire
the group ownership too.
And no, we don't do this with the primary gid of the users' accounts
because:
- people can work on multiple projects
- ideally people have a personal group, too, so that by having nobody
else in that group a umask of 002 or 007 still gives them privacy
for the files in their own account because group permissions there
(where file gid == user primary gid) don't open up any access for
others
There's plenty of way to do these things.
--
Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/
Prepare thy ablutions, worship the bean, and shun the abomination that is
decaf, and one day you too shall walk among the Blessd, whose blood flows
thick and brown with God's Chemical and whose hearts have been replaced with
the more efficient mechanism of a Mr. Coffee. - Keith Morris
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
