Re: critical floating point incompatibility

2009-01-26 Thread John Baldwin
On Friday 21 December 2007 3:16:33 pm Kostik Belousov wrote: > On Fri, Dec 21, 2007 at 10:11:24AM -0800, Bakul Shah wrote: > > Peter Jeremy wrote: > > > On Wed, Dec 19, 2007 at 09:40:34PM -0800, Carl Shapiro wrote: > > > >The default setting of the x87 floating point control word on the i386 > > >

WANTED! board models with Marvell 61XX chips

2009-01-26 Thread Søren Schmidt
Hi there! I thought I finally had a motherboard using one of the Marvell SATA/ PATA chips coming in, but unfortunately the delivery has been postponed to some unspecified date, oh well.. Thats where you come into the picture as I'd like to get another one, but finding boards that uses the

Re: threaded, forked, rethreaded processes will deadlock

2009-01-26 Thread Brian Fundakowski Feldman
On Thu, Jan 22, 2009 at 12:42:56AM -0500, Daniel Eischen wrote: > On Wed, 21 Jan 2009, David Schultz wrote: > >> I think there *is* a real bug here, but there's two distinct ways >> to fix it. When a threaded process forks, malloc acquires all its >> locks so that its state is consistent after a f

Re: write(2) to /dev/ad4 = EINVAL

2009-01-26 Thread Hans Petter Selasky
On Monday 26 January 2009, Lukasz Jaroszewski wrote: > 2009/1/26 Christoph Mallon : > > Lukasz Jaroszewski schrieb: > >> 2009/1/26 Hans Petter Selasky : > >>> On Monday 26 January 2009, Lukasz Jaroszewski wrote: Hi, > > It would be helpful, if you showed the actual code, instead of letting us > >

Re: freebsd-update's install_verify routine excessive stating

2009-01-26 Thread Oliver Fromme
Doug Barton wrote: > Oliver Fromme wrote: > > However, I think cmp wouldn't work here, because cmp only > > detects whether there is a difference between two files. > > > > In this case we need to know if one file is a subset of > > the other: For every hash there must be a .gz file, but

Re: write(2) to /dev/ad4 = EINVAL

2009-01-26 Thread Lukasz Jaroszewski
2009/1/26 Christoph Mallon : > Lukasz Jaroszewski schrieb: >> >> 2009/1/26 Hans Petter Selasky : >>> >>> On Monday 26 January 2009, Lukasz Jaroszewski wrote: Hi, after opening /dev/ad4 with success for O_RDWR, I am getting [EINVAL] from write(2), which according to man 2 write,

Re: write(2) to /dev/ad4 = EINVAL

2009-01-26 Thread Christoph Mallon
Lukasz Jaroszewski schrieb: 2009/1/26 Hans Petter Selasky : On Monday 26 January 2009, Lukasz Jaroszewski wrote: Hi, after opening /dev/ad4 with success for O_RDWR, I am getting [EINVAL] from write(2), which according to man 2 write, means `` [EINVAL] The pointer associated with

Re: write(2) to /dev/ad4 = EINVAL

2009-01-26 Thread Hans Petter Selasky
On Monday 26 January 2009, Lukasz Jaroszewski wrote: > 2009/1/26 Hans Petter Selasky : > > On Monday 26 January 2009, Lukasz Jaroszewski wrote: > >> Hi, > >> after opening /dev/ad4 with success for O_RDWR, I am getting [EINVAL] > >> from write(2), which according to man 2 write, means > >> ``

Re: write(2) to /dev/ad4 = EINVAL

2009-01-26 Thread Lukasz Jaroszewski
2009/1/26 Hans Petter Selasky : > On Monday 26 January 2009, Lukasz Jaroszewski wrote: >> Hi, >> after opening /dev/ad4 with success for O_RDWR, I am getting [EINVAL] >> from write(2), which according to man 2 write, means >> `` [EINVAL] The pointer associated with d was >> negative.

Re: write(2) to /dev/ad4 = EINVAL

2009-01-26 Thread Hans Petter Selasky
On Monday 26 January 2009, Lukasz Jaroszewski wrote: > Hi, > after opening /dev/ad4 with success for O_RDWR, I am getting [EINVAL] > from write(2), which according to man 2 write, means > `` [EINVAL] The pointer associated with d was > negative.'', as you can see below it is not true

write(2) to /dev/ad4 = EINVAL

2009-01-26 Thread Lukasz Jaroszewski
Hi, after opening /dev/ad4 with success for O_RDWR, I am getting [EINVAL] from write(2), which according to man 2 write, means `` [EINVAL] The pointer associated with d was negative.'', as you can see below it is not true, I have tried different block sizes, with same result. How ca