W. Wayne Liauh wrote:
Hi Jim,
This is a great proposal, I will be more than happy to participate.
I'll start working on a project proposal.
There are some others interested in helping out with a
beta test project.
Cheers,
Jim
___
indiana-discuss
On Wed, 25 Feb 2009 19:05:15 PST, you wrote:
> Last night (or I should say this morning) I stayed up until
> 2 am (or 7 am EST), because someone stated that he has no
> problem booting build 107 in VirtualBox (see one of the
> previous posts in this thread). I tried, tried, and tried.
> Same darn
> >> 1) Are there any simple procedures to check for
> error
> >> log output in the event of bugs as I described?
> >
> > Suppose build 107 is in your boot environment (BE)
> "opensolaris-2", which you have failed to boot into,
> and you are now booting into build 106, which has
> been installed a
W. Wayne Liauh wrote:
>> 1) Are there any simple procedures to check for error
>> log output in the event of bugs as I described?
>
> Suppose build 107 is in your boot environment (BE) "opensolaris-2", which you
> have failed to boot into, and you are now booting into build 106, which has
> been
> 1) Are there any simple procedures to check for error
> log output in the event of bugs as I described?
Suppose build 107 is in your boot environment (BE) "opensolaris-2", which you
have failed to boot into, and you are now booting into build 106, which has
been installed as BE opensolaris-1 .
In the spirit of contributing something useful to this thread, I have a few
questions.
First of all, I'm running OpenSolaris in VirtualBox 2.1.4. Build 107 didn't
boot for me once I installed the VirtualBox additions. I'm not sure why, and
I'm not familiar with the procedures to check the e
> W. Wayne Liauh wrote:
> > If the development team is short on hands,
> ostensibly due to RIFs, then
> > perhaps someone in control could try to enlist
> some of us (non-Sun) for the
> > pre-release (i.e., release of a build) testing.
> Anyway, the priority is to
> > get the job done right.
>
>
W. Wayne Liauh wrote:
If the development team is short on hands, ostensibly due to RIFs, then
> perhaps someone in control could try to enlist some of us (non-Sun) for the
> pre-release (i.e., release of a build) testing. Anyway, the priority is to
> get the job done right.
Wayne,
The testing
I think Glenn and Shawn captured things nicely in their responses. The
only thing I have to add is there has been a bug opened in the
VirtualBox bug tracking system
X server does not start w/Guest Additions on OpenSolaris guest
w/snv_107 packages
http://www.virtua
* W. Wayne Liauh (w...@hawaiilinux.us) wrote:
*SNIP*
> Talk is cheap, OK. Just show me the beef.
And here I thought we were capable of having an intelligent
discussion. It seems I was wrong. It's responses like this that
really make me wonder why I bother trying to educate people with
rationa
> * W. Wayne Liauh (w...@hawaiilinux.us) wrote:
> > > If you don't want to run the risk of running into
> > > surprises, then don't
> > > run the development builds.
> >
> > Don't give me that *($&@#$^& PLEASE!
>
> Let's keep things civil, shall we. No need to shout.
>
> > Only two, or at m
W. Wayne Liauh wrote:
If you don't want to run the risk of running into
surprises, then don't
run the development builds.
Don't give me that *($&@#$^& PLEASE!
You were given a reasonable, well thought-out response and there is no
good reason to respond that way.
A time-based release sc
* W. Wayne Liauh (w...@hawaiilinux.us) wrote:
> > If you don't want to run the risk of running into
> > surprises, then don't
> > run the development builds.
>
> Don't give me that *($&@#$^& PLEASE!
Let's keep things civil, shall we. No need to shout.
> Only two, or at most three, more mont
> If you don't want to run the risk of running into
> surprises, then don't
> run the development builds.
Don't give me that *($&@#$^& PLEASE!
Only two, or at most three, more months to the scheduled official "release"
date (according to your "definition"). As one very honorable person once
* W. Wayne Liauh (w...@hawaiilinux.us) wrote:
> > We try to document the known issues with each build
> > via the release
> > notes. In many cases, some of the issues won't be
> > seen from internal
> > testing for whatever reason (lack of certain
> > hardware, limited testing
> > in other locales
> We try to document the known issues with each build
> via the release
> notes. In many cases, some of the issues won't be
> seen from internal
> testing for whatever reason (lack of certain
> hardware, limited testing
> in other locales, different set of packages
> installed). As each set of
>
Hey,
On 25/02/2009, at 12:16 PM, david.co...@sun.com wrote:
Bug reporting is important, but personally I think it is equally
important that some of us be forewarned about certain build(s)--and
share the info--so we can make optimized choice of our time as to
whether we should save our efforts f
Bug reporting is important, but personally I think it is equally
important that some of us be forewarned about certain build(s)--and
share the info--so we can make optimized choice of our time as to
whether we should save our efforts for subsequent builds.
We try to document the known issues wit
Hi Alan,
Finally, I was advised two workarounds to run b107 with Japanese
environment
1) workaround for 6799381 (setlocale fails against ja_JP.UTF-8)
% cd /usr/lib/locale/ja_JP.UTF-8
% ln -s ../common/methods_unicode.so.3 .
2) workaround for 6801598 (Xorg 1.5 ignores kernel keyboard layout
s
W. Wayne Liauh wrote:
> One of Sun's bloggers in Japan specializing in OpenSolaris (Solaris 3分 クッキング)
> reported that image-update from 106 failed (今回は pkg image-update ではなく), so
> he booted from the build 107 LiveUSB instead.
>
> After having selected the Japanese keyboard and JP locale, he wa
This is bug 6799381 (setlocale fails against ja_JP.UTF-8).
It will be fixed in snv_109. Workaround is as follows.
% cd /usr/lib/locale/ja_JP.UTF-8
% ln -s ../common/methods_unicode.so.3 .
Thanks,
Fuyuki
W. Wayne Liauh wrote:
One of Sun's bloggers in Japan specializing in OpenSolaris (Solaris 3
> I gave a list of the problems expected from the X.Org
> build - failure to boot is
> not one of them. There's only a small window left
> to get fixes in for the
> 2009.06 release (a few more weeks for non-stopper bug
> fixes), so if you hit a
> bug that isn't on the list I posted, you need to f
Hi:
I must see that in my case, the upgrade went pretty smooth. The only
precautions I had to take were:
- The workaround to install correctly libc.so.
- The removal of the RgbPath line in xorg.conf file, because I have a
nVidia card with TwinView (it helped me to have tested the beta
binaries of
> > The problems of build 107 are so numerous and so
> severe, there is very
> > little we non-developers can do. As I mentioned
> several times in
> > separate threads, I have downloaded and installed
> every SXCE (or
> > equivalent) build since nv20, and this one is
> exceptionally bad.
>
> Act
david.co...@sun.com wrote:
The problems of build 107 are so numerous and so severe, there is very
little we non-developers can do. As I mentioned several times in
separate threads, I have downloaded and installed every SXCE (or
equivalent) build since nv20, and this one is exceptionally bad.
A
The problems of build 107 are so numerous and so severe, there is very
little we non-developers can do. As I mentioned several times in
separate threads, I have downloaded and installed every SXCE (or
equivalent) build since nv20, and this one is exceptionally bad.
Actually, many people have su
> other related problems (also kudos to VirtualBox).
BTW there is an interesting comment about Sun xVM VirtualBox in ComputerWorld:
"There may be better desktop virtualization programs available than VirtualBox,
but I haven't found one yet."
http://tinyurl.com/CompWorld-VB
Many of us would lik
> Alan Coopersmith wrote:
> > W. Wayne Liauh wrote:
> >
> >> With 2.1.4, I am able to install the Guest
> Addition. However, Build 107 now won't boot again
> with the installation of the GA. :-(
> >>
> >> As AlanC (?) mentioned in a separate thread, Build
> 107 involves major (an understatemen
Alan Coopersmith wrote:
W. Wayne Liauh wrote:
With 2.1.4, I am able to install the Guest Addition. However, Build 107 now
won't boot again with the installation of the GA. :-(
As AlanC (?) mentioned in a separate thread, Build 107 involves major (an
understatement) changes in X.org, many
W. Wayne Liauh wrote:
> With 2.1.4, I am able to install the Guest Addition. However, Build 107 now
> won't boot again with the installation of the GA. :-(
>
> As AlanC (?) mentioned in a separate thread, Build 107 involves major (an
> understatement) changes in X.org, many problems are expect
> Both are deficiences in VirtualBox 2.1.2, partly VBox
> itself, partly the guest additions for Solaris.
> Solved in 2.1.4, and you will love the improved
> speed.
> --
> ( Kees Nuyt
> )
> c[_]
With 2.1.4, I am able to install the Guest Addition. However, Build 107 now
won't boot again with
On Thu, 19 Feb 2009 13:10:38 PST, you wrote:
> 2. I then downloaded and installed the os0906_107 iso
> image (with VirtualBox, this does not take any effort).
> The installation was successful (I am posting this
> message from build 107), however, the initial booting
> took several minutes, and i
> > This has been discussed many times now:
> >
> http://defect.opensolaris.org/bz/show_bug.cgi?id=6331
>
> This is a totally different problem. In the
> subsequent process of diagnosis and re-installing, I
> might have further screwed up something else (big
> time). Now I don't even have the GR
On Wed, 18 Feb 2009 15:59:49 PST, W. Wayne Liauh wrote:
> Just image-updated from 106 to 107,
> running under VirtualBox 2.1.2 in Vista.
That VBox version has issues between Xorg software and VBox
guest additions, which appear to be solved in VirtualBox
2.1.4 (which is also much faster than 2.1
> This has been discussed many times now:
> http://defect.opensolaris.org/bz/show_bug.cgi?id=6331
This is a totally different problem. In the subsequent process of diagnosis
and re-installing, I might have further screwed up something else (big time).
Now I don't even have the GRUB screen. Th
This has been discussed many times now:
http://defect.opensolaris.org/bz/show_bug.cgi?id=6331
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indian
> Just image-updated from 106 to 107, running under
> VirtualBox 2.1.2 in Vista. Reboot failed. Tried
> twice, same failure, required a "hard" powering off
> (i.e., clicking on the "power off the machine" button
> for the VM).
>
> I have booted back to build 106. Don't have time to
> investigat
Just image-updated from 106 to 107, running under VirtualBox 2.1.2 in Vista.
Reboot failed. Tried twice, same failure, required a "hard" powering off
(i.e., clicking on the "power off the machine" button for the VM).
I have booted back to build 106. Don't have time to investigate it now. Any
38 matches
Mail list logo
