On Fri, Jul 28, 2006 at 10:06:38PM -0400, Matthew Miller wrote: > Practically speaking I suppose this is a question directly for Dave Jones. > > But I'm not picky. Bah, you almost made me feel special. > Fedora Core 4 is going to transition to Legacy status pretty much any minute > now. There is, however, kernel-2.6.17-1.2143_FC4 sitting in the > updates/testing area. Presumably this will be really pushed before the > cutoff? That one is kinda pointless, as all it really has is the security fix in 2.6.17.6 for the bug we aren't even vulnerable to. > Is there any chance that there might be one more after that? I know that FC4 > has been pretty closely tracking the FC5 kernel; it'll probably make the job > for the Legacy people much easier if those are as in-sync as possible. CVS has a kernel based on 2.6.17.7 right now, but there should be a .8 soon-ish, so I've been waiting on that appearing before devoting much time to it (and as usual, rawhide has consumed my time since I got back from kernel summit/OLS). > Byt really I ask because I finally sat down and figured out what's behind my > pet kernel bug, <https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189812>. > Turns out it's a recently-solved problem, fixed in 2.6.18-rc1. Man oh man > would it make my life easier for the next six months if the official FC4 > kernel included this patch in some way or another. (It's been broken since > 2.6.16.) Ouch, that's a nasty one. Given you've identified the actual cset, I'll ping the -stable people about this to see if they can get it into .8 If FC4 EOL's before this update is ready, I'll still be around to lend a hand if needbe. Dave -- http://www.codemonkey.org.uk -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
