I'm a blind sys admin and I've never installed speakup on a server. The
servers I work with have lightsout management whereby I can get remote
access to the console and get more than just bootup messages, but also the
post messages and even interact with the bios on some hardware.
Granted, there is a bit of a gap between the time the kernel loads and the
time the serial driver is loaded, but it hasn't prevented me from
diagnosing issues that were preventing the system from booting.
At my current place of employment, the unix ops don't even work in the
same city as the data center, nevermind the same building.
I'd be in favor of speakup in userspace if it meant speakup working with
usb devices and pcie serial cards.
On Wed, 8 Oct 2014, John G. Heim wrote:
Huh? Not having a choice doesn't mean it's not a reduction in access. That
logic makes no sense what so ever. I mean, you could argue that we are stuck
with it but that doesn't mean it won't hurt.
On 10/08/14 16:26, Deedra Waters wrote:
I dont see it as a reduction in access in all i mean i guess there is to
some degree but the reality is that this change in the end reguardless
of wether it comes in systemd or some other form is they're going to end
up moving the console out of the kernel if they do this, well, you wont
have working speech to begin with so how is it a reduction in access if
we have no choice in the matter?
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
