On Wed, Feb 25, 2009 at 1:51 PM, Shawn Walker
swal...@opensolaris.org wrote:
Sorry, I failed to understand it's annoying. Isn't
it just sitting
there? For the En-users,
what else need to do to input?
Let me count the ways it annoyed me:
* pointless use of resources unless you need
I had an issue with my /etc/X11/xorg.conf because I had made some
changes to suit Nvidia TwinView which broke gdm for me, moving it
sideways allowed gdm to launch correctly. But the systems you describe
where the same.
-James
Amit k. Saha wrote:
On Tue, Feb 24, 2009 at 8:21 PM, Greg Palmer
Yu Xiangning wrote:
Fuyuki Hasegawa - Sun Microsystems wrote:
Hi Aubrey,
Yap, I agree the feedbacks might not be enough, but we never can
meet all users's need... you know. :(
All locales except English (en_XX.UTF-8) still show iiim-panel by
default.
I don't understand why UTF-8 is an
Ghee Teo wrote:
Yu Xiangning wrote:
Fuyuki Hasegawa - Sun Microsystems wrote:
Hi Aubrey,
Yap, I agree the feedbacks might not be enough, but we never can
meet all users's need... you know. :(
All locales except English (en_XX.UTF-8) still show iiim-panel by
default.
I don't understand
* 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 months to the
Yu Xiangning wrote:
Fuyuki Hasegawa - Sun Microsystems wrote:
Hi Aubrey,
Yap, I agree the feedbacks might not be enough, but we never can
meet all users's need... you know. :(
All locales except English (en_XX.UTF-8) still show iiim-panel by
default.
I don't understand why UTF-8 is an
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
* 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
* 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
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
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
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,
Hello William,
Tuesday, February 24, 2009, 10:35:48 PM, you wrote:
WY Hi,
WY 6436517 is in the valex gate
WY 6753297 is soon to be in the valex gate as it seemed to show up in
WY relation to extended attributes (5105654)
WY There is not yet an ETA for valex integration but 6436517 6753297
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
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 .
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
The OpenSolaris development package repository
http://pkg.opensolaris.org/dev/
has been updated to reflect the changes in snv_108 for both x86/x64 and
SPARC platforms. This update also includes fixes to the Caiman Slim
Install and the Image Packaging System (IPS).
Users who wish to
hello all,
is it possible to have unison in os2008.11?
he...@delljm:~$ pfexec pkg install SUNWunison
Creating Plan /
pkg: the following package(s) violated constraints:
Package pkg:/sunwli...@0.5.11,5.11-0.108 conflicts with constraint
in installed pkg:/entire:
19 matches
Mail list logo
