On 04/28/10 09:02 PM, Frank Middleton wrote:
On 04/28/10 05:29 PM, Bart Smaalders wrote:
If you're on dev and upgrade to a release after 134, the only way to
install 2010.03 will be to boot an older BE, since 2010.03's build
version number will be somewhere between 134 and 135.
Sorry to be a pest, but why would you want to do that? And if
you wanted to, how would you do it? Will there actually be an
image-update to get to 2010.03, and would it also be on .../dev?
I am not sure what " Why would you want to do that ?" refer to. For
release builds there are often respins to address critical bugfixes.
These get unique ids. However in order to not mess up the monotonically
increasing numbers, these are typically lettered.
As in the past, /release will be set to the latest release build when
its available.
I imagine you could always install 2010.03 from scratch (even
on SPARC these days), so this isn't a convincing reason. But
the resource issue is fair enough, although one is tempted to
ask why not use the resources devoted to ploughing ahead to
accelerate 2010.03 instead? (I know, different resources, and
not a technical question).
Far too complicated to answer is an email.
-Sanjay
Thanks -- Frank
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
