The links in /usr/local/etc are created by the Fermi Linux
distribution installation scripts, and are ONLY automated when you
install ups/upd via this method. Therefore, you ARE root when you
do the installation. Not a problem.
The links point to files which are owned by ~products (the
$SETUPS_DIR files), and which are maintained by that account.
If you choose to manually install the bootstrap_coreFUE product from
fnkits (i.e., you bypass the Fermi Linux distribution), then you do
NOT automatically get links in /usr/local/products. You do not need
to be root to install/use ups/upd in the general case.
What kinds of complaints from users have you seen in this regard?
Is there something that we have mis-documented? Is it limited to
Linux, or have we missed something on other platforms as well? To
the best of my knowledge, you do NOT need to be root to install
ups/upd (except for on-site nodes which are supported by the
computing division, who request that you add /usr/local/etc links so
that when we log into your machine, we can find the FUE environment
no matter where you put it).
On Thursday 14 January 1999,
our friend Liz Sexton-Kennedy spaketh thusly:
> I will not be at this meeting but I wanted to comment on the following:
> > - if possible, let the RPM installation of bootstrap_coreFUE
> > be relocatable; and have the RPM installation script
> > perform any required post-installation "fix-up" for
> > self-consistency. Links in /usr/local/etc could be
> > an option (controlled by an on/off-site flag). Dan
> > Yocum and Connie Sieh are investigating whether or
> > not this is possible.
> I would say that if the on/off-site flag idea doesn't work then the
> part of the procedure that puts links in /usr/local/etc should be taken out!
> I know that a lot of people currently involved in this did not take part in
> the requirements gathering phase of the ups/upd design but believe me that
> the requirement that a remote sight be able to install coreFUE WITHOUT being
> root was a MAJOR requirement. In my opinion this was one of the two main
> reasons for the redesign in the first place, so seeing it being taken so
> lightly in this context is surprising to me. I have had several complaints
> from users about this, and I feel somewhat embarrassed about it since I did
> have something to do with the redesign...