Hi, On Saturday 24 February 2007 04:00:33 Blacky Gray wrote:
> Just for completeness: > modprobe from module-init-tools does support blacklisting. I used this feature > as long as hotplug++ did not support blacklisting. Oh, intereseting - I did not notice, thanks for pointing this out. > modprobe from the old modutils package does not support blacklisting, and i > believe that some other modpobe implementations from busybox and similiar > packages also don't support blacklisting. > > regards, > Gerhard > > Am Saturday, 24. February 2007 schrieb Rene Rebe: > > Hi all, > > > > despite beeing in production use for way over a year now, Mikael found a > > not so nice bug in the livecd/init where, if no block device is attached to > > the system. the shell code would accidently iterate over all device nodes > > and disktype stalls on the first blocking (character) device. > > > > On the way to tracking this down hotplug++ received some more > > segmentaion fault protection. > > > > If you wonder why we still use hotplug++ in the times of u/dev, the answer > > is simple: calling modprobe directly form u/dev rules (yes we tried this) > > does not feature a blacklist, and we need one (e.g. for evbug and the > > various instable FB drivers). > > > > Have fun and enjoy, > > René Rebe - ExactCODE GmbH -- René Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name +49 (0)30 / 255 897 45
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
