From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: early warning I hope
Date: Tue, 18 Feb 2020 04:06:03 -0500 [thread overview]
Message-ID: <alpine.NEB.2.21.2002180400500.24018@panix1.panix.com> (raw)
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.
--
next reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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
` 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=alpine.NEB.2.21.2002180400500.24018@panix1.panix.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).