On Mon, Dec 10, 2012 at 6:30 PM, Robert Simmons wrote:
> I'm having a problem building google v8 on FreeBSD with clang. I get
> this error:
>
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> clang++: error: linker command failed with exit code 1 (use -v to see
> invocation)
On Sun, Dec 09, 2012 at 09:57:30AM -0800, Richard Sharpe wrote:
R> > lsof and sockstat can be helpful. lsof may be able to help determine if
R> > there's a leak because it MAY will find sockets not associated with a
R> > process.
R> >
R> > Hope this helps.
R>
R> Thanks Alfred. After following
>>Ronald writes:
>>> the last Alpha to be produced was shipped way back in 2004... eight years
>>> ago... with a top speed of 1.3 GHz I now have a cheap little media player
>>> thingy sitting on my desk, and _each_ of its two cores runs faster than tha\
t.
>>> In short, Alphas hardly constitute hig
I'm not seeing:
* any references to driver code that exhibits that very broken behaviour;
* any patches from you to implement NCQ on your nforce chipset;
* any offer of incentive to any developer to add that support.
Now, (1) is definitely worrying but as you've not provided any actual
infor
On 2012-Dec-11 15:43:21 -0500, Dieter BSD wrote:
>I care about data integrity, so things like ECC are on my must-have list.
Well, that's supported by all server CPUs (AMD Opteron, Intel Itanium,
Intel Xeon, Oracle/Sun SPARC) and some desktop CPUs (most AMD x86 chips).
>A high clock rate doesn't
Eitan was asking me to update the FAQ section 5.7:
*5.7.* Why do I get the error "kernel: proc: table is full"?
That error is no longer relevant, but I also seemed to find out
something else interesting..
Been grepping through the code, and it seems like the only side-effect
of maxproc chan
6 matches
Mail list logo
