and the drive stays around. But if I do the same using mount/unmount on the command line, the drive and volume both go away, and gvfs does not know about the loop mount at all if I mount to /mnt. When mounting to /media/, it does work, though. This is desired behaviour, as otherwise the UI would be cluttered with loop mounts which are "system internal" (such as /mnt or temporary mounts from usb-creator).
If I mount/unmount the loop device in nautilus (i. e. through gvfs), it seems to work well:
Volume changed: 'Ubuntu 11.04 amd64' nitorGdu) removable- media-file] [drive- removable- media] [drive-removable] [drive] automount= 0
Volume(0): Ubuntu 11.04 amd64
Type: GProxyVolume (GProxyVolumeMo
ids:
unix-device: '/dev/loop0'
label: 'Ubuntu 11.04 amd64'
themed icons: [drive-
can_mount=1
can_eject=0
should_
Mount added: 'Ubuntu 11.04 amd64' /media/ Ubuntu% 2011.04% 20amd64 nitorGdu) location= file:// /media/ Ubuntu% 2011.04% 20amd64 removable- media-file] [drive- removable- media] [drive-removable] [drive] types: x-content/ win32-software
Mount(0): Ubuntu 11.04 amd64 -> file://
Type: GProxyMount (GProxyVolumeMo
default_
themed icons: [drive-
x_content_
can_unmount=1
can_eject=0
is_shadowed=0
and the drive stays around. But if I do the same using mount/unmount on the command line, the drive and volume both go away, and gvfs does not know about the loop mount at all if I mount to /mnt. When mounting to /media/, it does work, though. This is desired behaviour, as otherwise the UI would be cluttered with loop mounts which are "system internal" (such as /mnt or temporary mounts from usb-creator).