Re: Bug#451367: installation-reports: Does not allow ethernet over firewire
(Moving thread to cloned BR.)
On Thursday 15 November 2007, you wrote:
> the new stack is very promising,
> we will reconsider later if no eth1394 shows up,
> for now that's just a minor regression.
No, that is not a "minor" regression. Half the functionality of the old
drivers is missing!
> see discussions on d-kernel,
> nobody spoke up when the anncouncement about missing eth1394 was
> declared.
What discussion? I googled for it and after skimming through about 20 pages
I still have not found it. What I _did_ find is several other reports of
problems with the new stack, two of which complain about missing Ethernet
support:
- http://lists.debian.org/debian-kernel/2007/10/msg00414.html
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441206
- http://www.debianhelp.org/node/9328
So Google does not help. Let's check the changelog:
linux-2.6 (2.6.22~rc5-1~experimental.1) experimental; urgency=low
* Enable the new firewire stack labeled to be more simple and robust.
-- Bastian Blank <waldi@debian.org> Tue, 19 Jun 2007 17:49:52 +0200
Strange. No mention of the fact that the new stack is [1]:
- experimental
- not recommended for distributions by its upstream developers
- has a _major_ regression in it's lack of Ethernet support
- lacks userspace integration
- has had only limited testing
Hmm. One more try. Let's check the mailing list for June. Ah, a hit!
http://lists.debian.org/debian-kernel/2007/06/msg00079.html
No discussion though (at least, I don't usually call a single message a
discussion). Not all that surprising that no users spoke up since the
message is only to the kernel list, which is a _developer_ list.
I'd say the lack of response is a better indication of the fact that other
kernel developers did not really care about the change than about what
users think of it.
What you are forgetting is that unstable kernels also migrate to testing and
that Debian has been promoting testing as an alternative to stable for
users who want a more current desktop, but don't want to deal with the
frequent breakage of packages in unstable.
Thanks for confirming that the kernel team cares more about the latest and
greatest upstream than about its users.
Debian unstable and testing are _not_ testbeds for upstream development!
[1] http://wiki.linux1394.org/JujuMigration
Reply to: