The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: don@DonHopkins.com (Don Hopkins)
Subject: SGI Software Usability II (IRIX 5.1 memo)
Date: Thu, 12 Oct 2017 17:20:20 +0200	[thread overview]
Message-ID: <9582F0BA-C3BB-4BEB-9C25-1103D9C26B59@gmail.com> (raw)
In-Reply-To: <210DE044-1849-44C2-848C-76EF310F305A@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4106 bytes --]

https://en.wikipedia.org/wiki/SunOS#History <https://en.wikipedia.org/wiki/SunOS#History>

The SunOS 3.x => 4.x transition was also the BSD 4.2 => 4.3 transition.

Sun operating system version numbers seemed to parallel the version of Unix it was based on for a while there, until it started spinning out of control and got sucked up into the System V death star. 

Sun UNIX 0.7: UniSoftUNIX v7
SunOS 1.x: 4.1 BSD
SunOS 2.x: 4.2 BSD
SunOS 3.x: 4.2 BSD + some 4.3 BSD and some System V
SunOS 4.x: 4.3 BSD + even more System V 
SunOS 5.0: SVR4

-Don


> On 12 Oct 2017, at 17:09, Don Hopkins <SimHacker at gmail.com> wrote:
> 
> 
>> On 12 Oct 2017, at 16:59, Larry McVoy <lm at mcvoy.com <mailto:lm at mcvoy.com>> wrote:
>> 
>> That must have been really early on because by the time I got to Sun (4.0?
>> Maybe 4.1?) shared libraries worked properly.
> 
> Yeah, I remember that being a SunOS 3.x limitation. 4.x was a whole lot nicer! 
> 
> Wikipedia says: 
> 
> SunOS 4.0: Dec 1988: New virtual memory system, dynamic linking, automounter, System V STREAMS I/O. Sun386i support.
> 
> https://en.wikipedia.org/wiki/SunOS#History <https://en.wikipedia.org/wiki/SunOS#History>
> 
> Then it all went downhill from there… ;(
> 
> -Don
> 
> http://www.art.net/~hopkins/Don/unix-haters/slowlaris/sunos-died.html <http://www.art.net/~hopkins/Don/unix-haters/slowlaris/sunos-died.html>
> 
> The Day SunOS Died
> 
> Lyrics by N. R. "Norm" Lunde.
> Apologies to Don McLean.
> 
> Remember when those guys out West
> With their longish hair and paisley vests
> Were starting up, straight out of UCB?
> They used those Motorola chips
> Which at the time were really hip
> And looked upon the world through VME.
> Their first attempt ran like a pig
> But it was the start of something big;
> They called the next one the Sun-2
> And though they only sold a few
> It soon gave birth unto the new
> Sun-3 which was their pride
> And now they're singing
> 
> [chorus]
> 
> "Bye, bye, SunOS 4.1.3!
> ATT System V has replaced BSD.
> You can cling to the standards of the industry
> But only if you pay the right fee -- 
> Only if you pay the right fee . . ."
> 
> The hardware wasn't all they sold.
> Their Berkeley port was solid gold
> And interfaced with System V, no less!
> They implemented all the stuff
> That Berkeley thought would be enough
> Then added RPC and NFS.
> It was a lot of code to cram
> Into just four megs of RAM.
> The later revs were really cool
> With added values like SunTools
> But then they took us all for fools
> By peddling Solaris . . .
> And they were singing,
> 
> [chorus]
> 
> They took a RISC and kindled SPARC.
> The difference was like light and dark.
> The Sun-4s were the fastest and the best.
> The user base was having fun
> Installing SunOS 4.1
> But what was coming no one could have guessed.
> The installed base was sound
> And software did abound.
> While all the hackers laughed and played
> Already plans were being made
> To make the dubious "upgrade" 
> To Sun's new Solaris . . .
> And Sun was singing,
> 
> [chorus]
> 
> The cartridge tapes were first to go --
> The CD-ROM's a must, you know
> And floppy drives will soon go out the door.
> I tried to call and ask them why
> But they took away my TTY
> And left my modem lying on the floor.
> While they were on a roll
> They moved the damned Control.
> The Ethernet's now twisted pair
> Which no one uses anywhere.
> ISDN is still more rare -- 
> The bandwidth's even less!
> But still they're singing
> 
> [chorus]
> 
> But worst of all is what they've done
> To software that we used to run
> Like dbx and even /bin/cc.
> Compilers now have license locks
> Wrapped up in OpenWindows crocks --
> We even have to pay for GCC!
> The applications broke;
> /usr/local went up in smoke.
> The features we've depended on
> Before too long will all be gone
> But Sun, I'm sure, will carry on 
> By peddling Solaris,
> Forever singing,
> 
> [chorus]
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171012/0c0ceab7/attachment.html>


  reply	other threads:[~2017-10-12 15:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 13:04 Michael-John Turner
     [not found] ` <AC831F18-D52F-4C0F-9E31-E4C7CD3F4A1E@gmail.com>
2017-10-12 13:43   ` Don Hopkins
2017-10-12 14:00 ` Larry McVoy
2017-10-12 14:16   ` Don Hopkins
2017-10-12 14:55     ` Don Hopkins
2017-10-12 14:59       ` Larry McVoy
2017-10-12 15:09         ` Don Hopkins
2017-10-12 15:20           ` Don Hopkins [this message]
2017-10-12 14:22   ` AT&T taking over Sun: Panic! Don Hopkins
2017-10-13 15:59   ` SGI Software Usability II (IRIX 5.1 memo) Jose R. Valverde

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=9582F0BA-C3BB-4BEB-9C25-1103D9C26B59@gmail.com \
    --to=don@donhopkins.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).