> Oh I agree, but I bet there's a lot of us who have
> been using, live
> upgrading, testing and providing feedback on SXCE
> since it was a stroppy
> teenager and haven't made the leap into the
> OpenSolaris realm. It's
> been too stable for its own good.
>
> --
> Ian.
>
Of course! I have
Shawn Walker wrote:
On Jan 4, 2010, at 7:10 PM, Ian Collins wrote:
Alan Coopersmith wrote:
Volker A. Brandt wrote:
Happy new year every1!
130 is the final SXCE release planned though, as previously announced.
Which is too bad, really. Maybe
On Jan 4, 2010, at 7:10 PM, Ian Collins wrote:
> Alan Coopersmith wrote:
>> Volker A. Brandt wrote:
>>
>>> Happy new year every1!
>>>
>>>
>>>
130 is the final SXCE release planned though, as previously announced.
>>> Which is too bad, really. Maybe the infrastructure to b
Alan Coopersmith wrote:
Volker A. Brandt wrote:
Happy new year every1!
130 is the final SXCE release planned though, as previously announced.
Which is too bad, really. Maybe the infrastructure to build SXCE
can be kept in place a little bit longer. The final release of SXCE
* Peter Tribble (peter.trib...@gmail.com) wrote:
> On Mon, Jan 4, 2010 at 9:24 PM, Glenn Lagasse wrote:
> >
> > Or, just use automated installer images produced on or after build 130
> > as they are now bootable on both SPARC and x86 and can perform an
> > automated installation using a default AI
On Mon, Jan 4, 2010 at 9:24 PM, Glenn Lagasse wrote:
>
> Or, just use automated installer images produced on or after build 130
> as they are now bootable on both SPARC and x86 and can perform an
> automated installation using a default AI client manifest directly from
> the media. This new funct
* Bob Palowoda (palow...@fiver.net) wrote:
> > On 12/31/2009 10:49 AM, Ron Halstead wrote:
> > > Will there be a OpenSolaris Nevada sxce snv_130 or
> > is it dead?
> >
> > Last I heard SXCE 130 was planned for release after
> > the Sun US
> > employees responsible for the release get back into
> >
Casper:
I've noticed that more and more things have stopped working in SXCE;
specifically X which is now only partially delivered (no Xnest) and,
unfortunately, GDM was upgraded so getting Sun Ray to work is impossible,
it seems, except by using dtlogin.
In our testing, the new GDM works well
>casper@sun.com wrote:
>> I've noticed that more and more things have stopped working in SXCE;
>> specifically X which is now only partially delivered (no Xnest) and,
>
>We've always only delivered the Xnest built on Xsun, so it's there on
>SPARC, been gone on x86 since we removed Xsun on x86
> On 12/31/2009 10:49 AM, Ron Halstead wrote:
> > Will there be a OpenSolaris Nevada sxce snv_130 or
> is it dead?
>
> Last I heard SXCE 130 was planned for release after
> the Sun US
> employees responsible for the release get back into
> the office
> next week. (Sun's US offices are closed for
> This is probably like the time when people had to cross the Red Sea. Either
> you wait and stay with the legacy Solaris releases, drown in the misery of
> awaiting your migration planning, or you start MIGRATING to the other side.
Well, it depends on what you define as "the other side". Sure I
ken mays wrote:
> Well, this is the year to cut 'the baby string' from SXCE and see if the OSOL
> Live CD can stand the test of time.
>
> SXCE contans a lot of legacy parts and I think a few years ago there was
> talk of the distro constructor creating a larger OSOL Live DVD that replaced
> SXC
--- On Sun, 1/3/10, W. Wayne Liauh wrote:
> From: W. Wayne Liauh
> Subject: Re: [osol-discuss] snv_130
> To: opensolaris-discuss@opensolaris.org
> Date: Sunday, January 3, 2010, 5:21 AM
> > The time you need to install
> OpenSolaris is much
> > larger than installi
> The time you need to install OpenSolaris is much
> larger than installing
> SXCE, mostly trying to find which packages you've
> missed this time.
>
> Casper
>
This kind of "extra" effort is NOTHING compared to what those of us who are
moving from Linux to Solaris/OpenSolaris have to go throu
casper@sun.com wrote:
> I've noticed that more and more things have stopped working in SXCE;
> specifically X which is now only partially delivered (no Xnest) and,
We've always only delivered the Xnest built on Xsun, so it's there on
SPARC, been gone on x86 since we removed Xsun on x86 in snv_
Volker A. Brandt wrote:
> Happy new year every1!
>
>
>> 130 is the final SXCE release planned though, as previously announced.
>
> Which is too bad, really. Maybe the infrastructure to build SXCE
> can be kept in place a little bit longer. The final release of SXCE
> could then be cut in sync
[...]
> I've noticed that more and more things have stopped
> working in SXCE;
> specifically X which is now only partially delivered
> (no Xnest) and,
[...]
Isn't Xephyr there? In a number of situations, that's worked better
for me than Xnest.
--
This message posted from opensolaris.org
___
> I've noticed that more and more things have stopped working in SXCE;
> specifically X which is now only partially delivered (no Xnest) and,
> unfortunately, GDM was upgraded so getting Sun Ray to work is impossible,
> it seems, except by using dtlogin.
Hmmm... what would you consider the version
>Happy new year every1!
>
>
>> 130 is the final SXCE release planned though, as previously announc=
>ed.
>
>Which is too bad, really. Maybe the infrastructure to build SXCE
>can be kept in place a little bit longer. The final release of SXCE
>could then be cut in sync with the official OS 2010.0
Happy new year every1!
> 130 is the final SXCE release planned though, as previously announced.
Which is too bad, really. Maybe the infrastructure to build SXCE
can be kept in place a little bit longer. The final release of SXCE
could then be cut in sync with the official OS 2010.02 release.
Shawn Walker wrote:
> I should also note that many users are able to run b130 without issue,
> or with relatively minor workarounds. I'm one of them; it worked first
> boot.
It depends...
While it was possible to run Solaris versions from 2009 on Dell (based on Intel
Chipsets but not using
On 12/31/2009 1:11 PM, Anon Y Mous wrote:
Happy New Year all. Will there be a OpenSolaris Nevada sxce snv_130 or is it
dead?
--ron
I hope not. They should probably just skip snv_130 and go straight to snv_131
if the Solaris Express version is going to be anywhere near as buggy as the
blee
On 12/31/2009 10:49 AM, Ron Halstead wrote:
Will there be a OpenSolaris Nevada sxce snv_130 or is it dead?
Last I heard SXCE 130 was planned for release after the Sun US
employees responsible for the release get back into the office
next week. (Sun's US offices are closed for a winter holiday
On 12/31/09 03:11 PM, Anon Y Mous wrote:
Happy New Year all. Will there be a OpenSolaris Nevada sxce snv_130 or is it
dead?
--ron
I hope not. They should probably just skip snv_130 and go straight to snv_131
if the Solaris Express version is going to be anywhere near as buggy as the
bleed
> Happy New Year all. Will there be a OpenSolaris Nevada sxce snv_130 or is it
> dead?
> --ron
I hope not. They should probably just skip snv_130 and go straight to snv_131
if the Solaris Express version is going to be anywhere near as buggy as the
bleeding edge Indiana version was.
If they
Will there be a OpenSolaris Nevada sxce snv_130 or is it dead?
--ron
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Tue, 2009-12-29 at 12:19 +0100, solarg wrote:
> Le 28/12/09 11:00, solarg a écrit :
> >
> > On 12/26/09 11:45 AM, Adrian Carpenter wrote:
> >>
> >> I have just got the kernel to start by passing:
> >>
> >> acpi-user-options=0x8 (which I google told me to try to look for IDE
> >> timeouts)
> >
>
Le 28/12/09 11:00, solarg a écrit :
On 12/26/09 11:45 AM, Adrian Carpenter wrote:
I have just got the kernel to start by passing:
acpi-user-options=0x8 (which I google told me to try to look for IDE
timeouts)
i have the hang problem with a Sun Ultra 20 (old ultra20, not M2)
upgraded from b1
On 12/26/09 11:45 AM, Adrian Carpenter wrote:
I have just got the kernel to start by passing:
acpi-user-options=0x8(which I google told me to try to look for IDE
timeouts)
i have the hang problem with a Sun Ultra 20 (old ultra20, not M2)
upgraded from b129 (amd opteron 152) but it doesn
> There's a known problem in snv_130, fixed in snv_131:
Any idea when an OpenSolaris Indiana version based on snv_131 will be put on
genunix.org and in the /dev repository so we can either install or pkg
image-update to it?
I've been having a really rough time with updates from snv_111b to the
My machine is a homebrew based on:
AMD Athlon 64 3200+
ECS GS7610 Motherboard
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Adrian Carpenter wrote:
Just upgraded snv_129 to snv_130 but unfortunately it doesn't get past:
SunOS Release 5.11 Version snv_130 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved
Use is subject to license terms.
_ (blinking cursor)
Any hints? suggestions for working out
I have just got the kernel to start by passing:
acpi-user-options=0x8(which I google told me to try to look for IDE
timeouts)
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
did you use fast reboot? If yes, try normal boot. Had this, too, after i used
"reboot".
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Just upgraded snv_129 to snv_130 but unfortunately it doesn't get past:
SunOS Release 5.11 Version snv_130 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved
Use is subject to license terms.
_ (blinking cursor)
Any hints? suggestions for working out whats afoot?
Adrian
--
35 matches
Mail list logo