Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site meccts.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!stolaf!umn-cs!mmm!rosevax!dicomed!meccts!ahby From: ahby@meccts.UUCP (Shane P. McCarron) Newsgroups: net.sources.bugs Subject: Re: Could we have a standard "shar" file format? Message-ID: <226@meccts.UUCP> Date: Tue, 17-Sep-85 22:03:58 EDT Article-I.D.: meccts.226 Posted: Tue Sep 17 22:03:58 1985 Date-Received: Fri, 20-Sep-85 06:43:58 EDT References: <396@persci.UUCP> Reply-To: ahby@meccts.UUCP (Shane P. McCarron) Organization: MECC Technical Services, St.Paul, MN Lines: 18 Summary: In article <396@persci.UUCP> bill@persci.UUCP writes: >it looks for a line that starts with: > #!/bin/sh >or something like that. It does *NOT* work with shar files that start with >a colon in column 1 of the first line! On our Sys III Plexus, csh will attempt to execute any shell that has a '#' at the beginning of the first line. I assume that some other systems have a similar anomaly. However, starting the first line with a ':' will eliminate this problem. That is why some scripts generate a colon in the first line. -- Shane P. McCarron Minnesota Educational Computing Corporation - Technical Services UUCP ihnp4!dicomed!meccts!ahby