said before, I have things working, only reporting this on the possibility
that it's a bug worth investigating.
thanks
mds
Andi Kleen wrote:
Mark Studebaker <[EMAIL PROTECTED]> writes:
I upgraded from 2.6.5 to 2.6.11.2 and my ancient (libc4 a.out) /sbin/portmap
from 1994 that's been r
said before, I have things working, only reporting this on the possibility
that it's a bug worth investigating.
thanks
mds
Andi Kleen wrote:
Mark Studebaker [EMAIL PROTECTED] writes:
I upgraded from 2.6.5 to 2.6.11.2 and my ancient (libc4 a.out) /sbin/portmap
from 1994 that's been running
I upgraded from 2.6.5 to 2.6.11.2 and my ancient (libc4 a.out) /sbin/portmap
from 1994 that's been running without complaint
on kernels for 11 years now consistently segfaults.
I upgraded to a version 4 RPM (circa 2002) and that fixed it.
If some compatibility was broken on purpose, that's fine,
I upgraded from 2.6.5 to 2.6.11.2 and my ancient (libc4 a.out) /sbin/portmap
from 1994 that's been running without complaint
on kernels for 11 years now consistently segfaults.
I upgraded to a version 4 RPM (circa 2002) and that fixed it.
If some compatibility was broken on purpose, that's fine,
is there a way to do this solely in i2c-core without having to
add support to all the drivers?
Corey Minyard wrote:
I have an IPMI interface driver that sits on top of the I2C code. I'd
like to get it into the mainstream kernel, but I have a few problems
to solve first before I can do that. The
is there a way to do this solely in i2c-core without having to
add support to all the drivers?
Corey Minyard wrote:
I have an IPMI interface driver that sits on top of the I2C code. I'd
like to get it into the mainstream kernel, but I have a few problems
to solve first before I can do that. The
6 matches
Mail list logo
