public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: cut and paste still doesn't work
Date: Wed, 24 Apr 2002 20:25:36 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0204242023340.13034-200000@igueths> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 383 bytes --]

Hi Adam. Attached is the only script that I found in /etc/init.d
concerning keymaps. As far as I know, it doesn't reference any speakup
keymaps in any way, however correct me if I am wrong. I wouldn't advise
doing a -x on this script, for it seems to be loading keymaps that are
used by the kernel such as the qwertty-us one. Do you have any idea where
this script would be located?

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: TEXT/x-sh; name="keymaps-lct.sh", Size: 836 bytes --]

#!/bin/sh

#
# Load the keymaps *as soon as possible*
#

test -f /bin/loadkeys || exit 0

PACKAGE=console-tools

CONFDIR=/etc/${PACKAGE}

EXT=kmap

#KERNEL_KEYMAP=/var/state/misc/kernel.${EXT}

case "$1" in
    start | restart | force-reload | reload)
# 	# save kernel keymap
# 	if [ -d ${KERNEL_KEYMAP%/*} -a ! -r ${KERNEL_KEYMAP} ]
# 	then
# 	    /usr/bin/dumpkeys > ${KERNEL_KEYMAP}
# 	fi

	# load new map
	if [ -r ${CONFDIR}/default.${EXT} ] ; then
	    /bin/loadkeys ${CONFDIR}/default.${EXT}
	elif [ -r ${CONFDIR}/default.${EXT}.gz ] ; then
	    /bin/loadkeys ${CONFDIR}/default.${EXT}.gz
	fi
	;;

    stop)
# 	# ensure the saved kernel keymap is removed before halt/reboot
# 	rm -f ${KERNEL_KEYMAP}
	;;

    *)
	echo "Usage: $0 {start|stop|restart|reload|force-reload}"
	exit 1
	;;
esac

             reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Igor Gueths [this message]
 ` Adam Myrow

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.44.0204242023340.13034-200000@igueths \
    --to=igueths@attbi.com \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).