From: tuhs@ducky.net (Mike Haertel)
Subject: [TUHS] AT+T UNIX PC Information needed
Date: Sat, 18 Feb 2006 07:44:40 -0800 [thread overview]
Message-ID: <200602181544.k1IFieBg081209@ducky.net> (raw)
>I think it's System V Release 3.0 or thereabout
Basically the same machine was also sold as the 3b1; the difference
between the 7300 and the 3b1 is that the 3b1 has room for a taller
hard disk drive.
I think the OS would best be characterized as SVR2 with the addition
of the 4.1bsd VM system ("real" SVR2 had no demand paged VM) and the
further addition of its own unique approach to shared libraries.
It's definitely not SVR3; no "STREAMS".
next reply other threads:[~2006-02-18 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 15:44 Mike Haertel [this message]
2006-02-18 16:48 ` Michael Davidson
2006-02-20 10:03 ` Duncan Anderson
-- strict thread matches above, loose matches on Subject: below --
2006-02-21 3:46 Brian S Walden
2006-02-21 4:52 ` Corey Lindsly
2006-02-21 8:58 ` Duncan Anderson
2006-02-21 8:56 ` Duncan Anderson
2006-02-21 17:00 ` Sven Mascheck
2006-02-18 8:48 Duncan Anderson
2006-02-18 14:34 ` Brantley Coile
2006-02-18 15:25 ` Duncan Anderson
2006-02-18 15:32 ` Corey Lindsly
2006-02-18 20:19 ` Robert Tillyard
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=200602181544.k1IFieBg081209@ducky.net \
--to=tuhs@ducky.net \
/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).