Does anyone remember how patching worked in SunOS 4
in [Solaris]
|
Prev: Howto Monitor secure nfs
Next: solaris 10 locale
From: Tim Bradshaw on 5 Mar 2010 11:17 I realised I have no memory at all of how patching (and for that matter patching) worked in SunOS 4 (and before). Does anyone remember this? --tim (No, I don't still have systems this old, I was just curious)
From: Tim Bradshaw on 5 Mar 2010 11:18 On 2010-03-05 16:17:48 +0000, Tim Bradshaw said: > and for that matter patching s/patching/packaging/ Sorry!
From: Mike K Smith on 5 Mar 2010 11:40 On 5 Mar, 16:18, Tim Bradshaw <t...(a)tfeb.org> wrote: > On 2010-03-05 16:17:48 +0000, Tim Bradshaw said: > > > and for that matter patching > > s/patching/packaging/ From my recollection there was no structured way of adding a package. You would probably be sent a tarball, possibly an installation script and a set of instructions. You might have to run some commands manually, you might have to rebuild the kernel to add device drivers and you might have to add commands to /etc/rc.local. I can't remember if there was a structured way of patching or if it was as above. I haven't touched a SunOS 4 system since about 1996, I'm sure someone else can fill in the gaps in my memory. Mike
From: Bill Waddington on 5 Mar 2010 12:03 On Fri, 5 Mar 2010 08:40:30 -0800 (PST), Mike K Smith <mks-usenet(a)dsl.pipex.com> wrote: >On 5 Mar, 16:18, Tim Bradshaw <t...(a)tfeb.org> wrote: >> On 2010-03-05 16:17:48 +0000, Tim Bradshaw said: >> >> > and for that matter patching >> >> s/patching/packaging/ >From my recollection there was no structured way of adding a package. >You would probably be sent a tarball, possibly an installation script >and a set of instructions. You might have to run some commands >manually, you might have to rebuild the kernel to add device drivers >and you might have to add commands to /etc/rc.local. > >I can't remember if there was a structured way of patching or if it >was as above. > >I haven't touched a SunOS 4 system since about 1996, I'm sure someone >else can fill in the gaps in my memory. Ugh. I had managed to forget this until the OP brought it up :) I've still got links on the driver download site. Here's how we did it back in the day. By hand. Like I said, Ugh. It even includes a patched kernel to fix a bug when handling some Sbus cards. http://www.tahomatech.com/downloads/drivers/sunos/sbus/ Bill -- William D Waddington william.waddington(a)beezmo.com "Even bugs...are unexpected signposts on the long road of creativity..." - Ken Burtch
From: Doug McIntyre on 5 Mar 2010 12:08
Mike K Smith <mks-usenet(a)dsl.pipex.com> writes: >On 5 Mar, 16:18, Tim Bradshaw <t...(a)tfeb.org> wrote: >> On 2010-03-05 16:17:48 +0000, Tim Bradshaw said: >> >> > and for that matter patching >> >> s/patching/packaging/ >From my recollection there was no structured way of adding a package. >You would probably be sent a tarball, possibly an installation script >and a set of instructions. You might have to run some commands >manually, you might have to rebuild the kernel to add device drivers >and you might have to add commands to /etc/rc.local. >I can't remember if there was a structured way of patching or if it >was as above. No, there was no structured way of patching. Some had scripts, many did not. You pretty much had to read the README and follow along, mostly by renaming the old binaries, and untar'ing the patch set ontop. libc was always the hardest thing to do. Here's the README for one libc SunOS 4.1.4 patch. http://sunsolve.sun.com/search/document.do?assetkey=1-21-102545-13-1 |