The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Henry Bent <henry.r.bent@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] SunOS 4 in 2024
Date: Wed, 13 Mar 2024 16:12:41 -0400	[thread overview]
Message-ID: <CAEdTPBerG84uCpotSk1XqfRZBEJcKCL_OWLhDsNe11M7uFDNFg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 533 bytes --]

Hi all,

I've been working quite a bit recently with SunOS 4 on a SPARCstation 5,
seeing what I can coax out of it in terms of building and supporting a
modern computing environment.  I know that TUHS isn't really the right
place for this, but can someone point me to somewhere that is?  I've made
significant progress in some areas and spent a lot of cycles to get there -
for instance, I have GCC 3.4.6 up and running - so I'd like to contribute
to a community if one exists.  Is there a modern equivalent of sun-managers?

-Henry

[-- Attachment #2: Type: text/html, Size: 637 bytes --]

             reply	other threads:[~2024-03-13 20:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 20:12 Henry Bent [this message]
2024-03-13 20:23 ` [TUHS] " Erik E. Fair
2024-03-13 20:49 ` 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=CAEdTPBerG84uCpotSk1XqfRZBEJcKCL_OWLhDsNe11M7uFDNFg@mail.gmail.com \
    --to=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).