From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: 7eggert@gmx.de, Arjan van de Ven <arjan@infradead.org>,
Dirk <noisyb@gmx.net>,
linux-kernel@vger.kernel.org
Subject: Re: PATCH/FIX for drivers/cdrom/cdrom.c
Date: Thu, 17 Aug 2006 16:09:17 +0100 [thread overview]
Message-ID: <1155827358.15195.103.camel@localhost.localdomain> (raw)
In-Reply-To: <20060817143633.GF13641@csclub.uwaterloo.ca>
Ar Iau, 2006-08-17 am 10:36 -0400, ysgrifennodd Lennart Sorensen:
> I think hal should get an error when it tries to open the cdrom device
> when the burning application is using it. It shouldn't even get a
If it uses O_EXCL it will find the device busy assuming both parties use
O_EXCL properly.
> chance to issue an ioctl. I was assuming hal doesn't keep the cdrom
> device open at all times (if it does, well that would be stupid).
Indeed but this is HAL so I suggest you strace it first 8)
next prev parent reply other threads:[~2006-08-17 14:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6Kxns-7AV-13@gated-at.bofh.it>
[not found] ` <6Kytd-1g2-31@gated-at.bofh.it>
[not found] ` <6KyCQ-1w7-25@gated-at.bofh.it>
2006-08-17 12:27 ` PATCH/FIX for drivers/cdrom/cdrom.c Bodo Eggert
2006-08-17 12:35 ` Arjan van de Ven
2006-08-18 12:31 ` Bodo Eggert
2006-08-18 12:53 ` Arjan van de Ven
2006-08-18 16:45 ` Alan Cox
2006-08-17 13:39 ` Alan Cox
2006-08-17 13:23 ` Lennart Sorensen
2006-08-17 13:41 ` Jeff Garzik
2006-08-17 13:54 ` Lennart Sorensen
2006-08-17 14:38 ` Helge Hafting
2006-08-18 12:39 ` Bodo Eggert
2006-08-17 13:48 ` Alan Cox
2006-08-17 14:36 ` Lennart Sorensen
2006-08-17 14:38 ` Arjan van de Ven
2006-08-17 15:09 ` Alan Cox [this message]
2006-08-19 17:52 ` Oleg Verych
2006-08-21 17:31 ` Lennart Sorensen
2006-08-16 17:26 Dirk
2006-08-16 17:40 ` Jan Engelhardt
2006-08-16 18:37 ` Dirk
2006-08-16 18:37 ` Lennart Sorensen
2006-08-16 18:44 ` Arjan van de Ven
2006-08-16 19:30 ` Dirk
2006-08-16 19:08 ` Alan Cox
2006-08-16 22:25 ` Andrew Morton
2006-08-17 7:50 ` Jan Engelhardt
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=1155827358.15195.103.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=7eggert@gmx.de \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=noisyb@gmx.net \
/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