Jordan Vaughan wrote:
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
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 gene
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-ar
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 ac
On 01/ 4/10 09:57 AM, Enda O'Connor wrote:
Hi Jordan
Not being too familiar with the underlying technology, I assume
s10_boot.ksh is run every boot, as otherwise a patch can deliver
create_ramdisk to the system after it's removed.
Enda
Correct.
Thanks,
Jordan
_
Jordan Vaughan wrote:
On 12/23/09 12:40 AM, Frank Batschulat (Home) wrote:
On Tue, 22 Dec 2009 00:46:00 +0100, 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
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/~fli
On 12/23/09 12:40 AM, Frank Batschulat (Home) wrote:
On Tue, 22 Dec 2009 00:46:00 +0100, 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:/
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
Jorda
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,
This looks ok to me but don't we need to
> On Tue, 22 Dec 2009 00:46:00 +0100, 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/
Hi Frank,
Thanks for reviewing my fix. Native-branded zones will disappear when
Solaris Express dies (which should happen in a few builds); therefore,
it isn't worthwhile to fix this problem for native-branded zones. No
special script code is needed for ipkg-branded zones because IPS package
On Tue, 22 Dec 2009 00:46:00 +0100, 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
Jo
Excellent suggestion. I'll update CR 6912451. Meanwhile, I removed the
XXX comments and regenerated the webrev.
Thanks,
Jordan
On 12/21/09 06:12 PM, Edward Pilatowicz wrote:
i'd probably leave out the XXX comment and instead update 6912451 to
mention that part of the fix for 6912451 would i
i'd probably leave out the XXX comment and instead update 6912451 to
mention that part of the fix for 6912451 would involve removing the fix
for 6909222 (since it would essentially be obsoleting this fix.)
ed
On Mon, Dec 21, 2009 at 03:46:00PM -0800, Jordan Vaughan wrote:
> I need someone to revi
The bug mentions that this can also impact a nevada zone that was p2v'ed.
Should you fix usr/src/lib/brand/native/zone as well?
-Steve
On Mon, Dec 21, 2009 at 03:46:00PM -0800, Jordan Vaughan wrote:
> I need someone to review my fix for
>
> 6909222 reboot of system upgraded from 128 to build 129
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
Thanks,
Jordan
___
zones-disc
17 matches
Mail list logo
