Followup to: <2940.953253924@kao2.melbourne.sgi.com>
By author: Keith Owens <kaos@ocs.com.au>
In newsgroup: linux.dev.kernel
>
> On 15 Mar 2000 14:23:39 -0800,
> orc@pell.portland.or.us (david parsons) wrote:
> >In article <linux.kernel.3582.953084482@kao2.melbourne.sgi.com>,
> >Keith Owens <kaos@ocs.com.au> wrote:
> >>+#!/bin/bash
> >
> > What is this? None of the command this shell script runs are
> > bash builtins, and thus there's no particular reason to cripple
> > it by making it use bash.
>
> bash uses unset, *csh uses unsetenv for environment variables.
> Portability, what portability ;)?
>
The point being that you could use another Bourne shell derivative
(sh, ash, ksh, pdksh, zsh) instead. The standard path for Bourne
shell scripts is /bin/sh; for C shell scripts /bin/csh even though the
latter usually means tcsh.
-hpa
-- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:34 EST