[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#451367: installation-reports: Does not allow ethernet over firewire



On Thu, 15 Nov 2007, Frans Pop wrote:

> 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!

eth1394 is missing that is by far the less used firewire driver.

the switch to the juju stack allowed to close a huge nr. of bugs.
the old stack is just not supportable and never was, plus is a
security nightmare. ieee1394 in fact deserves the Kbuild variable BROKEN.
the new stack is aiming for feature parity, but with interface
incompatibility, so the various firewire userland needs to pick up
the switch. the new stack although more compact is already more stable.
 
> 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

i consider that smallish to the *huge* usability improvement
on not having a strange firewire ethernet device to choose
for your network connectivity in d-i.
so no tears for it.
 
> 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

if i'm wrong, we can still enable both and start blacklisting
the bad oldie one in m-i-t early enough.

RH did rewrite the stack and it's main upstream developer ships
it already enabled in 2 major releases fedora 7 and 8.
juju has already nicely improved since the 2.6.22 inclusion,
so still looks for the most promising option for the lenny release.

-- 
maks



Reply to: