On 05/13/10 20:42, [email protected] wrote:
Bart Smaalders wrote:
On 05/13/10 15:44, zhenghui xie wrote:
hmm, interesting. I just tried it myself. I found that using 138 I am
able to onu to my bits. but if install 134 then onu to my private bits,
it failed to load it.
for both case, publishers are set the same as follow:
r...@sol-v40z-1:/tmp# pkg publisher
PUBLISHER TYPE STATUS URI
opensolaris.org (preferred) origin online http://netinstall-osol.sfbay/
local origin online http://netinstall-osol.sfbay:9000/
There is no reason for us to stick with 134 so our problem is solved.
:-) Thanks.
Note that if starting at 134, you'll need to add in opensolaris.org
pkgs, since your 138 ON bits have dependencies on packages post 134 that
are not in ON.
hi, Bart
Would you please elaborate this a little? I am not sure I follows. If I
fresh installed osol 138, do I still need to add opensolaris.org pkgs?
Thanks
-Jan
Sorry; I was trying to point out why upgrading from 134 directly on just
ON bits on 138 was likely to be difficult.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
