Path: utzoo!attcan!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!deimos.cis.ksu.edu!uxc!garcon!uxf.cso.uiuc.edu!chris
From: chris@uxf.cso.uiuc.edu (Chris Martin)
Newsgroups: comp.unix.questions
Subject: Re: tcsh
Summary: not always that easy
Message-ID: <1111@garcon.cso.uiuc.edu>
Date: 24 May 89 19:07:03 GMT
References: <3693@udccvax1.acs.udel.EDU> <8170001@hpfcdq.HP.COM>
Sender: news@garcon.cso.uiuc.edu
Reply-To: chris@uxf.cso.uiuc.edu (Chris Martin)
Organization: University of Illinois at Urbana-Champaign
Lines: 30

In article <8170001@hpfcdq.HP.COM> benji@hpfcdq.HP.COM (Jeff Benjamin) writes:
>The proper usage for chsh is: chsh name [ shell ]
>
>This is on HP-UX, which is Berkely-derived and SysV compatible.
>The name (your login name) is NOT optional, though the shell is
>( it defaults to Bourne shell /bin/sh ).
>
>Try "chsh don /usr/local/tcsh"


It isn't always that simple.  Here's an excerpt from our man page on
a Pyramid 90x with OSx 4.4.

SYNOPSIS
     chsh name [ shell ]

DESCRIPTION
     ...
                                      If no shell is specified,
     then the shell reverts to the default login shell /bin/sh.
     Otherwise,	only /bin/csh, /bin/oldcsh, /bin/tcsh, or
     /usr/new/csh can be specified as the shell	unless you are
     the super-user.


=============================================================================
Christopher Martin           \        INTERNET:  chris@uxf.cso.uiuc.edu 
University of Illinois       /\       UUCP:      uunet!uiucuxc!uxf!chris 
at Urbana-Champaign         /  \      BITNET:    chris@uiucuxf            
=============================================================================