Ken,
That is pretty much my impression as well, that even SXCE is a walking dead man.
I am okay with the SXDE/SXCE branches getting pruned as long as Sun provides a
method to "live upgrade" from them to OpenSolaris. If they fail to do that,
then SXDE/SXCE users were abandoned. The machine with
John wrote:
> Ken,
> That is pretty much my impression as well, that even SXCE is a walking dead
> man.
> I am okay with the SXDE/SXCE branches getting pruned as long as Sun provides
> a method to "live upgrade" from them to OpenSolaris. If they fail to do
> that, then SXDE/SXCE users were aban
John writes:
> I don't know why we all need to speculate on what is going to happen on SXDE,
> SXCE, and opensolaris. Is it too much to ask for somebody in charge to build
> a development roadmap that is both accurate, detailed (with real dates), and
> maintained? Even if SXCE and openSolaris
>>LU effectively disappears in the OpenSolaris distribution (replaced by
>>'beadm' and IPS snap upgrades), so that's mostly a "no."
When will beadm show up on Solaris 10 and OpenSolaris snv_bxx and does this
impact thel support of lucreate and luupgrade commands?
Also will OpenSolaris 2008.05 Live
John Brewer writes:
> >>LU effectively disappears in the OpenSolaris distribution (replaced by
> >>'beadm' and IPS snap upgrades), so that's mostly a "no."
> When will beadm show up on Solaris 10
Never, I expect.
> and OpenSolaris snv_bxx
It's there now. It's been there for some time in the Ope
Shawn Walker wrote:
> John wrote:
>> Ken,
>> That is pretty much my impression as well, that even SXCE is a walking dead
>> man.
>> I am okay with the SXDE/SXCE branches getting pruned as long as Sun provides
>> a method to "live upgrade" from them to OpenSolaris. If they fail to do
>> that, th
This confusion is why I added this to my own Solaris mini-site:
What is opensolaris?
Opensolaris is three things:
1. A codebase that consists of most of Sun Solaris. (Some elements which
could not be open-sourced are not inc
I need to know to the code or password of maintenance administrator since the
install program asks for me and not it encounter by no side. Thanks
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@openso
OK , opensolaris distribution project indiana evolved from and now replaces
sxde [opensolaris.com]. Its here to stay.? Solaris express project nevada sxce
is now in limited release or will go away [opensolaris.org].??
Did sun have a release which belenix, martux mbe, nexentaos,and schillix
bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to get coloured syntax highlighting working in vim, and after
a lot of work it looks like i'm going to have to compile my own vim,
using ncurses.
Ncurses requires math.h but I can't find which package provides it.
A pointer to the package
On 21/08/2008, at 10:59 AM, john kroll wrote:
> OK , opensolaris distribution project indiana evolved from and now
> replaces sxde [opensolaris.com]. Its here to stay.? Solaris express
> project nevada sxce is now in limited release or will go away
> [opensolaris.org].??
At some stage in t
I probably should have mentioned, I'm running SXCE (snv_95). I've tried
all the TERM=xtermc, TERM=xterm-color stuff, and I'm still in black and
white.
Thanks
Matt
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Wed, Aug 20, 2008 at 6:24 PM, Matt Harrison
<[EMAIL PROTECTED]> wrote:
> I probably should have mentioned, I'm running SXCE (snv_95). I've tried
> all the TERM=xtermc, TERM=xterm-color stuff, and I'm still in black and
> white.
I have the following in my .vimrc:
:if has("terminfo")
: set
* Matt Harrison ([EMAIL PROTECTED]) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm trying to get coloured syntax highlighting working in vim, and after
> a lot of work it looks like i'm going to have to compile my own vim,
> using ncurses.
You don't mention what OS you're trying
* Matt Harrison ([EMAIL PROTECTED]) wrote:
> I probably should have mentioned, I'm running SXCE (snv_95). I've tried
> all the TERM=xtermc, TERM=xterm-color stuff, and I'm still in black and
> white.
Works just fine for me on SXCE 92 (and thus it should work just fine on
95). I'm setting TERM=x
Mike Gerdts wrote:
> On Wed, Aug 20, 2008 at 6:24 PM, Matt Harrison
> <[EMAIL PROTECTED]> wrote:
>> I probably should have mentioned, I'm running SXCE (snv_95). I've tried
>> all the TERM=xtermc, TERM=xterm-color stuff, and I'm still in black and
>> white.
>
> I have the following in my .vimrc:
>
Glenn Lagasse wrote:
> * Matt Harrison ([EMAIL PROTECTED]) wrote:
>> I probably should have mentioned, I'm running SXCE (snv_95). I've tried
>> all the TERM=xtermc, TERM=xterm-color stuff, and I'm still in black and
>> white.
>
> Works just fine for me on SXCE 92 (and thus it should work just fi
* Matt Harrison ([EMAIL PROTECTED]) wrote:
> Glenn Lagasse wrote:
>> * Matt Harrison ([EMAIL PROTECTED]) wrote:
>>> I probably should have mentioned, I'm running SXCE (snv_95). I've
>>> tried all the TERM=xtermc, TERM=xterm-color stuff, and I'm still in
>>> black and white.
>>
>> Works just fine
The one in /opt/sfw can produce 64bit code but is a 32bit binary. I couldn't
get a later version to compile, or if I did, it complained about not being able
to produce 64bit code even though the binary was 64bit.
Anybody have this package or can tar it up and be willing to share? Or can give
in
19 matches
Mail list logo
