From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#236343: udev breaks alsamixer settings
Date: Sun, 07 Mar 2004 10:37:59 +0000 [thread overview]
Message-ID: <20040307103759.GA24956@suse.de> (raw)
In-Reply-To: <4049FA7E.3030200@reactivated.net>
On Sun, Mar 07, Marco d'Itri wrote:
> On Mar 06, Olaf Hering <olh@suse.de> wrote:
>
> > On Sat, Mar 06, Marco d'Itri wrote:
> >
> >> Can this be fixed in udev or do I need to teach all users and
> >> maintainers to put call sleep in the install statements of
> >> modprobe.conf?
> >
> >do that stuff in the sound.agent, where it belongs.
>
> I can't see how this will eliminate the race.
> It even looks like that this will guarantee that sound.agent (called by
> default.hotplug) will be run before udev.hotplug by the hotplug
> multiplexer.
no, sound.agent runs when the driver is ready and triggers the event.
you will only need the rcalsafoo script if the driver is compiled into
th kernel. and you dont need a udev.hotplug either.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&opÃk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-03-07 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-06 16:21 Bug#236343: udev breaks alsamixer settings Daniel Drake
2004-03-06 16:27 ` Marco d'Itri
2004-03-06 16:32 ` Olaf Hering
2004-03-07 9:01 ` Alexander E. Patrakov
2004-03-07 10:04 ` Marco d'Itri
2004-03-07 10:37 ` Olaf Hering [this message]
2004-03-07 10:43 ` Marco d'Itri
2004-03-07 10:46 ` Olaf Hering
2004-03-07 12:37 ` Marco d'Itri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040307103759.GA24956@suse.de \
--to=olh@suse.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).