The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] Unix v6 problem with /tmp
Date: Wed, 27 Jul 2016 17:18:03 -0400	[thread overview]
Message-ID: <1469654287.23225.for-standards-violators@oclsc.org> (raw)

Clem Cole:

  Also to be fair, Dennis did symlinks before 4.2.   They were part of the V8
  I believe.

=======

I'm pretty sure they came from Berkeley nevertheless.  I don't know
the exact order of events, but the 8th Edition kernel was essentially
that from one of the later 4.1x BSDs, hacked in 1127 to remove sockets
and FFS (were they even there yet), then to add Dennis's stream I/O
system, Tom Killian's original /proc, and Peter Weinberger's neta
network-file-system client.  Perhaps a few other hooks as well.
Symlinks were already there, and although we made some limited careful
use of them, made nobody very happy because they made such a big
irregular lump in so many things: file system no longer a tree,
difference between stat and lstat, and so on.

One thing 8/e did differently from Berkeley was that ls by default
hid symlinks rather than trotting them out proudly.  If f was a
symlink, ls -l f showed the state of the target file, not that of
the link; one had to do ls -lL f to see the symlink itself.
That reflected a general feeling that symlinks should be neither
seen nor heard unless necessary.

Norman Wilson
Toronto ON


             reply	other threads:[~2016-07-27 21:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 21:18 Norman Wilson [this message]
2016-07-28  0:47 ` Clem cole
  -- strict thread matches above, loose matches on Subject: below --
2016-07-27 20:41 Norman Wilson
2016-07-27 20:28 Mark Longridge
2016-07-27 20:31 ` William Pechter
2016-07-27 20:57   ` Clem Cole
2016-07-27 21:01     ` Clem Cole
2016-07-27 21:10     ` William Pechter
2016-07-28  0:49       ` Clem cole
2016-07-28  1:03         ` William Pechter
2016-07-28  1:03       ` Clem cole

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=1469654287.23225.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).