kdeeject - unmouting media patch

Christian Hubinger e9806056 at student.tuwien.ac.at
Tue Jun 10 12:27:37 BST 2003

Hash: SHA1

On Tuesday 10 June 2003 08:44, Stephan Kulow wrote:
> On Monday 09 June 2003 23:06, you wrote:
> > Hi!
> >
> > For quiet a long time it really got on my nerves that when you use the
> > context menu entry "Eject" at the CDROM/CDRW desktop links a error
> > message pops up saying "Eject /dev/cdrom failed!" if the device is still
> > mounted.
> >
> > In the attatchement there is a small patch for
> > (kdebase/kdesktop/kdeeject) that checks if the device is mounted and asks
> > to unmount it before ejecting.
> >
> > Please let me know what you think about it.
> From man eject:
> "If the device is currently mounted, it is unmounted before ejecting."

not really :-(
here on my woody ejectt unmounts the device when i type eject /cdrom BUT if 
i'm using the device name eject /dev/cdrom (which is a symbolic link) eject 
does not umount and throws an error.
i don't know if thats special to the debian version of eject but here it 
definately does not work with the real device names (as used in /etc/fstab)

animal at shit:~$ mount /dev/cdrom
animal at shit:~$ eject /dev/cdrom <- does not work
eject: unable to eject, last error: Invalid argument
animal at shit:~$ umount /dev/cdrom
animal at shit:~$ eject /dev/cdrom <- works

animal at shit:~$ mount /dev/cdrom
animal at shit:~$ eject /cdrom <- works

so this seems to be a bug in eject. But i think for a quick workaround of that 
situation the patch i sent should be ok.

Please let me know if this behaviour is special to the debian version of 
eject, so that i can fill a bugreport about it. 


- -- 
Windows is a 32 bit shell for a 16 bit extension to an 8 bit
Operating System designed for a 4 bit microchip by a 2 bit
company which can't stand one bit of competition.
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the kde-core-devel mailing list