Upgrading

Michael P. Blinn (blinnmp@ns.versa-corp.com)
Wed, 15 Oct 1997 11:28:06 -0400 (EDT)


I'm sure this has come up before, but it hasn't come up within the time
I've been following the list.. Pre-apologies for repetition.

I've got an old version of Slackware (1.2.13), and in striving for network
aliasing and other utilities, I needed to upgrade the kernel. Currently
I'm running 2.0.30, 1.2.13, and 2.1.43. Apparently due to the file locking
differences between glibc1 and glibc2, I need to recompile all of my
fcntl-using binaries with glib, however this only becomes apparent when
running 2.1.43, not 2.0.30 (??) (2.1.43 needed for parport support).

I'm kind of at a loss. I need to upgrade my kernel to use parport, but if
I do, pop3, etc doesn't work until I recompile it and the other fcntl-
using binaries (At least, I think this is what it is.. Much digging and
the only clues I've come up with point there.. I'm also having a whale of
a time trying to recompile pine for my users.. :(

It has stroked my curiosity though, and I'm wondering the exact nature
behind the beast.. (And if there is a way around it! I'm stuck now,
because I cannot upgrade to the newer kernels until I can get pine to
recompile.. otherwise it ALWAYS opens the mailboxes as readonly).

Anyone have a light to shed on this?

Many many MANY thanks,
Michael Blinn