public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list <blinux-list@redhat.com>
Subject: Re: early warning I hope
Date: Wed, 19 Feb 2020 15:30:29 -0500	[thread overview]
Message-ID: <CAJKfDDG_M7XDxYPgRvV5s0tomokymQOqfBZGU4cw9gzrTeOKLw@mail.gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.21.2002180400500.24018@panix1.panix.com>

I help manage a massively active Linux community of over 100k members for
near a decade, I barely recall to have seen any Slackware user, Linux
questions website is one of oldest linux ressources and got around 15
slackware questions per day in the last two days but only 8 questions on
maybe 30 got answered so it's up to debate ... (Slackware is 7 of 250
active distros about 2.8% of Linux as a whole, while Debian is the base of
120 of 250 distros so 48% of Linux on a quick check)

Debian don't focus on accessibility so the mailing list might obviously be
less active but overall it's the support of a community that matter for
quick troubleshooting.

Stop making like distro hopping wars that are plain stupid, Slint seem to
lack the magnification gain of Compiz, make color filters and color
inversion more tedious so apart the move from console to gui maybe easier,
not sure how it compete with just ubuntu mate.

My aim with trying to merge Vinux and Sonar while adding new content would
have fixed that stupid fragmentation that does nothing to help end-users
but it has to be done the right way.

That Archlinux accessibility tools rarely break isn't enough, for a blind
user his system can't break, like a phone for 911, like tv or game
consoles, think critical server that can't be offline for decades or just a
pacemaker if you don't understand well how it matter.

Obviously that this stupid elite thinking that make me keep my jewels that
I could contribute cause they would be badly used and it would be done the
opposite way that what would needed to do ...

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
>
>

  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
   ` 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

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=CAJKfDDG_M7XDxYPgRvV5s0tomokymQOqfBZGU4cw9gzrTeOKLw@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).