The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Earl Baugh <earl.baugh@gmail.com>
To: Alan Coopersmith <alan.coopersmith@oracle.com>
Cc: Will Senn <will.senn@gmail.com>, tuhs@tuhs.org
Subject: [TUHS] Re: SunOS 4 in 2024
Date: Thu, 14 Mar 2024 16:23:39 -0400	[thread overview]
Message-ID: <055B3269-D5F9-4A55-B6FF-0FD7A3CD6E63@gmail.com> (raw)
In-Reply-To: <72bf032c-a945-4b9d-b0da-2d8e535b5311@oracle.com>

Another reason why it’s fun use the older OS’s.   For old Sun HW, I don’t believe SunView can be beat.
It was always very performant for me, and met the basic goals of a window manager that I needed.
(I’m not one that needs a huge amount of customization..)

Earl

> On Mar 13, 2024, at 8:40 PM, Alan Coopersmith <alan.coopersmith@oracle.com> wrote:
> 
> On 3/13/24 14:27, Will Senn wrote:
>> I recently saw that Solaris 11.4 SRU66 was released and had a yearning to see how things in Solaris land were doing (can't stand Gnome so OpenIndiana's a bust)...
> 
> You might not find Solaris much more to your liking then, since Solaris 11.0
> and later only include the GNOME desktop. (Solaris 2.6 through 10 also had
> CDE, and Solaris 1.0 through 8 also had OpenWindows.)  In Solaris 11.4, it's
> GNOME 3 - up to GNOME 41 in SRU 66.
> 
> OpenIndiana went with MATE instead of GNOME 3, and I believe has some other
> desktop choices as well.  The Tribblix distro of illumos offers a choice of
> Xfce, Mate, OpenCDE, or Enlightenment on top of the same core OS derived from
> OpenSolaris.
> 
>> but with Oracle's Solaris, it's a mess at least for hobbyists (only get release patches, so I'm guessing the most up to date 'release' was 11.4 in 2018).
> 
> There's also the "CBE" release from 2022 to allow people building open source
> to build & test on a somewhat newer base:
> https://blogs.oracle.com/solaris/post/announcing-the-first-oracle-solaris-114-cbe
> 
> It's roughly equivalent to a beta build of Solaris 11.4 SRU 42.  (Solaris 11.4
> issues "Support Repository Updates" or SRUs around once a month, so the SRU
> number is basically the count of the number of months after August 2018 that
> a given SRU was released.)
> 
> But yeah, if you want to stay up to date, you need a support contract.
> 
> -- 
>        -Alan Coopersmith-                 alan.coopersmith@oracle.com
>         Oracle Solaris Engineering - https://blogs.oracle.com/solaris
> 


      parent reply	other threads:[~2024-03-14 20:24 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
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 [this message]

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=055B3269-D5F9-4A55-B6FF-0FD7A3CD6E63@gmail.com \
    --to=earl.baugh@gmail.com \
    --cc=alan.coopersmith@oracle.com \
    --cc=tuhs@tuhs.org \
    --cc=will.senn@gmail.com \
    /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).