The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pechter@gmail.com (William Pechter)
Subject: [TUHS] the guy who brought up SVr4 on Sun machines
Date: Wed, 4 Jan 2017 16:57:26 -0500	[thread overview]
Message-ID: <16309908-e0e9-99dc-b435-1d44f6e65509@gmail.com> (raw)
In-Reply-To: <xoninpuo72v.fsf@anduin.eldar.org>

Brad Spencer wrote:
> Nevin Liber <nevin at eviloverlord.com> writes:
>
> [snip]
>
>> The release was (or was supposed to be, and I remember it as) "SunOS 4.1.3
>> u1" because we were told on no uncertain terms that there would be no
>> release called "SunOS 4.1.4" but it was OK to send out an update release
>> rolling up patches previously sent. I was *never* told why, which only made
>> me (and my management chain) push harder. There were enough changes to
>> warrant U1, U2, and U3 releases; I know U1 went out the door, and I know
>> that U3 was ready for release when I departed, I don't recall whether U2
>> made it out the door or not. I do not recall the method we used to triage
>> the changes into three releases.
> [snip]
>
> A small addition..  there was a 4.1.4, a.k.a. Solaris 1.1.2 [I think]
> that made it out the door [Google around for references].  I remember
> having the cd and installing it.  I also remember 4.1.3_U1, but not U2
> or U3, but I wouldn't be suprised that they existed.  I was at AT&T at
> the time and the group I was in resisted going to Solaris 2.x for as
> long as we could.  We were mostly interested in desktop and small server
> stuff, so SMP need not apply and Solaris 2.x where x <= 4 was painful.
> I remember the Sparc 5 Model 170 with SunOS 4.x which ran, for us, just
> as well as the Ultra 1.  Fun times....

I was keeping a group at Lucent running on some creaky Sparcstation2's
used as the department servers (we probably had the worst collection of
hardware in Lucent, but it was paid for and fully depreciated...) I had
to do the Y2k patches on the boxes and the corporate types were pushing
us to do weekly updates.  Patches dribbled out over a couple of months
requiring repeated passes over the hardware in a maintenance window.  Ugh.

I wrote a patch script and update cd and tape and applied the tar to all
the Sun machines the night before y2k -- avoiding the repeated patching
they (corporate IT) were requiring.  Of course most departments just
dumped the old hardware and  updated to  non-antiques.
The windows boxes were another nightmare.

After doing all of this I heard from an AT&T Manager that Lucent had a
product update tape they sold to AT&T that did all
the Y2k patches for one of their Sparcstation2 products.  Too bad this
wasn't available in-house.

Anyone archive the y2k patches for SunOS 4.1.3_U1 and 4.1.4.  I lost my
fixes in a move and I'd like to bring a couple of the
Sparcstations up again for fun.  I really liked that OS and hated
patching the libc for the resolver+ fixes. 

I think the main patches were for the date command, ms macros and some
stuff like diag reporting.  Realistically the Unix boxes
were the easiest to deal with.  Most y2k stuff was in application
programs.  If I still have the Sparc2 booting in 2038 it will be
interesting.

