From: kevin.bowling@kev009.com (Kevin Bowling)
Subject: [TUHS] Favorite UNIX
Date: Thu, 28 Sep 2017 20:36:25 -0700 [thread overview]
Message-ID: <CAK7dMtDvmQCtMeMMPnHfsHTc=njQqh7rkLo7B3jLsYL-r_UjxA@mail.gmail.com> (raw)
In-Reply-To: <20170929032828.GN28606@mcvoy.com>
I have the requisite hardware and media so I will give it a shake so I
can talk with you about it some time.
Auspex.. I have a story there believe it or not. Tore one apart at an
electronic junkyard I worked at part time in my teens. But I got it
booted up enough to test everything and sell as they wanted. The
hardware was very cool. I didn't know enough back then to evaluate
the software. I murdered a ton of interesting computers there sadly.
Still searching for salvation :D
Regards,
On Thu, Sep 28, 2017 at 8:28 PM, Larry McVoy <lm at mcvoy.com> wrote:
> On Thu, Sep 28, 2017 at 07:58:59PM -0700, Kevin Bowling wrote:
>> What is your favorite UNIX. Three possible categories, choose one or more:
>> 1) Free
>> 2) Forced to use a commercial platform. I guess that could include
>> macOS and z/OS with some vivid imagination, maybe even NT.
>> 3) Historical
>
> SunOS 4.1.3 Oh, man, how I wish that all of Unix today were based
> on that. If you like FreeBSD you would love that kernel. It's BSD
> for sure but then carefully moved forward into an excellent VM system,
> a virtualized the file system with the vnode stuff, it cared about
> the right picture. And all the bugs fixed.
>
> I've worked in lots of other kernel source bases. They all sucked in
> comparison. Including Solaris, fuck that shit, Bryan will yell at me
> but Solaris sucked. Yeah, they made it useful with all the work they
> did but it was never "home" and I think that even the people that worked
> on it get that. Or not, it was never home for me.
>
> SunOS had so much love and so much carefulness poured into it. And I
> can't claim any credit, it was the people who came before me, Rusty, Rob,
> Joe, Steve, those guys did the work that made me see the architecture
> that they left for me to see.
>
> Guy Harris worked on it, he left right around the time I joined, I think
> he went to Auspex (sp?) but he would come back and pound on the door
> to building 5 at around 6 or 7pm. Pope or I would go down and let him
> in and he'd find a machine and look at the source and start screaming
> about why haven't they fixed this bug? And he'd just fix it. He didn't
> work here and he fixed bugs. I get it, it took me years after I left
> Sun to stop saying "we" when we were talking about Sun.
>
> The level of love, as measured by the amount of time we all spent to make
> it better, was over the top. And it was because of the super stars who
> showed us what an OS could be.
>
> Today? Favorite? Grumble. It's sort of shitty. Linux is the obvious
> winner but is it what I like? It's what I run. Have to give it credit.
> It is pretty good. I'd prefer to be running a SunOS derived OS.
next prev parent reply other threads:[~2017-09-29 3:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 2:58 Kevin Bowling
2017-09-29 3:28 ` Larry McVoy
2017-09-29 3:36 ` Kevin Bowling [this message]
2017-09-29 6:56 ` Mutiny
2017-09-29 14:14 ` Larry McVoy
2017-09-29 12:08 ` Arthur Krewat
2017-09-30 15:40 ` Michael Parson
2017-09-30 17:53 ` Ian Zimmerman
2017-09-30 18:34 ` Michael Parson
2017-09-30 18:45 ` Arthur Krewat
2017-10-01 0:36 ` Larry McVoy
2017-10-01 0:51 ` Dave Horsfall
2017-10-01 1:10 ` Larry McVoy
2017-10-01 1:13 ` Cory Smelosky
2017-10-01 3:43 ` Arthur Krewat
2017-10-01 14:07 ` Don Hopkins
2017-10-01 3:05 ` Michael Parson
2017-10-01 3:15 ` Kevin Bowling
[not found] ` <201710011513.v91FDSMB011831@freefriends.org>
2017-10-01 19:35 ` Michael Parson
2017-10-01 15:27 ` [TUHS] " Michael Kerpan
2017-10-01 16:37 ` Derrik Walker v2.0
2017-10-01 16:51 ` George Michaelson
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='CAK7dMtDvmQCtMeMMPnHfsHTc=njQqh7rkLo7B3jLsYL-r_UjxA@mail.gmail.com' \
--to=kevin.bowling@kev009.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).