public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Janina Sajka <janina@afb.net>
To: <blinux-list@redhat.com>
Subject: Re: Problems with Brltty
Date: Mon, 19 Nov 2001 10:58:09 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0111191053210.2815-100000@toccata.grg.afb.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0111182218000.7615-100000@rupin.localnet>

Not that anyone asked ...

But I though I'd throw in my 2 cents regarding kudzu.

I have turned it off on my portable system. I find it's just a nuisance 
when I need to boot because it comes up too often asking me to remove 
something that it will then ask me to add next time I have the system 
docked. I find it easier to simply run kudzu from the command line when I 
truly have new hardware that requires configuration. It's not hard to 
remember this.

Frankly, I don't do this on my office systems, because it's not a problem 
there. I rarely boot them, and when I do, it's usually a matter of new 
hardware, so I appreciate kudzu at those times.

But the other question in the current circumstance with John seems to be 
that the braille display should be registered somehow with linux as a 
recognized and supported device, so that it will not be probed and reset 
by kudzu. Am I wrong about this?





  reply	other threads:[~ UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John J. Boyer
 ` Nicolas Pitre
   ` L. C. Robinson
     ` Nicolas Pitre
       ` L. C. Robinson
         ` Janina Sajka [this message]
           ` Dave Mielke
         ` Jude DaShiell
       ` John J. Boyer
         ` Nicolas Pitre
           ` Cheryl Homiak
             ` Dave Mielke
         ` kudzu Cheryl Homiak
           ` kudzu L. C. Robinson
         ` Problems with Brltty Dave Mielke
           ` John J. Boyer
             ` Dave Mielke
       ` Cheryl Homiak

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.4.33.0111191053210.2815-100000@toccata.grg.afb.net \
    --to=janina@afb.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).