Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Newsgroups: comp.unix.admin
Subject: Re: help removing a file
Message-ID: <.XQ53EG@xds13.ferranti.com>
Date: 7 Sep 90 19:42:22 GMT
References: <1212@tardis.Tymnet.COM> <13419@hydra.gatech.EDU>
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Distribution: usa
Organization: Xenix Support, FICC
Lines: 10

In article <13419@hydra.gatech.EDU> gt0178a@prism.gatech.EDU (BURNS,JIM) writes:
> Not on any system I've worked on. It always defaults to $SHELL, your
> current shell.

No, you mean ksh defaults to ksh. On every system I've ever used, sh defaults
to sh and csh uses the # hack to decide if it should use sh or csh. In my
opinion, this is an error: ksh should execute scripts with /bin/sh by
default... there are enough differences in behaviour between the two shells
that this can break stuff. Just try replacing "sh" with "ksh" to see what
I mean.
-- 
Peter da Silva.   `-_-'
+1 713 274 5180.   'U`
peter@ferranti.com