Bill




  parent reply	other threads:[~2017-01-04 21:57 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  2:41 Larry McVoy
2017-01-04  3:00 ` Warner Losh
2017-01-04  3:23   ` Dan Cross
2017-01-04  3:35     ` Larry McVoy
2017-01-04 12:24       ` Ed Carp
2017-01-04 16:17       ` ron minnich
2017-01-04 16:31         ` Joerg Schilling
2017-01-04 16:34           ` ron minnich
2017-01-04 16:57             ` Joerg Schilling
2017-01-04 17:06               ` Larry McVoy
2017-01-04 17:11                 ` Joerg Schilling
2017-01-04 17:15                   ` Larry McVoy
2017-01-04 17:40                     ` Joerg Schilling
2017-01-04 17:42                       ` Larry McVoy
2017-01-04 17:48                         ` Joerg Schilling
2017-01-04 17:57                           ` Larry McVoy
2017-01-04 18:24                             ` Dan Cross
2017-01-04 18:30                               ` Dan Cross
2017-01-04 18:25                             ` Joerg Schilling
2017-01-04 18:32                           ` Joerg Schilling
2017-01-04 18:46                             ` Dan Cross
2017-01-05 11:18                               ` Joerg Schilling
2017-01-06  2:09                                 ` Larry McVoy
2017-01-06  3:07                                   ` Steve Nickolas
2017-01-06 17:38                                   ` Warner Losh
2017-01-04 17:36               ` ron minnich
2017-01-04 17:41                 ` Joerg Schilling
2017-01-04 16:46           ` Larry McVoy
2017-01-04 17:02             ` Joerg Schilling
2017-01-04 17:10               ` Larry McVoy
2017-01-04 17:39                 ` Joerg Schilling
2017-01-04 17:52                   ` Larry McVoy
2017-01-04 18:23                     ` Joerg Schilling
2017-01-04 18:27                       ` Larry McVoy
2017-01-04 18:29                         ` Joerg Schilling
2017-01-04 18:44                       ` Larry McVoy
2017-01-05 11:50                         ` Joerg Schilling
2017-01-06  2:02                           ` Larry McVoy
2017-01-09 13:40                             ` Joerg Schilling
2017-01-09 17:48                               ` Larry McVoy
2017-01-10  3:58                               ` Larry McVoy
2017-01-10  4:16                                 ` Warner Losh
2017-01-08  1:37                       ` Larry McVoy
2017-01-05  2:26                 ` Wesley Parish
2017-01-04 18:56       ` Nevin Liber
2017-01-04 19:05         ` Warner Losh
2017-01-04 20:00         ` Clem Cole
2017-01-04 21:20         ` Brad Spencer
2017-01-04 21:57           ` William Pechter
2017-01-04 21:57           ` William Pechter [this message]
2017-01-05  0:36       ` Dave Horsfall
2017-01-05  0:43         ` Larry McVoy
2017-01-05  0:50           ` William Pechter
2017-01-05  1:01             ` Larry McVoy
2017-01-05  3:00               ` Wesley Parish
2017-01-05  3:13                 ` Larry McVoy
2017-01-05  8:12                   ` Andy Kosela
2017-01-05 16:23                     ` Larry McVoy
2017-01-05 16:31                       ` Clem Cole
2017-01-10 15:12 Berny Goodheart
2017-01-10 16:03 ` arnold
2017-01-10 16:20 ` Larry McVoy
2017-01-10 16:24   ` Joerg Schilling
2017-01-10 16:32     ` Berny Goodheart
2017-01-10 16:40       ` Chet Ramey
2017-01-10 16:41       ` Joerg Schilling
2017-01-10 16:20 ` Joerg Schilling
2017-01-10 16:34   ` Clem cole
2017-01-10 16:38     ` Chet Ramey
2017-01-10 16:57   ` Berny Goodheart
2017-01-10 17:10     ` Joerg Schilling
2017-01-10 17:47   ` Warner Losh
2017-01-10 18:28     ` Larry McVoy
2017-01-10 18:33       ` Warner Losh
2017-01-10 18:42         ` Larry McVoy
2017-01-10 19:21           ` Clem cole
2017-01-10 19:41             ` Clem cole
2017-01-11 21:03             ` Dan Cross
2017-01-11 20:56   ` Dan Cross
2017-01-11 22:57     ` Joerg Schilling
2017-01-11 23:06       ` Larry McVoy
2017-01-11 23:52         ` Joerg Schilling
2017-01-11 23:57           ` Larry McVoy
2017-01-12  0:07             ` Joerg Schilling
2017-01-12  1:58               ` Larry McVoy
2017-01-12 10:39                 ` Joerg Schilling
     [not found] ` <1154c8d8-2051-455e-a3f2-45415d901232.maildroid@localhost>
2017-01-10 16:34   ` Berny Goodheart
2017-01-10 15:38 Noel Chiappa
2017-01-10 21:26 Noel Chiappa
2017-01-11 18:07 Noel Chiappa
2017-01-11 19:37 ` Charles Anthony

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=16309908-e0e9-99dc-b435-1d44f6e65509@gmail.com \
    --to=pechter@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).