public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Darrell Shandrow" <nu7i@azboss.net>
To: <speakup@braille.uwo.ca>
Subject: Re: red hat 8.0 and the Speakup Modified
Date: Sat, 28 Sep 2002 18:59:11 -0700	[thread overview]
Message-ID: <000a01c2675b$d16b9a10$0201a8c0@NU7I> (raw)
In-Reply-To: <Pine.LNX.4.44.0209282018180.2089-100000@homerun.midsouth.rr.com>

Actually, I like to have a rather inclusive Kernel out of the box.  Then,
the feature I need at any given time is likely already in place, without
having to do a lot of compiling/patching/whatever to the Kernel.



----- Original Message -----
From: "Adam Myrow" <myrow@eskimo.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, September 28, 2002 6:38 PM
Subject: Re: red hat 8.0 and the Speakup Modified


> On Sat, 28 Sep 2002, Bear in SFO wrote:
>
> >
> > Excuse my ignorance but how does that (having Speakup in the kernel or
not)
> > affect a sighted user?!
>
> I suppose it depends.  If you have compiled it with a default synthesizer
> other than none, it will probe the serial ports if it's serial, possibly
> pausing the machine for quite some time trying to find the synth.  Also,
> if you've compiled the keymap into the kernel, you would have your numeric
> pad remapped even when Speakup isn't talking.  Of course, the CVS version
> has solved this particular issue enough that the keypad will still type
> numbers when numlock is pressed, and since the CVS version is required for
> kernel 2.4.19 and newer, it is likely the one in Redhat.  Lastly,
> including all the synthesizer drivers would make the kernel a bit larger
> than normal.  However, it doesn't surprise me that Redhat would include
> Speakup in the stock kernel.  One of the things I dislike about Redhat is
> that they always use some sort of patched kernel.  It is flat impossible,
> as far as I know, to tell what patches have been applied to the Redhat
> kernel when you install.  For example, EXT3 was available in Redhat long
> before it was considered ready for production.  I think it was in kernel
> 2.4.7, and it didn't even show up in stock kernels until 2.4.15.  When I
> tried to build a Redhat kernel once, there were numerous options I've
> never seen.  My belief is that a production system should use the fewest
> patches to the kernel that are needed to get the job done.  With
> Slackware, unless you explicitly choose a kernel with the Speakup patch,
> you get a kernel produced from a stock source.  Actually, there are a few
> patched kernels besides the Speakup ones, but reading the documentation,
> you will know what was patched and why and can even download the patch if
> desired.  The point is, you know exactly what you are getting.
>
> Don't get me wrong, I'm glad to see Redhat include Speakup, but I just
> wish they wouldn't be concerned about marketing to the point that they
> sacrifice compatibility.  As another example, Redhat 8 will use gcc
> 3.0.2, and Slackware is still beta testing the version 9 which also uses
> the newer gcc.  It will likely be a long time before we see other
> distributions start shipping with gcc 3.0.2, but Redhat is jumping the gun
> to make themselves up to date.  We'll see how it goes.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 should I wait for red hat 8.0? Jared
 ` Janina Sajka
   ` Darrell Shandrow
     ` Adam Myrow
     ` Sunfire
       ` Alex Snow
         ` Sunfire
           ` Alex Snow
             ` Sunfire
       ` Nick Pinney | Lutris
     ` Janina Sajka
       ` Darrell Shandrow
         ` Darragh
           ` Darrell Shandrow
           ` Janina Sajka
   ` Sunfire
     ` Alex Snow
       ` Sunfire
         ` Alex Snow
           ` Sunfire
   ` red hat 8.0 and the Speakup Modified Janina Sajka
     ` Gregory Nowak
     ` Sunfire
       ` Janina Sajka
         ` Sunfire
           ` Janina Sajka
             ` Darrell Shandrow
               ` Janina Sajka
     ` Darrell Shandrow
       ` Darragh
       ` Janina Sajka
     ` Bear in SFO
       ` William F. Acker WB2FLW +1-303-777-8123
         ` Adam Myrow
           ` Aaron Howell
             ` Adam Myrow
               ` Janina Sajka
               ` Aaron Howell
     [not found]             ` <Pine.LNX.4.44.0209281915320.1975-100000@homerun.midsouth.r r.com>
               ` Bear in SFO
                 ` Adam Myrow
                   ` Darrell Shandrow [this message]
                   ` Geoff Shang
         ` Aaron Howell
         ` Richard Villa
     [not found]       ` <Pine.LNX.4.44.0209281659170.8451-100000@wb2flw.octothorp.o rg>
         ` Bear in SFO
     ` Charles Crawford
     ` Geoff Shang
     [not found] <20020929005902.2973.94872.Mailman@speech.braille.uwo.ca>
 ` Thomas Ward

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='000a01c2675b$d16b9a10$0201a8c0@NU7I' \
    --to=nu7i@azboss.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).