From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: Re: Linux Quick Reference
Date: Sun, 06 Jan 2002 23:03:34 -0600 [thread overview]
Message-ID: <3.0.6.32.20020106230334.009f3d50@mail.doorpi.net> (raw)
In-Reply-To: <Pine.LNX.4.43.0201061803210.1584-100000@toccata.dsl092-170 -083.wdc1.dsl.speakeasy.net>
How expensive is the nbp one? The trouble with rfb material is the
inability to keep it forever. Is there any service like rfb that offers
books on tape like this to buy to keep forever? Granted, if one's in to
audio editing and the like, a four track can be copied to the PC, but
technically it's not legal in most cases, but there's no form to buy in
that's accessible.
At 06:05 PM 1/6/02 -0500, you wrote:
>Ooopps. John, I think you asked about a linux quick reference, and I
>mistakenly sent you emacspeak advice. Sorry.
>
>The best quick reference I know for linux --
>
>1.) National Braille Press has published a quick reference card in
>braille;
>
>2.) There's a HOWTO for DOS/Windows users which is very readable and
>provides many of the commands one needs early on. I'm sorry I don't have
>the exact url just now.
>
>
>--
>
> Janina Sajka, Director
> Technology Research and Development
> Governmental Relations Group
> American Foundation for the Blind (AFB)
>
>Email: janina@afb.net Phone: (202) 408-8175
>
>Chair, Accessibility SIG
>Open Electronic Book Forum (OEBF)
>http://www.openebook.org
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
next parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.43.0201061803210.1584-100000@toccata.dsl092-170 -083.wdc1.dsl.speakeasy.net>
` Brent Harding [this message]
` David Csercsics
` Brent Harding
` Prasad Chaturvedula
` Brent Harding
` Prasad Chaturvedula
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=3.0.6.32.20020106230334.009f3d50@mail.doorpi.net \
--to=bharding@doorpi.net \
--cc=blinux-list@redhat.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).