Re: Kernel 2.6.8 - SILO/initrd problems
David S. Miller <davem@davemloft.net> wrote:
> On Fri, 10 Sep 2004 21:26:13 -0700
> Joshua Kwan <joshk@triplehelix.org> wrote:
> > With our upcoming release in mind it may be a better idea to fix the
> > kernel instead of hacking around it in userspace...
> Why is the kernel in need of "fixing"?
> In particular, given the fact that from a distribution maker's
> perspective, the 2.6.x behavior (generating _ONLY_ x86 key codes
> to userspace regardless of architecture or keyboard type) is
> a boon for simplification for keyboard configuration. No more
> Sun/ARM/PPC/etc. specific crap needed anymore.
> In fact I find it quite puzzling that, given the above, you want
> to revert back to the 2.4.x days of complicated keyboard
> configuration.
Well I for myself just want things not to break on upgrade, which is exactly
what happens with keyboard support after switching to 2.6.*. It happened
here a few months ago after installing 2.6.3 and I was puzzled as well.
Maybe a big fat warning in the kernel-image-2.6.* sparc packages would help
a little, something along the lines of "Your keyboard might stop working
properly after reboot if you don't make the following changes: ..." if the
user is currently running a version lower than the version in which these
changes were done.
Zoran
Reply to: