Jumpstart Patches

[kHz]

On Sun's doc site they have documents and scripts to add packages and patches after the jumpstart installation by using finish scripts.

Why is that preferable to patching the boot image using:
patchadd -C /export/install/Solaris_9_904_sparc/Solaris9/Tools/Boot -M /var/tmp 105181-17

and then copying the patch to the installation path of the image:
/export/install/Solaris_9_904_sparc/Solaris_9/Patches/105181-17

Wouldn't the patches in the installation path of the image be installed during the initial jumpstart installation rather than at the end using a finish script?

I could see using a finish script to add a recommended patch cluster or sun alert patch cluster, but to add single patches for the kernel or drivers, etc., wouldn't it be better to patch the boot portion of the image and then copy the patch to the patch directory?

Thanks for any thoughts or info you have on this.

 

[spamly]

You're right, patching the boot image is the way to go.

I've only used the finish scripts to add custom software, scripts, and printers.

 

[daFranze]

afaik you can't patch the OS to be installed on the JS server, just the bootimage. Sun (or my contact at Sun) suggested to copy patches to the server after jumpstarting it, add a eg. rc1.d script which installs the patch(cluster), followed by a reboot and a boot to runlevel 3.

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years in the domain of the OS, Backup and Storage