From: John Heim <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup, 2.6.22, and the way forward
Date: Tue, 31 Jul 2007 20:54:11 -0500 [thread overview]
Message-ID: <008301c7d3de$e912eac0$5501a8c0@mcgee> (raw)
In-Reply-To: <20070731223653.GA27762@localhost.localdomain>
----- Original Message -----
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, July 31, 2007 5:36 PM
Subject: Re: speakup, 2.6.22, and the way forward
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, Jul 31, 2007 at 04:08:24PM -0500, John Heim wrote:
>> On the other hand, if linux doesn't talk at boot time, it will actually
>> make
>> my job less secure. I need to be able to listen to boot messages. That's
>> what I do for a living.
>
> That's what dmesg is for. The only time really when it is necessary to
> hear boot messages as they occur, is if you're booting a fresh kernel
> you've just built, that may not be configured correctly, (I.E. not
> have the necessary ide/sata/scsi/whatever controller included, not have
> the root file system included, ETC.), and you need to hear the boot
> messages in case of a kernel panic, so that you can review the screen,
> and see where things blew-up.
Another one is where you messed up menu.lst.
These things come up all the time for me. We install Windows via a live CD.
I modified the kernel on the live CD to include speakup so that I can tell
what's going on during an install. Same for installing linux. Of course, I
use Shane's modified debian install CD but I also use another open source
project called FAI or "Fully Automated Install" to do mass installs. Again,
it has a live CD to which I added a speakup modified kernel. And most of
our servers have custom kernels.
Being able to deal with these things on a pretty much level playing field
with my sighted colleagues has added a great deal to my prestige here at
the department. If I had to constantly call someone over to get help I
wouldn't have the reputation as the go-to guy that I do. I don't think I'm
paranoid. I just think it looks really bad when the linux expert has to get
help with a machine that won't boot. I'm supposed to be the guy they call
when a linux machine won't boot. I'm not supposed to be the one calling for
help.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
Daniel Drake
` John covici
` John Heim
` Gregory Nowak
` John Heim [this message]
` Gregory Nowak
` Kirk Reiser
` Travis Siegel
` Lorenzo Taylor
` John Heim
` Lorenzo Taylor
` Nick Gawronski
` Tomas Cerha
` Nick Gawronski
` John Heim
[not found] <E1IIS12-0005G6-38@gene3.ait.iastate.edu>
` Nick Gawronski
` Gregory Nowak
` Nick Gawronski
` Gregory Nowak
[not found] ` <20070808142123.GA22584@gmx.net>
` nick
[not found] ` <20070808001353.GA3980@lava-net.com>
` Nick Gawronski
` Gene Collins
` Nick Gawronski
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='008301c7d3de$e912eac0$5501a8c0@mcgee' \
--to=jheim@math.wisc.edu \
--cc=speakup@braille.uwo.ca \
/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).