From: "Chris K. Engel" <morbie@legions.org>
To: Ben Collins <bcollins@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sun Type5 Mapping 2.4 -> 2.6
Date: Mon, 12 Jan 2004 22:05:25 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.56.0401122200530.22986@cyberspace7.legions.org> (raw)
In-Reply-To: <20040113024708.GZ31486@phunnypharm.org>
Wow, I'm going to find the announcement for this, I'd love to see the
explanation for completely and blatantly trying to adhere uniformity
without at least a message in Documentation/Changes.
That's kind of... messed up.
---
Don't get me wrong, I have no problem with it whatsoever, it's just the
deployment that has me partially peturbed.
------------------------------------
Hier liegt ein Mann ganz obnegleich;
Im Leibe dick, an Suden reich.
Wir haben ihn in das Grab gesteckt,
Weil es uns dunkt er sei verreckt.
-PDQ Bach's Epitaph.
------------------------------------
Chris K. Engel
PS: Thank you all for the tip-offs. I feel like even more of a moron now.
^_^
On Mon, 12 Jan 2004, Ben Collins wrote:
> On Mon, Jan 12, 2004 at 07:54:02PM -0600, Chris K. Engel wrote:
> > I've noticed something strange.
> > When updating to 2.6.1, my type5's mapping was really, really set off.
> > Nothing would work, period. (And I've noticed an abundance of mapping
> > issues on non-US keyboard layouts.)
>
> Everything in 2.6 is an i386 key mapping. Switch your console key
> mapping to an i386 type, or just plain old disable the console key
> mapping and leave it up to the kernel (which is what I do).
>
> --
> Debian - http://www.debian.org/
> Linux 1394 - http://www.linux1394.org/
> Subversion - http://subversion.tigris.org/
> WatchGuard - http://www.watchguard.com/
>
prev parent reply other threads:[~2004-01-13 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 1:54 Sun Type5 Mapping 2.4 -> 2.6 Chris K. Engel
2004-01-13 2:07 ` Ciaran McCreesh
2004-01-13 2:47 ` Ben Collins
2004-01-13 4:05 ` Chris K. Engel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.56.0401122200530.22986@cyberspace7.legions.org \
--to=morbie@legions.org \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).