Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!sdd.hp.com!cs.utexas.edu!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [BSD4.3reno] /bin/sh problem?
Message-ID: <1992Nov5.032413.18546@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: University of Utah Computer Center
References: <1d9m3vINN8nh@charnel.ecst.csuchico.edu>
Date: Thu, 5 Nov 92 03:24:13 GMT
Lines: 29
In article <1d9m3vINN8nh@charnel.ecst.csuchico.edu>, rodmur@ecst.csuchico.edu (Dale Harris) writes:
|> I don't know if anyone has asked this before or not, but...
|>
|> Has anyone ever tried doing a function or sub-routine in a shell script
|> in BSD4.3 or BSD4.4, it doesn't seem to want to work, and it works on
|> several other flavors of Unix.
Works fine for me (look at the patch kit shell script, "patches"). Maybe you
aren't running under shell? I also don't understand why the lone ";".
You can forcibly run /bin/sh from the unpatched kernel by using:
1) /bin/sc <script_name> <parameters>
2) At the top of the file, use a single colon (":") instead of a comment
shell designator ("#/bin/sh").
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------