From: "John G. Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Shane's kernels
Date: Thu, 17 Jul 2008 20:44:09 -0500 [thread overview]
Message-ID: <024501c8e877$c5e23e30$5501a8c0@mcgee> (raw)
In-Reply-To: <20080716231310.GX4459@implementation>
----- Original Message -----
From: "Samuel Thibault" <samuel.thibault@ens-lyon.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, July 16, 2008 6:13 PM
Subject: Re: Shane's kernels
Kristoffer Gustafsson, le Thu 17 Jul 2008 01:01:44 +0200, a écrit :
> I can fix other packages as well, don't have much to do in the summer,
> just
> say what you want.
Well, for instance the debian installation manual probably deserves an
accessibility section...
And if you feel like diving into debian you could help John Heim with
his speechd-up package, to make it up to date with the debian policy, so
that we may then add it to Debian.
Yeah, I haven't been able to work on it this week. I put that speechd-up
package together because I needed it for an automatic linux installation
system we have at my work. I thought that if others can use it, that would
be fine. But it's time I took it to the next level. I just haven't been able
to work on it for one reason or another since you told me it was messed up.
All I've had time to do is compile the speechd-up binaries. I stillhaave to
fix/upgrade the init.d scripts and re-do the deb packaging
I'm a systems admin for the University of Wisconsin Department of
Mathematics and I know a little about everything but not a lot about
anything. I'm no shell scripting guru. I know enough to be dangerous. I
know next to nothing about packaging debs. I learned only what I needed to
know so that I could build a package that would install speechd-up during an
automatic linux install.The one advantage I have is that I have ready access
to every kind of hardware you can name. But I wouldn't mind if someone would
point out places where I've obviously gone off course.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
slackware 12.1 and ltlk synthesizer Jude DaShiell
` Best distro DON.RAIKES
` Foreign White Devil
` Tyler Littlefield
` Gregory Nowak
` Tyler Littlefield
` Samuel Thibault
` Foreign White Devil
` Gregory Nowak
` Michael Whapples
` Shane's kernels (was: Best distro) John Heim
` Shane's kernels Tony Baechler
` Foreign White Devil
` Daniel Dalton
` Tony Baechler
` Samuel Thibault
` Daniel Dalton
` Samuel Thibault
` Daniel Dalton
` Samuel Thibault
` Foreign White Devil
` Samuel Thibault
` Kristoffer Gustafsson
` Samuel Thibault
` John G. Heim [this message]
` Daniel Dalton
` Tony Baechler
` Samuel Thibault
` Daniel Dalton
` Foreign White Devil
` Daniel Dalton
` Samuel Thibault
` Foreign White Devil
` Best distro Foreign White Devil
` Tyler Littlefield
` Tony Baechler
` Samuel Thibault
` Foreign White Devil
` Tony Baechler
` Michael Whapples
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='024501c8e877$c5e23e30$5501a8c0@mcgee' \
--to=jheim@math.wisc.edu \
--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).