From: Henry Bent <henry.r.bent@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] The origin of /home
Date: Thu, 27 Sep 2018 18:18:51 -0400 [thread overview]
Message-ID: <CAEdTPBc=7xMN=T943Y765ko25R_OGb0CStkBO_JJ+OQryaM-iA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2O_keNWjS+YDgYdMt1Gsq-Qbk3NFCJHTzZ6=DkzGOizXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On Thu, 27 Sep 2018 at 18:06, Clem Cole <clemc@ccc.com> wrote:
>
> BTW: A thing to remember is that symbolic links are not a wide spread when
> all of this was going on in the early 1980s, so they really did not have a
> lot to do with the /home idea. In the case of symbolic links, Dennis had
> created them as part of V8, but 4.1BSD and System III (PWB 3.0) did not
> have the idea yet. BSD 4.2 would later get them as part of FFS, but I
> don’t remember if 4.1c did (the kernel source was not in Warren’s browsable
> archive so I could not check).
>
4.1c did indeed have symlinks; the "4.1c.1" source on the CSRG CD set has
the code for them. lib/libc/sys/symlink.c revision 4.1 is dated 82/12/04,
so that's about the time they went in.
-Henry
> ᐧ
>
[-- Attachment #2: Type: text/html, Size: 1670 bytes --]
next prev parent reply other threads:[~2018-09-27 22:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 12:08 Cág
2018-09-27 12:30 ` Alec Muffett
2018-09-27 12:58 ` Donald ODona
2018-09-27 13:54 ` John P. Linderman
2018-09-27 14:09 ` Ronald Natalie
2018-09-27 14:18 ` Jon Forrest
2018-09-27 14:28 ` Arrigo Triulzi
2018-09-27 15:36 ` Jon Forrest
2018-09-27 15:54 ` Arrigo Triulzi
2018-09-27 18:49 ` Jon Forrest
2018-09-28 0:50 ` Theodore Y. Ts'o
2018-10-01 1:52 ` Lyndon Nerenberg
2018-10-10 2:38 ` Dave Horsfall
2018-10-10 3:07 ` Grant Taylor via TUHS
2018-09-27 17:33 ` Donald ODona
2018-09-27 14:47 ` Dan Cross
2018-09-27 17:20 ` arnold
2018-09-27 20:42 ` Cág
2018-09-27 21:07 ` Dan Cross
2018-09-27 22:04 ` Clem Cole
2018-09-27 22:18 ` Henry Bent [this message]
2018-09-28 8:33 ` Tony Finch
2018-09-28 18:23 ` Jeremy C. Reed
2018-09-28 16:02 ` Nemo
2018-09-28 16:15 ` Grant Taylor via TUHS
2018-09-28 17:28 ` Arthur Krewat
2018-09-28 19:38 ` Grant Taylor via TUHS
2018-09-28 19:47 ` Grant Taylor via TUHS
2018-09-28 20:30 ` Arthur Krewat
2018-09-28 20:00 ` Nemo
2018-09-28 21:07 ` Grant Taylor via TUHS
2018-09-27 14:31 Noel Chiappa
2018-09-27 15:33 Noel Chiappa
2018-09-27 20:15 ` Dan Cross
2018-09-27 23:14 Noel Chiappa
2018-09-28 5:27 ` Lars Brinkhoff
2018-09-28 2:39 Doug McIlroy
2018-10-10 14:43 Norman Wilson
2018-10-10 16:26 ` arnold
2018-10-11 19:10 ` Lyndon Nerenberg
2018-10-10 17:08 ` Grant Taylor via TUHS
2018-10-11 0:22 ` Steve Nickolas
2018-10-11 2:33 ` David Arnold
2018-10-10 15:26 Noel Chiappa
2018-10-10 15:45 ` Clem Cole
2018-10-10 15:48 ` David
2018-10-13 6:58 ` Michael Kjörling
2018-10-12 0:15 ` Dave Horsfall
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='CAEdTPBc=7xMN=T943Y765ko25R_OGb0CStkBO_JJ+OQryaM-iA@mail.gmail.com' \
--to=henry.r.bent@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).