Frank Middleton wrote:
On 10/ 2/09 10:12 AM, I wrote:
But of course deleting old BEs may make your system un-upgradable.
http://defect.opensolaris.org/bz/show_bug.cgi?id=10807
http://defect.opensolaris.org/bz/show_bug.cgi?id=11221
Just did (yet another) upgrade, from snv111b to snv124 this time,
because of 10807. Was very careful to make sure that there were no
snapshots,, that /var/pkg/download was empty, and specifically did
# pkg set-property flush-content-cache-on-success true
Held breath and did beadm delete of old BE, and all snapshots.
Guess what - /var/pkg/download was still full of gigabytes of stuff.
Is this a bug or a feature?
There have been no reports of its failure. It has worked for me
personally. After *successful* completion of an image-update, install,
etc. /var/pkg/download should have been emptied, assuming that the
property was really set as you thought it was.
FWIW sxce snv123 install has an option in text mode to make /var a
separate dataset. If you use this option you only save around 0.5GB,
but it probably would help with OpenSolaris since the baseline is
otherwise too large to be upgradable in 16GB unless you can be sure
/var/pkg/download is on a different pool. Suggesting it here in case
someone actually wants to try to upgrade on a 16GB boot disk.
Making /var/pkg/download be on a separate dataset is being worked on.
Alternatively, you can set the PKG_CACHEDIR environment variable to a
directory of your choice.
Cheers,
--
Shawn Walker
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
