public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: the push to get rid of CONFIG_VT in the kernel and the future of Speakup
Date: Thu, 09 Oct 2014 07:32:21 -0700	[thread overview]
Message-ID: <87h9zd2u16.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <543696F6.7090109@math.wisc.edu> (John G. Heim's message of "Thu, 09 Oct 2014 09:08:54 -0500")

"John G. Heim" <jheim@math.wisc.edu> writes:

> Here at the University of Wisconsin, there
> are a lot of linux systems admin jobs. And for the majority of them,
> it would be a big problem if you couldn't access the boot messages.

Is the serial console support not appropriate / acceptable?
When I first started out with Linux, I had a Braille 'n Speak, and I
used it as a dumb terminal.  If I started the serial console at boot, I
got to see all of the boot messages from the kernel, regardless of
whether I had Speakup.  It's not really a good way to work, when
compared to Speakup, but for tasks such as diagnosing boot failures, it
was usable.
If I worked professionally as an on-site sysadmin, I might try to
do something similar today.  The BNS isn't manufactured any more, but
I'm sure there's something that would work as well.

-- Chris

  reply	other threads:[~ UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Chris Brannon
 ` Deedra Waters
   ` Hart Larry
   ` Brian Buhrow
   ` Igor Gueths
 ` Kyle
   ` Al Sten-Clanton
     ` covici
       ` Gregory Nowak
         ` John G. Heim
           ` Chris Brannon [this message]
             ` covici
             ` John G. Heim
               ` Chris Brannon
           ` Gregory Nowak
     ` Kyle
       ` Al Sten-Clanton
         ` Jupiter rocks; was " Cleverson Casarin Uliana
           ` Chris Brannon
             ` Kyle
           ` Hart Larry
           ` Kyle
             ` Cleverson Casarin Uliana
         ` Kyle
         ` Samuel Thibault
       ` Kelly Prescott
         ` Janina Sajka
         ` John G. Heim
           ` trouble shooting, was: " Gregory Nowak
           ` Brian Buhrow
     ` Deedra Waters
       ` John G. Heim
         ` Mike Ray
         ` Trevor Astrope
           ` John G. Heim
     ` John G. Heim
       ` Glenn
         ` John G. Heim
           ` Janina Sajka
             ` covici
             ` Chris Brannon
               ` Cleverson Casarin Uliana
               ` Janina Sajka
             ` John G. Heim
               ` Janina Sajka
       ` Chris Brannon
         ` covici
         ` Gregory Nowak
           ` Chris Brannon
         ` Janina Sajka
           ` Chris Brannon
             ` John G. Heim
               ` running VMs from a live environment Chris Brannon
               ` the push to get rid of CONFIG_VT in the kernel and the future of Speakup Gregory Nowak
               ` Janina Sajka
           ` Cleverson Casarin Uliana
   ` John G. Heim
     ` Janina Sajka
       ` Kyle
         ` John G. Heim
         ` Janina Sajka
 ` Talking with the systemd-consoled people (Was: the push to get rid of CONFIG_VT in the kernel and the future of Speakup) Samuel Thibault

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=87h9zd2u16.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=speakup@linux-speakup.org \
    /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).