Re: Customizing the console key map?
- To: "Paul D. Smith" <pausmith@nortelnetworks.com>
- Cc: debian-user@lists.debian.org
- Subject: Re: Customizing the console key map?
- From: Henrique de Moraes Holschuh <hmh@debian.org>
- Date: Sat, 2 Jun 2001 12:26:42 -0300
- Message-id: <[🔎] 20010602122642.C29247@godzillah>
- In-reply-to: <p5elt5bitm.fsf@lemming.engeast.baynetworks.com>; from pausmith@nortelnetworks.com on Thu, May 31, 2001 at 12:10:29PM -0400
- References: <p5ofscgpz6.fsf@lemming.engeast.baynetworks.com> <20010529133616.A32104@dmcom.net> <p5ae3wgfyv.fsf@lemming.engeast.baynetworks.com> <20010529164617.A14589@dmcom.net> <p5elt5bitm.fsf@lemming.engeast.baynetworks.com>
On Thu, 31 May 2001, Paul D. Smith wrote:
> >> console-tools (or kbd, I don't care much which one) my customizations
> >> are kept automatically without my having to go back in and fix them up.
>
> There must be some reason why upgrading these packages keeps installing
> new versions of the keymap files.
The reason is simple: These packages are buggy; they should never overwrite
user-customized data with their own without asking. That said, the console-*
packages in unstable allow you to tell them NOT to touch the keyboard maps
anymore on upgrade.
> This is what I want to do with the console key map: have my own file
> with _only_ the changes, not the entire keymap.
Request this feature to be added using a wishlist bug and filling it through
the Debian BTS. Do notice that the keyboard map would need to be reset
when an user logs out; otherwise, we'd have a security hazard.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: