From: ron minnich <rminnich@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Which years saw the introduction of (1) #! and (2) symbolic links
Date: Mon, 28 Dec 2020 21:03:31 -0800 [thread overview]
Message-ID: <CAP6exY+EZONYy5_o1yqaGmx1_E3k=kfL_ew8mPSNkwp-3uYgQA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2P8jcWbW2Rkju_SBcn5_+7QKeX72a5JaWTQt+8kuurAYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
reason I asked was my memory was #! in 1978 or so. But that's now sounding
like I compressed time a bit.
On Mon, Dec 28, 2020 at 6:08 PM Clem Cole <clemc@ccc.com> wrote:
> FYI: Dennis did symlinks before Joy did and it was 4.1a where they first
> show up in the BSD stream
> As for shebang, the idiom was recognized by the shell in user space in 1.0
> BSD, when the precursor to cshell (the Berkeley shell) was released - but
> it took a while to make it into the kernel as recognized look-a-side to be
> more automatic. My >>memory<< is we had it in the 2BSD release, but it
> might not have been added until 3BSD - look at the exec.c code in the BSD
> kernels which frankly I'm too lazy tonight to do myself.
> ᐧ
>
> On Mon, Dec 28, 2020 at 8:11 PM Ron Natalie <ron@ronnatalie.com> wrote:
>
>> Symlinks came out in 4.1BSD (1981), I think.
>> #! came out in 4. (1980
>> )
>> ------ Original Message ------
>> From: "ron minnich" <rminnich@gmail.com>
>> To: "TUHS main list" <tuhs@minnie.tuhs.org>
>> Sent: 12/28/2020 7:30:47 PM
>> Subject: [TUHS] Which years saw the introduction of (1) #! and (2)
>> symbolic links
>>
>> >I think I remember but want to ask the experts.
>>
>>
[-- Attachment #2: Type: text/html, Size: 2387 bytes --]
next prev parent reply other threads:[~2020-12-29 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 0:30 ron minnich
2020-12-29 1:04 ` Ron Natalie
2020-12-29 2:07 ` Clem Cole
2020-12-29 5:03 ` ron minnich [this message]
2020-12-30 17:15 ` Clem Cole
2020-12-29 1:41 ` Jeremy C. Reed
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='CAP6exY+EZONYy5_o1yqaGmx1_E3k=kfL_ew8mPSNkwp-3uYgQA@mail.gmail.com' \
--to=rminnich@gmail.com \
--cc=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.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).