Frank Middleton wrote:
On 10/ 5/09 03:21 PM, Shawn Walker wrote:
So, if you were expecting the /var/pkg/download in your original boot
environment to be purged, it won't be. However, if you check the new
boot environment's /var/pkg/download, it should be empty ...
But the reverse actually occurred. At the start it was empty and there
were no old BEs, snapshots, or clones to hide any in. After the install
/var/pkg/download was definitely not empty, and the cache flag was set.
You seem to be misunderstanding me. When you execute an image-update,
that creates a new BE. The old BE is the one that /usr/bin/pkg is
executing from when you started the image-update. The new BE is the one
that image-update created. The new BE once the image-update is
successful should have an empty /var/pkg/download.
No, these are unofficial. There are RFEs open to document and enhance
control over the download cache.
Fair enough, although I am partial to the sxce solution which lets you
move all of /var. If you are so constrained for space (e.g., 16GB boot
disk) that you need to move the download cache, you'll probably be
moving /var/dump, /var/crash, and swap anyway, so why not move
them all?
Currently, there's a requirement that the various directories all be
part of the same filesystem. At some point in the near future, it will
be possible to split it over multiple datasets. That's also something
being worked on so that the download cache can be shared between boot
environments (BEs).
Cheers,
--
Shawn Walker
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
