Re: [pickup] [RFC/PATCH] Nonotify - A simplistic way to determine directory content changes

[nf <nf2 scheinwelt at>]

> 1. There is the MMC2 eject event, that's also handled by HAL now, but
> only few devices support it
> (http://freedesktop.org/pipermail/hal/2004-May/000237.html and
> further, also in June).
> 2. Just unlock the drive (using ioctl()), and umount *when the media
> is already removed*, i.e. after we got the HAL call that the disc was
> removed, which is, in fact, bad. This is the way we handle stuff now
> tough.

I think number two (auto-Umounting when the media was removed) is a cool
thing. I don't believe in auto-mounting though. Mounting should be done
manually by the user by clicking on a drive-icon.

And now - my opinion on the drive-locking issue (maybe i am repeating
myself):

-) Cdroms don't need to get locked, because they are read-only. Locking
only makes sense for read/write devices (To prevent file-system
corruption).

-) Most other devices (Floppies, USB-Harddisks) cannot get locked
because they just don't have a lock.

--> FORGET about locking and NEVER lock anything!! CDROM-door-locking is
just a senseless tradition. ;-)

Please try to solve everything at the lowest possible level (in the
kernel) and keep things as simple as possible! Every new virtual-xyz
abstraction or event layer seems to cause even more problems...

Norbert