The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] Command line post-arguments with #!
Date: Wed, 14 Dec 2011 20:46:38 -0500 (EST)	[thread overview]
Message-ID: <1323913617.13187.for-standards-violators@oclsc.org> (raw)

Sven Mascheck:

  With "original implementation (post 7th ed", I meant the undistributed
  BellLabs-internal further development of 7th, the first system ever
  to implement #!, leading to 8th ed, etc. (4BSD just incorporated this).
  Not System V or other relatives, though.

=======

Can you cite a reference?

I'm quite familiar with what went on inside the system that was
later called 8th Edition, having been on the inside at Bell Labs
starting in mid-1984.  But that was after the original research
group's general move to VAXes--they had no PDP-11s left by then,
except a few LSI-11s running special-purpose systems rather than
UNIX.  In fact the VAX kernel they had adopted, I think sometime
earlier that year, was derived from that of 4.1 BSD.  (It diverged
quite a bit from that start later, for which I am appreciably
to blame, but that has nothing to do with #!).

So if #! was implemented in an earlier kernel I don't know just
what was done.  I'd assumed it was no different; if I'm
mistaken I'd love to see just how it really was.

Alas, the person I know was on the spot and was likely to
remember just what happened in what order can no longer answer
questions ...

Norman Wilson
Toronto ON



             reply	other threads:[~2011-12-15  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15  1:46 Norman Wilson [this message]
2011-12-15  3:07 ` Sven Mascheck
  -- strict thread matches above, loose matches on Subject: below --
2011-12-14 23:57 Norman Wilson
2011-12-15  0:25 ` Sven Mascheck
2011-12-08 23:08 [TUHS] speak.c, or sometimes the bits are under your nose Warren Toomey
2011-12-12  8:13 ` Jonathan Gevaryahu
2011-12-13  3:08   ` [TUHS] Command line post-arguments with #! Random832
2011-12-14 23:36     ` 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=1323913617.13187.for-standards-violators@oclsc.org \
    --to=norman@oclsc.org \
    /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).