From: Catlin, Brian (bcatlin@uslec.com)
Date: Tue May 10 2005 - 11:09:06 EDT
I am looking for other people's experiences in patching the miniroot
boot image for jumpstart
I have Solaris 8 2/04 and Sol 9 9/04 boot images in my jumpstart
server. I have applied the following patches to the Solaris 8 image:
112396-02, 108987-16, 109318-37
I have tried using JET (from bigadmin) [Jumpstart enterprise toolkit].
While it wouldn't do the dhcp boot, it did work well for other things.
One thing is that when you are adding a client it checks for `critical
patches in the boot image. (that's where the patches applied came from
above)
One of my questions is how was it determined that these are 'critical',
as the boot works fine before or after in my experience.
Another thing - applying the patch cluster to the boot image corrupts it
(using the -M option of patchadd to read the patch_order file). One of
the patches removes some critical info, that the rest of the patches
need so all subsequent patches fail.
so anyone have a best practices/sop for this??
BC
BTW - on my last question about sysidcfg dhcp boot asking for netmask,
I went to the default setup (netmask, ipv6) for the network setting and
load the necessary config files with the finish script. Box comes up
dhcp, and publishes its name via ddns to the dns server (windows based).
Brian C.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:40 EDT