From: LA Walsh <law@sgi.com>
To: God <atm@pinky.penguinpowered.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Annoying CD-rom driver error messages
Date: Tue, 06 Mar 2001 08:31:02 -0800 [thread overview]
Message-ID: <3AA510C6.7A2190D8@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0103060428100.878-100000@scotch.homeip.net>
God wrote:
>
> On Mon, 5 Mar 2001, Alan Cox wrote:
>
> > > > this isnt a kernel problem, its a _very_ stupid app
> > > ---
> > > Must be more than one stupid app...
> >
> > Could well be. You have something continually trying to open your cdrom and
> > see if there is media in it
>
> Gnome / KDE? does exactly that... (rather annoying too) .. what app
> specificaly I don't know...
---
So I'm still wondering what the "approved and recommended" way for a program
to be "automatically" informed of a CD or floppy change/insertion and be able to
informed of media 'type' w/o kernel warnings/error messages. It sounds like
there is no kernel support for this so far?
Then it seems the less ideal question is what is the "approved and recommended
way for a program to "poll" such devices to check for 'changes' and 'media type'
without the kernel generating spurious WARNINGS/ERRORS?
--
L A Walsh | Trust Technology, Core Linux, SGI
law@sgi.com | Voice: (650) 933-5338
next prev parent reply other threads:[~2001-03-06 16:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 17:27 Annoying CD-rom driver error messages LA Walsh
2001-03-05 17:37 ` LA Walsh
2001-03-05 17:47 ` Alan Cox
2001-03-05 17:48 ` LA Walsh
2001-03-05 17:51 ` LA Walsh
2001-03-05 17:56 ` Jens Axboe
2001-03-05 18:13 ` Alan Cox
2001-03-05 18:16 ` LA Walsh
2001-03-06 9:29 ` God
2001-03-06 16:31 ` LA Walsh [this message]
2001-03-06 16:49 ` Alan Cox
2001-03-06 16:53 ` LA Walsh
2001-03-06 17:02 ` Alan Cox
2001-03-06 17:04 ` LA Walsh
2001-03-06 16:52 ` Francis Galiegue
-- strict thread matches above, loose matches on Subject: below --
2001-03-06 17:28 David Balazic
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=3AA510C6.7A2190D8@sgi.com \
--to=law@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=atm@pinky.penguinpowered.com \
--cc=linux-kernel@vger.kernel.org \
/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