From: mascheck@in-ulm.de (Sven Mascheck)
Subject: [TUHS] History of #! interpretation in Unix
Date: Wed, 19 Jan 2011 21:35:06 +0100 [thread overview]
Message-ID: <20110119203506.GB12678@lisa.in-ulm.de> (raw)
In-Reply-To: <4D366439.8020808@laposte.net>
Cyrille Lefevre wrote:
> yet another reference but more in the spirit of what csh does, it only
> checks for a simple hash (#), no explaim mark (!), and is enclosed in
> UCB_SCRIPT define.
>
> http://minnie.tuhs.org/cgi-bin/utree.pl?file=2.9BSD/usr/src/sys/sys/sys1.c
Perhaps you missed the ! in the macro?
#define SCRMAG '#!'
> 2.11 BSD seems to have an enhanced version of this feature in the sense
> where the shell path may be followed by some arguments (i.e.: /bin/sh -x)
Yes, #! originally had not implemented arguments at all (this even applies
to 386BSD). Arguments ("all in one") came with 4.2BSD and later, variations
appeared like splitting up into argv[] or delivering only the "first" argument.
--
http://www.in-ulm.de/~mascheck/various/shebang/#results
next prev parent reply other threads:[~2011-01-19 20:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 8:43 Warren Toomey
2011-01-16 9:55 ` John Cowan
2011-01-16 13:20 ` Sven Mascheck
2011-01-16 17:17 ` John Cowan
2011-01-16 19:19 ` Sven Mascheck
2011-01-16 20:17 ` John Cowan
2011-01-16 20:42 ` Larry McVoy
2011-01-16 21:08 ` Sven Mascheck
2011-01-16 21:37 ` John Cowan
2011-01-17 16:35 ` Warner Losh
2011-01-17 20:47 ` John Cowan
2011-01-17 10:09 ` Tim Bradshaw
2011-01-16 10:53 ` Wilko Bulte
2011-01-17 16:25 ` Warner Losh
2011-01-17 19:02 ` Jeremy C. Reed
2011-01-17 20:51 ` John Cowan
2011-01-17 22:41 ` Jeremy C. Reed
2011-01-17 20:58 ` Sven Mascheck
2011-01-19 4:10 ` Cyrille Lefevre
2011-01-19 20:35 ` Sven Mascheck [this message]
2011-01-20 4:09 ` Cyrille Lefevre
2011-01-28 19:38 ` Jeremy C. Reed
2011-01-30 15:05 ` Sven Mascheck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110119203506.GB12678@lisa.in-ulm.de \
--to=mascheck@in-ulm.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).