Re: network installation

New Message Reply Date view Thread view Subject view Author view

Ralph Seguin (seguin++at++vr1.engin.umich.edu)
Thu, 11 Aug 1994 10:22:25 -0400

> We run performer on a number of machines (Onyx and Indigo 2) and would
> like to avoid having a full distribution of Performer on each machine,
> but rather would like to mount it from the server for all the machines.
> Unfortunately it seems that Performer inst-alls pieces of itself in a
> large number of places, so that one would have to mount a large number
> of rather high-level trees to all the machines, clearly an undesirable
> situation.
> Is there a way to install Performer in a single dir tree (/usr/Performer
> say) and export/mount that and maybe set a few env variables.... that
> sort of thing?
> It would both save a stack of disk space and make installation/upgrades
> easier (would only have to be done on the server).

I asked this same question a while back (about multiple packages
though). There is one "gross" way of doing it. Install it on
every machine, but have the installation tree be a shared location.

Eg:
machines: m1, m2, m3, m4

m1 has /disk1 exported NFS to m2, m3, m4
m2, m3, m4 automount /disk1 as /nfs/m1/disk1

on each of m2, m3, m4, make a symlink from
/nfs/m1/disk1/swroot into /usr/swroot
on m1, make a symlink from /disk1/swroot into /usr/swroot

now, on every machine, run inst like so...

inst -f /CDROM/dist -r /usr/swroot

advantages: one copy shared
disadvantages: takes LOTS of time, and lots of repeated work

I agree that there should be an easier way of doing this, but
SGI told me that there wasn't.

Ideally, there would be something that would run strictly the
finish up routines from inst (ie, to generate the necessary
symlinks, ...)

-Ralph

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:26 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.