jumpstart and patch_finish and patching and Solaris 2.8
2007-12-24 22:08:00
I was ready to ask this on the list, but found out what the fix is, so
here's the problem, and the solution, all in one, for the poor old sob
who's trying to do the same thing, and doesn't want to waste as much
time on it as I did.
1.
When you jumpstart Solaris 2.7, it will run the patch_finish script in
/cdrom/Solaris_2.7/Tools/Boot/usr/sbin/install.d/install_config/
The problem is that the script (by default) will apply the patches
based on timestamp, and it will bypass the patch-order file (this file
will be part of the jumbo patch (cluster patch, whatever) that you
download from SUN). So applying diff_patch_finish is a Good Thing.
2.
When you jumpstart Solaris 2.8, the same annoyance occurs (same fix)
(does this mean that nobody applies cluster patches with jumpstart?).
However, you also have to take into consideration that the marketing
folks, by calling it "Solaris 8", have misguided some developers as well.
So while patch_finish will look for /cdrom/Solaris_2.8/Patches, the NFS
mounted directory will show up under /cdrom/Solaris_8/Patches
fix (on your jumpstart box, where your images sit e.g. in /images/sol8)
with a simple
cd /images/sol8/; ln -s Solaris_8 Solaris_2.8
The reason I prefer to create the soft link instead of changing
patch_finish for this one, is that I don't know which other scripts are
making the same assumptions.
Now, if I could only convice patchadd to stop verifying diskspace and
just _install_ stuff, I'd cut down on install-time quite a bit..
CHeers,
Gert-Jan.
--
+++++++++++++ -------- +++++ --- ++ - +0+ + ++ +++ +++++ ++++++++ +++++++++++++
sed '/^[when][coders]/!d G.J.W. Hagenaars -- gj at hagenaars dot com
/^...[discover].$/d Remembering Mike Carty 1968-1994
/^..[real].[code]$/!d UltrixIrixAIXHPUXSunOSLinuxBSD, nothing but nix
' /usr/dict/words I'm Dutch, what's _your_ excuse?
*** patch_finish.old Mon Mar 11 15:04:07 2002
--- patch_finish Mon Mar 11 14:46:13 2002
***************
*** 96,102 ****
# because of space issue, now all patches donot allow backout
#/usr/sbin/patchadd -d -R ${INSTALLROOT} \
! patches=`\ls -rt .`
status=0
for patch in $patches ; do
--- 96,106 ----
# because of space issue, now all patches donot allow backout
#/usr/sbin/patchadd -d -R ${INSTALLROOT} \
! if [ -f patch_order ] ; then
! patches=`cat patch_order`
! else
! patches=`\ls -rt .`
! fi
status=0
for patch in $patches ; do
Comments
Got something to say?
You must be logged in to post a comment.
