havner napisał(a): > On Wed, Jan 04, 2006 at 12:43:33PM +0100, Fryderyk Dziarmagowski wrote: >> On Wed, 4 Jan 2006 11:52:15 +0100 >> havner <[EMAIL PROTECTED]> wrote: >> >>> Revision 1.137 2005/11/16 15:35:22 freetz >>> - removed hotplug symlink (it can't be done this way until /sbin/hotplug >>> is >>> a default kernel hotplug handler), added cleaned up hotplug_map.rules >>> (instead of creating it with script at build time), rel.1 >>> >>> So how should it be done? Cause now we end up with a booted system: >>> >>> $ sudo sysctl kernel.hotplug >>> kernel.hotplug = /sbin/hotplug >>> $ ls -l /sbin/hotplug >>> ls: /sbin/hotplug: No such file or directory >>> >>> /sbin/udev_start sets this to /sbin/udevsend but rc-scripts set it back >>> to hotplug. I dont care how it will be done (maybe remove it from >>> rc-scripts) but for now it cant stay this way. What was wrong in this >>> symlink? Cause i dont really get the "it can't be done this way until >>> /sbin/hotplug is a default kernel hotplug handler". Why? This package is >>> PLD specific and our rc-scripts set this to /sbin/hotplug so for us its >>> default. >> Symlink was wrong because was called after / is mounted and before udev >> was ready to start. That was leading to propagating device nodes on >> readonly filesystem. > > Was called by what? Existance of a file means its executed? I dont get > something here. And why this does not affect hotplug package itself > where /sbin/hotplug exists and /dev/ is on ro filesystem for whole > sysinit phase (no tmpfs)
Because hotplug wasn't creating any device nodes? _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
