-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Aug 21, 2008 at 03:10:12AM -0700, Tony Baechler wrote: > The problem is > Windows, not the ssh client. Yes, I'd agree. Specifically, the way I see it, the problem is using a text interface inside of a GUI interface, with a GUI screen reader. Ssh access for me at least, was lots better under a dosbox with the provox screen reader using win98, than it is nowadays in xp, regardless of if I'm using a ssh client via the cmd.exe xp command prompt, or using udf8 teratermpro, both via wineyes in my case. > The problem I run into > is that a GUI environment doesn't do well at handling console apps, > specifically GUI screen readers don't do well with command prompts or > text-based programs such as the Cygwin ssh client, telnet, etc. I'd definitely second that. > I > wouldn't quite go so far as to say that access from Linux to another > Linux system is seemless, but it's a lot better than going through > Windows. I've noticed that the Speakup keyboard echo is slightly less > responsive with ssh but I can certainly live with it. Maybe I should've qualified my previous statements. If you're interacting with a system at a remote location, what you describe is indeed the case. However, if you're interacting with another system on your home LAN, (which I believe is what Tyler is doing), then my previous statements do stand, ssh access from gnu/linux is indeed seamless in that case, speakup keyboard echo, and all. 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 at EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkitstoACgkQ7s9z/XlyUyA8GgCcCXwDFhIuqIms1uNaJ+gmEIL2 9EoAn2yNeivEMChCPpTRxt+IRXAgICY+ =eopg -----END PGP SIGNATURE-----
