AFAIK Herbert has fixed bugs in the past in 2.0.30 and the current debian version is already heavily patched. Its not the question of asking him. He already did it. The question is if all (dont take all to extremes...) bugs known have found some consideration by Herbert.
I have not had any trouble with 2.0.29. If Herbert has fixed 2.0.30 then lets take 2.0.30 but change the version number to 2.0.30deb or so to distinguish it from official Kernel releases. ---------- > From: John Goerzen <[EMAIL PROTECTED]> > To: Sven Rudolph <[EMAIL PROTECTED]> > Cc: Christoph <[EMAIL PROTECTED]>; debian-devel@lists.debian.org > Subject: Re: Kernel 2.0.30 a bad choice for 1.3 > Date: Friday, May 23, 1997 6:09 PM > > Sven Rudolph <[EMAIL PROTECTED]> writes: > > > Christoph <[EMAIL PROTECTED]> writes: > > > > > On 21 May 1997, John Goerzen wrote: > > > > > > > Since we know of a number of things that have been broken in 2.0.30 > > > > (such as IP masquerading being totally hosed), why are we distributing > > > > that version with 1.3? > > > > 2.0.30 has SYN_COOKIES. This is a critical feature. > > Agreed. However: > > * Those people that need SYN flood protection will know they need it > and will know how to compile their own kernel. (There are few > people that really need this desperately, in my estimation.) > > * The people that will suffer due to broken networking, etc. will not > necessarily know what the problem is, what to do about it, etc. > > Therefore, I reccommend using 2.0.29 instead of 2.0.30. Perhaps even > 2.0.27 or so if there is a problem with 2.0.29. (I do have a 386 that > 2.0.29 will refuse to boot on but 2.0.27 works fine on it). > > We could even include a README telling people that need SYN protection > how to get it. > > [ Regarding fixing Kernel bugs: ] > > > kernel-image, but we must not request him to fix arbitrary kernel > > bugs. > > Agreed. > > -- > John Goerzen | Running Debian GNU/Linux (www.debian.org) > Custom Programming | > [EMAIL PROTECTED] | > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
