On Thu, 10 Jul 2008, Marc Lehmann wrote: > On Thu, Jul 10, 2008 at 05:00:15PM +0200, maximilian attems <[EMAIL > PROTECTED]> wrote: > > right and i could close it right away as you rely on external stuff. > > I am completely confused what that means - I rely on loop-aes (from debian), > what does external mean? external to the kernel package? relying on software > external to the kernel package makes bugs against the kernel somehow void? > > sorry, I am totally confused as to what you want to tell me...
loop-aes is a very contested module with a strange author, you can't possibly know this. but if such code stays outside of mainline such long its quite a bad sign. thus relying for root on external modules is risky. > > sorry not provided. > > that's fine with me. > > > if you are using lvm it is pretty simple to set up and root that > > doesn't rely on that otherwise you have to wait. > > I am happy to wait and test with a 2.6.26 kernel once it hits unstable. > > I do not understand your reaction however, I don't see why you should close > valid bug reports ever if they aren't fixed, and I don't see why not being > able to test a package that isn't even in debian is required to keep a bug > report open. > > If you want to tell me that I should report bugs against the kernel in the > future, then I will happily comply. never said that. ring 0 code is special same way that tainted kernels are not supported. kind regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
