On Jul 18, Marco d'Itri wrote: > Sorry, you are very confused. Coldplugging has nothing to do with > kerneld, and hotplug just uses modprobe.
I know hotplug uses modprobe. And, sorry, it's not kerneld anymore, it's the kernel module loader now, which also uses modprobe to load modules. Both mechanismen are fighting each other, as the kernel loader only loads modules which are needed by a process (accessing a device) and hotplug (with it's coldplug mechanism) tries to load all modules which it means to recognize hardware for it at startup. The kernel loader is configured which module it has to load for which device (with aliases). Hotplug has no configuration which devices are needed, it simply tries to load ALL modules e.g. for any PCI id it founds at startup. > If you do not like automatic > hardware detection then disable it as explained in README.Debian. I do like automatic hardware detection if I (hot)plug a new device to my system, otherwise I would not have installed hotplug ;-). But I have disabled coldplugging now (HOTPLUG_RC_* set to no), because it was the only way to get my system back usable. Either this mechanism did not exist on woody or it did work different. > This is not a bug. If a system which was running without problems with woody and kernel 2.2 gets unusable after upgrading to sarge and kernel 2.4 this is a bug for me. To make it more clear: One of the systems did not have a login screen after upgrade and reboot, because hotplug has loaded a module which prevented the graphics driver from work, the other system needed nearly half an hour to boot after the upgrade because hotplug probably did not respect the configured aliases for my network interfaces and changed the numbering of the network devices, so that nameservice and network mounts were not available after reboot. These are things which should not happen on a debian upgrade (and such drastical things never happend before on a debian upgrade for me). All these effects were fixed after disabling coldplugging (HOTPLUG_RC_* set to no). > > As a simple example: I never use a joystick on my system. So why > > should hotplug load a module for the joystick at startup? Only because > > my soundcard has a joystick port? This wastes my memory and by the way > Yes. If one or two pages are a big issue for you then you should > obviously build your own kernels and probably not even use modules. These are not only one or two pages, as hotplugs coldplugging mechanism loads a couple of modules which i do not need. I have my own kernel build. And why not using modules? They are made for using memory only if the module is really needed. Not like a monolythic kernel which occupies all the time the space for all device drivers which potentially will be used. Same does hotplug now with a modular kernel by loading all (needed or not needed) modules at startup. But that's not the problem, I can disable this. The problem is the upgrade, which may make the whole system unusable for somebody who does not know this mechanisms. > > module to a joystick device (if not already an assignment exist) and > > let kerneld load the module if a process accesses the device. > Except that this is not possible if the devices does not exist yet, as > it happens when udev is installed. That may be a problem, never have used that ... cu, Uwe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
