> After applying the patch to the kernel, compiling and installing
> modutils-970317m, killing kerneld (which is started by my init scripts),
> doing "depmod -a" and running modald as root, I observed the following:
>
> * mount /dev/fd0 /fd0 outputs "Continued" (I'm using mount 2.6b) and the
> floppy module is not loaded
The Continued message is OK. I'm putting the process waiting for the
loading request into the terminated state and waiting it up by sending the
corresponding signal (SIGCONT) to it. Some programms catch this and even
some reply by this peculiar message. But it shouldn't hurt...
> * an strace of modald's process while doing this shows:
>
> SYS_167(0, 0x9, 0xbffff940, 0x100, 0xbffff93c) = 0
> fork() = 18834
> wait4(-1, NULL, 0, NULL) = 18834
> --- SIGCHLD (Child exited) ---
> kill(18833, SIGCONT) = 0
> SYS_167(0, 0x9, 0xbffff940, 0x100, 0xbffff93c) = 0
> fork() = 18835
> wait4(-1, NULL, 0, NULL) = 18835
> --- SIGCHLD (Child exited) ---
> kill(18833, SIGCONT) = 0
> SYS_167(0, 0x9, 0xbffff940, 0x100, 0xbffff93c
That's what I actually intended.
>
> * when I run an audio program, the sound module is not loaded--in fact, no
> modules seem to be loaded at all
Interresting..
>
> * syslogd records these new errors:
>
> Mar 26 13:25:28 topside modprobe: can't locate module block-major-2
> Mar 26 13:25:44 topside last message repeated 3 times
> Mar 26 13:27:10 topside modprobe: can't locate module char-major-14
> Mar 26 13:34:23 topside modprobe: can't locate module block-major-2
> Mar 26 13:34:23 topside modprobe: can't locate module block-major-2
> Mar 26 13:39:32 topside modprobe: can't locate module char-major-14
> Mar 26 13:39:36 topside modprobe: can't locate module char-major-14
Op's that there again the incompatiblity between some module
configurations. Did You store the modules in
/lib/modules/kernel_version/... ??? I will fix it anyway by trying to
ensure the old behaviour...
>
> * if I start modald more than once, the later invocations start heating up
> the CPU with:
>
> SYS_167(0, 0x9, 0xbffff940, 0x100, 0xbffff93c) = -1 EBUSY (Device or
> resource busy)
>
Ops It should return nicely... I don't intend to allow more then one of
them beeing run at one time. (For obvious reasons=
> * the man page included is for bdflush.
Oh Yes.......... ;-)
Thank's for bothering yourself with it! I will try to make some
corrections next time. Esp. there seem to still be some problems with the
location of modules by the new modprobe and depmod utils....
The rest of the stuff found there was highly experimental. (Tough it still
works fine for me.) And mainly intended for discussions about the
technical concept shouwed therein. As it seems it got quite acceptance.
Esp. Volker Lendecke seems to give me positive feedback :-).
I will therefore try to make it more usable next time.
Bye
Marcin