On Thu, Jun 08, 2000 at 02:54:42PM +0100, Graeme Mathieson wrote: > > OK, you've got me there. I suspect, however, that it wasn't a direct > result of profile.d that $PATH was screwed up. oh really? well i sure don't see anything else that could have caused it (well it could be any number of redhat obfuscations but..): [eb@www eb]$ echo $PATH /usr/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/eb/bin [eb@www eb]$ cat .bash_profile | grep PATH PATH=${PATH}:$HOME/bin export USERNAME BASH_ENV PATH EDITOR [eb@www eb]$ cat /etc/profile | grep PATH PATH="$PATH:/usr/X11R6/bin" export PATH PS1 HOSTNAME HISTSIZE HISTFILESIZE USER LOGNAME MAIL [eb@www eb]$ cat /etc/issue Red Hat Linux release 5.2 (Apollo) Kernel 2.0.36 on an i586 now can you tell me where else that lame PATH could have come from? ;-) > > why use a bunch of little files? > > Simple. The package itself should have created the requisite small file. > In my case, certain packages are only installed on certain machines, > so their profile.d scripts are only pushed to those machines. that may indeed be useful in some rare cases, but i don't think the benifit is worth the cost, see above. it creates a frigging mess, perhaps for adding a NEW independant variable it could work ok, but for patching existing standard variables such as PATH you get a mess. > > I use NIS for auth, and as the man page for yppasswdd says: well NIS is not the standard setup. (and IMO that is a lame restriction, especially on systems like *ahem* slowaris that insist on using that awful ksh as a default. ) -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgpjZKZIrNigA.pgp
Description: PGP signature