Hi!
> > The very fact that this turned into a discussion is a sign that the ABI
> > breakage wasn't handled well enough. Usually, when we do something, nobody
> > ever even notices.
>
> There was the grand total of *ONE* user who was personally
> impacted by the userspace API change (the two other, one was hit by a
> bug, now fixed, one was hit because of kernel API change + external
> driver). And I immediately proposed to postpone the change to a later
> time.
The fact that all the wireless tools print...
Warning: Driver for device eth1 has been compiled with version 20
of Wireless Extension, while this program supports up to version 17.
...shows that wireless is not as backwards compatible as usual kernel
ABIs are. I'm afraid that wireless extensions can not be helped
(designed with back-compatibility at wrong place), but can we make
sure new netlink ABI does not have similar problems?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]