Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: RH7J vs. JIS keyboard layout
- To: tlug@example.com
- Subject: Re: RH7J vs. JIS keyboard layout
- From: Antony Stace <antony@example.com>
- Date: Mon, 05 Feb 2001 17:36:39 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- References: <011801c08f4a$cfc6d480$0f01a8c0@example.com>
- Reply-To: antony@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <tUKFWC.A.OZH.cYmf6@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: antony@example.com
Is this the same problem, this is on Redhat 6.2(Non Japanese version) with a Japanese keyboard. The keyboard mapping is fine when X is running(someone here did a hack to get it going), but before X is running it is missing a few key mappings and is very annoying. Anyone know how to fix this? Feb 5 09:09:43 noosa keytable: Loading keymap: Feb 5 09:09:43 noosa keytable: Loading /usr/lib/kbd/keymaps/i386/qwerty/jp106.kmap.gz Feb 5 09:09:43 noosa keytable: loadkeys: /usr/lib/kbd/keymaps/i386/qwerty/jp106.kmap.gz:6: Feb 5 09:09:43 noosa keytable: Loading system font: Feb 5 09:09:43 noosa keytable: adding map 2 violates explicit keymaps line) Feb 5 09:09:44 noosa rc: Starting keytable failed Cheers Tony SN_Diamond wrote: > > This time, an answer! But not to any of the questions I asked here. > > Red Hat 7J contains corrupt configuration files for the JIS 106-key keyboard > layout (i.e. the layout which 99% of their Japanese customers surely have). > Simon McCorkindale reported the problem in RH 6.2J and RH gave it "normal" > priority. After all, who needs to input characters like an underscore and > two others, and who needs to remember which characters match the keycaps vs. > which characters think they came from a US keyboard layout? For other > national layouts RH gave this problem a high priority, but for Japanese, no, > looks like it'll never be fixed. > > Anyway, in 1 out of my 4 installations of RH 7J, the keyboard worked right > away! The trick seemed to be to install the "server" configuration AND > select to customize packages during installation AND make sure that X11 gets > in during the initial installation. As far as I could tell, the > configuration files were still broken, but the keyboard magically worked > anyway. > > For the others, I found that /etc/X11/XF86Config-4 is the magic file that > needs editing. Find the string "jp" and change it to "jp106". I'm still > not sure why this fixes it either though. As far as I can tell, several > other configuration files are still involved in mapping the keyboard and > some of them are still broken. > > By the way Dr. Breen, notice that RH 6.2J had a .2 in it. It's no use > waiting for any version at all. We can get broken Linux systems for free or > we can buy broken Windows 2000 systems for money. Except, my employer paid > money for RH 7.0J. But it was still cheaper than W2000, especially if > several dozen clients decide they want to connect. > > Yours sincerely, > Norman Diamond > > ----------------------------------------------------------------------- > Next Nomikai Meeting: Fri, February 16 19:30- Tengu Tokyo Eki Mae > Next Technical Meeting: March (date TBA) > ----------------------------------------------------------------------- > more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
- Follow-Ups:
- Re: RH7J vs. JIS keyboard layout
- From: "SN_Diamond" <Norman.Diamond@example.com>
- References:
- RH7J vs. JIS keyboard layout
- From: "SN_Diamond" <Norman.Diamond@example.com>
Home | Main Index | Thread Index
- Prev by Date: RH7J vs. patches for RH7J
- Next by Date: Re: RH7J vs. JIS keyboard layout
- Prev by thread: RH7J vs. JIS keyboard layout
- Next by thread: Re: RH7J vs. JIS keyboard layout
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links