Oh, and with regards to the release notes, this too should help:
http://blogs.sun.com/observatory/entry/release_notes
Regards,
Brian
W Brian Leonard wrote:
> Hi Frank,
>
> The following should help:
>
> http://blogs.sun.com/observatory/entry/updating_to_a_specific_build
>
> Regards,
> Brian
>
>
Hi Frank,
The following should help:
http://blogs.sun.com/observatory/entry/updating_to_a_specific_build
Regards,
Brian
Frank Grimes wrote:
> Sorry, I'm not sure which release notes you're referring to...
>
> I read the bug you mentioned and I must admit that I understood almost none
> of it.
http://blogs.sun.com/observatory/entry/updating_to_a_specific_build
-- Alan
On 03/16/10 06:38 AM, Frank Grimes wrote:
> Sorry, I'm not sure which release notes you're referring to...
>
> I read the bug you mentioned and I must admit that I understood almost none
> of it.
>
> So, if I understood
Sorry, I'm not sure which release notes you're referring to...
I read the bug you mentioned and I must admit that I understood almost none of
it.
So, if I understood what you're saying, if I update to 132 then update to 134
it should work?
If so, how do I update to a specific build using the p
Frank Grimes wrote:
> It looks like the following bug is back:
> http://opensolaris.org/jive/thread.jspa?threadID=121582
Yes - if you upgrade to 133 or later without going through 132 on the way, you
hit:
http://defect.opensolaris.org/bz/show_bug.cgi?id=14906
> I had to revert back to 1
It looks like the following bug is back:
http://opensolaris.org/jive/thread.jspa?threadID=121582
I had to revert back to 131 to get the terminal in gnome working correctly
again.
--
This message posted from opensolaris.org
