From: joshk@triplehelix.org (Joshua Kwan)
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Can't eject a previously mounted CD?
Date: Fri, 26 Dec 2003 19:12:57 -0800 [thread overview]
Message-ID: <20031227031257.GG12871@triplehelix.org> (raw)
In-Reply-To: <3FECD2FB.4070008@ntlworld.com>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
On Sat, Dec 27, 2003 at 12:31:55AM +0000, Matt wrote:
> If you are on debian i have noticed recently that gnomevfs (on unstable)
> requires famd. famd will open /cdrom after it is mounted and run a dir
> notification on it. now i think famd needs some fixing, firstly to not
> bother running dir notice on ro filesystems, and secondly allow an
> authorised user (other than the original program (in this case
> nautilus)) to drop specific mount point dirs from the notification list.
> so yes this is a userland problem as far as i can see.
I am using Debian. This is a good point. However, I have no component of
fam installed on this Debian machine at all.
And why does the eject command work? I decided to strace it to see where
it gets this invalid argument from..
open("/dev/hdc", O_RDONLY|O_NONBLOCK) = 3
ioctl(3, 0x5309, 0xbffff948) = -1 EIO (Input/output error)
ioctl(3, FIBMAP, 0xbffff7f0) = 0
ioctl(3, FIBMAP, 0xbffff7f0) = 0
ioctl(3, FIBMAP, 0xbffff7f0) = 0
ioctl(3, BLKRRPART, 0xbffff7f0) = -1 EINVAL (Invalid argument)
ioctl(3, FDEJECT, 0xbffff948) = -1 EINVAL (Invalid argument)
ioctl(3, SNDCTL_MIDI_MPUMODE, 0xbffff900) = -1 EINVAL (Invalid argument)
It wasn't as revealing as I thought it would be, but does this mean
anything to someone more knowledgeable than I?
Note that as mentioned in a previous message, eject _does_ eject the CD.
--
Joshua Kwan
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2003-12-27 3:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 0:31 Can't eject a previously mounted CD? Matt
2003-12-27 0:44 ` Rob Love
2003-12-27 1:13 ` Ed Sweetman
2003-12-27 15:11 ` Matt
2003-12-27 3:12 ` Joshua Kwan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-29 1:56 Walt H
2003-12-29 2:04 ` Ed Sweetman
2003-12-29 3:45 ` Walt H
2003-12-29 6:23 ` Ed Sweetman
2003-12-29 7:41 ` Ed Sweetman
2003-12-29 7:56 ` Ed Sweetman
2003-12-29 16:36 ` Walt H
2003-12-29 17:53 ` Ed Sweetman
2003-12-29 18:05 ` Walt H
2003-12-29 19:23 ` Walt H
2003-12-29 19:40 ` Jens Axboe
2003-12-26 8:15 Joshua Kwan
2003-12-26 10:34 ` Vojtech Pavlik
2003-12-26 19:44 ` Joshua Kwan
2003-12-26 19:54 ` Samuel Flory
2003-12-26 20:27 ` Joshua Kwan
2003-12-26 23:26 ` Ed Sweetman
2003-12-26 23:56 ` Nuno Silva
2003-12-27 2:28 ` Joshua Kwan
2003-12-29 0:20 ` Samuel Flory
2003-12-29 0:28 ` Ed Sweetman
2003-12-29 1:36 ` Ed Sweetman
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=20031227031257.GG12871@triplehelix.org \
--to=joshk@triplehelix.org \
--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