My Take on using ksh:)
------------- Begin Forwarded Message -------------
Date: Thu, 14 Dec 2000 11:04:20 -0800 (PST)
From: Octave Orgeron <oorgeron@ha2mil-mail>
Subject: Re: [slackware-alphadevel] future plans
To: asl@launay.org
Mime-Version: 1.0
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-MD5: xxxiqQ8F4wspPJHk/ZbN2A==
Hey...
Ksh is the way to go! Bash has a lot of issues, bash2 does not even work right
on the Alpha. Also, Ksh has the vast majority of the "cool" features of bash.
Besides.. ksh can be found on all commerical unix's... as where bash is not. I
would rather have a portable script in ksh that I could bring to any unix box
than to have to install bash on every box. Bash has a long history with Linux, I
know.. I've been using linux since .98.5.x kernel release... however, bash
teaches you a lot of bad habits.. just like gcc. I would rather adhere to
something that works right across platforms with as little effort as possible.
And speaking of DEC osf/1(a.k.a. Digital Unix.. Tru64..) it's by far one of the
best Unix's out there. Now.. look at my email address.. what does that tell you?
Well... soapbox mode off..
-Octave
>Date: Thu, 14 Dec 2000 11:39:22 +0100
>From: "Arnaud S . Launay" <asl@launay.org>
>To: slackware-alphadevel@slackware.com
>Subject: Re: [slackware-alphadevel] future plans
>Mail-Followup-To: slackware-alphadevel@slackware.com
>Mime-Version: 1.0
>Content-Disposition: inline
>Content-Transfer-Encoding: 8bit
>User-Agent: Mutt/1.2.5i
>X-PGP-Key: http://launay.org/pgpkey.asc
>
>Le Wed, Dec 13, 2000 at 11:38:35PM -0800, Chris Lumens a écrit:
>> Then, I'll be playing games with the shell. We are merging ksh into
>> Slackware. I'll be doing things a bit differently from the Intel
>> distribution - namely, placing ksh in as the system's sh. It seems to be
>
>??
>
>Why that ?
>
>bash is the choice shell for Linux, and we're not trying to make
>another dec osf, right ? and don't forget that many linux
>proggy's rely on system sh to be bash. generic sh writing is gone
>for a long, long time...
>
>> functioning just fine on my test machines. Also, I'm thinking about
>> renaming bash to bash2, and bash1 to bash. That means that bash 1.14.7
>> would be "bash". So make menuconfig would work.
>
>It works here on a lot of machines
>
>cassis:~/docs$ bash --version
>GNU bash, version 2.04.0(1)-release (i686-pc-linux-gnu)
>
>ok, it's an intel...
>
>hmm
>
>asl@alpha:~/linux$ bash --version
>GNU bash, version 2.03.0(1)-release (alpha-unknown-linux-gnu)
>
>and there it works fine. apha ev56, ruffian. (debian based)
>
> Arnaud.
>--
>BOFH excuse:
>High nuclear activity in your area.
******************************************************
* Octave J. Orgeron * Specializing in : *
* Unix Systems Administrator * Solaris/Tru64/Linux *
* Sun Microsystems, Inc. * Certified Solaris *
* octave@sun.com * Systems Administrator *
******************************************************
------------- End Forwarded Message -------------
******************************************************
* Octave J. Orgeron * Specializing in : *
* Unix Systems Administrator * Solaris/Tru64/Linux *
* Sun Microsystems, Inc. * Certified Solaris *
* octave@sun.com * Systems Administrator *
******************************************************
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT