You're getting this kernel out of the preview/ directory? Any glibc
package with ".2.4" at the end of the release is built without any
support for kernels older than 2.4. This makes glibc faster, as it
does not have to figure out what kernel is running to determine which
kernel interfaces to use.
You should not install the glibc-2.1.92-14.2.4 package if you are
planning on running 2.2 kernels on your system.
The headers in this case are not what matters.
Cheers,
Matt
On Sun, Oct 08, 2000 at 11:50:26PM +0200, Svante Signell wrote:
> Thank you RH for updating the RawHide release.
>
> A few thoughts though:
>
> Trying to install the latest glibc (2.1.92-14.2.4) conflicts with the
> kernel I'm currently running: 2.2.16. (Wont change to 2.4.0-pre until I've
> resolved how to replace the masquerade setup in ipchains with iptables.)
>
> # rpm -Uvh
> error: failed dependencies:
> kernel < 2.4.0 conflicts with glibc-2.1.92-14.2.4
>
> 1. If installing the new glibc by temporarily booting
> kernel-2.4.0-0.x, will it be possible to run kernel-2.2.x again??
> Since kernel-2.2.16-24 is shipped together with
> kernel24-2.4.0-0.29.1 it seems to be the case. Can someone
> please enlighten me.
> 2. Obviously there is a dependency between kernel header files and
> glibc header files. Should this dependency rule out possibilities
> to boot various kernels, eg 2.2.x and 2.4.0-prex given a glibc
> version?
> 3. As I've understood, glibc should be compiled with the latest kernel
> header files installed. Shouldn't the dependency check above be on the header
> file level, instead of the kernel currently running?
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
