John> How about something like:
[snip]
John> <insert text>To install in the default locations (under
John> /usr/local) this will normally mean you have to be root. If you
John> are not installing as root you will need to specify installation
John> directories for which you have write permission. </insert>
This text is simply not true on all systems. I have write access to
/usr/local on our machines because this is how we setup our filesystem
permissions. The proposed text above, while being true for some sites,
will cause serious concerns on other sides. A package which insists to
be installed root is always a bit suspect if it does not have very
good reasons to do so. That is the reasons why the things that
definitely need root permission have their own installation target
(sinstall).
John> ... and voila! it works!! (chmod -R a+rX /usr/local/lib/*)
[This is a very drastic as you make blindly all files readable, which
might be correct, but some exceptions might exist somewhere in
/usr/local/lib/*]
This is most likely a problem of the umask value under your root
account. There is nothing we can do to protect people from using a
narrow masks and later not being able to read the files. This is UNIX,
a bit complicated at the beginning. But once you did learn all these
lessons, you will love it. ;-)
You, like everybody else, are happily invited to submit text for the
FAQ document so that others can learn from your experiences. ;-)
Juergen
Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw
Technical University Braunschweig, Dept. Operating Systems & Computer Networks
Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3283)
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.