From: "Erik E. Fair" <fair-tuhs@netbsd.org>
To: Henry Bent <henry.r.bent@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SunOS 4 in 2024
Date: Wed, 13 Mar 2024 13:23:46 -0700 [thread overview]
Message-ID: <16117.1710361426@cesium.clock.org> (raw)
In-Reply-To: <CAEdTPBerG84uCpotSk1XqfRZBEJcKCL_OWLhDsNe11M7uFDNFg@mail.gmail.com>
Henry,
I think you're going to be a whole lot happier with NetBSD or OpenBSD on 32-bit Sun SPARC hardware than trying to coax SunOS into a usable state for the modern, unfortunately rather hostile, Internet.
However, I think you're also going to want to make use of the cross-compilation tools provided, i.e., build software on [ugh] fast x86 or ARM hardware rather than wait for the old SPARCs to grind through it.
I hope you have cheap electic power service where you are - old Suns run warm and use a lot more electricity per cycle than modern processors.
The other way: emulation on modern power-efficient hardware, e.g., with qemu.
Erik
next prev parent reply other threads:[~2024-03-13 20:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 20:12 [TUHS] " Henry Bent
2024-03-13 20:23 ` Erik E. Fair [this message]
2024-03-13 20:49 ` [TUHS] " Kevin Bowling
2024-03-13 20:59 ` Henry Bent
2024-03-13 23:28 ` Alexis
2024-03-13 23:39 ` Henry Bent
2024-03-14 0:44 ` Alexis
2024-03-14 13:49 ` Theodore Ts'o
2024-03-13 21:27 ` Will Senn
2024-03-13 21:31 ` Henry Bent
[not found] ` <E4752C7E-2799-4978-B221-9DB86F872C6A@baugh.org>
2024-03-13 21:56 ` Henry Bent
[not found] ` <F3E036CF-277C-4B2B-9335-D42F5ABAFD6B@baugh.org>
2024-03-13 22:09 ` Henry Bent
[not found] ` <54A3AD3C-1296-41EB-8D7B-E940AF2740CD@baugh.org>
2024-03-13 22:23 ` Henry Bent
2024-03-14 0:40 ` Alan Coopersmith
2024-03-14 0:51 ` segaloco via TUHS
2024-03-14 20:23 ` Earl Baugh
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=16117.1710361426@cesium.clock.org \
--to=fair-tuhs@netbsd.org \
--cc=henry.r.bent@gmail.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).