Re: maybe race condition & alsa

[Francisco Lobo <lobo.f@blueyonder.co.uk>]

Marco d'Itri wrote:
 >
 > I'm using this:
 >
 > /etc/dev.d/snd/controlC0/alsa.dev:
 >
 > #!/bin/sh -e
 > exec /usr/sbin/alsactl restore 0
 >

Brilliant !!!
I must start thinking in udev ways from now on...

Greg KH wrote: (about /dev/console)
 >
 > It's not needed for me. It all depends on your distro's needs.
 >

I don't really understand: at present I am running Arch Linux, but I 
can't see anything special with their boot setup, it's a plain BSD style 
init; and their init compilation is very much LFS style, no special hacks.

Do you mean using a /linuxrc to start udev, before init? (Maybe I should 
try that someday...) The init manpage says it defaults the system 
console to /dev/console or inherits the CONSOLE var from the kernel 
command-line; it needs it to report its messages I guess.

Well... I would really like to know how you did it.

Greg KH wrote: (about hotplug)
 >
 > Ick, ick, ick.  NO.  do not do this.  Lots of other stuff will not work
 > properly in your system if you do this.
 >

Hum... I see everything (I use) working... Although I have to confess 
that I don't use usb devices, or plug and unplug any hardware regularly.

What will not work?
Is there any specific problem with using /sbin/udev as the hotplug program?

As far as I understand (and for my simple needs), I only require the 
correct device nodes to be created after I insert a kernel module. I 
shouldn't need a script that calls a script that calls a script..., 
every time I load a module. But this is my personal point of view, and I 
understand that a general all-scenarios solution cannot be done in 
another way.

Thank you both!
Francisco.


PS:
I did try the latest hotplug in the meantime, which now does a good job 
of discovering hardware via sysfs!

Yet I have some reservations with respect to its init script. I don't 
want to configure all my hardware at boot but only as I need it, so I am 
force to blacklist a lot of modules. Also, it is curious that my alsa 
sound card module does not get loaded, because the oss one comes first 
in modules.pcimap and I put it on the blacklist (from what I could 
understand from the scripts), so I cannot have several modules for the 
same device(?).

Of course, this is not related to using hotplug as the "hotplug 
program"; these are simply examples, which I think begin to support my 
notion that what the hotplug scripts try to automate is in fact 
something that is very specific to system/user preference (i.e. like 
init scripts). Without having the time to get familiar with all the 
scripts at the moment, I would rather do without it.


-------------------------------------------------------
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=click
_______________________________________________
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