Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote:
But it does:
$ cat /proc/mounts | grep flashdisk
/dev/flashdisk /media/flashdisk vfat
rw,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1
0 0
(But not as /dev/sda, of course.)
That's the problem: /dev/flashdisk and /dev/sda do not identify the same
device (i.e. one is a char device and the other's a block device, or the
rdev numbers do not match) and the device file paths are different. So
how should the software know that it's mounted?
Just to be sure; post the output of ls -ld /dev/{sda,flashdisk}
Regards, Mathias
Benedikt
___
Thunar-dev mailing list
Thunar-dev@xfce.org
http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt.
Benedikt Meurer, 29.01.2007 10:48:
Mathias Brodala wrote:
$ cat /proc/mounts | grep flashdisk
/dev/flashdisk /media/flashdisk vfat
rw,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1
0 0
(But not as /dev/sda, of course.)
That's the problem: /dev/flashdisk and /dev/sda do not identify the same
device (i.e. one is a char device and the other's a block device, or the
rdev numbers do not match) and the device file paths are different. So
how should the software know that it's mounted?
Just to be sure; post the output of ls -ld /dev/{sda,flashdisk}
But I alread told you[0] that /dev/flashdisk is just a symlink to /dev/sda
provided by one of my custom udev rules. So it IS the same device, only known
under an unstable (read: changes depending on the order I plug the devices in)
and a more meaningful and stable identifier.
Regards, Mathias
[0] http://foo-projects.org/pipermail/thunar-dev/2007-January/003852.html
--
debian/rules
signature.asc
Description: OpenPGP digital signature
___
Thunar-dev mailing list
Thunar-dev@xfce.org
http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote:
$ cat /proc/mounts | grep flashdisk
/dev/flashdisk /media/flashdisk vfat
rw,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1
0 0
(But not as /dev/sda, of course.)
That's the problem: /dev/flashdisk and /dev/sda do not identify the same
device (i.e. one is a char device and the other's a block device, or the
rdev numbers do not match) and the device file paths are different. So
how should the software know that it's mounted?
Just to be sure; post the output of ls -ld /dev/{sda,flashdisk}
But I alread told you[0] that /dev/flashdisk is just a symlink to /dev/sda
provided by one of my custom udev rules. So it IS the same device, only known
under an unstable (read: changes depending on the order I plug the devices in)
and a more meaningful and stable identifier.
Well, if it's a symlink, then exo-mount-point should be able to locate
that... weird... post the output of ls -ld /dev/{sda,flashdisk}.
Regards, Mathias
Benedikt
___
Thunar-dev mailing list
Thunar-dev@xfce.org
http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Benedikt Meurer wrote:
Mathias Brodala wrote:
$ cat /proc/mounts | grep flashdisk
/dev/flashdisk /media/flashdisk vfat
rw,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1
0 0
(But not as /dev/sda, of course.)
That's the problem: /dev/flashdisk and /dev/sda do not identify the same
device (i.e. one is a char device and the other's a block device, or the
rdev numbers do not match) and the device file paths are different. So
how should the software know that it's mounted?
Just to be sure; post the output of ls -ld /dev/{sda,flashdisk}
But I alread told you[0] that /dev/flashdisk is just a symlink to /dev/sda
provided by one of my custom udev rules. So it IS the same device, only known
under an unstable (read: changes depending on the order I plug the devices
in)
and a more meaningful and stable identifier.
Well, if it's a symlink, then exo-mount-point should be able to locate
that... weird... post the output of ls -ld /dev/{sda,flashdisk}.
And just to be sure: You are using Thunar 1.0 and exo 0.3.2 now?
Benedikt
___
Thunar-dev mailing list
Thunar-dev@xfce.org
http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt.
Benedikt Meurer, 29.01.2007 11:24:
Benedikt Meurer wrote:
Mathias Brodala wrote:
$ cat /proc/mounts | grep flashdisk
/dev/flashdisk /media/flashdisk vfat
rw,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1
0 0
(But not as /dev/sda, of course.)
That's the problem: /dev/flashdisk and /dev/sda do not identify the same
device (i.e. one is a char device and the other's a block device, or the
rdev numbers do not match) and the device file paths are different. So
how should the software know that it's mounted?
Just to be sure; post the output of ls -ld /dev/{sda,flashdisk}
But I alread told you[0] that /dev/flashdisk is just a symlink to /dev/sda
provided by one of my custom udev rules. So it IS the same device, only
known
under an unstable (read: changes depending on the order I plug the devices
in)
and a more meaningful and stable identifier.
Well, if it's a symlink, then exo-mount-point should be able to locate
that... weird... post the output of ls -ld /dev/{sda,flashdisk}.
And just to be sure: You are using Thunar 1.0 and exo 0.3.2 now?
No, not yet. (Since when exists version 1.0 of Thunar? Wasn’t version 0.8
released just recently?) Thunar is running as 0.5.0rc2 and libexo as
0.3.1.12rc2.
If Thunar only needs to access libexo files via file system (and does not need
them to be loaded in memory or something like that), then I can try building
both from SVN once again and check if the error appears there. I’ll look if I
can do this today.
Regards, Mathias
--
debian/rules
signature.asc
Description: OpenPGP digital signature
___
Thunar-dev mailing list
Thunar-dev@xfce.org
http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote: No, not yet. (Since when exists version 1.0 of Thunar? Wasn’t version 0.8 released just recently?) Thunar is running as 0.5.0rc2 and libexo as 0.3.1.12rc2. Err, 0.8.0 of course and there's the problem: 0.5.0rc2 doesn't resolve device symlinks. You'll need thunar 0.8.0 and exo 0.3.2. Regards, Mathias Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 29.01.2007 12:36: Mathias Brodala wrote: No, not yet. (Since when exists version 1.0 of Thunar? Wasn’t version 0.8 released just recently?) Thunar is running as 0.5.0rc2 and libexo as 0.3.1.12rc2. Err, 0.8.0 of course and there's the problem: 0.5.0rc2 doesn't resolve device symlinks. You'll need thunar 0.8.0 and exo 0.3.2. Yeah, you’re right. I tried it with Thunar from SVN which I build the last time and there no error appears when mounting. So this issue seems solved to me, I just have to wait a few more days until the upload of Xfce 4.4 is completed and I can upgrade. So, as many times before: Thanks! Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello. Mathias Brodala, 16.01.2007 18:09: I guess you could use volume.label of the device but I must admit that I don’t know how to set volume labels for fat32 partitions/devices. I tried mkdosfs but the label did not appear in hal-device’s output. Now it did after I let the flashdisk lie around for a while. (Don’t ask me why it didn’t work immediately.) The correct label appears in hal-device’s output now and Thunar shows this one but doesn’t allow me to mount it through this. It states that there’s no mount point for /dev/sda. And of course I set up none by purpose; as I said, I want Thunar to mount /dev/flashdisk. But it seems like Thunar doesn’t know of this device and its mount point. Any ideas? Regards, Mathias PS: After an mount error occured, Thunar should not activate „Unmount device“, since the device could not been mounted. It should only do this on successful mounts. -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote: PS: After an mount error occured, Thunar should not activate „Unmount device“, since the device could not been mounted. It should only do this on successful mounts. Is the volume.is_mounted property set? Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 28.01.2007 17:41: Mathias Brodala wrote: PS: After an mount error occured, Thunar should not activate „Unmount device“, since the device could not been mounted. It should only do this on successful mounts. Is the volume.is_mounted property set? Yes, it is. Before: volume.is_mounted = false (bool) volume.mount_point = '' (string) After: volume.is_mounted = true (bool) volume.mount_point = '/media/flashdisk' And now that I’ve seen this output, I tried mounting it again, got the mentioned error but this time actually entered the directory. And what can I say: Thunar did, aside from the error, mount the device correctly. (And obviously did before; the error message lead me to think that the mount has failed.) Can you do something about the error message? Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote: Hello Benedikt. Benedikt Meurer, 28.01.2007 17:41: Mathias Brodala wrote: PS: After an mount error occured, Thunar should not activate „Unmount device“, since the device could not been mounted. It should only do this on successful mounts. Is the volume.is_mounted property set? Yes, it is. Before: volume.is_mounted = false (bool) volume.mount_point = '' (string) After: volume.is_mounted = true (bool) volume.mount_point = '/media/flashdisk' And now that I’ve seen this output, I tried mounting it again, got the mentioned error but this time actually entered the directory. And what can I say: Thunar did, aside from the error, mount the device correctly. (And obviously did before; the error message lead me to think that the mount has failed.) Can you do something about the error message? Post the error message. Regards, Mathias Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 28.01.2007 19:06: Mathias Brodala wrote: Benedikt Meurer, 28.01.2007 17:41: Mathias Brodala wrote: […] I tried mounting it again, got the mentioned error but this time actually entered the directory. And what can I say: Thunar did, aside from the error, mount the device correctly. (And obviously did before; the error message lead me to think that the mount has failed.) Can you do something about the error message? Post the error message. Follows: Failed to mount Flashdisk. Failed to determine the mount point for /dev/sda. Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote: Hello Benedikt. […] I tried mounting it again, got the mentioned error but this time actually entered the directory. And what can I say: Thunar did, aside from the error, mount the device correctly. (And obviously did before; the error message lead me to think that the mount has failed.) Can you do something about the error message? Post the error message. Follows: Failed to mount Flashdisk. Failed to determine the mount point for /dev/sda. Thunar was unable to find /dev/sda in /proc/mounts, which is rather weird if the file system was mounted. Regards, Mathias Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 28.01.2007 22:03: Mathias Brodala wrote: […] I tried mounting it again, got the mentioned error but this time actually entered the directory. And what can I say: Thunar did, aside from the error, mount the device correctly. (And obviously did before; the error message lead me to think that the mount has failed.) Can you do something about the error message? Post the error message. Follows: Failed to mount Flashdisk. Failed to determine the mount point for /dev/sda. Thunar was unable to find /dev/sda in /proc/mounts, which is rather weird if the file system was mounted. So the question is why Thunar searches for a way to mount /dev/sda when it already did mount it? Something more I can do here? Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Samuel. Samuel Verstraete, 17.01.2007 08:39: Mathias Brodala wrote: OK, then I guess it’s my turn to find out how to set labels for fat32 devices. $ mkfs.vfat mkfs.vfat 2.11 (12 Mar 2005) No device specified! Usage: mkdosfs [-A] [-c] [-C] [-v] [-I] [-l bad-block-file] [-b backup-boot-sector] [-m boot-msg-file] [-n volume-name] [-i volume-id] [-s sectors-per-cluster] [-S logical-sector-size] [-f number-of-FATs] [-h hidden-sectors] [-F fat-size] [-r root-dir-entries] [-R reserved-sectors] /dev/name [blocks] hint... you want the volume-name ;) I already tried that first (and wrote that I did) but it didn’t help; no label. Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 16.01.2007 08:39: Mathias Brodala wrote: […] This [error] appears when I try to compile libexo from SVN. Pass --enable-maintainer-mode to autogen.sh. OK, this worked. Now could you tell me how I can point Thunar to look for libexo in my special directory instead of the usual ones? It is currently installed under ~/Archive/deb/xfce/exo/svn/install and Thunar has to look there since my local version is too old. Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote: Hello Benedikt. Benedikt Meurer, 16.01.2007 08:39: Mathias Brodala wrote: […] This [error] appears when I try to compile libexo from SVN. Pass --enable-maintainer-mode to autogen.sh. OK, this worked. Now could you tell me how I can point Thunar to look for libexo in my special directory instead of the usual ones? It is currently installed under ~/Archive/deb/xfce/exo/svn/install and Thunar has to look there since my local version is too old. Setting PKG_CONFIG_PATH, LDFLAGS and CPPFLAGS should do the trick. Tho, there I'm no sure if libtool will pick up the correct lib if the old one is installed in the linker default path. Regards, Mathias Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 16.01.2007 16:35: Mathias Brodala wrote: Hello Benedikt. Benedikt Meurer, 16.01.2007 08:39: Mathias Brodala wrote: […] This [error] appears when I try to compile libexo from SVN. Pass --enable-maintainer-mode to autogen.sh. OK, this worked. Now could you tell me how I can point Thunar to look for libexo in my special directory instead of the usual ones? It is currently installed under ~/Archive/deb/xfce/exo/svn/install and Thunar has to look there since my local version is too old. Setting PKG_CONFIG_PATH, LDFLAGS and CPPFLAGS should do the trick. Tho, there I'm no sure if libtool will pick up the correct lib if the old one is installed in the linker default path. It worked like a charm. The command I used, just for the archive: $ PKG_CONFIG_PATH=../../../exo/svn/install/lib/pkgconfig \ LDFLAGS=-L../../../exo/svn/install/lib \ CPPFLAGS=-I../../../exo/svn/install/include \ ./autogen.sh --enable-maintainer-mode Thunar could be started, but it shows my flashdisk as „131M entfernbarer Datenträger“ which is not that much better to me than just „sda“. Oh, and after plugging in the device, the following messages appeared: libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 16.01.2007 17:34: Mathias Brodala wrote: Thunar could be started, but it shows my flashdisk as „131M entfernbarer Datenträger“ which is not that much better to me than just „sda“. Well, this means that no better string could be determined. The fallback to the device file name was replaced with size Removable Volume, which is consistent with HAL and gnome-vfs. This is IMHO better than sda as it tells you (a) it's removable and (b) the size. You got one point there. The information that the device is removable is not that useful since all devices in that section are. But the size at least allows me to determine what’s what. With information about the device tree I could try to add some more smartness to exo-hal to figure out an even better name for your flashdisk. You’re talking about my devices? What exactly do you need? Oh, and after plugging in the device, the following messages appeared: libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. Looks like an old HAL version. Version 0.5.8.1 is running here. But since it’s only an info, I won’t worry about it. Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote: You got one point there. The information that the device is removable is not that useful since all devices in that section are. But the size at least allows me to determine what’s what. Right, I forgot about that. ;-) But exo-hal cannot only be used for volumes, but for HAL devices in general... With information about the device tree I could try to add some more smartness to exo-hal to figure out an even better name for your flashdisk. You’re talking about my devices? What exactly do you need? hal-device dump of the volume, it's storage device and the parent of the storage device might help. Oh, and after plugging in the device, the following messages appeared: libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. Looks like an old HAL version. Version 0.5.8.1 is running here. But since it’s only an info, I won’t worry about it. Hm, 0.5.8.20061224 here, but I don't see that warning. Regards, Mathias Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt.
Benedikt Meurer, 16.01.2007 17:46:
Mathias Brodala wrote:
With information about the device tree I could try to add some more
smartness to exo-hal to figure out an even better name for your flashdisk.
You’re talking about my devices? What exactly do you need?
hal-device dump of the volume, it's storage device and the parent of the
storage device might help.
Here it is:
0: udi = '/org/freedesktop/Hal/devices/volume_uuid_F874_A601'
volume.unmount.valid_options = { 'lazy' } (string list)
volume.mount.valid_options = { 'ro', 'sync', 'dirsync', 'noatime',
'nodiratime', 'noexec', 'quiet', 'remount', 'exec', 'utf8', 'shortname=',
'codepage=', 'iocharset=', 'umask=', 'dmask=', 'fmask=', 'uid=' } (string
list)
org.freedesktop.Hal.Device.Volume.method_execpaths = { 'hal-storage-mount',
'hal-storage-unmount', 'hal-storage-eject' } (string list)
org.freedesktop.Hal.Device.Volume.method_argnames = { 'mount_point fstype
extra_options', 'extra_options', 'extra_options' } (string list)
org.freedesktop.Hal.Device.Volume.method_signatures = { 'ssas', 'as', 'as'
} (string list)
org.freedesktop.Hal.Device.Volume.method_names = { 'Mount', 'Unmount',
'Eject' } (string list)
info.interfaces = { 'org.freedesktop.Hal.Device.Volume' } (string list)
volume.ignore = false (bool)
info.udi = '/org/freedesktop/Hal/devices/volume_uuid_F874_A601' (string)
info.product = 'Volume (vfat)' (string)
volume.size = 131072000 (0x7d0) (uint64)
volume.num_blocks = 256000 (0x3e800) (int)
volume.block_size = 512 (0x200) (int)
info.capabilities = { 'volume', 'block' } (string list)
info.category = 'volume' (string)
volume.is_partition = false (bool)
volume.is_disc = false (bool)
volume.linux.is_device_mapper = false (bool)
volume.is_mounted_read_only = false (bool)
volume.is_mounted = false (bool)
volume.mount_point = '' (string)
volume.label = '' (string)
volume.uuid = 'F874-A601' (string)
volume.fsversion = 'FAT32' (string)
volume.fsusage = 'filesystem' (string)
volume.fstype = 'vfat' (string)
storage.model = '' (string)
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
(string)
block.is_volume = true (bool)
block.minor = 0 (0x0) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sda' (string)
linux.hotplug_type = 3 (0x3) (int)
info.parent =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
(string)
linux.sysfs_path_device = '/sys/block/sda/fakevolume' (string)
linux.sysfs_path = '/sys/block/sda/fakevolume' (string)
1: udi =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
info.addons = { 'hald-addon-storage' } (string list)
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
(string)
info.udi =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
(string)
storage.partitioning_scheme = 'none' (string)
storage.removable.media_size = 131072000 (0x7d0) (uint64)
storage.requires_eject = false (bool)
storage.hotpluggable = true (bool)
info.capabilities = { 'storage', 'block' } (string list)
info.category = 'storage' (string)
info.product = 'USB 2.0 128MB' (string)
info.vendor = '' (string)
storage.size = 0 (0x0) (uint64)
storage.removable = true (bool)
storage.removable.media_available = true (bool)
storage.physical_device =
'/org/freedesktop/Hal/devices/usb_device_ea0_2168_31191A401F52404B_if0'
(string)
storage.lun = 0 (0x0) (int)
storage.firmware_version = '2.00' (string)
storage.serial = 'USB_USB_2.0_128MB_31191A401F52404B' (string)
storage.vendor = '' (string)
storage.model = 'USB 2.0 128MB' (string)
storage.drive_type = 'disk' (string)
storage.automount_enabled_hint = true (bool)
storage.media_check_enabled = true (bool)
storage.no_partitions_hint = false (bool)
storage.bus = 'usb' (string)
block.is_volume = false (bool)
block.minor = 0 (0x0) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sda' (string)
linux.hotplug_type = 3 (0x3) (int)
info.parent =
'/org/freedesktop/Hal/devices/usb_device_ea0_2168_31191A401F52404B_if0_scsi_host_scsi_device_lun0'
(string)
linux.sysfs_path_device = '/sys/block/sda' (string)
linux.sysfs_path = '/sys/block/sda' (string)
I guess you could use volume.label of the device but I must admit that I don’t
know how to set volume labels for fat32 partitions/devices. I tried mkdosfs but
the label did not appear in hal-device’s output.
Regards, Mathias
--
debian/rules
signature.asc
Description: OpenPGP digital signature
___
Thunar-dev mailing list
Thunar-dev@xfce.org
http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote:
Hello Benedikt.
Benedikt Meurer, 16.01.2007 17:46:
Mathias Brodala wrote:
With information about the device tree I could try to add some more
smartness to exo-hal to figure out an even better name for your flashdisk.
You’re talking about my devices? What exactly do you need?
hal-device dump of the volume, it's storage device and the parent of the
storage device might help.
Here it is:
0: udi = '/org/freedesktop/Hal/devices/volume_uuid_F874_A601'
volume.unmount.valid_options = { 'lazy' } (string list)
volume.mount.valid_options = { 'ro', 'sync', 'dirsync', 'noatime',
'nodiratime', 'noexec', 'quiet', 'remount', 'exec', 'utf8', 'shortname=',
'codepage=', 'iocharset=', 'umask=', 'dmask=', 'fmask=', 'uid=' } (string
list)
org.freedesktop.Hal.Device.Volume.method_execpaths = {
'hal-storage-mount', 'hal-storage-unmount', 'hal-storage-eject' } (string
list)
org.freedesktop.Hal.Device.Volume.method_argnames = { 'mount_point fstype
extra_options', 'extra_options', 'extra_options' } (string list)
org.freedesktop.Hal.Device.Volume.method_signatures = { 'ssas', 'as', 'as'
} (string list)
org.freedesktop.Hal.Device.Volume.method_names = { 'Mount', 'Unmount',
'Eject' } (string list)
info.interfaces = { 'org.freedesktop.Hal.Device.Volume' } (string list)
volume.ignore = false (bool)
info.udi = '/org/freedesktop/Hal/devices/volume_uuid_F874_A601' (string)
info.product = 'Volume (vfat)' (string)
volume.size = 131072000 (0x7d0) (uint64)
volume.num_blocks = 256000 (0x3e800) (int)
volume.block_size = 512 (0x200) (int)
info.capabilities = { 'volume', 'block' } (string list)
info.category = 'volume' (string)
volume.is_partition = false (bool)
volume.is_disc = false (bool)
volume.linux.is_device_mapper = false (bool)
volume.is_mounted_read_only = false (bool)
volume.is_mounted = false (bool)
volume.mount_point = '' (string)
volume.label = '' (string)
volume.uuid = 'F874-A601' (string)
volume.fsversion = 'FAT32' (string)
volume.fsusage = 'filesystem' (string)
volume.fstype = 'vfat' (string)
storage.model = '' (string)
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
(string)
block.is_volume = true (bool)
block.minor = 0 (0x0) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sda' (string)
linux.hotplug_type = 3 (0x3) (int)
info.parent =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
(string)
linux.sysfs_path_device = '/sys/block/sda/fakevolume' (string)
linux.sysfs_path = '/sys/block/sda/fakevolume' (string)
1: udi =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
info.addons = { 'hald-addon-storage' } (string list)
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
(string)
info.udi =
'/org/freedesktop/Hal/devices/storage_serial_USB_USB_2_0_128MB_31191A401F52404B'
(string)
storage.partitioning_scheme = 'none' (string)
storage.removable.media_size = 131072000 (0x7d0) (uint64)
storage.requires_eject = false (bool)
storage.hotpluggable = true (bool)
info.capabilities = { 'storage', 'block' } (string list)
info.category = 'storage' (string)
info.product = 'USB 2.0 128MB' (string)
info.vendor = '' (string)
storage.size = 0 (0x0) (uint64)
storage.removable = true (bool)
storage.removable.media_available = true (bool)
storage.physical_device =
'/org/freedesktop/Hal/devices/usb_device_ea0_2168_31191A401F52404B_if0'
(string)
storage.lun = 0 (0x0) (int)
storage.firmware_version = '2.00' (string)
storage.serial = 'USB_USB_2.0_128MB_31191A401F52404B' (string)
storage.vendor = '' (string)
storage.model = 'USB 2.0 128MB' (string)
storage.drive_type = 'disk' (string)
storage.automount_enabled_hint = true (bool)
storage.media_check_enabled = true (bool)
storage.no_partitions_hint = false (bool)
storage.bus = 'usb' (string)
block.is_volume = false (bool)
block.minor = 0 (0x0) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sda' (string)
linux.hotplug_type = 3 (0x3) (int)
info.parent =
'/org/freedesktop/Hal/devices/usb_device_ea0_2168_31191A401F52404B_if0_scsi_host_scsi_device_lun0'
(string)
linux.sysfs_path_device = '/sys/block/sda' (string)
linux.sysfs_path = '/sys/block/sda' (string)
I guess you could use volume.label of the device but I must admit that I don’t
know how to set volume labels for fat32 partitions/devices. I tried mkdosfs
but
the label did not appear in hal-device’s output.
The volume.label is used if not-empty. Besides that there doesn't seem
to be a lot of useful information available. Not even the info.vendor is
set. We could use info.product, but that's not really useful
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 16.01.2007 18:26: The volume.label is used if not-empty. Besides that there doesn't seem to be a lot of useful information available. Not even the info.vendor is set. We could use info.product, but that's not really useful either. OK, then I guess it’s my turn to find out how to set labels for fat32 devices. Thanks for your help once again. Oh, and thanks for thunar-volman too of course! Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
I had a similar problem, but plugging it into any Windows machine [I used my friends laptop] and setting it through there works lovely. No more fudding around for me! - Cory Christison Mathias Brodala wrote: Hello Benedikt. Benedikt Meurer, 16.01.2007 18:26: The volume.label is used if not-empty. Besides that there doesn't seem to be a lot of useful information available. Not even the info.vendor is set. We could use info.product, but that's not really useful either. OK, then I guess it’s my turn to find out how to set labels for fat32 devices. Thanks for your help once again. Oh, and thanks for thunar-volman too of course! Regards, Mathias ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
On Tue, 16 Jan 2007 15:58:26 -0600 Cory Christison [EMAIL PROTECTED] wrote: I had a similar problem, but plugging it into any Windows machine [I used my friends laptop] and setting it through there works lovely. No more fudding around for me! - Cory Christison Mathias Brodala wrote: Hello Benedikt. Benedikt Meurer, 16.01.2007 18:26: The volume.label is used if not-empty. Besides that there doesn't seem to be a lot of useful information available. Not even the info.vendor is set. We could use info.product, but that's not really useful either. OK, then I guess it’s my turn to find out how to set labels for fat32 devices. $ mkfs.vfat mkfs.vfat 2.11 (12 Mar 2005) No device specified! Usage: mkdosfs [-A] [-c] [-C] [-v] [-I] [-l bad-block-file] [-b backup-boot-sector] [-m boot-msg-file] [-n volume-name] [-i volume-id] [-s sectors-per-cluster] [-S logical-sector-size] [-f number-of-FATs] [-h hidden-sectors] [-F fat-size] [-r root-dir-entries] [-R reserved-sectors] /dev/name [blocks] hint... you want the volume-name ;) Thanks for your help once again. Oh, and thanks for thunar-volman too of course! Regards, Mathias ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Sorry, I wanted to send this to thunar-dev instead. Benedikt Meurer, 15.01.2007 22:22: I just released the first version of the Thunar Volume Manager. It adds automatic management of removable drives and media to Thunar, without adding another daemon to your desktop sessions. It requires Thunar 0.5.1svn or above, HAL 0.5.0 or above and D-BUS 0.32 or above. Just to make sure: Will thunar-volman know to mount, say, my digital camera based on its entry in /etc/fstab? I’ve created some udev rules and specific directories to dedicate each of my usb devices its own symlink under /dev and directory to mount. This way I don’t have to mess with /dev/sdXn devices, whereas X and n are almost always different, depend on the order I plug devices in. Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
2007/1/15, Benedikt Meurer [EMAIL PROTECTED]: Hello everybody, I just released the first version of the Thunar Volume Manager. It adds automatic management of removable drives and media to Thunar, without adding another daemon to your desktop sessions. It requires Thunar 0.5.1svn or above, HAL 0.5.0 or above and D-BUS 0.32 or above. Website: http://www.xfce.org/~benny/projects/thunar-volman/index.html Documentation: http://thunar.xfce.org/documentation/C/using-removable-media.html Release notes: http://developer.berlios.de/project/shownotes.php?release_id=12027 Download: http://developer.berlios.de/project/showfiles.php?group_id=910release_id=12027 Have fun, Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev Just a silly question but, how does it manage to get the events without being a daemon ? ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Alexandre Moreira wrote: I just released the first version of the Thunar Volume Manager. It adds automatic management of removable drives and media to Thunar, without adding another daemon to your desktop sessions. It requires Thunar 0.5.1svn or above, HAL 0.5.0 or above and D-BUS 0.32 or above. Just a silly question but, how does it manage to get the events without being a daemon ? Voodoo magic ;-) Ok, maybe not... Thunar acts as a proxy between hald and thunar-volman. Since Thunar is running and monitoring HAL events anyway, that's pretty easy. Whenever HAL reports a new device, Thunar runs thunar-volman to handle the new device (if Volume Management is enabled). Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Guess I have to CC thunar-dev now, but it’s my own fault. Benedikt Meurer, 15.01.2007 22:40: Mathias Brodala wrote: I just released the first version of the Thunar Volume Manager. It adds automatic management of removable drives and media to Thunar, without adding another daemon to your desktop sessions. It requires Thunar 0.5.1svn or above, HAL 0.5.0 or above and D-BUS 0.32 or above. Just to make sure: Will thunar-volman know to mount, say, my digital camera based on its entry in /etc/fstab? I’ve created some udev rules and specific directories to dedicate each of my usb devices its own symlink under /dev and directory to mount. This way I don’t have to mess with /dev/sdXn devices, whereas X and n are almost always different, depend on the order I plug devices in. thunar-volman uses exo-mount. Since HAL refuses to mount fstab entries, exo-mount will use plain old mount command to mount the device. So, yes, that should work. It's exactly the same as mounting devices from Thunar. And the latter does not work for me. *That* was the reason I asked. I was sure that I already described this, but anyway: I plug in my Hama flashdisk for example. Thanks to hal+udev I now have the following entries in /dev: lrwxrwxrwx 1 root root 3 2007-01-15 22:46 /dev/flashdisk - sda brw-rw 1 root floppy 8, 0 2007-01-15 22:46 sda But Thunar shows only „sda“ in its sidepanel instead of „flashdisk“. We already discussed this somewhere else and you (or maybe someone else, I’m not sure) told me that this was a hal problem. I remember sending a mail regarding this to the hal ML but never received an answer. So, what will thunar-volman do? Will it show/mount the device as sda or flashdisk? Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
2007/1/15, Benedikt Meurer [EMAIL PROTECTED]: Alexandre Moreira wrote: I just released the first version of the Thunar Volume Manager. It adds automatic management of removable drives and media to Thunar, without adding another daemon to your desktop sessions. It requires Thunar 0.5.1svn or above, HAL 0.5.0 or above and D-BUS 0.32 or above. Just a silly question but, how does it manage to get the events without being a daemon ? Voodoo magic ;-) Ok, maybe not... Thunar acts as a proxy between hald and thunar-volman. Since Thunar is running and monitoring HAL events anyway, that's pretty easy. Whenever HAL reports a new device, Thunar runs thunar-volman to handle the new device (if Volume Management is enabled). Thanks for the information. And thanks for the great piece of software too. I must say, I was never quite fond of file managers (theres some sort of magnetism that kicks me back to bash for file management every once in a while) but, since Thunar, I use bash only for programming-related file management, and I'm even considering start using Thunar for that too. :) Great work, and it keeps getting better everytime. Best regards, Alexandre Moreira. Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote: I just released the first version of the Thunar Volume Manager. It adds automatic management of removable drives and media to Thunar, without adding another daemon to your desktop sessions. It requires Thunar 0.5.1svn or above, HAL 0.5.0 or above and D-BUS 0.32 or above. Just to make sure: Will thunar-volman know to mount, say, my digital camera based on its entry in /etc/fstab? I’ve created some udev rules and specific directories to dedicate each of my usb devices its own symlink under /dev and directory to mount. This way I don’t have to mess with /dev/sdXn devices, whereas X and n are almost always different, depend on the order I plug devices in. thunar-volman uses exo-mount. Since HAL refuses to mount fstab entries, exo-mount will use plain old mount command to mount the device. So, yes, that should work. It's exactly the same as mounting devices from Thunar. And the latter does not work for me. *That* was the reason I asked. I was sure that I already described this, but anyway: I plug in my Hama flashdisk for example. Thanks to hal+udev I now have the following entries in /dev: lrwxrwxrwx 1 root root 3 2007-01-15 22:46 /dev/flashdisk - sda brw-rw 1 root floppy 8, 0 2007-01-15 22:46 sda But Thunar shows only „sda“ in its sidepanel instead of „flashdisk“. We already discussed this somewhere else and you (or maybe someone else, I’m not sure) told me that this was a hal problem. I remember sending a mail regarding this to the hal ML but never received an answer. So, what will thunar-volman do? Will it show/mount the device as sda or flashdisk? That seems to be a rather old version of Thunar. Update to the latest SVN version, that should fix the problem. Regards, Mathias Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Benedikt Meurer wrote: thunar-volman uses exo-mount. Since HAL refuses to mount fstab entries, exo-mount will use plain old mount command to mount the device. So, yes, that should work. It's exactly the same as mounting devices from Thunar. And the latter does not work for me. *That* was the reason I asked. I was sure that I already described this, but anyway: I plug in my Hama flashdisk for example. Thanks to hal+udev I now have the following entries in /dev: lrwxrwxrwx 1 root root 3 2007-01-15 22:46 /dev/flashdisk - sda brw-rw 1 root floppy 8, 0 2007-01-15 22:46 sda But Thunar shows only „sda“ in its sidepanel instead of „flashdisk“. We already discussed this somewhere else and you (or maybe someone else, I’m not sure) told me that this was a hal problem. I remember sending a mail regarding this to the hal ML but never received an answer. So, what will thunar-volman do? Will it show/mount the device as sda or flashdisk? That seems to be a rather old version of Thunar. Update to the latest SVN version, that should fix the problem. ...and here's why: ;-) Up to 0.5.0, Thunar used pmount, gnome-mount or halmount, whatever was available. However all these utilities behave differently, and of course, they behave differently on various platforms. Esp. pmount is tricky, since it doesn't use the HAL Mount method, which could confuse HAL (and software using HAL - Thunar, xfdesktop, ...). That's why I added exo-mount, which uses HAL if possible (as said, HAL cannot mount entries in fstab) and (hopefully) behaves the same on different platforms (some platforms require special care, and exo-mount takes care of that). Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Hello Benedikt. Benedikt Meurer, 15.01.2007 23:22: Mathias Brodala wrote: Thanks for the explanation, but there’s still one point unclear to me: when HAL doesn’t use /etc/fstab, how will exo-mount know that it should take flashdisk instead of sda? And how will it know where to mount it? Where will exo-mount retrieve its information from? It asks HAL for the device file path, then checks whether this device file is listed in /etc/fstab, comparing by device no rather than by path, and if so, uses plain old mount. Otherwise HAL's Mount method will be used. Since there'll be no more RCs, it'd be nice if you could test the SVN version so in case of a problem, we can fix that for the final release. OK, I’ll try tomorrow since I have to get up early tomorrow and don’t seem to get this done quickly: $ make /usr/bin/make all-recursive make[1]: Entering directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk' Making all in exo make[2]: Entering directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk/exo' /usr/bin/make all-am make[3]: Entering directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk/exo' make[3]: *** No rule to make target `exo-aliasdef.c', needed by `libexo_0_3_la-exo-aliasdef.lo'. Stop. make[3]: Leaving directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk/exo' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk/exo' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk' make: *** [all] Error 2 This appears when I try to compile libexo from SVN. Regards, Mathias -- debian/rules signature.asc Description: OpenPGP digital signature ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
Re: [Thunar-dev] thunar-volman 0.1.0
Mathias Brodala wrote: Hello Benedikt. $ make /usr/bin/make all-recursive make[1]: Entering directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk' Making all in exo make[2]: Entering directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk/exo' /usr/bin/make all-am make[3]: Entering directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk/exo' make[3]: *** No rule to make target `exo-aliasdef.c', needed by `libexo_0_3_la-exo-aliasdef.lo'. Stop. make[3]: Leaving directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk/exo' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk/exo' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/ashura/Archive/deb/xfce/exo/svn/trunk' make: *** [all] Error 2 This appears when I try to compile libexo from SVN. Pass --enable-maintainer-mode to autogen.sh. Regards, Mathias Benedikt ___ Thunar-dev mailing list Thunar-dev@xfce.org http://foo-projects.org/mailman/listinfo/thunar-dev
