I really need some help here udevhotplugusbusbmount etc etc. 2027

Bob Hauck

Actually what I have now does work, and yes, usbmount and hotplug are both now obsoleted by udev.

My udev handles all change of device events, and although it has stub calls to link to historical hotplug stuff, usbmount has been utterly ignored.

Once I had a working system with a udev that worked with the kernel, it was a trivial issue.

Create a new rule inetc-udev

This file is called 0.Nikon.rules

BUS=="scsi", SYSFS{model}=="NIKON DSC E775 ", SYMLINK+="Nikon" BUS=="scsi", SYSFS{model}=="NIKON DSC E775 ", ACTION=="add" RUN+="-bin-mountdev-Nikonmedia-camera"

and is symlinked toetc-udev-rules.d-0.Nikon.rules

Provided usb-storage is loaded (I think udev does this as part of its startup, which is why the broken udev-kernel relationship didn't load it) the plugging in of the camera will generate a udev event that has (amongst a lot of other stuff) a Scsi event involving the camera as uniquely ID'ed ..this rule is unique to that, and both sets up a symlink to a reliable device point for the formatted device..(I suspect it makes and breaks a link to the raw device as well actually..maybe NAME=="sd?1" would sort that?) and the second line (could that be concatenated with the first?) using RUN rather than PROGRAM (PROGRAM runs BEFORE the symlink. RUN commands are grouped and run AFTER the main work of udev) mounts the device just where I want it.

Investigation shows that all removable block devices are unmounted post removal by the HAL subsystem, (seeetc-hal-* andetc-udev-hal.rules) so I haven't bothered to explicitly dismount it. A quick test seems to show its unmounted after switching the camera off.

I probably have some perms to fix up to allow the pictures to be erased. and maybe some sync issues as well - USB flash doesn't like lots of writes...but the basic problem is resolved.

I can see the camera via a samba mount and my wife can see it via a appletalk mount.

Which is, after all, all I wanted..

It DID. I e-mail Marco, and he swore blind it wouldn't, but it did.

The startup file explicitly checks the kernel and aborts if its lower than that.

However the package install did not abort when I grabbed and installed it.

Search the net and you will find that this is not an isolated occurrence with this package...;-)

You have modified your apt setup in an unsupported way, or

No, I didn't. I did not know enough to do that, then. Until I explicitly downloaded an unstable kernel and used teh crude method to install it. Which FIXED the problem,

I did. There is, or *was* till I sent an email, a brorken dependency situation on the debian stable udev package.