+-- Tom Wickline wrote (Thu, 14-Oct-2010, 11:16 +0800):
| On Thu, Oct 14, 2010 at 12:26 AM, Charles Seeger wrote:
|
| > FWIW... six weeks ago I tried Skype with a self-compiled wine 1.2 release.
| > It ran long enough to register a new account, but it crashed immediately
| > after that. I did
Hi
I came across this article
http://wiki.openindiana.org/pages/viewpage.action?pageId=4882475 on using a
heavily patched 134 kernel for OI, so I just wonder - will 148 be based on
using this 134+ kernel, or will this kernel be available as a choice in 148, or
will us storage folks need to bui
all,
I installed build 147 via the upgrade method from osol b 134 recently,
and it's working fine, with one ... interesting effect though:
When I log into a GUI (seen this with KDE and gnome and two different
accounts), "the system" (ie X) thinks my screen is 3200 pixels wide,
which would be nice
* Edward Ned Harvey [2010-10-14 12:15]:
> You guys have been busy, nice job! ;-)
>
>
>
> I am wondering how much similarity there is between OI and osol? Would it
> be fair to say oi 147 is approx what osol 147 would have been?
OI 147 is roughly the same as OS b147 would have been, there ar
Hello,
* Alexandre Borges [2010-10-14 12:15]:
> Mrs. and Ms,
>
> Good evening. Yesterday I sent an e-mail to Alasdair about my
> interest in contributing to OpenIndiana/Illumos documentation.
>
> As I explained to him, I'm instructor at Sun/Oracle since 2001 in
> Sao Paulo, Brazil. I'm currentl
* Roy Sigurd Karlsbakk [2010-10-14 12:15]:
> Hi
>
> I came across this article
> http://wiki.openindiana.org/pages/viewpage.action?pageId=4882475 on using a
> heavily patched 134 kernel for OI, so I just wonder - will 148 be based on
> using this 134+ kernel, or will this kernel be available a
sorry to reply to myself ...
On Thu, Oct 14, 2010 at 12:52, Michael wrote:
> all,
>
> I installed build 147 via the upgrade method from osol b 134 recently,
> and it's working fine, with one ... interesting effect though:
>
> When I log into a GUI (seen this with KDE and gnome and two different
>
* Michael [2010-10-14 14:02]:
> it seems all I have from nvidia is the driver that came w. osol 134 -
> could that be the case (even then, I can't remember seeing this with
> any build of osol)?
Yes, OpenIndiana does not provide newer versions of the closed
Nvidia driver.
--
Guido Berhoerster
hi all
http://wiki.openindiana.org/pages/viewpage.action?pageId=4882475 <-- this talks
about a stable 134+ build, which seems an extremely good idea for an
opensolaris 134 replacement.
Now, is there a place where this is available either in complete source code
for me to build, or as a binary
> From: Guido Berhoerster [mailto:g...@openindiana.org]
>
> We definetly have our own roadmap and goals, that is to provide
> stable releases with free security and bug fixes. Oracle and
> Illumos are our upstream on which we add some branding and
> usability changes and in the future also additio
Edward Ned Harvey wrote:
>> From: Guido Berhoerster [mailto:g...@openindiana.org]
>>
>> We definetly have our own roadmap and goals, that is to provide
>> stable releases with free security and bug fixes. Oracle and
>> Illumos are our upstream on which we add some branding and
>> usability changes
Hello all,
This probably has a very simple answer (I hope). I have been fighting
with this for days. I installed the R package from blastwave, works
fine. Trying to get Rcommander installed. The required package aplpack
keeps kicking out due to
Error in firstlib(which.lib.loc, package)
* Edward Ned Harvey [2010-10-14 16:19]:
> That's really excellent, cuz that was always a downfall for opensolaris.
> "You want what? Security bugfixes? Downgrade to solaris 10 and pay, and
> you can get those updates." The end result was IT discomfort and fear to
> put either one into public in
On Thu, Oct 14, 2010 at 1:26 AM, Charles Seeger wrote:
> In the meantime, the https://imo.im/ Skype web proxy seems to work,
Don't forget: https://imo.im/privacy.html — that completely stops me
from using it.
--
Kind regards, BM
Things, that are stupid at the beginning, rarely ends up wisely.
> From: Alan Coopersmith [mailto:alan.coopersm...@oracle.com]
>
> If you were going to pay, just
> pay
> for the OpenSolaris support that includes security fixes in the
> OpenSolaris
Pay for what now? Opensolaris support? I didn't even know there was such a
thing. And even now, browsing openso
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edward Ned Harvey wrote:
>
> Pay for what now? Opensolaris support? I didn't even know there
> was such a thing. And even now, browsing opensolaris.com to look
> for it specifically ... I still don't see it. I bet they don't
> sell much of it as a
Daniel,
Haven't yet built it on openIndiana; we are R users ourselves, also on Solaris
10 (SPARC).
Rather than Blastwave, we'd used SunFreeware's R package - in fact, asked Steve
to build with The R_HOME option, so as to support the shared lib model option
in R. Don't know if blastwave bui
Excellent, I will try the sunfreeware version instead and let you know what
happens. I am installing on OI 147 on a V40z with 4x2.5 dual core opterons
and 32gb of ram.
On Thu, Oct 14, 2010 at 2:06 PM, Lou Picciano wrote:
> Daniel,
>
>
> Haven't yet built it on openIndiana; we are R users ours
+-- Guido Berhoerster wrote (Thu, 14-Oct-2010, 14:15 +0200):
| * Michael [2010-10-14 14:02]:
| > it seems all I have from nvidia is the driver that came w. osol 134 -
| > could that be the case (even then, I can't remember seeing this with
| > any build of osol)?
|
| Yes, OpenIndiana does not
On 13 Oct 2010, at 15:36, russell wrote:
> Hi,
>
> While OpenIndiana (OpenSolaris/Solaris) provide 32 and 64 bit libraries for
> building 64 bit applications.
> However if you want to include bindings to Perl for example, the version
> shipped with OpenIndiana is 32bit including it libraries. S
On Thursday, 14 October, 2010 14:19, "Alasdair Lumsden"
said:
> Hi Russell,
>
> That looks like an oversight in the OS worth addressing.
>
> I imagine getting a combined 32/64bit perl on the system would be very
> difficult,
> given perl modules install native extensions. Essentially you'd ne
Alasdair,
I'd lobby for the separate directory approach. We were running into this in
openSolaris, when trying to build PostgreSQL. Our issues were related to
multiple versions of perl, granted, not multiple architectures.
There was a bit of back-and-forth as to whether it was an 'OS layout
Guido Berhoerster,
Good evening. Thanks for your answer.
In fact, I don't have an account in wiki. I'll join #oi-dev, ask for one and
add myself to Documentation team.
After that, I'll prepare a list of possible tutorials to write. I belive
that be necessary to write a kind of "tutorial seri
Daniel and Lou,
If you're happy with the sunfreeware build of R, that's fine. You can
continue to use both sunfreeware and Blastwave on OpenIndiana, but I
should point out they're primarily targeted toward Solaris 10 and
earlier where proper integration with the system software was not
possible.
On 14 Oct 2010, at 22:31, Kevin J. Woolley wrote:
> I don't believe a combined 32/64-bit Perl is possible. If it was, it'd still
> be pretty icky, from an implementation point of view. (Is it possible for a
> 64-bit binary to dynamically load 32-bit libs? I'm pretty sure the reverse
> isn't
On Thursday, 14 October, 2010 17:09, "Alasdair Lumsden"
said:
> So perhaps not too impossible, and hopefully not too icky. Just need someone
> who
> has the time to implement it, either by modifying/extending the SFW Perl 5.10
> build, or to replace that with a JDS style specfile.
Ah, a mixed
Good to know, Albert,
I've put a few feelers out about 'Best Practices' in this Brave New World in
the last couple of weeks... Trying to be not only a good citizen, but a
contributor, as well.
Yours is a good, concrete pointer. Thanks! Lou Picciano
- Original Message -
From: "Alb
27 matches
Mail list logo