[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Distributed *.deb

In ka.lists.linux.debian.devel, I wrote:

[about the setup at our university]

>[It's actually more complicated and flexible, details upon request.]

There was a request, so here I go :-)

The central concept is that of a "segment", a group of machines
belonging together, for example for a workstation pool or an
institute.  These may share a common administrator.

The layout contains the following directrories:

/usr/machine/{bin|lib...}     for site and architecture dependent things,
			      which need to be kept local.  Example: ssh.
			      Updated by central admins, the same

/usr/local/{bin|lib...}       For admins of local machines.  

/usr/segment/{bin|lib...}     segment-wide stuff, applications which are
			      shared between a group of machines.  Resides
			      on a segment server via NFS.  Example: tex
			      binary.  Same everywhere.
			      Updated by central admins.

/usr/app/{bin|lib...}         segment-wide applications.  Updated by
			      segment admins.

/usr/common		      everything site-wide that can be shared
			      between architectures

/usr/common/machine/{etc|...} Arch-independent things which need to be
			      kept locally.  Administrated centrally,
			      identical everywhere.
			      Example: ssh_known_hosts.

/usr/common/segment/{lib|...} Arch-independent things for a segment.
			      Example: emacs *.el files.  Updated by
			      segment admins.

/usr/rzserv/{lib|...}         This which are kept only at one place, because
			      they take up loads of space, and aren't needed
			      often.  Rarely-used apps, for example.

/usr/common/rzserv/{lib|...}  Like above, only arch-independent.  (Metafont
			      source code).

/usr/common/app               You can probably guess :-)

There are three levels of administration, which are clearly separated:

- Central administration, for the whole campus

- Segment administration (for example, an institute may decide to install
  some additional software)

- Machine administration (somebody may want to install the latest and
  greatest stuff on his personal workstation, for example).

This is a very clean concept, which can accomodate something as diverse
as an university with 150 institutes.  I like it, and I'd like to
see dpkg integrated into it :-)
Thomas Koenig, Thomas.Koenig@ciw.uni-karlsruhe.de, ig25@dkauni2.bitnet.
The joy of engineering is to find a straight line on a double
logarithmic diagram.

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . Trouble? 
e-mail to templin@bucknell.edu .

Reply to: