Re: woody security updates
On Thu, 2005-12-08 at 08:10 +0100, Martin Schulze wrote: dann frazier wrote: Yes. I really said woody. I've imported the woody 2.4 kernel trees into an svn repository: svn.debian.org/var/lib/gforge/chroot/home/users/dannf/woody We're currently tracking 160 issues, across the 6 woody source trees: svn://svn.debian.org/svn/kernel/patch-tracking Thanks a lot! However, please let us first roll out the update I've prepared already. Ah; didn't realize you had already prepared one. If you've only worked on 2.4.18, I don't think there's been much duplication of effort. So far I've just been merging patches that were already in 2.4.18 into the other trees - I'm just now getting to patches that aren't yet in 2.4.18. It only needs to be ported forward / backward to 5 kernels... The source for 2.4.18 is here: http://klecker.debian.org/~joey/security/kernel/kernel-source-2.4.18_2.4.18-14.4.diff.gz http://klecker.debian.org/~joey/security/kernel/kernel-source-2.4.18_2.4.18-14.4.dsc http://klecker.debian.org/~joey/security/kernel/kernel-source-2.4.18_2.4.18.orig.tar.gz Thanks. I'll merge that into the svn repository. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody security updates
dann frazier wrote: On Thu, 2005-12-08 at 08:10 +0100, Martin Schulze wrote: dann frazier wrote: Yes. I really said woody. I've imported the woody 2.4 kernel trees into an svn repository: svn.debian.org/var/lib/gforge/chroot/home/users/dannf/woody We're currently tracking 160 issues, across the 6 woody source trees: svn://svn.debian.org/svn/kernel/patch-tracking Thanks a lot! However, please let us first roll out the update I've prepared already. Ah; didn't realize you had already prepared one. If you've only worked I've even asked on debian-security for help, and got dilinger to help. No status update though. on 2.4.18, I don't think there's been much duplication of effort. So far I've just been merging patches that were already in 2.4.18 into the other trees - I'm just now getting to patches that aren't yet in 2.4.18. Ok. Regards, Joey -- Have you ever noticed that General Public Licence contains the word Pub? Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
woody security updates
Yes. I really said woody. I've imported the woody 2.4 kernel trees into an svn repository: svn.debian.org/var/lib/gforge/chroot/home/users/dannf/woody We're currently tracking 160 issues, across the 6 woody source trees: svn://svn.debian.org/svn/kernel/patch-tracking I've been slowly going through these and applying fixes where relevant (and noting where not), but could definitely use some help. Research/porting assistance would be appreciated, as would any compile/runtime testing. Joey Andres have posted patches for a number of these issues: http://klecker.debian.org/~joey/security/kernel/patches/ http://squishy.cc/woody/ -- dann frazier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody security updates
dann frazier wrote: Yes. I really said woody. I've imported the woody 2.4 kernel trees into an svn repository: svn.debian.org/var/lib/gforge/chroot/home/users/dannf/woody We're currently tracking 160 issues, across the 6 woody source trees: svn://svn.debian.org/svn/kernel/patch-tracking Thanks a lot! However, please let us first roll out the update I've prepared already. It only needs to be ported forward / backward to 5 kernels... The source for 2.4.18 is here: http://klecker.debian.org/~joey/security/kernel/kernel-source-2.4.18_2.4.18-14.4.diff.gz http://klecker.debian.org/~joey/security/kernel/kernel-source-2.4.18_2.4.18-14.4.dsc http://klecker.debian.org/~joey/security/kernel/kernel-source-2.4.18_2.4.18.orig.tar.gz Regards, Joey -- Have you ever noticed that General Public Licence contains the word Pub? Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
