On 2008-01-07 17:26, Paul Brossier wrote: > Does this merge implies there is an agreement on folding back to the > 'old' firewire stack?
Unfortunately, I don't know about an agreement. I have done the merge because the kino bug report is a "subset"/consequence of the kernel-compilation bug report. My personal oppinion: - I understand that a module with security concerns as the "old" firewire stack is claimed to be, should not be activated in the standard kernel by default. - I also understand the developers of kino and other applications, that they do not support a new module (juju) that is called unstable and not recommended by its developers yet. - To wait until the new juju kernel module is considered stable _and_ all firewire applications support it, is also no solution for me. So I would give the user the choise if she whats the new one, the old one or none of them (without compiling a own kernel), maybe as separate packages (including a description of the pros and cons in the package). Best regards, Philipp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
