public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: BLINUX Documentation Project <oedipus@leb.net>
To: root@zygote.ivory.com, brian@henge.com
Cc: Blind Access to Linux List <blinux-list@goldfish.cube.net>,
	linux-access <linux-access@ssv1.union.utah.edu>,
	uab-l <uab-l@sawnet.com>
Subject: Re: UltraSonix screen-reader for X-windows available at BLINUX site
Date: Wed, 9 Oct 1996 05:25:16 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.3.95.961009045242.18348A-100000@beirut.leb.net> (raw)

aloha, brian!

you are correct in stating that there is no linux port of the ultrasonix
source code at the present time, hence the filename:

	UltraSonix.source-7.0.tar.Z  (2.4 MB)

and, as you noted, 
>The file
>listed above is the original public release of the UltraSonix sources
>which were written for a SPARCstation + Solaris.
>  There is a Linux port under way, but it has
>only just begun.

now, a question...

since you're working on the port, would you be willing to keep the members
of blinux-list, as well as linux-access and uab-l, apprised of the port's
progress?  i've linked your web pages concerning the port to the blinux
web site (http://leb.net/blinux) and would like, when you are ready for
such a step, to add a link to the "Betas in Search of Testers" page...
and, with your permission, i'd like to mirror the port update page
in ASCII form at the BLINUX FTP Archive,

	ftp://leb.net/pub/blinux

as for the rest of you hackers, once you download the public 
non-commercial release of the UltraSonix source code 
(ftp://leb.net/pub/blinux/UltraSonix.source-7.0.tar.Z) please keep the
rest of us apprised of you work/progress and let us know when you need
our input--after all, that's the primary purpose of these lists... 

thanks for the clarification brian--i apologize for any misunterstanding
and confusion i may have caused with my original post...

gregory.

----------------------------------------------------------------------------
	   Gregory J. Rosmatia, oedipus@leb.net or blinux@leb.net
			http://leb.net/blinux
			ftp://leb.net/pub/blinux
			ftp://leb.net/incoming/blinux
  electronic archivist and webmaster for The BLINUX Documentation Project
----------------------------------------------------------------------------


             reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 BLINUX Documentation Project [this message]
     [not found] <199610110725.BAA01013@zygote.ivory.com>
     [not found] ` <MRjXy0r1JQNW089yn@ccs.covici.com>
   ` John Covici
  -- strict thread matches above, loose matches on Subject: below --
 michael malver
 ` brian
     [not found]   ` <bYaXy0r1JI2D089yn@ccs.covici.com>
     ` John Covici
       ` Nicolas Pitre
 ` AARON HOWELL
 UltraSonix-FAQ zocki
 ` UltraSonix screen-reader for X-windows available at BLINUX site BLINUX Documentation and Development Project

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=Pine.LNX.3.95.961009045242.18348A-100000@beirut.leb.net \
    --to=oedipus@leb.net \
    --cc=blinux-list@goldfish.cube.net \
    --cc=brian@henge.com \
    --cc=linux-access@ssv1.union.utah.edu \
    --cc=root@zygote.ivory.com \
    --cc=uab-l@sawnet.com \
    /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).