On Thu, 5 Jan 2006, Danny Kukawka <dkukawka@suse.de> wrote:-
On Thursday 05 January 2006 03:46, David Bolt wrote:
Don't bother using mount. Just plug it in and, after a few moments, hotplug
No, it's not hotplug, it's a HAL mount helper.
My mistake, thanks for pointing it out. You can tell I'm still more used to using hotplug can't you :)
should have picked it up and created the mount point for it. Just looking into the directory is enough for it to be mounted.
One annoying feature that I have noticed with both SUSE 9.3 and 10.0[0], is that a device mounted this way doesn't show it's free capacity with "df" and I have to either guess just how much free space is left, or temporarily mount the file-system as root to find out.
IMO this should also work if you temporarily access the device or a directory/file on the device as normal user. I think this is a problem of submount/subfs and this should be present longer than 9.3 ago.
With 9.0 and 9.1, hotplug controls the USB devices, creates the directories under /media, but doesn't mount the device. Instead, a normal user is allowed to mount a device, which then lets df return the proper figures for usage, capacity and free space. This isn't done under 10.0. Instead HAL does the job hotplug used to do, but it also looks like it automounts the device whenever it's accessed. It's this difference that stops df working properly and requires the use of mount/umount as root to provide the same information. Personally, I can see benefits to both methods. HAL allows devices to literally unplugged at any time, reading/writing from/to the device notwithstanding, but df doesn't supply information for the device. Hotplug allows users to get information but requires the device be mounted/unmounted before you can use it. What would be nice is to retain the ease of use of HAL, and also be able to see the device status without needing to become root or use sudo. <FX:time passes and tests carried out> Looks like I was partially wrong. I can get the information from df, if I perform a df with that specific mount point, and if I do so 2 seconds, or less, after performing some other action on the device: davjam@adder:~> ls /media/usbdisk >/dev/null ; df ; sleep 2 ; df /media/usbdisk Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda16 3739652 246748 3302940 7% / <snippety multiple partitions> //my-ste/spam 62918572 32800004 30118568 53% /media/spam //playing/shared 113108992 86861824 26247168 77% /media/shared //playing/shares 82567168 24102912 58464256 30% /media/share Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 511712 22728 488984 5% /media/usbdisk davjam@adder:~> ls /media/usbdisk >/dev/null ; df ; sleep 3 ; df /media/usbdisk Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda16 3739652 246748 3302940 7% / <snippety occurred again> //my-ste/spam 62918572 32801508 30117064 53% /media/spam //playing/shared 113108992 86861824 26247168 77% /media/shared //playing/shares 82567168 24102912 58464256 30% /media/share Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 0 0 0 - /media/usbdisk Regards, And have a Happy New Year David Bolt -- Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/ AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11 AMD2400(32) 768Mb SUSE 10.0 | RPC600 129Mb RISCOS 3.6 | Falcon 14Mb TOS 4.02 AMD2600(64) 512Mb SUSE 10.0 | A4000 4Mb RISCOS 3.11 | STE 4Mb TOS 1.62