Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!hubcap!ncrcae!opusc!bert
From: bert@opusc.CS.SCAROLINA.EDU (Bert Still)
Newsgroups: comp.unix.questions
Subject: Re: tcsh
Summary: /etc/shells not as standard as you think...
Message-ID: <198@opusc.CS.SCAROLINA.EDU>
Date: 1 Jun 89 19:00:38 GMT
References: <3693@udccvax1.acs.udel.EDU> <6622@xyzzy.UUCP> <13721@dartvax.Dartmouth.EDU>
Distribution: na
Organization: Univ. of South Carolina, Columbia
Lines: 27

In article <13721@dartvax.Dartmouth.EDU>, pete@northstar89 writes:
>>  In article <3693@udccvax1.acs.udel.EDU> don@vax1.acs.udel.EDU writes:
>>  Note that the shell names that chsh(1) will accept are *compiled in*!
>>  So, if it won't take your requests to change your shell talk to your
>>  system administrator.  He/She can either (1) just edit the /etc/passwd
>>  file (assuming a non-YP system, of course), or (2) if source for
>>  chsh(1) is around, update/recompile it.
> Nope, the valid shells are in a text file called /etc/shells.  Just add
> a line to that file (your sysadmin has to do it most probably) that
> points to where your tcsh is located.

Well.... The /etc/shells construction is not yet universally used on
BSD based systems (forget System V for a moment here -- I can't recall
having seen chsh on System V.3...).  For example, our VAX-11/750 runs
MtXinu-4.3 and uses /etc/shells; however, our Sun-4/260s run SunOS
Sys4-3.2, which does not use /etc/shells.  Thus, both of you are
"right" although Don's suggestion of using the good old ``vipw''
will always work (supposing ``vipw'' exists ;-)

					bert@cs.scarolina.edu



-- 
Domain:  bert%opus@cs.scarolina.edu   #####   BITNET:  T410119@UNIVSCVM
LarynxNet: Bert Still
AcadNet: Computer Services Division, University Of South Carolina