From: "Ron Natalie" <ron@ronnatalie.com>
To: "ron minnich" <rminnich@gmail.com>,
"TUHS main list" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Which years saw the introduction of (1) #! and (2) symbolic links
Date: Tue, 29 Dec 2020 01:04:54 +0000 [thread overview]
Message-ID: <em19b12615-119c-4bef-af40-477ea3c9e844@r1.local> (raw)
In-Reply-To: <CAP6exYJMNUuU=EFo659=SEj-coD2eo5_yNGeKzAojDqp1tKObQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2020-12-29 1:11 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 [this message]
2020-12-29 2:07 ` Clem Cole
2020-12-29 5:03 ` ron minnich
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=em19b12615-119c-4bef-af40-477ea3c9e844@r1.local \
--to=ron@ronnatalie.com \
--cc=rminnich@gmail.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).