• Subject: Re: python support in CVS.
  • From: Scott Klement <klemscot@xxxxxxxxxxxx>
  • Date: Mon, 27 Nov 2000 14:57:46 -0600 (CST)

On 28 Nov 2000, Carey Evans wrote:

> Scott Klement <klemscot@klements.com> writes:
> > True, /bin/sh is not bash on FreeBSD.   However, I wasn't having the
> > problem that Carey was describing....
> It's quite possible that the *BSD sh has been improved since someone
> from Debian ported it to Linux and called it "ash", more than three
> years ago:
> } This is a very simple port of ash taken from NetBSD-current on
> } 1997/06/18.  The file setmode.c was taken from src/libc/gen and is
> } needed since the Linux libc does provide getmode(3) or setmode(3).
> } History editing is disabled to avoid code bloat.  This also means that
> } building the package is possible without the BSD libedit.
> The man page looks just the same as the NetBSD sh(1) man page I found
> online, though.

The FreeBSD man pages are online as well, if it helps....


Its possible that this shell comes from "ash", and I've just never heard
it called that?  I'm certainly no expert. :)  The FreeBSD project refers
to it as "sh", or "Bourne Shell".  

On the topic of man pages (see how smoothly I worked that in?), the man
page for lp5250d is still describing the command-line-switch syntax,
instead of the ~/.tn5250rc type of config that it has been using since
July...   It would be much appreciated if you could update that... :)


| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].