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
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.)
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
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
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
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
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
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
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
___
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
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
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,
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
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
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
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
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
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
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
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
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
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
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
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
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 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.
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.
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,
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
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
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
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.
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
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?
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
35 matches
Mail list logo
