Return to BSD News archive
Xref: sserve comp.unix.bsd:8793 comp.sys.sun.admin:7713
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uunet!mcsun!sunic!dkuug!ruc.dk!mac-jba.ruc.dk!jba
From: jba@dat.ruc.dk (Jan Bruun Andersen)
Newsgroups: comp.unix.bsd,comp.sys.sun.admin
Subject: Re: [386bsd / SunOS] Inviting Religious Pathname Flamewars (Not)
Message-ID: <1992Dec10.101413.8897@ruc.dk>
Date: 10 Dec 92 10:14:13 GMT
References: <peter.723756894@hilly>
Sender: news@ruc.dk
Organization: Roskilde Universitetscenter
Lines: 35
X-Xxmessage-Id: <A74CD4C595029153@mac-jba.ruc.dk>
X-Xxdate: Thu, 10 Dec 92 10: 04:37 GMT
Nntp-Posting-Host: mac-jba
X-Useragent: Nuntius v1.1.1d14
In article <peter.723756894@hilly> Peter Galbavy, peter@micromuse.co.uk writes:
> As part of a small project to get standard sets of binaries up on a
> number of platforms (Sun, 386bsd in particular) I am using things like
> amd and a perl script to do lots of automounting and sys-linking
> around that place, and I am having a problem with finding a good
> working set of path names for popular packages.
While we don't use it (yet) I think you should have a look at something
called "The Depot". I think I still have the article somewhere in my office,
but basically Depot allows the administrator to install sources and
binaries for different architectures in a well-defined directory structure,
and then using auto- and/or loopback mounts to have it all appear in
a 'logical' correct place. Appearently Depot scales very well.
> [...]
> What I want to know is should I lose the "local" bit of /usr/local and
> also maybe for GNU packages use /usr/gnu or /gnu etc? One particular
> aim is to be able to add the *minimum* number of components to the
> users exec path, but still have a reasonably logical seperation of
> packages.
I have been very pleased with a package called "Module". The administrator
only needs to write a small script (module) for each package a user may need.
The script will usually just prepend or append to PATH and MANPATH and
set a few environment variables. The beauty of it all, is that the script is
written in its own language (TCL extensions) and subsequently eval'ed by
an interpreter that emits the required shell-commands based on the invoking
users shell (sh, bash, csh, tcsh currently supported).
--
/| / Jan Bruun Andersen /^^^\ .----------------.
/ | / Datalogi, RUC { o_o } | SIMULA does it |
/--|/ \ o / --> | with CLASS |
`--' ' <jba@dat.ruc.dk> --mm---mm-- `----------------'