home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!ferkel.ucsb.edu!taco!rock!stanford.edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!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: [386BSD] Unable to exec #!/bin/sh scripts
- Message-ID: <1992Nov11.023420.21323@fcom.cc.utah.edu>
- Sender: news@fcom.cc.utah.edu
- Organization: University of Utah Computer Center
- References: <INKARI.92Nov10021140@lk-hp-12.hut.fi>
- Distribution: comp
- Date: Wed, 11 Nov 92 02:34:20 GMT
- Lines: 24
-
- In article <INKARI.92Nov10021140@lk-hp-12.hut.fi>, inkari@snakemail.hut.fi (Juha Inkari) writes:
- |>
- |> Shell scripts are not executed right on my 386BSD systems. Exec()
- |> results in cannot execute error and if I try to execute a script from
- |> C-Shell, the shell tryes to interpret the commands resulting in syntax
- |> errors etc. Whats the matter and how to fix it ?
-
- 1) Install the patch in the patchkit that fixes this, and rebuild the
- kernel (it modifies kern_exec.c).
- 2) Use ":" instead of "#!/bin/sh" as the first line. This works in the
- default exec() call.
-
-
- 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
- -------------------------------------------------------------------------------
-