Re: profile.d [was Re: UMASK 002 or 022?]

[Graeme Mathieson <graeme+from@mathie.cx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Ethan Benson <erbenson@alaska.net> writes:

> i am of the opinion that stuff like alaises and other fancy
> non-standardisms should not go into the global profiles at all, they
> belong in ~/.fooshellrc and ~/.fooshell_profile.  you want that stuff
> by default put it in /etc/skel/*  

Is there a mechanism for individual packages to update /etc/profile?  For
instance, it's a pest for each of your users, individually, to have to 
update their path to include /usr/bin/mh for nmh.

And putting stuff in /etc/skel doesn't solve the problem of rolling changes
out to existing users.

OK, so cross-shell compatibility doesn't worry me, since bash is the only
shell used[1].  I have a profile.d directory with a selection of scripts,
including one to add nmh to $PATH, one to set the default $CVSROOT and
$CVS_RSH and one to do colour-ls.  These scripts are rolled out from a
config-server (currently just using opt-depot, but eventually using
cfengine).

[1] By policy.  No other shells are installed, and users cannot run chsh
anyway.
- -- 
Graeme.
graeme+sig@mathie.cx

"Life's not fair," I reply. "But the root password helps." - BOFH
-----BEGIN PGP SIGNATURE-----

iD8DBQE5P3hKPjGH3lNt65URAqkIAJ9UFDuX/YXbOiexdCv6i+MmS5VBYQCgrPow
kLsb/6OXaMDFxzYnbq6fZPY=
=5sG/
-----END PGP SIGNATURE-----