> i've uploaded your work. hotplug is maintained by fredl. good he has been silent wrt initscirpts as well. I hope he's not following fpons ...
> btw your changes result in quite some changes (are you sure we haven't > lost any features ?) : you never know till you test it. > --- hotplug--files.old 2003-11-17 12:06:28.000000000 +0100 > +++ hotplug--files.new 2003-11-17 12:06:28.000000000 +0100 > @@ -1,37 +1,27 @@ > /etc/hotplug > -/etc/hotplug.d > -/etc/hotplug.d/default > -/etc/hotplug.d/default/default.hotplug /etc/hotplug/blacklist > -/etc/hotplug/dasd.agent > -/etc/hotplug/firmware.agent looks like reverse diff to me. [...] > -/usr/share/doc/hotplug-2003_08_05 > -/usr/share/doc/hotplug-2003_08_05/ChangeLog > -/usr/share/doc/hotplug-2003_08_05/README > +/usr/share/doc/hotplug-2002_04_01 > +/usr/share/doc/hotplug-2002_04_01/ChangeLog > +/usr/share/doc/hotplug-2002_04_01/README mine is based on post-2003_08_05 CVS :) > ********************************************************* > --- hotplug--requires.old 2003-11-17 12:06:28.000000000 +0100 > +++ hotplug--requires.new 2003-11-17 12:06:28.000000000 +0100 > @@ -1,5 +1,4 @@ > /bin/sh > -bash > chkconfig > ifplugd > libc.so.6 I do not know actually; is it direct or reverse diff? >> > Should I make it an option in mkinitrd ? >> > >> >> I guess yes. But this is compatibility problem. It is not supported >> on vanilla kernel so you have to detect patched kernel somehow. And >> how are you going to do it? You will get a flood of "bug reports" >> from users who compiled their own kernels (vanilla ones or whatever) >> and cannot load initrd. > > just check for /mdk/ and ! /custom/ in uname -r output that is still just wild guess :(