<quote who="[EMAIL PROTECTED]"> > > I'm using RHEL3, with RH's 4.0.1 versioned SRPM (which includes the > > local root compromise fix). > > Which I think answers another question I had, you compile your own? What > compiler? I think RH patch their compilers, and libc, too, so I guess it's > possible that an RHEL kernel might have a problem outside an RHEL > environment. (well, anything is possible)
It's unlikely that these would have a significant effect, although when used in combination, sure. Using an NPTL kernel and NPTL glibc on a distro with no active support for NPTL is going to have uncertain consequences. :-) > > The patches applied when building on x86 add up to about 5MB when > > bzipped - lots of changes. New drivers, patches from various kernel > > trees, backported stuff like cryptoapi, etc. I'll put up the patch some > > time, or point you to the Debian packages when they're done. > > I can wait, I've spent a bit of time going through spec files, trying to > work out what patches to apply, and in what order. I don't really feel > like upgrading anytime soon. Let RPM do the work for you. :-) Or, someone else. (It seems my desktop at work has crashed, so I can't get the patch right now.) > > Probably because it's cool. Red Hat do an incredible job on the kernel > > (it is a pretty ridiculous chunk of their engineering, really), so > > particularly if you're using RHEL, there is *no sensible reason* to > > build a Linus kernel > > Linus kernels are odd, aren't they? 2.3 2.5 2.7 :) I mean stable kernels, regardless of who they're maintained by. No distro uses pristine upstream kernel source. - Jeff -- GVADEC 2004: Kristiansand, Norway http://2004.guadec.org/ "And, most importantly, we now have modules named 'fontilus' and 'themus' -- the two founders of GROME." - Jonathon Blandford -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
