From: Henry Bent <henry.r.bent@gmail.com>
To: Kevin Bowling <kevin.bowling@kev009.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SunOS 4 in 2024
Date: Wed, 13 Mar 2024 16:59:02 -0400 [thread overview]
Message-ID: <CAEdTPBcNU8tm7OFubw_CjHGfN5RF5X+sQP4JHDSwa-hTEE1gkg@mail.gmail.com> (raw)
In-Reply-To: <CAK7dMtCxLMPgc=V1Qys2s_7EkqgmUXAC2wDWezohNQo=rcuuLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
On Wed, 13 Mar 2024 at 16:49, Kevin Bowling <kevin.bowling@kev009.com>
wrote:
>
>
> On Wed, Mar 13, 2024 at 1:13 PM Henry Bent <henry.r.bent@gmail.com> wrote:
>
>> 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
>>
>
> The sun-rescue list has some 4.x traffic.
> http://www.sunhelp.org/mailman/listinfo/rescue_sunhelp.org
>
> There are some discord communities that are fairly active
>
> SGI discord:
> https://discord.gg/bYbWBEFcG2 (has active channels for other companies)
>
> Sun discord:
> https://discord.gg/NwBMkfGD
>
Thank you, I just subscribed to sun-rescue. I have greybeard syndrome
about Discord - I just don't trust that it's going to be a useful resource.
-Henry
[-- Attachment #2: Type: text/html, Size: 2507 bytes --]
next prev parent reply other threads:[~2024-03-13 20:59 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 ` [TUHS] " Erik E. Fair
2024-03-13 20:49 ` Kevin Bowling
2024-03-13 20:59 ` Henry Bent [this message]
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=CAEdTPBcNU8tm7OFubw_CjHGfN5RF5X+sQP4JHDSwa-hTEE1gkg@mail.gmail.com \
--to=henry.r.bent@gmail.com \
--cc=kevin.bowling@kev009.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).