The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] OT: critical Intel design flaw
Date: Thu, 4 Jan 2018 14:16:46 -0700	[thread overview]
Message-ID: <CANCZdfqTOYata4LwqsSe4oC2sU_Sd0gitx3DeGikUe78tkLFhQ@mail.gmail.com> (raw)
In-Reply-To: <20180104205631.GL23371@thunk.org>

On Thu, Jan 4, 2018 at 1:56 PM, Theodore Ts'o <tytso at mit.edu> wrote:

> On Thu, Jan 04, 2018 at 10:29:59AM -0800, Bakul Shah wrote:
> > 16MB of memory) and installed 386bsd. I also played with
> > linux-0.11 but I recall reading something about Linus using
> > SysV as a reference and that was the end of my interest in
> > linux!
>
> As far as I know that was never true.  We used used POSIX as a
> reference mainly because it was more easily available as a
> specification.  So that meant that we implemented termios support, and
> not termio, or the BSD variant.  The networking layer was all BSD
> sockets; we certainly never implemented STREAMS, for goodness sake!  :-)
>

There was a natural bias towards SysV interfaces, which highlighted the
differences with BSD interfaces in some areas and may have left that
impression...

Linus certainly had access to SysV or SysV derived systems, but there
wasn't even a whisper at the time he copied code from there. And the few
maybe less than completely legit versions of SysV that are now available
bear this out: they look nothing at all like the 0.11-linux tree.

Thank goodness for the sockets thing... Even though it's a horrible
interface, it was less horrible than STREAMS...

Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180104/c29cb5ef/attachment.html>


  reply	other threads:[~2018-01-04 21:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 13:43 Noel Chiappa
2018-01-03 14:26 ` Clem Cole
2018-01-03 17:28   ` Bakul Shah
2018-01-03 17:46     ` ron minnich
2018-01-03 18:28       ` Bakul Shah
2018-01-03 18:27     ` Clem Cole
2018-01-03 18:39       ` Forrest, Jon
2018-01-03 18:50         ` ron minnich
2018-01-03 19:56       ` Paul Winalski
2018-01-03 20:24       ` Bakul Shah
2018-01-03 23:40       ` Theodore Ts'o
2018-01-04  0:51         ` Larry McVoy
2018-01-04  2:13           ` Bakul Shah
2018-01-04  2:26             ` Larry McVoy
2018-01-04  3:31               ` Bakul Shah
2018-01-04  2:09         ` Arthur Krewat
2018-01-04  3:21           ` Dan Cross
2018-01-04 17:42             ` Arthur Krewat
2018-01-04 11:53         ` Harald Arnesen
2018-01-04 14:03           ` Clem Cole
2018-01-04 15:54             ` Larry McVoy
2018-01-04 16:45             ` Theodore Ts'o
2018-01-04 17:10               ` Andy Kosela
2018-01-04 17:17               ` Larry McVoy
2018-01-04 18:29                 ` Bakul Shah
2018-01-04 18:50                   ` Larry McVoy
2018-01-04 20:52                     ` Warner Losh
2018-01-04 20:56                       ` Bakul Shah
2018-01-04 20:56                   ` Theodore Ts'o
2018-01-04 21:16                     ` Warner Losh [this message]
2018-01-04 22:55                       ` Andy Kosela
2018-01-05 14:27                         ` Clem Cole
2018-01-04 21:17                     ` Bakul Shah
2018-01-04 17:20               ` Tom Ivar Helbekkmo
2018-01-04 17:28                 ` Warner Losh
2018-01-03 17:07 ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2018-01-03 17:06 Norman Wilson
2018-01-03  7:53 Andy Kosela
2018-01-03 11:57 ` Ron Natalie
2018-01-03 14:22   ` Random832

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=CANCZdfqTOYata4LwqsSe4oC2sU_Sd0gitx3DeGikUe78tkLFhQ@mail.gmail.com \
    --to=imp@bsdimp.com \
    /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).