On Sat, Jan 25, 2003 at 02:59:56PM -0600, Roger Glover wrote:
> Mike Brown wrote:
> 
> > Some shells have a 'noclobber' option that controls whether or
> > not '>' will overwrite an existing file or raise an error. How
> > you set this option depends on what shell you're using.
> > #!/bin/sh implies Bourne shell,
> 
> In Posix-compliant systems (most modern UNIX variants, including all
> formulations of Linux I have used), it implies Korn shell.  The original
> Bourne shell does not have a "noclobber" feature at all.

  Wrong... all unix I used had a Boune shell for /bin/sh
Korn shell is "ksh" a version used on System V and AIX, but certainly
not as /bin/sh, the syntax was hugely different.
  All Linux ship with bash "Bourne Again shell" as /bin/sh
which is backward compatible with the Bourne shell. This is actually
stipulated by the Linux Standard Base.

Daniel

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard@xxxxxxxxxx  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list