From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Re: Re: ltlk issue again
Date: Sat, 25 Apr 2009 14:13:58 -0500 [thread overview]
Message-ID: <20090425191358.GA28193@linux1> (raw)
In-Reply-To: <alpine.DEB.2.00.0904251230060.30185@maranatha>
Hi Cheryl,
On Sat, Apr 25, 2009 at 01:28:27PM -0500, Cheryl Homiak wrote:
> I may have found the problem but not the source of the problem. In
> /sys/module I have both a speakup_ltlk and a speakup. speakup_ltlk has ser
> and start under it; speakup has parameters. Should the speakup_ltlk not be
> there or is this normal? I did try at one point to run ltlk with the debian
> modules and had it in /etc/modules but I removed it.
There will be a directory in /sys/module for each module in the kernel,
so having the directories for speakup and speakup_ltlk in there is
normal.
William
prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak
` William Hubbs
` Cheryl Homiak
` Michael Whapples
` Cheryl Homiak
` Michael Whapples
` Cheryl Homiak
` Gregory Nowak
` Cheryl Homiak
` Cheryl Homiak
` William Hubbs
` Cheryl Homiak
` William Hubbs [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=20090425191358.GA28193@linux1 \
--to=w.d.hubbs@gmail.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).