It's an RTFM - see FAQ on www.xfree86.org (search for libc - it's
somewhere nearby). Just replace arch/i386/kernel/ioport.c from 2.0.33
with one from a recent 2.1.* kernel (I used one from '92 and it worked
fine).
To the original poster: I recently (about a week ago) went through the
process of upgrading my system (slackware) from 2.0.33/libc5/gcc 2.7.*
to 2.1.9*/glibc2/gcc 2.8.1 (in reverse order as a matter of fact). Not
everything went smoothly, but actually I had to resort to booting in
single-user mode only once... Eventually most of the stuff got
straightened out, and right now it all works, well, more or less. The
biggest problem was (and still is) to get, recompile and properly
install all the utilities that used libc5 so that they'd use
glibc2. Some things are available in binary glibc2 form, but lots of
things need to be compiled unless you go with a glibc2-based
distribution (e.g. redhat 5) - but I didn't. Also, many vital progs,
if you compile and install them yourself, install by default in
/usr/local/... while the system actually needs them in /.... Which was
a pain (for me) to weed out. And sometimes I got situations when a
prog was linked against *both* libc5 and glibc2 (via another library -
e.g. ncurses) - and that does *not* work. So have your boot/root disks
ready.
-- Cheers, -Dima.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu