public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: Speakup in user space, why or why not?
Date: Sun, 2 Oct 2005 15:00:58 -0400	[thread overview]
Message-ID: <000701c5c783$a0206d10$6701a8c0@QUARK> (raw)
In-Reply-To: <20051002183440.GA15682@romuald.net.eu.org>

Hi Greg,

*smile*, thanks for the company line, ... So, no seriously, I'm not kidding,
*grin*

Yes, I know I can do it that way ... In fact, I am doing it that way, but it
doesn't answer the question.

Thanks for the response, and the smile, though.

Take care,
Sina

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Gregory Nowak
Sent: Sunday, October 02, 2005 2:35 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Speakup in user space, why or why not?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Oct 02, 2005 at 02:03:37PM -0400, Sina Bahram wrote:
> For example, I want to learn FreeBSD, because a friend of mine has 
> been telling me all about it, and I'd like to play around with it.
> I would, of course, like to use speakup with it. Could this be possible? 

Yes, it could. Netbsd, and probably freebsd as well allows you to install
the system via a serial console. Once that's done, you can use ssh on a
speakup-enabled gnu/linux system to access your freebsd box, thus being able
to use speakup in freebsd (grin). Seriously though, yes, I know this isn't
exactly what you meant, but not having speakup run in user space is not a
big obstacle to using freebsd, provided that you have at least 2 computers
that you can use, one to run gnu/linux, and the other to run freebsd.

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.2.3 (GNU/Linux)

iD8DBQFDQChA7s9z/XlyUyARAlerAKC3g169ihiQ6gvZMxYtzY8dKZXdjACeMPUr
5UYqwQCpojXSeZ7bZuPPj1Y=
=GirF
-----END PGP SIGNATURE-----

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



      parent reply	other threads:[~ UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Sina Bahram
 ` Gregory Nowak
   ` Garrett Klein
     ` Sina Bahram
       ` Janina Sajka
         ` Sina Bahram
           ` Janina Sajka
             ` Kenny Hitt
               ` Sina Bahram
             ` Lorenzo Taylor
               ` Sina Bahram
                 ` Gene Collins
                   ` Sina Bahram
                     ` Gene Collins
                       ` Sina Bahram
                     ` Scott Howell
                       ` Charles Hallenbeck
                         ` Sina Bahram
                       ` ace
                         ` Sina Bahram
                   ` Sina Bahram
         ` Lorenzo Taylor
           ` Sina Bahram
           ` Luke Yelavich
           ` Jim Grimsby
   ` Sina Bahram [this message]

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='000701c5c783$a0206d10$6701a8c0@QUARK' \
    --to=sbahram@nc.rr.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).