[arch-general] Fwd: udev events and /usr not mounted

Tom Gundersen teg at jklm.no
Fri Nov 25 18:21:14 EST 2011

On Fri, Nov 25, 2011 at 11:44 PM, Myra Nelson <myra.nelson at hughes.net> wrote:
> ---------- Forwarded message ----------
> From: Myra Nelson <outerrimlogging at gmail.com>
> Date: Fri, Nov 25, 2011 at 15:45
> Subject: udev events and /usr not mounted
> To: General Discussion about Arch Linux <arch-general at archlinux.org>
> No gripes, complaints, or rants, just a question about udev rules. This is
> one of those /usr not mounted things that's broken.
> Fri Nov 25 12:06:54 2011: :: Loading User-specified Modules    [BUSY]
> udevd[398]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl
> restore 0': No such file or directory
> It's easy to work around but I was wondering, is it possible to move
> 78-sound-card.rules and/or 90-alsa-restore.rules to say /etc/udev/rules.d
> then source them, myself, after /usr is mounted? Or would that cause other
> unwanted and unnecessay problems, security issues, or just plain not work?

You can't really "source" udev rules, so I don't think this would work
(you'd have to somehow replay the relevant events, but I don't know
how you'd manage to only trigger some specific rule files, so I don't
think it is a good idea).

You could just wait for the /usr support to land in initramfs (should
be "any day now"), which would solve this and similar problems.

However, I think in the case of alsa, this is not a real problem.
Provided you also enable the alsa rc script. If I understand correctly
it is ok for the alsa udev rules to fail on boot, because the rc
script would anyway do the same job (restore mixer levels). The point
of the udev rules is to deal with hotplugged sound devices that are
added after boot (and hence would not be dealt with by the rc script).
I have not looked at the rules/scripts in any detail so please take
this with a grain of salt :-)



More information about the arch-general mailing list