Hi,
Cool, but I missed something. Now it traps... should there be a bootadm
command in there somewhere?
panic[cpu0]/thread=180e000: BAD TRAP: type=31 rp=180b550 addr=be0
mmu_fsr=0 occurred in module "procfs" due to a NULL pointer dereference
: trap type = 0x31
addr=0xbe0
pid=0, pc=0x7be72440, sp=0x180adf1, tstate=0x4480001601, context=0x0
g1-g7: 0, 143, 8d97c2a44a880, 0, 487eda70ca, 10, 180e000
000000000180b260 unix:die+74 (10c6400, 180b550, be0, 0, 8, 180b320)
%l0-3: 000000007be72440 0000000000000000 0000000000100000 0000000001000000
%l4-7: 0000000000002000 00000000010c6458 00000000010c6400 000000000000000b
000000000180b340 unix:trap+9e8 (180b550, 1fff, 31, ea5f6be0, 1828530, 5)
%l0-3: 0000000000000000 0000000000000000 0000000000010000 000000000185eec0
%l4-7: 0000000000000001 000000000180c000 0000000000000001 0000000000000000
000000000180b4a0 unix:ktl0+64 (60021c03e08, 60024ca7280, 1, 18fcb80,
60021ca0b80, 1)
%l0-3: 000000000180c000 0000000000000000 0000004480001601 000000000101ef48
%l4-7: 0000060021c0d54a 0000000000000001 0000000000000000 000000000180b550
000000000180b5f0 genunix:vfs_setpath+d8 (60024cc9e18, 60024ca7280,
180b910, 60021c03e08, 0, 0)
%l0-3: 00000000018fc0b8 00000000018ae800 0000000000000000 0000060021c93a40
%l4-7: 000006002049c6e0 0000000000000002 00000000018a1800 000006002049c6d0
000000000180b6a0 genunix:domount+ac8 (60024cc9e18, 180b910, 60024ca7280,
ffffffffffffffff, c, 1)
%l0-3: 0000000000000006 0000000000000001 0000000000000000 00000000012614a8
%l4-7: 0000000000000000 0000060021c1d568 0000060021c1d570 00000000018ad040
000000000180b850 genunix:vfs_mountfs+48 (1261740, 1261748, 1261748,
fffffffffffffff8, 1261508, c)
%l0-3: 0000000001261618 0000000001909800 00000000018ae800 000000000190e400
%l4-7: 00000000018fc400 0000000003f50002 00000000018fd000 0000000001262c00
000000000180b950 genunix:vfs_mountroot+1f4 (18ad1c0, 8077, 60021cc6000,
18da578, 1261538, 60021c93a40)
%l0-3: 0000000000000002 0000000001909000 000000000185eec0 00000000018accc0
%l4-7: 000000000185eec0 0000000001909000 000000000185eec0 0000000001866c00
000000000180ba10 genunix:main+c4 (182b400, 180bec0, 182b7c0, 185eec0, 1,
1860558)
%l0-3: 000000000180e000 0000000070002000 0000000000000000 0000000001866400
%l4-7: 0000000000000000 000000000180c000 0000000070002000 0000000000000000
syncing file systems... done
skipping system dump - no dump device configured
rebooting...
Bart Smaalders wrote:
Jon Aimone wrote:
Hi,
I have some systems running older builds, like 2008.11, on which I
now need to do some testing with build 111b2 (a.k.a. 2009.06), and
then move on to build 116 without loosing the 2008.11 installation. I
was hoping there would be a way to use image-update to create a BE
for 2009.06, and then another BE for 116; but I see no way to tell
image-update exactly what I would like updated.
The easy way to do this is to create the boot environment you want, and
then to use the -R (just like pkgadd) option to pkg install to update
the "entire" incorporation, which will force the rest of the packages
to upgrade:
beadm create osol_2009.6
beadm mount osol_2009.6 /mnt
pkg -R /mnt install [email protected]@111
beadm unmount osol_2009.6
beadm activate osol_2009.6
Should do the trick for you.
This will update all wos packages; it won't get the latest version of
any unbundled pkgs, though.
- Bart
--
~~~\0/~~~~
Cheers,
Jon.
{-%]
========
If you always do what you've always done, you'll always get what you've always
gotten.
- Anon.
--------
When someone asks you, "Penny for your thoughts," and you put your two cents
in, what happens to the other penny?
- G. Carlin (May 12, 1937 - June 22, 2008)
begin:vcard
fn:Jon Aimone
n:Aimone;Jon
org:Sun Microsystems, Inc.;Storage Systems Quality Assurance
adr:MPK12-126;;12 Network Circle;Menlo Park;CA;94025;US
email;internet:[email protected]
title:Member of Technical Staff
tel;work:(650)786-8210
x-mozilla-html:FALSE
url:www.sun.com
version:2.1
end:vcard
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
