>For example, on my system, when I did an image-update from build 110 to >build 111, with all of the data to be installed downloaded already, it >only took about five minutes to upgrade 666 packages and move around 480 >megabytes worth of data. That's not too shabby if you ask me.
Compare upgrading from build 128 to later :-) >Except that pkg(5) actually does both. It keeps the package data >spooled locally, and if the user has chosen to purge the download cache, >it can retrieve just the data it needs. So when "upgrade image" dies, e.g., because there's a symlink or directory in the "wrong place" and you remove the offending file, why does it download everything again? >I think you're confused about what I've said here. And no, the data is >intentionally stored by digest and not by its original name. It would >neither be practical, nor efficient to store the files in the repository >by their delivered name. The size of the /dev repository is currently >around 63.6G and growing... A hardlink doesn't cost (much) of additional storage. Casper _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
