public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Alex Snow" <alex_snow@gmx.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Is this card supported
Date: Wed, 9 Oct 2002 06:32:42 -0400	[thread overview]
Message-ID: <005301c26f7f$333c1320$6401a8c0@computer> (raw)
In-Reply-To: <Pine.LNX.4.44.0210082045100.1712-100000@homerun.midsouth.rr.com>

I think a kernel rebuild is going to happen sometime in the near future,
especially since i need to put speakup in.  The reason I hesitate building
the module into the kernel is because like most other techies, my linux box
will not have the same hardware from one day to the next, since I like
playing with different hardware.
Explorer has caused a general protection fault in module kernel32.dll. I'm
sick of Winblows!
----- Original Message -----
From: "Adam Myrow" <amyrow@midsouth.rr.com>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, October 08, 2002 9:50 PM
Subject: Re: Is this card supported


> Did you edit /etc/rc.d/rc.modules at some point?  If so, you need to find
> where you had it load the 3com module and comment it back out with a
> number sign.  If that's not the case, remove /etc/rc.d/rc.netdevice which
> is the file that netconfig creates.  As a last resort, you could build a
> custom kernel with just the module for your new network card, but this
> shouldn't be necessary although I generally do so because I like to
> customize my system.  Good luck and let us all know 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: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Alex Snow
 ` Adam Myrow
   ` Alex Snow
     ` Adam Myrow
       ` Alex Snow
         ` Adam Myrow
           ` Alex Snow
             ` Adam Myrow
               ` Alex Snow [this message]
 ` Jude DaShiell

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='005301c26f7f$333c1320$6401a8c0@computer' \
    --to=alex_snow@gmx.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).