On 01/ 4/10 10:25 AM, Jerry Jelinek wrote:
Jordan Vaughan wrote:
On 01/ 4/10 09:54 AM, Jerry Jelinek wrote:
Jordan Vaughan wrote:
On 01/ 4/10 07:26 AM, Jerry Jelinek wrote:
Jordan Vaughan wrote:
I need someone to review my fix for
6909222 reboot of system upgraded from 128 to build 129 generated
error from an s10 zone due to boot-archive
My webrev is accessible via
http://cr.opensolaris.org/~flippedb/onnv-s10c
[...]
Jordan,
I don't think so since the boot_archive files are not delivered by any
pkg. Thus, there is nothing in the change-variant process which will
touch those files.
Thanks,
Jerry
/boot/solaris/bin/create_ramdisk is installed by SUNWckr, right?
---8<---
jv227347 arrakis [10:13:45 0]% pkg search
/boot/solaris/bin/create_ramdisk
INDEX ACTION VALUE PACKAGE
path file boot/solaris/bin/create_ramdisk
pkg:/sunwc...@0.5.11-0.79
path file boot/solaris/bin/create_ramdisk
pkg:/sunw...@0.5.11-0.108
[...]
pkg:/sunw...@0.5.11-0.127
path file boot/solaris/bin/create_ramdisk
pkg:/sunw...@0.5.11-0.128
path file boot/solaris/bin/create_ramdisk
pkg:/sunw...@0.5.11-0.129
path file boot/solaris/bin/create_ramdisk
pkg:/sunw...@0.5.11-0.130
---8<---
Will changing variants not affect SUNWckr?
Jordan,
Maybe I'm not understanding the bug's evaluation but it seems to say
that the problem is caused by the presence of boot archive files.
Jerry
Jerry,
It is. However, bootadm(1M) infers the existence of boot archives from
the existence of /boot/solaris/bin/create_ramdisk. If we remove the
latter from a zone, then bootadm(1M) won't try to update boot archives
in the zone's root filesystem. Changing package variants during ipkg
p2v should remove /boot/solaris/bin/create_ramdisk and thus prevent
bootadm(1M) from updating ipkg-branded zones' boot archives.
Thanks,
Jordan
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
