On 01/09/09 15:49, Dan Price wrote:
On Fri 09 Jan 2009 at 03:42PM, Danek Duvall wrote:
On Fri, Jan 09, 2009 at 03:25:01PM -0800, Stuart Kreitman wrote:
I first tried it this morning around 9am. It got pretty busy, and created
the new clone "solaris-1",
which I'm booting into. Could this be related to upgrade activities that
may have taken place this morning?
Possibly. The output of "pkg history" may be useful, but it sounds like it
found something to upgrade to, since it created a new BE. There are a
couple of "build 101" package sets -- if you'd installed with an earlier
one, and upgraded before build 105 was pushed earlier today, then your
system would have done a bunch of thinking and spinning, downloaded next to
nothing, but created a new BE that was essentially identical to the
original one.
But that assumes that you've got your authority set to pkg.opensolaris.org,
which you obviously don't, since you're a Sun employee and you've been
asked dozens of times not to do, since using the internal server saves us
money, right?
It's likely that what he got was the minor respin to just the "entire"
incorporation which happened at some point. It wouldn't matter if he's
following ipkg.sfbay or pkg.o.o. Unless he specifically hooked up to
the dev repo there, he won't get b105.
-dp
I just tried the set-authority, and it made a BE with snv_105.
Only problem is that I don't have /usr/bin/scanpci, which is from a
package that I added in 103 :-(
S
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
