From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: some comments on the speakup-modified fedora install howto
Date: Thu, 19 Jul 2007 21:02:57 -0700 [thread overview]
Message-ID: <20070720040257.GA6753@localhost.localdomain> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
I've just read through the speakup-modified fedora installation howto,
and the telnet mini-howto, and have some comments I'd like to make.
1. When describing the speakup-supported synthesizers, the install
howto says:
"iTripleTalk internal (PCI card) and Doubletalk internal (isa card)
dtlk."
I wasn't aware that the tripletalk pci was supported by speakup. When
did this development take place?
2. The install howto says:
"1. Switch to the second console by holding down the left Alt key and
pressing the F2 key. When you release these
you'll find that you're at a # prompt.i Notice that this prompt
is truly indicated by the pound sign--the # '#'
symbo."
I'm guessing that "prompt.i" should simply say "prompt.", and that
"symbo" should really be "symbol"
3. The telnet howto explains how to install over telnet, but it
doesn't mention anything about logging in without speech
afterwords. Can one assume that the openssh server, if installed, is
ready for logins, and that root can login over ssh? Can one assume the
same for a telnet server, even though using telnet isn't
secure, unless you're on a trusted private lan? Finally, can one
assume that /etc/securetty is setup for allowing root to login on
pts/x consoles? I would suggest that this be mentioned in the telnet
mini-howto, so as to not leave the user without a hardware synth, and
without software speech ready to go, guessing at how to login after
the install. It also may not be a bad idea to mention either in the
main howto, or in the mini-howto, how you could make sure that a
telnet/ssh server is installed and ready to go after you reboot the
system once the install is done. Otherwise, this is as usual, well
written.
Greg
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGoDPx7s9z/XlyUyARAoWfAJ9OFkii3Q3GKIYf9GFzg5SfXcIemwCfYNVO
ukxTYvZfEuRCcAc8hV5n54M=
=a5NU
-----END PGP SIGNATURE-----
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak [this message]
` Janina Sajka
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=20070720040257.GA6753@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).