*BSD News Article 10138


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA7271 ; Mon, 18 Jan 93 10:50:58 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!csus.edu!netcom.com!hasty
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: why isn't #! /bin/sh working for me on 386BSD?
Message-ID: <1993Jan20.040631.19888@netcom.com>
Keywords: 386bsd
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
References: <1jhmnkINNl5v@usenet.INS.CWRU.Edu> <1993Jan19.215030.22775@cunews.carleton.ca>
Date: Wed, 20 Jan 1993 04:06:31 GMT
Lines: 25

In article <1993Jan19.215030.22775@cunews.carleton.ca> watpod77@alfred.carleton.ca (Andrew Cornwall) writes:
>In article <1jhmnkINNl5v@usenet.INS.CWRU.Edu> au141@cleveland.Freenet.Edu (Amber M. Spillers) writes:
>>   correct me if I am wrong butthe line 
>>
>>#! /bin/sh
>>
>>  at the beginning of a shell script (the first line) is suposed to

You need the patches for kern_execve.c :-)

They are part of Terry's patch kit or you can go out to ref.tfs.com
and grab the patched kern_execve.c

In addition to the patches distributed, there was a patch to kern_execve.c
to allow it work better with tk ...

Hope this helps,
Amancio


-- 
This message brought to you by the letters X and S and the number 3
Amancio Hasty           |  
Home: (415) 495-3046    |  ftp-site depository of all my work:
e-mail hasty@netcom.com	|  sunvis.rtpnc.epa.gov:/pub/386bsd/incoming