The Unix Heritage Society mailing list
 help / color / Atom feed
From: arnold@skeeve.com
To: tuhs@minnie.tuhs.org, egbegb2@gmail.com
Subject: Re: [TUHS] Question: stdio - Who invented and ...
Date: Mon, 23 Mar 2020 04:32:34 -0600
Message-ID: <202003231032.02NAWY4v022713@freefriends.org> (raw)
In-Reply-To: <CAHTagfFDzaeXXom=oAGVWXNw_ByEFfZM1qXNWJc-jDo+RLB4Tw@mail.gmail.com>

Ed Bradford <egbegb2@gmail.com> wrote:

> I've forgotten who created stdio, USG or the research group. Can any of the
> youthful BTL folks of the 1970's refresh my mind.

It was part of V7. I think DMR gets most of the credit.

> Given that stdio was invented and, in my opinion at the time, a reasonable
> and usable standard interface to IO on Unix, I am curious why no standard
> for networking was developed or proposed and discussed. Sockets just
> defined a new and very quirky IO interface for Unix based systems.
>
> Was any thought given to defining networking
> using the
>   creat/open/read/write/close/mknod/link/unlink/chmod/chown
>
> model of IO in UNIX?

Much of this has been discussed (to death) already on this list, and fairly recently, too.

At that time networking was still a research topic. The Bell Labs folks worked
on it, and this is visible in the streams stuff in V8/V9/V10 and early Plan 9,
but by that time their work was less influential on the wider Unix community.

There were efforts to integrate networking into the Unix file namespace, but
it doesn't fit overly cleanly, and such things didn't spread.

BSD networking adopted sockets from other, earlier efforts. IMHO less thought was
given to "integration with Unix ideas" as opposed to just getting something working
and usable, but that's just my opinion based on hindsight.

BSD sockets spread because BSD was in the right place at the right time: it ran
on the Vax, it also provided paging. Straight research Unix did not support
the vax at the time, and people were looking to move to the 32 bit environment.
All that plus csh with its interactive features (history, job control) and the
vi screen editor (with ed inside it), made BSD (and thus its networking) very
popular.

Again, all of this is my 2 cents, and there's much more to be found in
the list archives.

HTH,

Arnold

  reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 10:18 Ed Bradford
2020-03-23 10:32 ` arnold [this message]
2020-03-23 13:46   ` Clem Cole
2020-03-23 13:59     ` arnold
2020-03-23 14:24       ` Jaap Akkerhuis
2020-03-23 14:45         ` Clem Cole
2020-03-23 18:47         ` Richard Salz
2020-03-23 19:22           ` Jaap Akkerhuis
2020-03-23 21:38     ` Dave Horsfall
2020-03-24  2:02     ` Greg A. Woods

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=202003231032.02NAWY4v022713@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=egbegb2@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

The Unix Heritage Society mailing list

Archives are clonable: git clone --mirror http://inbox.vuxu.org/tuhs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.tuhs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git