Coldplug should contain "before net" line, so it starts before network initialisation. It is required to have network modules properly loaded.
No it isn't. It can start the network modules for you, and people use it for that. What in the script requires network initialized?
I am afraid you didn't understand. It needs to be started BEFORE network initialisation, so it can load modules, which are then used for setting up network!
Ah, I see your point. But the old hotplug.rc file never had that dependancy, so why should the coldplug.rc file have it?
It had, because previously everything was working fine. And even if it wasn't there (but it was!) you need to start coldplug before network to have your network card modules in place.
Again, that dependancy was not present in the hotplug.rc file. So, how did that work for you then? Why not just put the modules that you need to have loaded for your hardware in the modules.autoload directory? That's the recommend place for them, and then you don't have to use the coldplug stuff at all.
In that case you don't need hotplug/coldplug at all. I really can't understand what are cons of doing that (I can't think any of them). Typical situation: you have a PC with network card; card gets broken; you replace it with model of your choice, and it works. But currently you need to add it do autoload.d (which is bad place by the way, because proper way of doing things is aliasing - e.g. alias eth0 ne2k-pci).
Exactly, coldplug is not needed at all in that case. That's the point. And if you want to use module aliases, fine, that works too. But if you _do_ want to use coldplug, and it works for you, great, that's even better. That's why the package is there, for users that want it, and for those few that it will work for.
OK. As you wish. One of ppl on forum recommended "rc-update add coldplug boot", which could resolve that. Anyway I give up with that bug :D.
