From: Scott Ford <scotte.ford@gmail.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: FC 8 Questions
Date: Thu, 22 Nov 2007 07:57:38 -0500 [thread overview]
Message-ID: <008001c82d07$43e7b9e0$cbb72da0$@us> (raw)
In-Reply-To: <20071121234754.GF416@rednote.net>
Janina,
No I do not want to do any such thing. I do not see an explanation
of how to apply the patch. I have never used an RPM before. I did not se
any information about what to do after one finishes doing the fc8 telnet
install. I do not know what to do after it is installed. Thank you for
any help
Scott
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Janina Sajka
Sent: Wednesday, November 21, 2007 6:48 PM
To: Speakup is a screen review system for Linux.
Subject: Re: FC 8 Questions
The SpeakupModified already provides kernels for Fedora 8 patched with
Speakup. We provide them as standard Fedora rpm files to make
installation easy for you. Is there some particular reason you think you
need to roll your own, instead? If so, get ready for a very steep
learning curve and a lot of frustration. I will back out of the way, if
you're really just into learning to patch and build kernels. But, if you
just want a talking Werewolf, that's much easier and we will help.
Janina
Scott Ford writes:
> Hello Everyone,
> I am an inexperienced Linux user, so I need things spelled out
> explicitly. I would like to install Werewolf, fc 8 i86 64bit if possible.
> I do not know how to patch a kernel, would someone know where I could read
a
> how to on patching fc8 with Speakup? I am assuming the following is the
> process for getting a patched fc8 up and running could someone confirm
> that I am correct with my assumptions?
> First I would just go and download the FC8 from the repository?
> Next I would do the telnet install as per the telnet how to.
> Finally I would telnet into the machine after the reboot, and patch the
> kernel with the Speakup patch?
> Thank you for any help.
> Scott
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
--
Janina Sajka, Phone: +1.202.595.7777; sip:janina@a11y.org
Partner, Capital Accessibility LLC http://CapitalAccessibility.Com
Marketing the Owasys 22C talking screenless cell phone in the U.S. and
Canada
Learn more at http://ScreenlessPhone.Com
Chair, Open Accessibility janina@a11y.org
Linux Foundation http://a11y.org
_______________________________________________
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: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
cursor questions and a reading question Daniel Dalton
` Gaijin
` FC 8 Questions Scott Ford
[not found] ` <1195654474.1159.0.camel@sparky>
` Scott Ford
` Janina Sajka
` Scott Ford [this message]
` cursor questions and a reading question Michael Whapples
` 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='008001c82d07$43e7b9e0$cbb72da0$@us' \
--to=scotte.ford@gmail.com \
--cc=scott@adaptiveit.us \
--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).