Hi Pat, I was playing with udev-0.97 from current, with kernel-2.6.18 from testing, trying some custom udev rules. I noticed that using "udevcontrol reload_rules" would not apply my new custom rules, so I tried other methods. I tried your rc.udev script like this: /etc/rc.d/rc.udev restart ( would not work ), /etc/rc.d/rc.udev reload ( would not work ), /etc/rc.d/rc.udev force-reload ( would not work ).
The only thing which would reload my rules was /etc/rc.d/rc.udev stop && /etc/rc.d/rc.udev start ( or /etc/rc.d/rc.udev start ). So back to my question, is that a bug in udev-0.97's implementation of "udevcontrol reload_rules" command ? I think so.
Maybe you could modify your /etc/rc.d/rc.udev script to fix the "restart / reload / force-reload" before the release of Slackware-11.0.0 ? I've talked with one of my friends who is running -current and kernel-2.6.18, and he has the same problem as me.