From: "brian Moore" <admin@bmoore.yi.org>
To: speakup@braille.uwo.ca
Subject: adding speakup to server distros
Date: Wed, 02 Jan 2002 04:10:20 -0500 [thread overview]
Message-ID: <200201020410200630.00187E7E@mail> (raw)
In-Reply-To: <200201012028420370.0065B56A@mail>
Greetings all. Has anyone been successful at adding speakup to any of
the pre-built server linux distros? I am currently using a program
called sme server formerly e-smith from Mitel. http://www.e-smith.org
to run my network at home and provide mail, ftp, etc for my domain. I
realize I could use standard distros to do the same thing but I am not
good enough yet to get all the services running securely as well as
achieve the same functionality I have with one of these server distros
in a production environment.
I would love to add speakup to the sme server distribution which I am
using now. it is based on redhat 7.0 but is using kernel 2.2.197.08
which is not the standard kernel shipping with redhat 7.0 In theory, I
could get ethe source dor tis kernel which I have and apply speakup
patches to the tree and recompile and just replace my vmlinuz file but
I don't know about moduel dependancies andthings and would probably
break a bunch of things. has anyone else ever attemptedto compile
speakup into a server distribution. I would be willing to switch from
mitel sme server to have this ability since I tend to reinstall
machines regularly and speakup would be a wonderful addition.
if anyone has done this or has any idea about how this could be
accomplished with either this distribution or something like clark
connect or some other distro, I would appreciate hearing from you.
thanks. Brian.
next parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201012028420370.0065B56A@mail>
` brian Moore [this message]
` Geoff Shang
` brian Moore
` William F. Acker WB2FLW +1-303-777-8123
` brian Moore
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=200201020410200630.00187E7E@mail \
--to=admin@bmoore.yi.org \
--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).