From: john slee <indigoid@higherplane.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, dank@kegel.org
Subject: Re: Asynchronous CDROM Events in Userland
Date: Mon, 4 Feb 2002 23:43:45 +1100 [thread overview]
Message-ID: <20020204124344.GA4757@higherplane.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0202032333200.1158-100000@rtlab.med.cornell.edu> <a3l4uc$laf$1@cesium.transmeta.com>
In-Reply-To: <a3l4uc$laf$1@cesium.transmeta.com>
[ added dan to cc list ]
On Sun, Feb 03, 2002 at 09:07:24PM -0800, H. Peter Anvin wrote:
> > If not what do you guys think about extensions to the cdrom drivers to
> > handle these types of things?
> >
>
> Rather than a signal, it should be a file descriptor of some sort, so
> one can select() etc on it. Personally I can't imagine polling would
> take any appreciable amount of resources, though.
>
> A more important issue is probably to get notification when the eject
> button is pushed and the device is locked, so that it can try to
> umount and eject it, unless busy.
not so long ago dan kegel suggested an interface to signals based on
file descriptors, and perhaps even an alpha patch implementing such.
this allowed you to select() on them.
http://marc.theaimsgroup.com/?l=linux-kernel&m=99356014431024&w=2
of particular interest is this quote from dan's fantasy manpage:
> HISTORY
> sigopen() first appeared in the 2.5.2 Linux kernel.
a bit late, but an uncanny prediction.
dan, are you nostradamus ? :-)
j.
--
R N G G "Well, there it goes again... And we just sit
I G G G here without opposable thumbs." -- gary larson
next prev parent reply other threads:[~2002-02-04 12:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 4:41 Asynchronous CDROM Events in Userland Calin A. Culianu
2002-02-04 5:07 ` H. Peter Anvin
2002-02-04 5:19 ` Calin A. Culianu
2002-02-04 12:43 ` john slee [this message]
2002-02-04 15:23 ` Calin A. Culianu
2002-02-04 16:20 ` H. Peter Anvin
2002-02-04 7:04 ` Erik Andersen
2002-02-04 7:57 ` Jens Axboe
2002-02-04 9:33 ` Gregor Jasny
2002-02-04 9:39 ` Jens Axboe
2002-02-04 14:05 ` hugang
2002-02-05 7:43 ` Jens Axboe
2002-02-04 12:16 ` Alan Cox
2002-02-04 20:51 ` oops booting 2.4.18-pre7-ac3 Todd M. Roy
2002-02-05 4:04 ` Asynchronous CDROM Events in Userland Stevie O
2002-02-05 4:28 ` H. Peter Anvin
2002-02-05 4:44 ` Calin A. Culianu
2002-02-05 4:47 ` H. Peter Anvin
[not found] ` <a3l4uc@cesium.transmeta.com>
2002-02-06 14:22 ` Pavel Machek
2002-02-06 22:48 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2002-02-05 13:17 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=20020204124344.GA4757@higherplane.net \
--to=indigoid@higherplane.net \
--cc=dank@kegel.org \
--cc=hpa@zytor.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