Dear managers
First of all, sorry for the late summary,
and many thanks to
Simon Tardell <tardell_at_particle.kth.se>
Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>
My original question is at the bottom of this mail.
Basically, one has to be very, VERY carefull with all the posible links
which have to be redone on the clients, otherwise they would not "see"
the software and keep track of all files which are not written to /usr/opt.
So I will let it stay as it is for the moment until I have
more time or get an idea of the proper way to do it.
I include both answers including one reply to a question of the list
regarding the Fortran compiler which was kindly sent to me by Simon Tardell.
Regards,
Monica
*****************************************************************************
From: Simon Tardell <tardell_at_particle.kth.se>:
> Maybe part of the answer is in this reply to an earlier question on the list.
> As you might deduce from it, part of the problem is that the software might
> reside there, but there are an awful lot of links installed pointing to it
> which you have to recreate on all the clients, one way or the other. I'm not
> sure there is a catch all way to do this.
>
> Regards,
>
> Simon.
>
> Simon Tardell, voice +46 8 162688 fax +46 8 347817
> Fysikum, Stockholms universitet simon_at_physto.se, tardell_at_particle.kth.se
>
> ------- Forwarded Message
>
> X-Mailer: exmh version 1.6.1 5/23/95
> To: behrooz_at_rudolf.nscl.msu.edu (Kevin Behrooz)
> Subject: Re: Installing Fortran and other progs in /usr/local
> In-reply-to: Your message of Mon, 16 Sep 1996 08:27:37 EDT.
> <9609161227.AA21035_at_rudolf.nscl.msu.edu>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Date: Mon, 16 Sep 1996 21:55:47 +0200
> From: Simon Tardell <tardell_at_msia02.msi.se>
>
>
> Your message dated: Mon, 16 Sep 1996 08:27:37 EDT
> >Hello managers.
>
> Hi Kevin!
>
> >I would like to install the DEC supplied applications (e.g. FORTRAN,
> >etc) in /usr/local/*, so I can export them to my NFS clients.
>
> You're certainly not the only one to think about this. I didn't solve the
> problem, but I have some leads you might want to investigate.
>
> >I am wondering what is the easiest way to do this. Trying to hunt down
> >what was installed in /usr/bin, and /usr/lib and trying to create links
> >don't seem to be the right solutions.
>
> setld -i DFACOM380 (etc.) will do that for you. Find the files, that is. It
> won't find any links, or any mods to configuration files that the installation
> of any specific product needs, though. To make things more complicated, some
> products install themselves directly in /usr/bin/ (etc.) while others drop
> into /usr/opt and set up links. Note that many products will expect to find
> their files in specific places.
>
> I have been toying with the idea of tricking setld into running the parts of
> the subset control scripts that does the configuration part of the
> installation (i.e. starting after the actual unpacking of the subset). Check
> out:
> stl_scp (4) - setld subset control program conventions
> and Programming Support Tools
>
> I imagine something like
> setld -D /ashareddisk/ -l SUBSET100
> then, on each node:
> linking the files in the SUBSET to the places indicated in
> the .inv-file (what is what setld -i will tell you)
> setld -c SUBSET100 POST_L
> setld -c SUBSET100 INSTALL
>
> I don't know if I am on the right track, though. Didn't have the time to play
> with it.
>
> Also, note that it might be a bad idea to share between computers runtime
> libraries and certain executables, since you don't want to swap through the
> network.
>
> If you devise a method which has general enough application, please let me
> know.
>
> >I am wondering how the rest of managers solve this problem.
>
> Regards,
>
> Simon.
>
> Simon Tardell, voice +46 8 162688 fax +46 8 347817
> Fysikum, Stockholms universitet simon_at_physto.se, tardell_at_particle.kth.se
>
******************************************************************************
From: Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>:
> Regards,
>
> Before I did this I would assure myself that none of these subsets had
> dependent files/libraries other places than in /usr/opt ....
>
> This can be done by doing a check on the files in /usr/.smdb. Remember that
> if you only export and mount /usr/opt containing all these subsystems then
> the clients don't 'see' via setld that they have these subsystems
> installed.
************************************************************************************
My original question:
> Dear managers,
>
> I am just thinking of saving diskspace and looking at all the optional
> products installed in the different DU boxes (Alpha Stations 255 and 500
> and an Alpha Server 8400 all with DU4.0A). This products are, for example:
>
>
> BRX310, BRX321, CDE100, DIA220, DSRS110, ESL3000, FSF, FUS310, KPCBASE300, KPFBASE300, LDB407,
> MME220, MPI100, NAS800, O3D410, PSE110, PPM110, PVM100, XMDLOA330, XMDMAN330, XMDPLL330,
> XMDSCI330, XMRLOA330, XMRPLL330, XR6320, ZE3, advfsd, dtadvfs, alt, lib, obsolete,
> pm, posix, s5, sterling, ultrix
>
> Is it save to export this directory, say from the Alpha Server to all the
> others?
>
> Thanks for any help
> Monica
>
>
>
>
Received on Fri Feb 21 1997 - 19:24:55 NZDT