From: Warner Losh <imp@bsdimp.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] /bin vs /sbin
Date: Wed, 27 Jan 2021 15:22:55 -0700 [thread overview]
Message-ID: <CANCZdfqyVS++qdo6=2qym4mpi=sRFxrsiwW8hAR445-dVOoFSg@mail.gmail.com> (raw)
In-Reply-To: <64f487fb-6fed-e741-4e7b-daed1f646e37@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 3351 bytes --]
On Wed, Jan 27, 2021 at 12:06 PM Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
wrote:
> On 1/26/21 10:56 PM, Greg A. Woods wrote:
> > [not replying privately even though this is an old thread from back
> > in the time when I was still enjoying a care-free summer vacation,
>
> <thumbs up>
>
> > and even though Grant and/or his mailer set "reply-to" to be his
> > own address, not the list address,
>
> It's not me or my mailer setting the Reply-To:. It seems as if the
> mailing list is setting that on senders who's domain uses DMARC, which
> mine does.
>
> > but because I'm still having rDNS issues and Grant's mailer won't
> > let mine deliver to him...]
>
> I've added central... to my hosts file, so hopefully you can email me
> directly if you want to.
>
> > Note that "Solaris" is a marketing name for a whole OS package
> > including the kernel, base system, user interface, and even some
> > applications.
>
> <head tilt>
>
> That's ... a different explanation than I've heard before.
>
> I'm not saying I disagree with it, just that it's completely new to me.
>
> > On the other hand "SunOS" the name of the base system OS (i.e. kernel
> > and userland).
>
> Please elaborate. Including using the same terms for both names. How
> does "userland" compare to "base system" and / or "user interface"?
>
> I'm also curious what differentiates between SunOS and a minimal install
> of Solaris.
>
Solaris 2.x == SunOS 5.x + OpenWindows
Solaris 1.x == SunOS 4.x + OpenWindows
Solaris, back in the day, was SunOS + OpenWindows.
> > The name "SunOS" pre-dated the name "Solaris" but continues on as
> > the name of the base OS within the Solaris package.
>
> I thought the "SunOS" vs "Solaris" was a marketing change around the
> time SunOS / Solaris transitioned from being more BSD to more Sys V.
>
No. Solaris 2 was System V. Solaris 1 was BSD. Though it did pop up around
SunOS 4.1 time frame when it became clear that SunOS 5 would be System V
based and a big rewrite.
When Solbourne chose their name, Sun told them they could pick anything
they wanted, except Solaris because they were going to use that to market
SunOS.
> I also thought that the retention of "SunOS" in the kernel name and
> versioning was for backward compatibility.
>
Not entirely... It was very explicit in the marketing literature that SunOS
5 was the kernel for Solaris 2, but that Solaris 2 also included other
components like OpenWindows. The status of the base userland tools (eg
/bin/ls) wasn't ever talked about, but was generally understood to be in
the SunOS side of the world...
> > Sun even back-pedaled and re-branded SunSO 4 as Solaris 1.0 before
> > the switch from BSD to something Sun liked to think was akin to SVR4.
>
> I was not aware that some of -- what I'll call -- the naming shenanigans
> happened to SunOS 4. I was only aware of things at SunOS 5.
>
Yes. I had (but no longer have) a Solaris 1.1 Sparc CD that had SunOS 4.1.4
and OpenWindows 1.1 on it. I think Solaris 1.0 had 4.1.3 on it.
I worked for Solbourne Computers in Longmont CO in the early 1990s and
this distinction was what drove our group to create OI (Object Interface)
set of tools that implemented the OpenWindows and Motif look and feel since
it wasn't clear that Sun would license OpenWindows when Solbourne started
and we needed a desktop story...
Warner
[-- Attachment #2: Type: text/html, Size: 4696 bytes --]
next prev parent reply other threads:[~2021-01-27 22:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 17:55 Grant Taylor via TUHS
2020-07-21 18:15 ` Warner Losh
2020-07-21 22:42 ` David Arnold
2020-07-22 3:33 ` Warner Losh
2020-07-21 18:22 ` arnold
2020-07-21 18:33 ` Warner Losh
2020-07-21 18:43 ` Larry McVoy
2020-07-22 1:16 ` tytso
2020-07-22 3:27 ` Grant Taylor via TUHS
2020-07-22 3:35 ` Warner Losh
2021-01-27 5:56 ` Greg A. Woods
2021-01-27 19:06 ` Grant Taylor via TUHS
2021-01-27 22:22 ` Warner Losh [this message]
2021-01-27 22:35 ` Greg A. Woods
2021-01-28 5:24 ` Grant Taylor via TUHS
2020-07-22 1:44 ` Dan Cross
2020-07-22 2:17 ` Jon Forrest
2020-07-22 2:20 ` Adam Thornton
2020-07-22 13:30 ` Clem Cole
2020-07-22 13:43 ` Richard Salz
2020-07-22 2:27 ` Kurt H Maier
2020-07-21 19:24 ` Clem Cole
2020-07-22 13:39 ` Clem Cole
2021-01-29 23:50 ` Chris Hanson
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='CANCZdfqyVS++qdo6=2qym4mpi=sRFxrsiwW8hAR445-dVOoFSg@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@minnie.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).