From: Chet Ramey <chet.ramey@case.edu>
To: "Greg 'groggy' Lehey" <grog@lemis.com>,
emanuel stiebler <emu@e-bbes.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] BSD/386 (was: Old 386 Unix Versions, was: Re: PCC for the i386)
Date: Thu, 18 Jul 2019 11:01:06 -0400 [thread overview]
Message-ID: <714626ee-af90-4806-7f24-339d842a220d@case.edu> (raw)
In-Reply-To: <20190718000425.GB73488@eureka.lemis.com>
[-- Attachment #1.1: Type: text/plain, Size: 781 bytes --]
On 7/17/19 8:04 PM, Greg 'groggy' Lehey wrote:
> I started using BSD/386 in mid-March 1992, a couple of days before
> Jolitz released 386BSD. In contrast to 386BSD, it was solid,
> installed easily, and cost $1000 (with source; I think there were
> cheaper binary-only options). It blew Interactive UNIX out of the
> water. This was a Beta, so I sent reports which I have published at
> http://www.lemis.com/grog/diary-mar1992.php#18
Agreed. We used BSD/386 and BSD/OS pretty heavily at Case. We ran a
significant portion of the infrastructure services on it. It was
solid.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-07-18 15:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 14:53 [TUHS] PCC for the i386 Jason Stevens
2019-07-11 15:12 ` arnold
2019-07-11 15:37 ` Clem cole
2019-07-11 15:50 ` Jason Stevens
2019-07-11 16:30 ` Clem cole
2019-07-11 16:42 ` Richard Salz
2019-07-11 16:48 ` Warner Losh
2019-07-11 17:05 ` Clem Cole
2019-07-11 19:39 ` Charles H Sauer
2019-07-12 0:14 ` Clem Cole
2019-07-11 16:50 ` A. P. Garcia
2019-07-11 16:54 ` Clem Cole
2019-07-12 3:44 ` Michael Parson
2019-07-17 7:37 ` [TUHS] Old 386 Unix Versions, was: " emanuel stiebler
2019-07-17 8:10 ` arnold
2019-07-17 9:28 ` Arrigo Triulzi
2019-07-17 10:09 ` Jason Stevens
2019-07-17 10:42 ` emanuel stiebler
2019-07-17 15:40 ` Adam Thornton
2019-07-17 18:01 ` Clem Cole
2019-07-17 12:32 ` Ben Greenfield via TUHS
2019-07-17 12:50 ` Dagobert Michelsen
2019-07-17 13:38 ` Arrigo Triulzi
2019-07-17 14:41 ` Clem Cole
2019-07-17 15:08 ` Ben Greenfield via TUHS
2019-07-17 21:09 ` Dagobert Michelsen
2019-07-18 8:56 ` Arrigo Triulzi
2019-07-17 16:04 ` William Pechter
2019-07-17 14:34 ` Clem Cole
2019-07-17 23:22 ` Bakul Shah
2019-07-18 0:04 ` Clem cole
2019-07-17 22:48 ` Chris Hanson
2019-07-18 8:39 ` Wesley Parish
2019-07-17 14:15 ` Clem Cole
2019-07-17 15:11 ` Larry McVoy
2019-07-17 15:31 ` Warner Losh
2019-07-17 15:36 ` Jason Stevens
2019-07-17 16:56 ` Larry McVoy
2019-07-24 1:04 ` Lyndon Nerenberg
2019-07-24 1:30 ` Arthur Krewat
2019-07-24 21:53 ` Kevin Bowling
2019-07-25 19:16 ` Lyndon Nerenberg
2019-07-25 19:29 ` [TUHS] AT&T 3b4000 (was Re: Old 386 Unix Versions) Kevin Bowling
2019-07-25 20:47 ` Clem Cole
2019-07-26 18:18 ` Seth J. Morabito
2019-07-26 19:24 ` Clem Cole
2019-07-18 0:04 ` [TUHS] BSD/386 (was: Old 386 Unix Versions, was: Re: PCC for the i386) Greg 'groggy' Lehey
2019-07-18 0:16 ` Richard Salz
2019-07-18 1:08 ` Greg 'groggy' Lehey
2019-07-18 15:01 ` Chet Ramey [this message]
2019-07-26 18:40 Richard Tobin
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=714626ee-af90-4806-7f24-339d842a220d@case.edu \
--to=chet.ramey@case.edu \
--cc=emu@e-bbes.com \
--cc=grog@lemis.com \
--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).