> Does 'eject' work from the command line at all on your system?

Yes and no.

The eject command works great to open and close the drive tray --- until I insert a disk. When I insert a disk and the drive tray closes, the eject command stops working. When I use the drive button to eject the disk, the eject command thereafter starts working again.

Hence my previous comment that there might be some kind of soft lock occuring.

I don't know why this does not happen on your system. Do you build with both WITH_HAL=ON and WITH_TDEHW=ON? If yes, possibly HAL is grabbing the Eject and Safely Remove commands rather than TDEHW?

I see that the Safely Remove option is a service type:

Exec=kio_media_mounthelper -s %u

and the Eject command is a service type too:

Exec=kio_media_mounthelper -e %u

Looks like kio_media_mounthelper is a good place to troubleshoot? Perhaps that command builds differently under WITH_HAL and WITH_TDEHW?

> Regarding the CD/DVD mountpoint, I am not entirely
> comfortable using the disk volume name as the mountpoint.  I am especially
> concerned about what might happen if more than one disk uses the same
> name--normally this results in a nested mount on Linux, which is NOT what would
> be desired in this case.

Yet this is the way TDE creates mount points on a HAL system and has been that way for years. :-)

How many people have two optical drives on their system and how many people insert two identical disks with the same volume label? That would be one heck of an unusual corner case. :-)

I have a spare box with both a CD reader and a DVD burner that has both KDE3 and TDE installed. I'll burn two identical CDs and see what happens.

I don't think breaking from the tradition or being different from the other desktops with this one feature will go over well with users. I hate WTF moments. :-)

Darrell