The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] OT: critical Intel design flaw
Date: Thu, 4 Jan 2018 13:17:40 -0800	[thread overview]
Message-ID: <4DA9612F-4459-4026-9E1C-23F32BCCFB6A@bitblocks.com> (raw)
In-Reply-To: <20180104205631.GL23371@thunk.org>

On Jan 4, 2018, at 12: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!  :-)

I remember sysV coming up in connection with Linux....
Ok, found it:

https://groups.google.com/forum/#!searchin/comp.os.minix/linus$201991%7Csort:date/comp.os.minix/3dSbdErXdUc/uoBUzk9NEEsJ

1. WHAT IS LINUX 0.11
  LINUX 0.11 is a freely distributable UNIX clone.  It implements a
subset of System V and POSIX functionality.
...
2. LINUX features
  - System call compatible with a subset of System V and POSIX
...
8. FUTURE PLANS
...
     - STREAMS

The only mention of BSD is WRT pmake.


  parent reply	other threads:[~2018-01-04 21:17 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
2018-01-04 22:55                       ` Andy Kosela
2018-01-05 14:27                         ` Clem Cole
2018-01-04 21:17                     ` Bakul Shah [this message]
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=4DA9612F-4459-4026-9E1C-23F32BCCFB6A@bitblocks.com \
    --to=bakul@bitblocks.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).