Hey,
I'm trying to decide which of the following methods would be less heavy
handed or more admin friendly for path modification (root's path :) ).
If a PATH line is in root's .dot files (.bashrc, .tcshrc, .cshrc) and
doesn't not contain a $PATH or equivalent entry
{Method 1}
- suck off the value being set. Search $PATH for existence of these
"hardcoded" values and append to the front any that don't already
exist, e.g., PATH=$unique_items:$PATH
{Method 2}
- have a hardcoded set of standard root path items (see below) and append
these to the front of the PATH line followed by $PATH. It would likely
make since to remove any existing occurance of these items to reduce cruft.
Common list of root paths from RH9.0 & MDK9.0 .dot files:
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin: \
/usr/X11R6/bin
There are pros/cons to both approaches and both are about the same to do as
far as implementation so it's more a matter of what's less intrusive or
more expected behaviour?
Also, FWIW, the reason for the required $PATH in root's area is that OSCAR
puts things lots of things in /opt areas and they're not typically in the
search path. (And MDK hardcode's root's path w/o any inclusion of $PATH.)
Thanks,
--tjn
_________________________________________________________________________
Thomas Naughton [EMAIL PROTECTED]
Research Associate (865) 576-4184
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
