-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thus spake Kirk Lowery: # I am exactly where you are in this process. The word is that packet # writing support in *not* in the main kernel source tree for 2.6.x and # that you must patch the sources and compile a custom kernel.
Which raises one of two rather interesting, and perhaps important questions: a) Why does Debian include a package that doesn't work with any of the kernels it provides? or b) Why are stock Debian kernels not built with the proper patches to handle all the included packages? I don't really have a problem with compiling a custom kernel, except for the fact that every time there is an upgrade I would have to do it again if I want to keep testing the latest kernels as I'm doing now. I just find it odd that packages are included in Debian that don't work with Debian kernels or that the Debian kernel isn't built to handle all packages that are included with Debian. Just my thoughts, and I'm not saying either that I won't create the correct kernel package that can handle udftools if someone will help me get it into Debian. If I can get this package into Debian, I might not be able to patch both the 2.4 and 2.6 kernels, but I would be happy to patch all available versions of 2.6 kernels, assuming of course that they will all accept the patch. PRINCE -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAfz8xAl2SNUPt1I8RAqDFAKCC8BQFAOQVpzLB+LDemhtusYJSuACcDm6e W3Nn6aR0CzehK7wOngDWy4w= =gmjF -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]