From: "Tom Moore" <tom@tomstroubleshooting.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: CentOS
Date: Wed, 23 Jul 2008 11:26:27 -0400 [thread overview]
Message-ID: <00a501c8ecd8$7ecf8740$6a01a8c0@ZEUS> (raw)
In-Reply-To: <7886E30AFD334C46A3C6F8BD7C185F6F039B8DA9@COCMAIL3.coc.ca>
As far as I know this hasn't been done yet.
I was planning on starting some work on this, but never got the process off
the ground.
One thing I am unsure of is exactly which kernel should I make my patch off
of. 2.6.18, 2.6.18.4, this I am unclear about.
I found some instructions on how to add the needed lines to the spec file to
add Speakup in, but didn't try out a test build.
This guide tells how to modify the kernel on Centos.
http://wiki.centos.org/HowTos/Custom_Kernel
Hope this might be enough to get you started.
This in itself though isn't all that is needed. This would just add Speakup
in to the kernel so that after the system was installed I could get it
talking.
This probably doesn't fix keymap issues with in the installer itself though.
For doing the install I use a kickstart file to answer the questions I want,
but I had to come up with this one by trial and error so this took some
time.
Also one bad thing I can think of is that Centos doesn't have a telnet
install option. From what I remember they do their remote installs via vnc
and this won't work for us.
Tom
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Dawes, Stephen
Sent: Wednesday, July 23, 2008 9:26 AM
To: Speakup is a screen review system for Linux.
Subject: CentOS
Has anyone ported speakup to CentOS? For those of you who don't know,
CentOS is a RedHat product. (Basically the enterprise version without
support) CentOS is extremely stable, and does not come out with new
versions at the same speed as Fedora does. (Fedora, another RedHat
product.)
I am interested in a Centos install if it can be considered as a
candidate for speakup, and all the other accessibility offerings found
in fedora.
Steve Dawes
Phone: (403) 268-5527
Email: SDawes@calgary.ca
NOTICE -
This communication is intended ONLY for the use of the person or entity
named above and may contain information that is confidential or legally
privileged. If you are not the intended recipient named above or a person
responsible for delivering messages or communications to the intended
recipient, YOU ARE HEREBY NOTIFIED that any use, distribution, or copying of
this communication or any of the information contained in it is strictly
prohibited. If you have received this communication in error, please notify
us immediately by telephone and then destroy or delete this communication,
or return it to us by mail if requested by us. The City of Calgary thanks
you for your attention and co-operation.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
installing via serial Tyler Littlefield
` Tom Moore
` Tyler Littlefield
` CentOS Dawes, Stephen
` Tom Moore [this message]
` CentOS Trevor Astrope
` installing via serial Kerry Hoath
` Tyler Littlefield
` Nick Stockton
` Kerry Hoath
` John Heim
` Kerry Hoath
` Tyler Littlefield
-- strict thread matches above, loose matches on Subject: below --
centos Steve Dawes
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='00a501c8ecd8$7ecf8740$6a01a8c0@ZEUS' \
--to=tom@tomstroubleshooting.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).