The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tih@hamartun.priv.no (Tom Ivar Helbekkmo)
Subject: [TUHS] Why BSD didn't catch on more, and Linux did
Date: Wed, 07 Feb 2018 18:52:23 +0100	[thread overview]
Message-ID: <m2inb8bsbs.fsf@thuvia.hamartun.priv.no> (raw)
In-Reply-To: <20180207151347.GA29650@thunk.org> (Theodore Ts'o's message of "Wed, 7 Feb 2018 10:13:47 -0500")

Theodore Ts'o <tytso at mit.edu> writes:

> Indeed.  From http://www.freebsddiary.org/linux.php, "Why is Linux
> Successful?  An Opinion", published at Uniforum NZ in April 1999:
>
>     "Linux has always had a pragmatic view of hardware, whist the BSDs
>     carried a purist view. When I got my first 386 I had MFM style
>     disk drives. At that the BSDs only supported SCSI.  [...]

I wonder when that was...  *My* first 386 was the one I ran 386bsd on,
and later, when it came into existence, NetBSD.  It had good old ST506
type disk drives (20MB MFM drives, but I formatted them RLL to get 30MB
out of them).  Managed to get four such drives onto it, actually, by
modifying the driver to support multiple controllers, and then rewiring
one controller to hook it to a different interrupt line on the ISA bus.

See item 5.1.7 here: http://www.csci.csusb.edu/dick/doc/386bsd.FAQ.txt

-tih
-- 
Most people who graduate with CS degrees don't understand the significance
of Lisp.  Lisp is the most important idea in computer science.  --Alan Kay
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180207/3cee7d6f/attachment.sig>


  parent reply	other threads:[~2018-02-07 17:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 22:13 Dan Stromberg
2018-02-06 22:38 ` Clem Cole
2018-02-06 22:44 ` Warner Losh
2018-02-06 22:59   ` Pete Wright
2018-02-06 22:59 ` Derek Fawcus
2018-02-07  1:14   ` Dave Horsfall
2018-02-06 23:02 ` Theodore Ts'o
2018-02-07  0:22   ` Andy Kosela
2018-02-07  1:02     ` Robert Brockway
2018-02-07  3:47       ` George Michaelson
2018-02-07  1:29   ` Clem Cole
2018-02-07 15:13     ` Theodore Ts'o
2018-02-07 16:59       ` Jon Forrest
2018-02-07 17:27       ` Clem Cole
2018-02-07 19:21         ` Dan Cross
2018-02-07 21:24           ` Clem Cole
2018-02-07 19:31         ` Nemo
2018-02-07 19:49         ` Theodore Ts'o
2018-02-07 19:53           ` Dan Cross
2018-02-07 20:26             ` Theodore Ts'o
2018-02-07 21:06               ` Clem Cole
2018-02-07 21:31               ` Clem Cole
2018-02-07 17:52       ` Tom Ivar Helbekkmo [this message]
2018-02-07  8:04   ` Tom Ivar Helbekkmo
2018-02-07  8:51   ` Arrigo Triulzi
2018-02-07  8:27 ` Wesley Parish
2018-02-07  8:39   ` emanuel stiebler
2018-02-07 10:44     ` Arrigo Triulzi
2018-02-07 13:14   ` Chet Ramey
2018-02-07 14:42   ` Nemo
2018-02-09  2:53     ` Wesley Parish
2018-02-11 20:22       ` Derek Fawcus
2018-02-12  0:31         ` Robert Brockway

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=m2inb8bsbs.fsf@thuvia.hamartun.priv.no \
    --to=tih@hamartun.priv.no \
    /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).