From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: Linux flavor recommendations?
Date: Fri, 26 May 2017 09:11:08 -0500 [thread overview]
Message-ID: <260d664c-f72a-1080-2a61-34545914c49a@johnheim.com> (raw)
In-Reply-To: <CY4PR13MB1464A0675F44CDFEC4C3D3CEB4FC0@CY4PR13MB1464.namprd13.prod.outlook.com>
You probably want to point your virtualization software directly at the
ISO file for whatever distro you choose. You don't need to write it to a
disk first.
I've found the accessibility in the latest version of debian to be
really good. It's worth considering. I use ubuntu in my job and that has
been fine too.
On 05/26/2017 05:31 AM, Linux for blind general discussion wrote:
> 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
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
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=260d664c-f72a-1080-2a61-34545914c49a@johnheim.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).