Sorry to reply to myself here, but it seem that the unix domain sockets are loaded twice. Much earlier in the log, I see this:
PCI: Probing PCI hardware Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 ...and later this: INIT: version 2.85 booting NET4: Unix domain sockets 1.0/SMP for Linux NET4.0 insmod: /lib/modules/2.4.20-powerpc/kernel/net/unix/unix.o Cannot open /proc/ksyms No such file or directory insmod: insmod: a module named unix already exists insmod: insmod: Cannot open /proc/ksyms No such file or directory insmod: insmod: insmod net-pf-1 failed It seems that the unix sockets are loaded before init starts. But if that's true, the /proc/ksyms warning is confusing. Or are there multiple things going wrong here? It's also strange that the 'insmod:' gets repeated. Frank On Thursday 03 July 2003 1:54, Frank Murphy wrote: > I've been getting these warning messages on boot for a while. I get them > with stock kernel-images 2.4.19-2 and 2.4.20-4. The system boots fine, so > the warnings seem harmless, but I'd prefer they weren't there. > > insmod: /lib/modules/2.4.20-powerpc/kernel/net/unix/unix.o Cannot open > /proc/ksyms No such file or directory > insmod:insmod:a module named unix already exists > insmod:insmod:Cannot open /proc/ksyms No such file or directory > insmod:insmod:insmod net-pf-1 failed > > After boot, lsmod shows 'unix' is loaded. Perhaps two different scripts are > trying to load the same module? > > Any ideas are appriciated. > > Frank
