From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: AW: Re: Linux flavor recommendations?
Date: Mon, 29 May 2017 18:42:52 +0200 [thread overview]
Message-ID: <v79b85m52mecqd54t400q90g.1496075990512@email.android.com> (raw)
Howdy,
Fenrir runs on fedora as well.
By the way i need some Russian testers (or others with non western encoding) for test my autoencoding stuff. Maybe someone with that setup has time and fun to help me out here.
Cheers chrys
-------- Ursprüngliche Nachricht --------
Von Linux for blind general discussion <blinux-list@redhat.com>
Datum: 29.05.2017 14:44 (GMT+01:00)
An Linux for blind general discussion <blinux-list@redhat.com>
Betreff Re: Linux flavor recommendations?
Those are two good choices except for one problem with Fedora. There's
no one packaging kernel staging modules these days, and that leaves you
doing your own work to compile Speakup for each new kernel.
I understand Vinux is moving to Fedora, which would obviate the above
issue. I'm thrilled that's happening, because Fedora is a very good
environment in many, many ways. I still run it on my server, where I
have no use for Speakup as all my access i over ssh.
The above reason prompted me to leave Fedora for Arch something over a
year ago.
Janina
Linux for blind general discussion writes:
> Hi all,
>
> I'm just trying to get into Linux in general, and have been doing some
> reading about OSes.
>
> I've been reading a lot of good things about fedora, so my plan was to
> try it out in a VM before I do anything else.
>
> Trouble is, the media writer util doesn't seem to be accessible on
> windows with NVDA at all, so I'm just curious if fedora's still an
> option for blind folks?
>
> Or, even better and I know this is quite a broad topic, but if anyone
> has any OS recommendations that they think work particularly well, then
> please do let me know!
>
> I've heard good things about arch, which is the second one on my list if
> you will, any thoughts?
>
> Thanks for any help,
>
>
> Daniel
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina@rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=v79b85m52mecqd54t400q90g.1496075990512@email.android.com \
--to=blinux-list@redhat.com \
/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).