Re: "No Shell"
From: Kevin Collins (spamtotrash_at_toomuchfiction.com)
Date: 05/20/04
- Next message: Otto Wyss: "Re: Advancing from Unix Sysadmin to Programmer"
- Previous message: Kevin Collins: "Re: Execute all processes in the background from bash."
- In reply to: David Douthitt: "Re: "No Shell""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 20 May 2004 17:11:19 GMT
In article <c8gm54$o8m$1@grandcanyon.binc.net>, David Douthitt wrote:
> Kevin Collins wrote:
>
>> Out of curiousity, why do you prefer ksh over bash as a user shell? I
>> personally use ksh as a user shell, but use /bin/bash for root.
>
> Several reasons:
>
> * Standard: There are no extensions to trip over when I take a Linux ksh
> script into a HP-UX or Unixware environment... ksh is standard.
While I generally agree with that, there are differences and incompatibilities
between pure ksh88 and pdksh. The folks who post to this group who are
"portability oriented" would probably disagree more strongly.
> * Clean vi-editing support - everytime I enable vi command history
> editing, I find out immediately if I'm in bash or not. Bash gives nasty
> prompts and in general acts funny.
>
> * Minimalist: pdksh (or ash, by the way) support nearly everything from
> ksh and are much smaller than bash.
>
> * Familiarization: this is personal, and somewhat professional, but I
> was programming in ksh (and using csh) before bash came along. I
> finally switched to ksh when I started work here as ksh was the standard
> shell already and I wanted to learn it (I could have used csh).
Thanks, all valid reasons and ones I mostly share :)
Kevin
- Next message: Otto Wyss: "Re: Advancing from Unix Sysadmin to Programmer"
- Previous message: Kevin Collins: "Re: Execute all processes in the background from bash."
- In reply to: David Douthitt: "Re: "No Shell""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|