Guus Sliepen <guus@debian.org> wrote:
> I do not see why making the old stack available again, but blacklisted
> by default, discourages testing of the newer stack. If you have both
> available, then yes, users can switch to the new stack more easily,
> but at least they will still be using Debian kernel packages, and they can
> switch back to the juju stack just as well. If you do not make this
> option available, those who have problems with the new stack will have
> to compile their own kernels, and then they will not track the Debian
> kernel packages anymore.
Unfortunately there *are* serious security problems with the old
stack, but as Guus said, not providing the old stack does not help at
all, because right now people will only be annoyed (and seriously
annyoed if they discover that the installer regressed (no installation
over firewire possible any more!) without notice!). So IMHO provide
the new stack by default and add a big notice somewhere like:
*Some drivers (e.g. eth1394) do not yet work with the firewire stack
enabled by default. For security and performance reasons we strongly
recommend to use the drivers provided by default. But if the driver
happens to be unusuable, then
a) Report this as a bug and
b) Do x, y and z to reenable the old driver
This way people can use Debian kernels, will provide feedback and
improve the situation. Otherwise (like I did, cf. #450836) those people
will not test the kernels (and probably will not benefit and test
updates regularly either).
Greetings
Helge
--
Dr. Helge Kreutzmann debian@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
Attachment:
signature.asc
Description: Digital signature