From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list <blinux-list@redhat.com>
Subject: Re: early warning I hope
Date: Tue, 18 Feb 2020 22:28:24 -0500 [thread overview]
Message-ID: <CAJKfDDFSWCnqVdnyjaYhFE5gRUQ8_5+Fd7wij1-k5BF5Q8JRkg@mail.gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.21.2002180400500.24018@panix1.panix.com>
Do you realize that archlinux is intended to advanced users and that a
rolling release might break things anytime when a blind user absolutely
can't use his computer if the accessibility tools he need don't work ?
On the other side, Slint is Slackware based, out of the 5 majors
distributions bases, it's one of the two far less used so the user have
barely no community to help him in case of issues.
So Debian make sense since it's the base of 80% of all distributions so
it's by far the widest community so support is a no brainer, also Debian
name is stability and blinds need it at point way higher than average
end-users.
Ubuntu Mate stability is lower so LTS versions are heavily recommended for
blinds, for regular not blind end-users version 19.10 have an edge for a
few features but they should swap and keep 20.04 LTS as soon as released.
For outdated accessibility stack it's mostly false, Debian stable with
backports or Debian testing are even more updated than Ubuntu after all
Ubuntu is based from Debian testing but it's slightly outdated since they
have to make a release first.
Knoppix Adrianne is not suited for an installed setup.
For low vision users and color blinds, Mate tweak allow to add Compiz that
add color filters color inversion and magnification shortcuts.
For the rest, without knowing features I wanna implement, you may underlook
Debian but with them, it may be game changer but I won't hand my jewels
cause I need to release a whole set of ideas as a proof of concept,
otherwise idiots would waste ideas that could change everything and solve
many linux issues at the same time.
Michaël Caron Couturier
Le mar. 18 févr. 2020, à 04 h 07, Linux for blind general discussion <
blinux-list@redhat.com> a écrit :
> I just ran a kernel update a few minutes ago on archlinux and tried
> rebooting.
> Some uuid cannot be found and I got thrown into an emergency shell. All
> of this of course without screen reader working.
> I found this out as a result of talking to a be my eyes volunteer on the
> phone after she examined my screen.
> I have no idea what caused that and have minimal usb stuff connected to
> the computer. I had disconnected a flash drive from the computer thinking
> the flash drive was the cause of the missing uuid but that wasn't the
> case.
> Fortunately I use solid state drives and have another different system on
> one of them or I'd be offline for a while.
> The volunteer didn't read me the long number after that uuid error.
>
>
>
> --
>
>
> _______________________________________________
> 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: 20+ 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
` 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
` 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
` Linux for blind general discussion
` 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=CAJKfDDFSWCnqVdnyjaYhFE5gRUQ8_5+Fd7wij1-k5BF5Q8JRkg@mail.gmail.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).