Wbumount has two goals: (1): Make a "statement" how i would deal with the "umount - device is busy"-problem on the free desktop. (2): To provide a simple tool which makes life easier for people using the linux desktop - until someone comes up with a better solution.
Wbumount helps unix destop users to find out, which processes block unmounting or ejecting devices (such as cdroms, usb-harddisks...).
Wbumount only deals with mount points which are under user control ("user"-option in fstab or mtab).
wbumount consists of two parts:
Why show a list of processes to the user when he wants to umount a device? No other operating System does such a stupid thing!First, i believe that a good desktop-GUI should not hide the underlying operating-system from the user, but rather make it more transparent and easier to handle. I think there are only two ways to solve the "umount - device is busy" annoyance on the free desktop:
I would prefer the second option. Especially on read/write devices (USB-harddisks...). With a "clean" umount one can be sure, that the filesystem is not getting messed up. Why does wbumount-gtk list the file managers next to "fam"? Fam is used by a lot of applications!It's just a guess - most of the times it's true. Unfortunately "fam" does not tell us, which process has created a certain monitor. Fam lacks a control/status-api - and that's very bad. My drives don't show up in the "Mountpoint"-menu.Look at your /etc/mtab! Wbumount only deals with devices, which can be mounted/unmounted by the current user ("user" flag in fstab/mtab). Are you using supermount? |
"fuser" from the psmisc package http://psmisc.sourceforge.net/
To use the gui-frontend "wbumount-gtk" you will need pygtk2.0 (http://www.pygtk.org). People who use package-based distros might need the "pygtk2.0-devel" package.
wbumount [mountpoint] wbumount-gtk [mountpoint (optional)]
./configure make su make install
Before downloading, read the LICENSE.