Yes I use mdadm.
Michael Biebl wrote:
François LEIBER schrieb:
I confirm that this bug is annoying: not only does it prevent hal to
work (I confirm the processes left running), but it also messes up all
packages updates which depend on hal.
Example at every update since more than a week:
Setti
I've also experienced this bug. I'm using software RAID (madm).
My distribution is amd64 / unstable.
Blaz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
François LEIBER schrieb:
> I confirm that this bug is annoying: not only does it prevent hal to
> work (I confirm the processes left running), but it also messes up all
> packages updates which depend on hal.
> Example at every update since more than a week:
>
> Setting up hal (0.5.10-2) ...
> Rel
I confirm that this bug is annoying: not only does it prevent hal to
work (I confirm the processes left running), but it also messes up all
packages updates which depend on hal.
Example at every update since more than a week:
Setting up hal (0.5.10-2) ...
Reloading system message bus config...d
Package: hal
Version: 0.5.10-1
Severity: serious
This is serious because dpkg fails to upgrade hal, since the init.d
script exits with code 1. Here is what's going on:
piper$ sudo /etc/init.d/hal stop
Stopping Hardware abstraction layer: hald.
piper$ ps aux | grep hal
piper$ sudo hald --daemon=
5 matches
Mail list logo