Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!ukc!its63b!xsimon
From: xsimon@its63b.ed.ac.uk (Simon Brown)
Newsgroups: comp.unix.questions
Subject: Re: Why does vipw *require* /bin/csh ?
Message-ID: <573@its63b.ed.ac.uk>
Date: Tue, 11-Aug-87 06:13:57 EDT
Article-I.D.: its63b.573
Posted: Tue Aug 11 06:13:57 1987
Date-Received: Fri, 14-Aug-87 01:44:22 EDT
References: <2647@lifia.UUCP>
Reply-To: xsimon@its63b.ed.ac.uk (Simon Brown)
Distribution: world
Organization: Computer Science Department, Edinburgh University
Lines: 18
Keywords: vipw

In article <2647@lifia.UUCP> phs@lifia.UUCP (Philippe Schnoebelen) writes:
>When you call vipw in order to modify the passwd file under UNIX BSD4.3, it
>performs several so called "sanity checks", e.g.  that you have su'ed, that
>noone else  is currently modifying  it, ...  but more surprisingly  it also
>verifies that your shell  is bin/csh or /bin/sh, which  forbids  you to use
>another shell when su'ed.
>
>Is there any  way around this other than patching the source and recompiling?

Yeah - fire up an "adb -w", and change that "c" in csh to something more useful 
- like a "k", perhaps?
-- 
----------------------------------
| Simon Brown                    | UUCP:  seismo!mcvax!ukc!its63b!simon
| Department of Computer Science | JANET: simon@uk.ac.ed.its63b
| University of Edinburgh,       | ARPA:  simon%its63b.ed.ac.uk@cs.ucl.ac.uk
| Scotland, UK.                  |
----------------------------------     "Life's like that, you know"