From: ron minnich <rminnich@gmail.com>
To: cmhanson@eschatologist.net
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Unix APIs: elegant or not?
Date: Sun, 4 Nov 2018 07:34:03 -0800 [thread overview]
Message-ID: <CAP6exYLvcAeR1Mb3A2GcEo+A5QH0zjG8SUR22pHWf4etDtvtoA@mail.gmail.com> (raw)
In-Reply-To: <9AD89116-0552-440F-A251-1E93AA150B93@eschatologist.net>
On Sun, Nov 4, 2018 at 4:00 AM Chris Hanson <cmhanson@eschatologist.net> wrote:
> This was broken from the start though, and always really meant everything looks like a file *descriptor*, not a path in the filesystem.
OK, I only got into this game in 1976, and a lot had happened in Unix by then,
and maybe you saw some earlier stuff. But certainly in 1976, as
compared to the other 4 PDP-11 operating systems I was using,
the fact that resources had names visible to every program was very
important to us. On the competitor systems the naming would be built
into individual programs,
e.g. PIP or (non-PDP11) the MPE fcopy program, one of the few programs
on that system where you could name, e.g., the tape drive on your
terminal.
Being able to use a path name for resources was a very big deal for us
at the time. And we didn't say file descriptors, we said names.
Hence, I rate your comment as "interesting if true" but I see no
evidence to support it.
ron
next prev parent reply other threads:[~2018-11-04 16:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 4:38 Warren Toomey
2018-10-31 15:47 ` Paul Winalski
2018-10-31 17:22 ` Clem Cole
2018-10-31 19:33 ` Lawrence Stewart
2018-10-31 20:57 ` G. Branden Robinson
2018-10-31 21:31 ` Dave Horsfall
2018-11-01 7:42 ` Pierre DAVID
2018-11-01 10:20 ` Dave Horsfall
2018-11-01 12:57 ` Clem Cole
2018-11-01 14:19 ` ron minnich
2018-11-01 14:41 ` Clem Cole
2018-11-01 16:43 ` Warner Losh
2018-11-01 16:48 ` ron minnich
2018-11-01 16:56 ` Warner Losh
2018-11-02 5:24 ` Bakul Shah
2018-11-04 10:53 ` Chris Hanson
2018-11-04 15:34 ` ron minnich [this message]
2018-11-04 17:06 ` Warner Losh
2018-11-04 20:00 ` ron minnich
2018-11-04 18:52 ` Bakul Shah
2018-11-04 10:49 ` Chris Hanson
2018-11-04 12:28 ` arnold
2018-11-04 21:34 ` Chris Hanson
2018-11-05 14:11 ` Donald ODona
2018-11-04 13:35 ` Warner Losh
2018-11-04 19:47 ` Dave Horsfall
2018-11-01 15:39 Noel Chiappa
2018-11-04 22:29 Theodore Y. Ts'o
2018-11-04 22:37 Noel Chiappa
2018-11-05 4:04 ` 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=CAP6exYLvcAeR1Mb3A2GcEo+A5QH0zjG8SUR22pHWf4etDtvtoA@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=cmhanson@eschatologist.net \
--cc=tuhs@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).