On Wed, Feb 01, 2006 at 12:00:26AM +0100, Sjoerd Simons wrote:
> On Tue, Jan 31, 2006 at 10:54:08PM +0100, Marco d'Itri wrote:
> > On Jan 30, Michael Ott <[EMAIL PROTECTED]> wrote:
> >
> > > I believe that dbus or fam will mount my disk. But my mobile memory will
> > > mount with udev 0.082 and not with 0.083. I remember that it works
> > > yesterday and after update it did not work.
> > I see that #350762 has been opened too against HAL, but I still do not
> > know what's wrong. Sjoerd, do you have any ideas about this? Kay?
> >
> > The relevant rules are:
> >
> > ENV{SEQNUM}=="[0-9]*", ENV{UDEVD_EVENT}=="1",
> > RUN+="/usr/lib/hal/hal.hotplug"
> >
> > BUS="scsi",KERNEL="sd[a-z]*",
> > PROGRAM="/etc/udev/scripts/device-removable.sh %k 'usb ieee1394'",
> > RESULT="1", MODE="0640", GROUP="hal"
> >
> > BUS="usb", KERNEL="ub[a-z]*", MODE="0640", GROUP="hal"
>
> As you guessed correctly in an earlier mail. Not adding $SUBSYSTEM as $1 to
> programs anymore breaks the hal hotplug helper.
>
> The hal currently in experimental has udev passing events over a socket
> instead
> of using the helper, so it works fine. Didn't upload it to unstable directly
> because it had the first version of my priv. patch applied to it.
>
> Luckily the priv. sep. patch seems to work fine. So i'm planning to upload
> hal
> 0.5.6 with the current priv. sep. patch and some other patches from HAL CVS
> to
> unstable which should fix this issue :)
Oh, yeah, sorry forgot the old hal helper cause we don't use it anymore for a
long time. Adding $env{SUBSYSTEM} to the rule should fix it. The current HAL
will
install its own rule in the udev directory by default.
Kay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
