>
> My devfsd.conf includes the following :
>
> # Enable module autoloading. You may comment this out if you don't use
> # autoloading
> LOOKUP .* MODLOAD
>
> # Extra lookups and registers for sound, modem, printer etc.
> LOOKUP dsp MODLOAD
redundant
> REGISTER sound/dsp PERMISSIONS root.audio 660
>
> LOOKUP mixer MODLOAD
ditto
> REGISTER sound/mixer PERMISSIONS root.audio 660
>
> LOOKUP tts/0 MODLOAD
ditto
> REGISTER tts/0 PERMISSIONS root.dialout 660
>
> LOOKUP printers/0 MODLOAD
ditto
> REGISTER printers/0 PERMISSIONS root.lp 660
>
> And my /etc/modules.conf contains:
> alias /dev/tts* serial
> alias /dev/printers* lp
>
> Here's the problem(s):
> My ppp dialup script specifies /dev/tts/0 as the location of my modem so
> when I run "ppp-go" to dialup I expect it to call for /dev/tts/0 and then
> devfs to handle the MODLOAD, passing it over to modules.conf which then
> sends back to devfs to load the serial module, and hey presto we have
> tts/0!
>
> But this is not happening. When I manually "modprobe serial" I get my
> device node and all is well. But the autoload is not working correctly.
>
what is in your /etc/modules.devfs? What is modutils version (anyone knows
if there was a version that could not handle wildcards in aliases?) What
devfsd version?
what happens if you just do
ls /dev/tts/0
finally, strace devfsd when doing ls /dev/tts/0:
strace -f -o /tmp/out -p PID-of-devfsd
it will show you how modprobe is really called.
-andrey
> I get the same problem when I try to send to my printer on /dev/printers/0
> which I have specified in /etc/printcap. lp is not being autoloaded and so
> /dev/printers/0 is not being created.
>
> Please can someone point out what I have done wrong with my configuration.
> For comparison, XMMS calls to /dev/dsp work just fine, autoloading my
> sound
> modules no problemo.
>
> Many thanks,
> Francis Barton.
|