From: "Glenn / Lenny" <glennervin@cableone.net>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: finished with slackware
Date: Sat, 7 Feb 2015 08:43:54 -0600 [thread overview]
Message-ID: <DC378A9A0FEB4742BD08AF4D0DC000A2@LennyPC> (raw)
In-Reply-To: <20150207085257.GG2032@linlap.wavecable.com>
You know, I use Ubuntu, and I have become disenchanted with Linux. With
every new release, we have to rebuild accessibility.
Sure it is free, and it is safer and more powerful than Windows, but Windows
is still more accessible than Linux.
I had big hopes for Linux, and I have reached a point now where it is just a
tool in the toolbox, mainly for drive manipulation.
Glenn
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@linux-speakup.org>
Sent: Saturday, February 07, 2015 2:52 AM
Subject: Re: finished with slackware
I hate hearing stuff like this; we have made so much progress over the
years in making Linux accessible and then these things start coming
up. When you can't even boot a basic system with current versions of
installer and kernel, then there is something seriously wrong!
I grew up on Slackware clear back in 1994 or so. I then had to login
from a different computer running a terminal emulator but that was a
start.
As for me, I like Arch Linux and there is a current talking image
available. I thought Fedora was currently accessible; no?
On Fri, Feb 06, 2015 at 08:37:32PM -0500, Jude DaShiell wrote:
> I was trying to install a current version of slackware using the litetalk
> synthesizer earlier. Given slackware's installer kernel is broken, I got
> some remote sighted assistance and was told wait 30 seconds then key in
> boot parameters and that fails persistently insofaras getting speech up.
> So apparently slackware and Fedora have something in common. In both
> cases an installer interested in doing an accessible installation needs to
> find and download an earlier version of the operating systems that did
> install accessibly and use that version to install then upgrade through
> the versions to get to current versions. Moonshine on Fedora worked on
> intel machines in the past and if my memory is correct, maybe slackware
> 11.2 ought to be able to get it done in this case. What I will do now is
> take a stab at getting slackware 11.2 to speak and if that fails as time
> and my download quotas permit will try other versions in the future. This
> is now a low priority back burner project. I was surprised the
> distribution got broken in this way.
>
>
>
> jude <jdashiel@shellworld.net> Twitter: @JudeDaShiell
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
Jude DaShiell
` Steve Holmes
` Mike Ray
` Glenn / Lenny [this message]
` John G. Heim
` Mike Ray
` John G. Heim
` Jason White
` John G. Heim
` John G. Heim
-- strict thread matches above, loose matches on Subject: below --
Martin G. McCormick
Jude DaShiell
` Mike Ray
` Gregory Nowak
` John G Heim
tony seth
Jude DaShiell
Jude DaShiell
` Cleverson Casarin Uliana
` Glenn / Lenny
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=DC378A9A0FEB4742BD08AF4D0DC000A2@LennyPC \
--to=glennervin@cableone.net \
--cc=speakup@linux-speakup.org \
/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).