Hello Benedikt.
Benedikt Meurer, 29.01.2007 11:14:
> 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}.
OK, here it is:
> $ ls -ld /dev/{sda,flashdisk}
> lrwxrwxrwx 1 root root 3 2007-01-29 11:17 /dev/flashdisk -> sda
> brw-rw---- 1 root floppy 8, 0 2007-01-29 11:17 /dev/sda
Nothing extraordinary from my point of view.
Regards, Mathias
--
debian/rules
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Thunar-dev mailing list [email protected] http://foo-projects.org/mailman/listinfo/thunar-dev
