Re: udev 070 not create dvb device

["Alexander E. Patrakov" <patrakov@ums.usu.ru>]

I wrote:

> Anyway, I think that the following will work safely enough if one 
> ignores the input subsystem:
>
> 1. Apply that kernel patch, add udev rules for modaliases and 
> firmware, build the relevant extras. Install updated module-init-tools 
> for blacklist support. Do not install hotplug.
> 2. In S00mountkernfs initscript, mount /proc and /sys as usual.
> 3. In S10udev initscript, mount tmpfs on /dev, run "UDEV_RUN=0 
> /sbin/udevstart" and create additional directories and symlimks in 
> /dev. For Matthew: it is the same as the default udev initscript in 
> LFS does, but with UDEV_RUN=0.
> 4. In S40mountfs initscript, mount /usr and the rest of filesystems, 
> as usual.
> 5. In the new S55coldplug-emit initscript (to be used instead of 
> S55hotplug), do those echoes to "uevent" files in sysfs. Thus, modules 
> will be loaded, devices will be created (yes, udevstart's work 
> duplicated) and RUN rules will be also applied.
>
> Benefit for BLFS: those RUN rules will be applied with /usr certainly 
> mounted, thus there's no longer any need to wait for /usr in the alsa 
> RUN helper.
>
> Kay, could you please look at this and tell if anything is certainly 
> wrong/unsafe/bad except for the input subsystem?

Already found, sorry for the noise: eth0 fails to be brought up. No way 
around this proc/pidof hack.

-- 
Alexander E. Patrakov



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel