FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux General Discussion

 
 
LinkBack Thread Tools
 
Old 11-25-2011, 09:44 PM
Myra Nelson
 
Default Fwd: udev events and /usr not mounted

---------- Forwarded message ----------
From: Myra Nelson <outerrimlogging@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@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?

Currently I don't want to try to migrate /usr to /. / is only 4 GB and /usr
is 8+ GB and everything works to well so I'll just do a fresh install
later. Otherwise sudo /usr/bin/alsactl start works well.

Myra

Brain Dead
--
Chaos! Panic! Disaster! (My work here is done)



--
Life's fun when your sick and psychotic!
 
Old 11-25-2011, 10:00 PM
Thomas Bächler
 
Default Fwd: udev events and /usr not mounted

Am 25.11.2011 23:44, schrieb Myra Nelson:
> ---------- Forwarded message ----------
> From: Myra Nelson <outerrimlogging@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@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?
>
> Currently I don't want to try to migrate /usr to /. / is only 4 GB and /usr
> is 8+ GB and everything works to well so I'll just do a fresh install
> later. Otherwise sudo /usr/bin/alsactl start works well.
>
> Myra
>
> Brain Dead

You can work around this by mounting /usr from initramfs. There are RFC
patches around for doing this, I don't know where right now (search this
mailing list, this topic has come up).

It is known that having /usr separate causes problems like the ones you
describe, see [1].

[1] http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
 
Old 11-25-2011, 10:21 PM
Tom Gundersen
 
Default Fwd: udev events and /usr not mounted

On Fri, Nov 25, 2011 at 11:44 PM, Myra Nelson <myra.nelson@hughes.net> wrote:
> ---------- Forwarded message ----------
> From: Myra Nelson <outerrimlogging@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@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 :-)

Cheers,

Tom
 
Old 11-26-2011, 03:26 AM
Myra Nelson
 
Default Fwd: udev events and /usr not mounted

On Fri, Nov 25, 2011 at 17:21, Tom Gundersen <teg@jklm.no> wrote:

> On Fri, Nov 25, 2011 at 11:44 PM, Myra Nelson <myra.nelson@hughes.net>
> wrote:
> > ---------- Forwarded message ----------
> > From: Myra Nelson <outerrimlogging@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@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 :-)
>
> Cheers,
>
> Tom
>

Tom:

Thanks for the reply. As I said it's not a problem, I was just trying to
determine how or if I needed to correct the problem. It doesn't seem to
cause any problems and as I said, sudo /usr/bin/alsactl restore works from
a terminal after the machine boots.

Myra


--
Life's fun when your sick and psychotic!
 

Thread Tools




All times are GMT. The time now is 12:43 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org