Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!public!thad
From: thad@public.BTR.COM (Thaddeus P. Floryan)
Newsgroups: comp.sys.att
Subject: Re: KSH and Layers
Message-ID: <1932@public.BTR.COM>
Date: 26 Feb 91 14:17:56 GMT
References: <119@cvpath.UUCP> <519@genco.bungi.com> <251@rml.UUCP> <1789@svin02.info.win.tue.nl>
Organization: BTR Public Access UNIX, MtnView CA, Contact: cs@btr.com 415-966-1429
Lines: 25

In article <1789@svin02.info.win.tue.nl> debra@info.win.tue.nl writes:
>Put the following line in your .profile, assuming ksh is in /bin:
>SHELL=/bin/ksh; export SHELL
>
>That'll do the trick.

True!  But even faster, per the "optimization" tricks in "The KORN Shell",
would be:

export SHELL=/bin/ksh

which can also be stated:

set -a
SHELL=/bin/ksh

In the first example, other env vars can be set in the same "line."  In the
second example, the "set -a" (where "a" = allexport) means all vars set will
be automatically exported.

I strongly urge people to acquire a copy of "The KORN Shell" which is THE
definitive reference work regarding ksh (besides which it contains numerous
"tricks" and addresses efficiency issues).

Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]


Brought to you by Super Global Mega Corp .com