The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Earl Baugh <earl.baugh@gmail.com>
To: Al Kossow <aek@bitsavers.org>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] SUN (Stanford University Network) was PC Unix
Date: Fri, 9 Apr 2021 21:30:46 -0400	[thread overview]
Message-ID: <10F4818F-9DF2-40A5-A67A-605CA9B8D8DF@gmail.com> (raw)
In-Reply-To: <731c6353-1adb-f66c-6ff4-d89b257fd0eb@bitsavers.org>

Thanks for clarifying that!! I should have said “I believe it might not have had. I wasn’t quite sure what the problem was which caused the issue.  I had in my notes that something would prevent implementing virtual memory ( and that the person thought it might be a missing MMU ).  I should have relayed that more accurately.    Always appreciate clarifying and better info.  

I’ll also add the Ubisoft note.  I have some copies of a few of the earlier releases but I don’t think the tar files have a company name on them.   I’ve not unpacked them yet. 

Does anyone have any source that has a better “how many Sun 1’s were made” number?  I have a few sources that say “maybe 300” and “maybe 400” and “maybe 600”.   Obviously that’s not very exact. :-) The serial numbers bounce around ( from the units I’ve identified ) and it’s not clear they started at 1... some info says there was some arbitrary number that they started at.  And that chunks of numbers might have been skipped.  I’ve just not been able to find a more definitive or more trustworthy source. 

( though I haven’t seen if old stock info filings might have more info - but I’m thinking those would have been after the fact, time wise )

Earl 

Sent from my iPhone

> On Apr 9, 2021, at 4:08 PM, Al Kossow <aek@bitsavers.org> wrote:
> 
> On 4/9/21 1:02 PM, Earl Baugh wrote:
> 
>> And the original CPU boards didn’t have an MMU.
> 
> wrong
> 
> They didn't have a 68010 capable of recovering from page faults
> 
> The original unix shipped on Sun 1's was a Unisoft port. The same
> one sold by several other companies that sold the original Sun CPU
> design.l
> 

  parent reply	other threads:[~2021-04-10  1:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  5:31 Jason Stevens
2021-04-09  6:13 ` Jon Steinhart
2021-04-09  6:34   ` Rich Morin
2021-04-09 15:08     ` Clem Cole
2021-04-09  7:22 ` Lars Brinkhoff
2021-04-09  9:29   ` Lars Brinkhoff
2021-04-09 17:02   ` Al Kossow
2021-04-09 18:37     ` Lars Brinkhoff
2021-04-09 10:12 ` emanuel stiebler
2021-04-09 11:13   ` U'll Be King of the Stars
2021-04-09 17:22     ` Rob Gowin
2021-04-09 20:16       ` joe mcguckin
2021-04-10  2:22     ` Dave Horsfall
2021-04-09 14:08 ` Tom Lyon
2021-04-09 14:23   ` Jim Geist
2021-04-09 15:11   ` Clem Cole
2021-04-09 20:02     ` Earl Baugh
2021-04-09 20:08       ` Al Kossow
2021-04-09 20:46         ` Clem Cole
2021-04-10  1:30         ` Earl Baugh [this message]
2021-04-09 14:41 Noel Chiappa
2021-04-09 15:18 ` Clem Cole
2021-04-09 15:34 Paul Ruizendaal via TUHS
2021-04-09 17:01 ` Dan Cross
2021-04-09 17:20   ` Lawrence Stewart
2021-04-09 18:32     ` Jon Steinhart
2021-04-09 22:28       ` Warner Losh
2021-04-10  3:16 ` Dave Horsfall
2021-04-10 12:06   ` David Arnold
2021-04-13 21:57     ` Dave Horsfall
2021-04-13 22:30       ` Bakul Shah
2021-04-15  5:01   ` Robert Brockway
2021-04-16  1:17     ` Brad Spencer
2021-04-10  2:41 Jason Stevens

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=10F4818F-9DF2-40A5-A67A-605CA9B8D8DF@gmail.com \
    --to=earl.baugh@gmail.com \
    --cc=aek@bitsavers.org \
    --cc=tuhs@minnie.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).