quoting Dave Uhring (Sat, 21 Jun 2008 19:00:11 -0500):
> I have been unable to find anything regarding live upgrade of one ZFS
> boot environment to a newer one but did work it out and someone might
> find this useful:
>
> lucreate -n snv_91
> lofiadm -a /export/home/duhring/sol-nv-b91-x86-dvd.iso
> mkdir /a /b
> mount -F hsfs /dev/lofi/1 /b # *not* /a
> luupgrade -u -n snv_91 -s /b
> luactivate snv_91
> init 6

Strange. I just did a lofiadm on /iso of the solaris b91.iso and after
that:
# lucreate -n snv91
# luupgrade -u -n snv91
# luactivate snv91
# init 6

WHY did you create a /b directory? Without it upgrading b90 to b91
worked flawlessly. Just curious.

--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ | SunOS 10u5 05/08 ++

On Sun, 22 Jun 2008 09:06:00 +0200, Dick Hoogendijk wrote:

> Strange. I just did a lofiadm on /iso of the solaris b91.iso and after
> that:
> # lucreate -n snv91
> # luupgrade -u -n snv91
> # luactivate snv91
> # init 6
>
> WHY did you create a /b directory? Without it upgrading b90 to b91
> worked flawlessly. Just curious.

Because luupgrade(1m) appears to require the -s argument.

Upgrading an Operating System Image
The luupgrade command uses -u to upgrade an operating system
image. The syntax is as follows:

luupgrade -u -n BE_name [ -l error_log ] [ -o outfile ][-N]
-s os_image_path [ -j profile_path [-D] ]

quoting Dave Uhring (Sun, 22 Jun 2008 08:17:23 -0500):
> On Sun, 22 Jun 2008 09:06:00 +0200, Dick Hoogendijk wrote:
>> WHY did you create a /b directory? Without it upgrading b90 to b91
>> worked flawlessly. Just curious.
>
> Because luupgrade(1m) appears to require the -s argument.

My mistake. You lofi mounted the iso on /b.
But he /a is not needed. It's created by LU.

--
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ | SunOS 10u5 05/08 ++