[lkml]   [1999]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: A module bug in 2.2.1?
>I made unix domain socket as a module in 2.2.1. When I booted up, I
>got so many
>insmod: a module named /lib/modules/2.2.1/misc/unix already exists
>Any ideas?

kmod in the kernel is trying to demand load unix domain sockets with
'modprobe -s -k unix'. modprobe gets some error. Because modprobe
was given "-s", it calls syslog to record the error. syslog tries to
use a unix domain socket, causing the kernel to again 'modprobe -s -k unix'
again, continuing the recursive cycle.

I am not sure why you are getting an error in the first place though,
especially that error. Do you perhaps have a custom module of your own
named "unix"?

By the way, a bunch of x86 machines at Yggdrasil at this moment are running
the same 2.2.1 kernel binary that is built with unix domain sockets
as a loadable module, so rest assured that it can be done. On the
other hand, there is a kludge in each of the different initial ramdisks
that these identical fully modularized kernels boot that disables loading
of the unix domain sockets module until the hard disk is mounted
and a new conf.modules has been automatically generated from the
machine's detected hardware configurations This is to prevent just
the scenario you are describing if there is a problem with the initial
modprobe configuration.

Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104 \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:50    [W:0.101 / U:0.588 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site