Re: userspace breakage

Ryan Anderson
2005-12-30T00:38:33Z

[-- Attachment #1: Type: text/plain, Size: 3019 bytes --]

Dave Jones wrote:
> On Thu, Dec 29, 2005 at 12:49:16PM -0800, Linus Torvalds wrote:
>
> > Umm.. Complain more. I upgrade kernels a lot more often than I upgrade
> > distros, and things don't break. They're not allowed to break, because I
> > refuse to upgrade my user programs just because I do kernel development.
> > But I'd only notice a small part of user space, so if people don't
> > complain, they break not because we don't care, but because we didn't even
> > know.
> >
> > So if you have a user program that breaks, _complain_. It's really not
> > supposed to happen outside of perhaps kernel module loaders etc things
> > that get really really chummy with kernel internals (and even that was
> > fixed: the modern way of loading modules isn't that chummy any more, so
> > hopefully we'll not need to break even module loaders again).
> >
> > If we change some /proc file thing, breakage is often totally
> > unintentional, and complaining is the right thing - people might not even
> > have realized it broke.
> >
> > At least _I_ take breakage reports seriously. If there are maintainers
> > that don't, complain to them. I'll back you up. Breaking user space simply
> > isn't acceptable without years of preparation and warning.
>
> The udev situation I mentioned has been known about for at least a month,
> probably longer. With old udev, we don't get /dev/input/event* created
> with 2.6.15rc.
>
> At some point in time it became defacto that certain things like udev, hotplug,
> alsa-lib, wireless-tools and a bunch of others have to have kept in lockstep
> with the kernel, and if it breaks, it's your fault for not upgrading
> your userspace.

The biggest complaint I've seen about udev isn't the fact that you
sometimes need to upgrade to use a new kernel, that's something that
people like Dave can handle via package dependencies.

The part of the udev situation that I've heard as a complaint (though I
haven't experienced myself) is that the new udev wasn't backwards
compatible with certain older kernels. I think the description I've
heard is that you need one udev for < 2.6.12, one for 2.6.12 - 2.6.14,
and now a new one for 2.6.15, and at least, jumping from < 2.6.12 to
2.6.15 is pretty much guaranteed to be difficult to get right. (If the
kernel fails, you have a udev installed that won't work on the older
kernel correctly, apparently.)

This, for what it's worth, is the same breakage that Dave seemed to be
most frustrated with during his OLS keynote, regarding ALSA versions,
and a few other things that caused breakage and the user space failed to
work correctly when the kernel was reverted. (I hope I'm not putting
words in your mouth, Dave).

That's my perspective from someone who has only dealt with the issue
from the point of view of a user, and only in the case of the Debian
udev packages flat out refusing to install while running a "too old"
kernel, which was rather, umm, annoying.

--

Ryan Anderson
sometimes Pug Majere

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]