[comp.unix.wizards] Where to get a cheap shell with history

lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani) (12/22/87)

In article <6874@ncoast.UUCP>, allbery@ncoast.UUCP (Brandon Allbery) writes:
	[previous quotation deleted]
> 
> Which answer begs for another question:  What are those of us who run an SVR2
> (or SVR3) without the Korn shell available AND WITHOUT A SOURCE LICENSE
> supposed to do for a history mechanism, then?
> 
> Brandon S. Allbery		      necntc!ncoast!allbery@harvard.harvard.edu
>  {hoptoad,harvard!necntc,cbosgd,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery
> 			Moderator of comp.sources.misc


You need to get a copy of the "bourne" code from an archive site.
Look in comp.sources.unix for information about how to retrieve
files.  I have not used "bourne" or an archive site so I can't
comment on them.  The description of "bourne" said it was the
Bourne shell with job control, tilde, history, and some other stuff.
This is available for little or no charge.  I don't know if it
will port to SVR[23] but it is probablys good start.

-- 
	Larry Cipriani AT&T Network Systems at
	cbosgd!osu-cis!tut!lvc Ohio State University

mjr@osiris.UUCP (Marcus J. Ranum) (12/22/87)

	What is the status of the sh(1) released with MINIX ? It's 
a re-implement of the Bourne shell, and isn't it freely distributable ?
Might not be too hard to get a copy of that and hack and snip...

--mjr();
-- 
Once, there was NO fun... 
This was before MENU planning, FASHION statements or NAUTILUS equipment...
Then, in 1985..  FUN was completely encoded in this tiny MICROCHIP...  
It contains 14,768 vaguely amusing SIT-COM pilots!!

randy@umn-cs.cs.umn.edu (Randy Orrison) (12/23/87)

In article <1486@osiris.UUCP> mjr@osiris.UUCP (Marcus J. Ranum) writes:
>	What is the status of the sh(1) released with MINIX ? It's 
>a re-implement of the Bourne shell, and isn't it freely distributable ?
>Might not be too hard to get a copy of that and hack and snip...

Alas, this isn't true.  Minix (including utilities) is copyright by Prentice
Hall, with limited redistribution allowed, and that for educational purposes
only.

However, someday, hopefully, GNU will provide you with what you want.  Send
them money, or write a sh and donate it to them!

	-randy
-- 
Randy Orrison, University of Minnesota School of Mathematics  |
UUCP:	{ihnp4, seismo!rutgers, sun}!umn-cs!randy	      |  (hello?)
ARPA:	randy@ux.acss.umn.edu		BITNET: randy@umnacca |
"I need a unit to sample and hold, but not the angry one: a new design."

allbery@ncoast.UUCP (Brandon Allbery) (12/28/87)

As quoted from <3427@tut.cis.ohio-state.edu> by lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani):
+---------------
| In article <6874@ncoast.UUCP>, allbery@ncoast.UUCP (Brandon Allbery) writes:
| > Which answer begs for another question:  What are those of us who run an SVR2
| > (or SVR3) without the Korn shell available AND WITHOUT A SOURCE LICENSE
| > supposed to do for a history mechanism, then?
| 
| You need to get a copy of the "bourne" code from an archive site.
+---------------

I said, "without a source license".  The "bourne" code is patches to the
source for the 4.2BSD Bourne shell, which is even worse than the original
idea:  I have to buy not only a SVR3 source license, I need a 4.3BSD license
too!

The simplistic answer, BTW, is to use a front end; I've seen a shell script
front end (bcsh) and have contemplated one in C, but in order to have the
front end not choke on Bourne shell programming constructs (and believe me,
I use them.  Often.) I'd have to virtually rewrite the Bourne shell from
scratch into my front-end; while this effectively obviates the need for
/bin/sh as a back-end, it makes things far more complex -- and, while I
consider myself a fairly good programmer, I *know* I'm not up to writing a
Bourne shell.  (My last attempt showed me why csh parses the way it does.)

Oh well, I may as well admit defeat on this one.
-- 
	      Brandon S. Allbery, Moderator of comp.sources.misc
 {hoptoad,harvard!necntc,cbosgd,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery
     [This space reserved for future quotes and similar brain twisters.]

allbery@ncoast.UUCP (Brandon Allbery) (12/29/87)

As quoted from <3282@umn-cs.cs.umn.edu> by randy@umn-cs.cs.umn.edu (Randy Orrison):
+---------------
| In article <1486@osiris.UUCP> mjr@osiris.UUCP (Marcus J. Ranum) writes:
| >	What is the status of the sh(1) released with MINIX ? It's 
| >a re-implement of the Bourne shell, and isn't it freely distributable ?
| >Might not be too hard to get a copy of that and hack and snip...
| 
| Alas, this isn't true.  Minix (including utilities) is copyright by Prentice
| Hall, with limited redistribution allowed, and that for educational purposes
| only.
+---------------

The Minix sh was written at Waterloo(?), and is PD; but it will take far more
than just a little hacking to add command history and shell functions/aliases
to it:  I looked it over when it came out.  I did hear that someone was working
on it, but I haven't seen any results yet... probably a proof that it *is* a
nightmare to add those abilities.
-- 
	      Brandon S. Allbery, Moderator of comp.sources.misc
 {hoptoad,harvard!necntc,cbosgd,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery
     [This space reserved for future quotes and similar brain twisters.]

kimcm@ambush.UUCP (Kim Chr. Madsen) (12/29/87)

allbery@ncoast.UUCP (Brandon Allbery) writes:

>The simplistic answer, BTW, is to use a front end; I've seen a shell script
>front end (bcsh) and have contemplated one in C, but in order to have the
>front end not choke on Bourne shell programming constructs (and believe me,
>I use them.  Often.) I'd have to virtually rewrite the Bourne shell from
>scratch into my front-end; while this effectively obviates the need for
>/bin/sh as a back-end, it makes things far more complex -- and, while I
>consider myself a fairly good programmer, I *know* I'm not up to writing a
>Bourne shell.  (My last attempt showed me why csh parses the way it does.)

In the UNIX/WORLD Volume IV, Number 5, May 1987 - there is an article
called "Making History" by Ray Swartz, which describes how to write a
frontend to the bourne shell providing it with a history mechanism,
saving of history, editing of history. The whole script is 114 lines
code. I haven't tried it so I don't know how eficient it is! 

For more information refer to the magazine or if you can't get hold of
a copy to dropping a letter to Ray Swartz at the following address:
	ihnp4!sun!uworld!ray

					Happy New Year
					Kim Chr. Madsen.

bak@csd_v.UUCP (Bruce) (12/31/87)

In article <574@ambush.UUCP>, kimcm@ambush.UUCP (Kim Chr. Madsen) writes:
> allbery@ncoast.UUCP (Brandon Allbery) writes:
> 
> >The simplistic answer, BTW, is to use a front end; I've seen a shell script
> 
> In the UNIX/WORLD Volume IV, Number 5, May 1987 - there is an article
> called "Making History" by Ray Swartz,...

I tried it before I had ksh.  The basic problem is that it (and all my
attempts to front end sh) break system 5 functions.  I don't remember 
exactly why though.

Bruce Kern                                 |  uunet!swlabs!csd_v!bak  
Computer Systems Design                    |  1-203-270-0399          
29 High Rock Rd., Sandy Hook, Ct. 06482    |  This space for rent.    
-- 
  Bruce Kern                                 |  uunet!swlabs!csd_v!bak  
  Computer Systems Design                    |  1-203-270-0399          
  29 High Rock Rd., Sandy Hook, Ct. 06482    |  This space for rent.