This only works with usb-storage? it seems that it doesn't work with Low Performance USB Driver, you could make it work ti it, it doesn't seem to e difficult, thanks anyway :)

Why not use HAL, sysfs and IVMAN.

It's still a little buggy but is maturing quite quickly.

I think using 3 daemons for a unice task (automount) should never be fresh thing. I think it started in the wrong way,i still can use supermount for it. Althought i'm still waiting for a decent way of automounting :)

There is also kvm (kde volume manager).
Does someone know, which way to go, ivman or kvm?

Thanks

For example because I've never managed to compile hal. It halts on ./configure!!! With gcc-3.4.3, glibc-2.3.4, linux-2.6.10-cko3+ck5.
It makes me crazy with:
checking for BLKGETSIZE64... no
configure: error: BLKGETSIZE64 is not defined
It seems I am the only person who is suffering this trouble on the Net! :'-(

Hi, I understand your frustration, I had many problems configuring, many problems compiling, many problems running HAL. As it is now, I tend to think this software is a piece of crap. When I finally got it to run though, it was quite nice. Unfortunately, it is not stable enough for me to use it permanently.

Well, maybe this will help you build it (HAL 0.4.7):

Remember, im using Slackware, maybe this wont apply to your distro...

I use the kernel headers version 2.4.29, but it seems the fix also work with 2.4.27. I dont know about headers version 2.6.x.

In /usr/include/linux
find the file called fs.h,
then find the line beginning with:

#define BLKGETSIZE64 _IOR(0x12,114,sizeof(u64))

and change it to:

#define BLKGETSIZE64 _IOR(0x12,114,size_t)

I know, i know, changing kernel headers is not a "nice thing to do" TM, but as I saw many times in many forums, it seems to be a bug in the kernel headers, so... Well, maybe its not a bug there, but in HAL (more likely), but anyway, it makes it compile dammit!

Note: it also helps if you disable doc building... check configure --help.

My distro is a Slackware, too, but a little bit recompiled :-)
Searching through headers of 2.6.10 vanilla, I found that BLKGETSIZE64 was already defined as you told me. Looking through config.log I found other problems concerning this request:
In file included from /usr/include/linux/fs.h:19,
from conftest.c:35:
/usr/include/linux/prio_tree.h:22: error: parse error before "pgoff_t"
/usr/include/linux/prio_tree.h:27: error: parse error before "pgoff_t"
/usr/include/linux/prio_tree.h: In function `prio_tree_iter_init':
/usr/include/linux/prio_tree.h:29: error: `iter' undeclared (first use in this f
unction)
/usr/include/linux/prio_tree.h:29: error: (Each undeclared identifier is reporte
d only once
/usr/include/linux/prio_tree.h:29: error: for each function it appears in.)
/usr/include/linux/prio_tree.h:29: error: `root' undeclared (first use in this f
unction)
/usr/include/linux/prio_tree.h:30: error: `r_index' undeclared (first use in thi
s function)
conftest.c: In function `main':
conftest.c:40: warning: 'main' is normally a non-static function
conftest.c: In function `main':
conftest.c:43: warning: implicit declaration of function `ioctl'
conftest.c:43: warning: nested extern declaration of `ioctl'
It seems great problems are there in the linux headers.
My question is, if I compile hal with kernel 2.4.xx (so without sysfs) will it run with 2.6.xx?
Thanks a lot for your advice and knowledge!