> What I am wondering is, what do they mean by $HOME? I have the application
> installed in /usr/local/src/buffalo, so I figured I should have
> LD_LIBRARY_PATH=/usr/local/src/buffalo ?? Does this sound right or wrong?
> If I use $HOME the application will never be found??
$HOME is the current account's home directory: /root (by default) for
root, /home/grape for some user named grape, etc.
> Could someone have a look at this an maybe explain why I should use $HOME
> versus the real path? (/usr/local/src/buffalo)..
install to $HOME if the program will only be used by the user who
installed it. Eggdrop is a common example (in fact the Makefile does this
already by default). This method is used mostly on shell servers (machines
that provide shell access to its users), or when dealing not with program
binaries, but with user-level configuration, etc.
install to the global paths (/usr/bin, /usr/local/bin, etc) when the
program is to be accessible to all users of a system. This includes ssh,
the different network utils like traceroute, ping, route, etc, among
other things.
/usr/local/src is um.. not familiar to me. /usr/src is where rpm does
package (re)building, and where the Linux kernel source is kept (when
applicable).
Programs are most often installed to /usr/bin or /usr/local/bin (whatever
the default is in the Makefile or the suggested install path found in the
documentation of a package).
LD_LIBRARY_PATH isn't used for the most part unless a library is
installed to a non-standard path (such as in $HOME someplace). For system
libraries (ones that everyone will use), they'll go into places like /lib,
/usr/lib, and /usr/local/lib. After installation, you'll always want to
run /sbin/ldconfig (as root) in order to add the entries to the lil list
that the linker (ld) looks at to find things :)
Um.. that's my two cents.
-Statux
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
