Okay, so now your distribution is aware of this configuration
issue.
> Indeed. Initial impression of people upgrading a kernel from 2.4 to 2.5/6
> is that "sound doesn't work in 2.5/6". Not good.
... but now it isn't. What gives ?
(Besides, you've just added the "silent" flag as another config item
besides the volume setting, using different interfaces, different
permissions, etc.)
> And all for the fact that when the user sets up the system, it just
> works. With sensible defaults. Instead of being an elitist piece of
> crap that only l33t g33ks can use.
Fine. But this discussion isn't about the end-user experience,
but about where a certain parameter should be set, and what its
transient default value should be.
Unexperienced users will just install a set of packages to upgrade
to a new kernel. So this change can just be included in one of
these upgrades. No superhuman effort needed.
As far as those are concerned who painstakingly build their own
kernel, update the things listed in Documentation/Changes, avoid
suble traps like CONFIG_SERIO_I8042, don't get confused by needing
new module utilities, etc., I'm fairly confident that they'll
consider setting the volume a rather minor challenge.
And you could even take the sting out of this one by adding an
appropriate warning to Documentation/Changes. That's a about all
the kernel-side support this issue deserves.
- Werner
-- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/