The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Grant Taylor <gtaylor@tnetconsulting.net>,
	The Unix Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Question about BSD disklabel history
Date: Tue, 2 Jan 2024 15:30:25 -0500	[thread overview]
Message-ID: <CAEoi9W7Hz+=1kqAGCUpgiQwQtr_gM9SdH3nuFP4rUMEztn+_8g@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W4CU0OpD1JJf45Sk83yki60m-04t6Kg7jEsSKJX+Y762g@mail.gmail.com>

On Tue, Jan 2, 2024 at 2:50 PM Dan Cross <crossd@gmail.com> wrote:
> On Tue, Jan 2, 2024 at 2:00 PM Warner Losh <imp@bsdimp.com> wrote:
> > [snip]
> > Yea, I have a memory of the Sun 3 (68k) machines having a different ROM than the Sun 4 (sparc) machines in the late 80s/early 90s with similar interfaces, but the Sun 3's being simpler. Maybe I just worked with older Sun 3's that didn't have a newer OpenFirmware.
>
> Sun 3/50 and Sun 3/60 definitely had a different PROM arrangement than
> SPARCstations. However, I have a vague memory that the Sun 3/80 used
> OpenFirmware. The 3/80 (and similar Sun-3x machines introduced at the
> same time) would have been among the last, if not the last,
> MC68k-based Sun3 machine. I may be wrong, though; it's been a while.
> Regardless, I vaguely remember the "ok" prompt on a 3/80.

Hmm: correcting myself here. I can find no evidence that the 3/80 used
OBP, but I can find documentation to the contrary (mostly in the form
of documentation on how to rewrite the HostID when the NVRAM battery
fails...Gah, the things one not only forgets but actively blots out of
one's memory). It seems likely that Sun never shipped OF on 68k.

        - Dan C.

  parent reply	other threads:[~2024-01-02 20:31 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 17:30 [TUHS] " Grant Taylor via TUHS
2023-12-31 17:38 ` [TUHS] " arnold
2023-12-31 20:07   ` Warner Losh
2024-01-01  0:13     ` Bakul Shah
2023-12-31 20:27   ` Phil Budne
2023-12-31 21:02     ` Warner Losh
2024-01-01  0:26   ` Grant Taylor via TUHS
2024-01-01  2:22     ` Warner Losh
2024-01-01  3:24       ` Grant Taylor via TUHS
2023-12-31 21:31 ` Clem Cole
2023-12-31 22:07   ` Warner Losh
2024-01-01 16:00     ` Clem Cole
2024-01-02 18:49       ` Warner Losh
2024-01-02 19:30         ` Chet Ramey
2024-01-02 20:07           ` Clem Cole
2024-01-02 19:50         ` Dan Cross
2024-01-02 19:55           ` Jim Capp
2024-01-02 20:11             ` Dan Cross
2024-01-02 20:30           ` Dan Cross [this message]
2024-01-02 20:50             ` Clem Cole
2024-01-02 21:04               ` Dan Cross
2023-12-31 22:46   ` G. Branden Robinson
2023-12-31 23:06     ` Larry McVoy
2023-12-31 23:37       ` Al Kossow
2023-12-31 23:41       ` Alec Muffett
2024-01-02 20:48       ` Dan Cross
2024-01-02 21:17         ` John Cowan
2024-01-03  3:33         ` Theodore Ts'o
2024-01-03  3:57           ` Warner Losh
2024-01-03  4:03             ` Warner Losh
2024-01-03  4:30             ` Theodore Ts'o
2024-01-03  5:10               ` Warner Losh
2024-01-03 15:56                 ` Dan Cross
2024-01-03 16:37                   ` Theodore Ts'o
2024-01-03 16:41                     ` Dan Cross
2024-01-04  8:42                     ` arnold
2024-01-04 18:26                       ` Kevin Bowling
2024-01-03 14:39           ` Dan Cross
2023-12-31 23:08     ` Phil Budne
2023-12-31 23:37       ` G. Branden Robinson
2023-12-31 23:59         ` Warner Losh
2023-12-31 23:50     ` G. Branden Robinson
2024-01-01  0:09       ` Al Kossow
2023-12-31 21:55 Norman Wilson

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='CAEoi9W7Hz+=1kqAGCUpgiQwQtr_gM9SdH3nuFP4rUMEztn+_8g@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=gtaylor@tnetconsulting.net \
    --cc=imp@bsdimp.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).