Re: [OpenIndiana-discuss] XEN and Crossbow

2010-09-24 Thread Emanuele Pucciarelli
Hello Boris! > I followed standard procedure suggested by Mark Johnson to install OI 147 as > PV DomU at Xen 4.0.1 Linux Dom0 (2.6.32.21 pvops ) , like i would work with > OSOL 134 ( BTW, OSOL 134 gets installed with no problem) . > Installation crashes right away I installed OI 147 from the ISO

Re: [OpenIndiana-discuss] IPS on pkg.openindiana.org "Framework stall"

2010-09-27 Thread Emanuele Pucciarelli
On Mon, Sep 27, 2010 at 13:01, Volker A. Brandt wrote: > It is possible that your problem with pkg-1.de is related. Symptoms > are that the machine works fine and then suddenly is not reachable > for 5-20 minutes, then works fine again.  No error messages, no > faults, are visible in the server lo

Re: [OpenIndiana-discuss] IPS on pkg.openindiana.org "Framework stall"

2010-09-27 Thread Emanuele Pucciarelli
On Mon, Sep 27, 2010 at 15:38, Jesus Cea wrote: > I am using Solaris 10, and disabling DAD kill networking in Zones. What > a pain... Apparently there was no such problem with OpenSolaris (I'm running b127 on that box at the moment). Zones kept working just fine. But this is very handy to know be

Re: [OpenIndiana-discuss] gcc linker

2010-10-12 Thread Emanuele Pucciarelli
On Tue, Oct 12, 2010 at 09:09, Edward Martinez wrote: > I'm not very knowledgeable about gcc, so   is there a way to change the gcc > Id  without compiling, like, adding a environmental variable  or do i need > to compile gcc with the correct id? I'm not knowledgeable about LibreOffice, but in g

Re: [OpenIndiana-discuss] Solaris 11 Express available

2010-11-17 Thread Emanuele Pucciarelli
On Wed, Nov 17, 2010 at 09:27, Nikola M wrote: > Only way you can be sure is when you use OS that is Open Source. > Everything closed makes very much reasonable to be paranoid. This is not true. The paranoid have to agree with Ken Thompson: http://cm.bell-labs.com/who/ken/trust.html . If one cla

Re: [OpenIndiana-discuss] SunStudio

2010-11-17 Thread Emanuele Pucciarelli
Hi, > The following code snipped from /usr/include/sigc++-2.0/sigc++/signal.h > shows how the two compilers handle things: [...] Sun Studio may very well have bugs, but I have a hunch that this one isn't really a bug: it just depends on what STL implementation you are using. If I am not mistaken