Sjoerd Simons wrote:
>> Please wait. I tried to restart udev and tried to restart hal in all
>> ways,
>>
>>tried to restart whole system with no success: lshal always reports the same
>>errors and hald dies after a few minutes.
>>
>>
>
>This bug is another issue than the one you reported, plea
On Tue, Feb 07, 2006 at 07:43:09PM +0100, Mau wrote:
> > > Could you try to restart the udev daemon (/etc/init.d/udev restart)?
>
> > It worked. My bad I suppose: i really didn't think about restarting udev
> > after HAL upgrade.
>
> > Thanks for your help, I suppose the bug can be really closed
> > Could you try to restart the udev daemon (/etc/init.d/udev restart)?
> It worked. My bad I suppose: i really didn't think about restarting udev
> after HAL upgrade.
> Thanks for your help, I suppose the bug can be really closed now.
Please wait. I tried to restart udev and tried to restart
Sjoerd Simons wrote:
Which hack ?
This one:
In file /etc/udev/hal.rules change
ENV{SEQNUM}=="[0-9]*", ENV{UDEVD_EVENT}=="1",
RUN+="/usr/lib/hal/hal.hotplug"
with
ENV{SEQNUM}=="[0-9]*", ENV{UDEVD_EVENT}=="1",
RUN+="/usr/lib/hal/hal.hotplug $env{SUBSYSTEM}"
Debian Sid on AMD64, hal 0.5.6
On Mon, Feb 06, 2006 at 12:05:37AM +0100, Mau wrote:
> > Does /etc/udev/hal.rules contain
> >``RUN+="socket:/org/freedesktop/hal/udev_event"'' ?
>
> My /etc/udev/hal.rules:
>
> # Have udev pass data over a socket to hal
> RUN+="socket:/org/freedesktop/hal/udev_event"
>
> # unmount block devices
> Does /etc/udev/hal.rules contain
>``RUN+="socket:/org/freedesktop/hal/udev_event"'' ?
My /etc/udev/hal.rules:
# Have udev pass data over a socket to hal
RUN+="socket:/org/freedesktop/hal/udev_event"
# unmount block devices when they are removed
SUBSYSTEM=="block",ACTION="remove", RUN+="/usr/li
On Sat, Feb 04, 2006 at 10:15:14AM +0100, Fabio Rosciano wrote:
> I'd like to confirm that hal 0.5.6-2 doesn't handle mounting properly.
>
> I started hald like this:
>
> # hald --daemon=no --verbose=yes
>
> and plugging in a USB thumbdrive (/dev/sdc as I have two SATA drives)
> does not trigge
I'd like to confirm that hal 0.5.6-2 doesn't handle mounting properly.
I started hald like this:
# hald --daemon=no --verbose=yes
and plugging in a USB thumbdrive (/dev/sdc as I have two SATA drives)
does not trigger *any* events.
The device is correctly created by udev:
nostromo:~# ls -l /
8 matches
Mail list logo