From: "Zachary Kline" <klinez@onid.orst.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: slackware 12.0
Date: Fri, 21 Mar 2008 15:17:54 -0700 [thread overview]
Message-ID: <000601c88ba1$6915c8d0$0401a8c0@ZKDESKTOP> (raw)
In-Reply-To: <Pine.BSF.4.64.0803211641190.62162@freire2.furyyjbeyq.arg>
Hi,
Perhaps I missed the initial message in this thread, but I was curious
why you'd need to go through the DD steps and all?
I just ran the speakup.s install directly. Granted, I have a hardware
synthesizer, so that makes a difference. It just worked for me though--dd
seems an extremely brute force approach. I don't like brute force in most
circumstances.
Hope this helps,
Zack.
----- Original Message -----
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: <speakup@braille.uwo.ca>
Sent: Friday, March 21, 2008 2:48 PM
Subject: slackware 12.0
> What may work for that version for speakup install is to install only
> packages that come off of disc1 then use dd -if /kernel/speakup.s -of
> /boot/vmlinuz. The setup script doesn't ask which kernel to install and
> probably forcibly installs the boot kernel if any even though speakup.s is
> used to do the install. I tried a full installation and never got disc2
> out to replace it with disc1 so tried this alternate approach this
> afternoon. I'll try it again and do the last dd -if step and see if I can
> get me something that works. Real hairy this time.
>
>
> _______________________________________________
> 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
Jude DaShiell
` Zachary Kline [this message]
` Alex Snow
` Adam Myrow
` Steve Holmes
` Adam Myrow
` Alex Snow
Jude DaShiell
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='000601c88ba1$6915c8d0$0401a8c0@ZKDESKTOP' \
--to=klinez@onid.orst.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).