From: Daniel Dalton <d.dalton@iinet.net.au>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup drivers with 2.6.24
Date: Sun, 30 Mar 2008 20:53:36 +1100 (EST) [thread overview]
Message-ID: <alpine.DEB.0.99999.0803302049590.11261@laptop1> (raw)
In-Reply-To: <000301c8921e$210f8ac0$0401a8c0@ZKMOBILE>
On Sat, 29 Mar 2008, Zachary Kline wrote:
> Hi,
> I must admit I'm not sure about the reasons behind all this. Call me a
> traditionalist, but I've always associated /proc as being the main place
> where such configurable kernel parameters are kept. Is there a reason
> behind moving stuff out of there?
I only use speakup on my laptop since its annoying to take the braille
display everywhere, but
the thing I quite liked was to be able to set up bash scripts to adjust
speakup settings.
I could call these on boot or have them in my path so they were quickly
accessible...
--
Daniel Dalton
http://members.iinet.net.au/~ddalton/
d.dalton@iinet.net.au
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Kirk Reiser
` Chuck Hallenbeck
` Nick Stockton
` William Hubbs
` Zachary Kline
` Daniel Dalton [this message]
` Samuel Thibault
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=alpine.DEB.0.99999.0803302049590.11261@laptop1 \
--to=d.dalton@iinet.net.au \
--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).