On 02/21/10 05:29 PM, Alan Coopersmith wrote:
Jürgen Keil wrote:
it freezes during the "Creating plan" when running pkg image-update,
either from b131 be or b132 (I kept both).
A "pkg" process that is using huge amounts of memory could explain this...
The upgrade from previous builds to 133 is known to make pkg use more
memory than previous upgrades due to having to deal with twice the number
of packages (all the packages with old names being obsoleted and the new
names replacing them). Discussion of improvements to that would likely
be held on pkg-discuss.
Well, I ended up installing b133 from cdrom image. Smooth and,
relatively fast compared to what I hear !
backed-up my user filesystems (home) to my home server and restored with
zfs send/receive.
Actually quite painless.
The only painful part was to use pkg to install packages missing from
cdrom, that was the longest part.
I'm still wondering why pkg is so long, barely usable I would say,
especially the long disk write AFTER it reports everyting to have been
downloaded and installed !! Even for a single package install... I tried
to disable index rebuild but nope.
Bruno
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
