From: "david poehlman" <david.poehlman@handsontechnologeyes.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: voiceover and unix/linux
Date: Tue, 3 May 2005 12:33:47 -0400 [thread overview]
Message-ID: <00db01c54ffd$e217fbf0$6501a8c0@DAVIDPC> (raw)
In-Reply-To: <Pine.BSF.4.51.0505031221160.26637@vegeta.city-net.com>
You can run pine, lynx, sirc and a whole host of other apps and utilities.
apple downloads is full of them. You can telnet into osx with ssh and it's
got a ready made set of shells right out of the box. You can use the
terminal application on the mac its self but the interface with VoiceOver
needs some work. I don't know that you can boot directly into the command
line though.
--
Johnnie Apple Seed
----- Original Message -----
From: ".dan." <ddunfee@city-net.com>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, May 03, 2005 12:27 PM
Subject: voiceover and unix/linux
In the original post I was fishing for some possibility of using the
underlying os more directly then doing a linux dual boot approach. It's my
understanding that the os is in the unix/linux family, the "bst" term comes
to mind as a unix/linux workalike as the mac os being used. If it is so
related, can pine and lynx etc. be compiled and used instead of doing a
dual boot linux thing? Further, what speech approach might be possible? I
ask again about doing dosemu in either case, will dos talk to the mac
hardware?
Thanks
XB
IC|XC
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
.dan.
` david poehlman [this message]
` Sean McMahon
` Jane Lee
-- strict thread matches above, loose matches on Subject: below --
.dan.
.dan.
` Jane Lee
` Luke Yelavich
` hank smith
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='00db01c54ffd$e217fbf0$6501a8c0@DAVIDPC' \
--to=david.poehlman@handsontechnologeyes.com \
--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).