Calum Mackay wrote:
thanks,

That entirely depends on how your filesystem is setup/split.

That workaround should work if you are using the default filesystem
setup that an install from an OpenSolaris LiveCD gives you.

I think I am; I installed 127 from USB, into a 100GB partition of a larger disk.

ca...@miles:~$ zfs list -r rpool
NAME                   USED  AVAIL  REFER  MOUNTPOINT
rpool                 13.3G  84.6G    83K  /rpool
rpool/ROOT            5.41G  84.6G    21K  legacy
rpool/ROOT/osol-127   12.2M  84.6G  2.37G  /
rpool/ROOT/osol-128a  5.40G  84.6G  4.53G  /
rpool/dump            3.97G  84.6G  3.97G  -
rpool/swap            3.97G  88.5G  72.9M  -

Given that, would you suggest it reasonable to try PKG_CACHEDIR=/var/tmp for the image-update to 129?

I hesitated, as in 12986 we're talking about a single package, not "entire".

Yes, it should work. Remember, image-update should operate using an alternate BE, so even if the upgrade failed part of the way, no harm should be done to the current BE.

--
Shawn Walker
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to