Re: "No Shell"

From: David Douthitt (ddouthitt_at_cuna.coop)
Date: 05/20/04

  • Next message: Charles Banas: "Re: Google groups email spider,Auction software, Directory PPC search engine software, email spiders - 4" 
    Date: Wed, 19 May 2004 17:13:50 -0500

    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.

    * 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).

  • Next message: Charles Banas: "Re: Google groups email spider,Auction software, Directory PPC search engine software, email spiders - 4"

    Relevant Pages

    • Re: vi horizontal split screen
      ... I'm an old ksh hacker, but bash will do fine. ... I started on the SysV R2 Bourne shell, and used csh for a better ... Several ksh improvements were designed to make it faster and more efficient at processing scripts, and one way to do that was substitute built-ins for external commands called from the script. ...
      (comp.editors)
    • Re: Which shell interpreter has priority: The declared, the current or calling?
      ... >> Imagine I have the three shells csh, ksh and bash. ... > most shells), executing the script as if written in ksh. ... > shebang indicates that the script is probably written in bash. ...
      (comp.unix.questions)
    • Re: need to confirm I can change roots login shell to something other than /sbin/sh
      ... sh does, ksh does, /usr/bin/echo does, bash and csh do not. ... and AFAIK there have been reservations in the BSD camp ...
      (comp.unix.solaris)
    • Re: function definition syntax
      ... :>> So ksh isn't even compatible with itself. ... that doesn't make is a standard. ... :> largely by the rush of people to push things towards a POSIX standard ... :> "get" that ksh was a recognizable shell without POSIX behavior. ...
      (comp.unix.shell)
    • Re: function definition syntax
      ... there was no standard; the book defined a language not a standard. ... > largely by the rush of people to push things towards a POSIX standard ... > It wasn't the ksh standard that was affected. ... POSIX shell and not call it ksh. ...
      (comp.unix.shell)