dbus + hal + ivman doesnt need any kernel patches. GNOME and KDE have
their own ivman equivalents built in that also use hal + dbus.

They seem the way the way it's going.

I personally, as of 6 hours ago am using a udev rule like phrakture suggested, 

BUS="usb", KERNEL="sd*", NAME="%k", RUN="/usr/bin/automount"

and /usr/bin/automount contains:
#! /bin/bash
if [ $ACTION == "remove" ]; then
    umount $DEVNAME
else
    pmount $DEVNAME
fi

pmount will, if the device doesnt have a fstab entry to mount it with,
it will create the mountpoint and fstab entry and then mount it.
pmount is available in the repos, as it is also what ivman uses. this
rule only covers devices with udev entries, /dev/sdXX, whereas ivman
does cds and everything.

When I began with linux, I used mandrake, and back in those days,
kernel based automounters, or at least, supermount, in particular
caused countless crazy problems that you would never even consider
tracing back to it.

James

On 9/17/05, Andrew Conkling <[EMAIL PROTECTED]> wrote:
> On 9/17/05, James Rayner <[EMAIL PROTECTED]> wrote:
> > as a kernel person, dont use any kernel based ones :)
> 
> I'm with you, but are there any to rule out because they don't work
> with a stock kernel?  ATM, I'm using your archck (cheers) but I want a
> solution that would work even if I switched back to the standard
> kernel.
> 
> IIRC one of the mounters I listed said something about needing to
> patch the kernel, even recent versions of 2.6!  (At this point, that
> just seems silly.)
> 
> --
> http://aconkling.blogspot.com
> 


-- 
iphitus - www.iphitus.tk

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to