On Fri 25 Jul 2008 at 07:57PM, [EMAIL PROTECTED] wrote:
> >As I said in the bug report, I hate having to do this, but I hate
> >bricking people's systems even more.
>
> Perhaps we do need to do this now but do we know from either Ethan
> and/or Jan where we are with
>
> 1979 libbe: be_activate needs to run installgrub
> http://defect.opensolaris.org/bz/show_bug.cgi?id=1979
>
> as I think it would be obviously better to just fix the issue. :-)
>
> I suppose refering to a URL on opensolaris.org is fine although I'm
> wondering if it's time to begin delivering knowledge articles under
> sun.com/msg.
Brock pointed out to me that current users won't get this message
anyway, since they won't be running the bits that contain the
message if they just type 'image-update' without first updating
their packaging bits to get the new 'pkg' which contains the
message.
I was specifically designing this for the *next* nasty flag day,
not for the one we have now. Although, if we were going to e.g.
issue an updated 2008.05 based ISO, then it'd be nice to get this
fix in there.
I guess my feeling was that to remove this message we'll need to:
1) Detect that SUNWipkg is downrev and abort with appropriate
instructions if so.
2) Ensure that we've got appropriate hook mechanisms in the
code in order to cope with flag days such as this.
I think we can try (offline) to make a list of all of the possible
flag day type scenarios we can imagine, and then work through them
to see what's common and what's unique about each.
Thanks,
-dp
--
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
