public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "jim grimsby" <jimgrims@pacbell.net>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: Using sftsyn
Date: Thu, 31 Mar 2005 14:02:36 -0800	[thread overview]
Message-ID: <000701c5363d$5c4fb640$220110ac@jim> (raw)
In-Reply-To: <20050331101427.GA956@blackbox>



Hi.  Your next step is to build your kernel and include support for
softsynth.  The docs you will want to read will depend on how you decide
to go.

Do you want to stick with a 2.4 kernel or move to a 2.6 kernel? Do you
want to build the kernel the way described in the kernel source tree or
do you want to be lazy like me and build it as a Debian package?
Any advantage in upgrading the kernel and as for the second idea is
there any way that one this would help others deebien users if we built
it as a package 
And 2 is there any way we might update what we already have on cd so the
newist kernel is included for one and the soft synth is included for
two.  
I know what you mean about the more you learn the more you want to
learn.  One of the cool things about Linux is you can usually find docs
to help you do almost anything you want with your computer.
The only problem with all this is there are so many things to read that
you find your self reading more and getting less done.  Also the emount
of docs can be over welming at times.  And the web sights for
downloading the docs can be strange.  Everyone keeps saying I should
read a book called linux in a nut shell.  I wonder how I might go about
getting this book.   Thanks again 




  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 jim grimsby
 ` Kenny Hitt
   ` jim grimsby
     ` Kenny Hitt
       ` jim grimsby [this message]
         ` Kenny Hitt

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='000701c5363d$5c4fb640$220110ac@jim' \
    --to=jimgrims@pacbell.net \
    --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).