On 06/ 1/10 10:11 PM, solarg wrote:
hello all,
on a Sun X4150, i have os2009.06 (b111b) installed. Yesterday, i startrd
an image-update to b134 (dev repo), and it is not finished after 10 hours!
Install Phase 162016/162016
Update
On 06/ 2/10 08:09 AM, Danek Duvall wrote:
solarg wrote:
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
3931 root 520M 513M cpu3400 10:55:01 12% pkg/1
What's pstack 3931 tell you? Does ptree 3931 show anything other than just
the one pkg
solarg wrote:
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
3931 root 520M 513M cpu3400 10:55:01 12% pkg/1
What's pstack 3931 tell you? Does ptree 3931 show anything other than just
the one pkg process?
Note that you're far enough along in the
solarg wrote:
is there another workaround?
Terminate the process, and edit the grub menu to point to the BE you want
to boot. It's not quite the same as truly activating the BE, but should be
close enough that you won't notice.
Danek
___
On 06/ 2/10 04:24 PM, Danek Duvall wrote:
solarg wrote:
is there another workaround?
Terminate the process, and edit the grub menu to point to the BE you want
to boot. It's not quite the same as truly activating the BE, but should be
close enough that you won't notice.
do you mean that
solarg wrote:
do you mean that i can boot on b134 even if pkg image-update is killed?
Given where the update is in its process, yes. All the bits have been laid
down, the search indices have been regenerated, the boot archive updated,
etc. The only thing left to do is to activate the new BE
