I fully agree with that. This was a small company, with one Unix System 
admin guy who was a total jerk. Interestingly, the project I was on owned 
all of the systems. Even the manager of the group could not get them to 
allow the engineers to have root passwords on their own systems. One 
reason was that some of our systems were used as build machines.  
Even at Raytheon on HP-UX, the system admins supported ksh and 
bash as well as csh. In any case, it was only a 3 month contract. Had I 
been full time or the contract been longer, I would have asserted myself 
more. Any case, my 10 or so contracting years at DEC spoiled me. 

On 19 Jun 2000, at 15:42, Paul Lussier wrote:

> You're sysadmin people should have been tortured and shot.  IMO, there's no 
> good reason for not adding ksh to /etc/shells.  If they were lazy, then it's 
> trivial to have an NFS mounted fs which contains the master 'shells' list, 
> then just symlink everyone's /etc/shells to it, or rdist the sucker around.

Jerry Feldman <[EMAIL PROTECTED]>
Associate Director
Boston Linux and Unix user group
http://www.blu.org

**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to