Matthew Burgess wrote these words on 09/13/05 15:05 CST: > Hmm, I'd equate that with telling folks to grab the blfs-bootscripts > package and do a 'make install' (i.e. install every single bootscript, > whether it's required or not).
No Matt, that is a bad analogy. Bootscripts run at boot time and will fail with ugly messages if the required software/hardware doesn't exit. A Udev rules file sets up parameters to create device nodes if, *and only if*, the hardware exists. The device nodes need to be created if the hardware exists. A properly set up Udev rules file ensures the device nodes are properly created. Having a Udev rules file installed in *LFS* that works for any possible hardware scenario on the system is IMHO the sensible approach. There is no harm in having a properly created rules file in LFS. There is no overhead, so why not? My question is this: What exactly is gained by your proposal? To me, it is a step downhill. Improper device nodes will be created for hardware that exists on the system. How can this be a good thing? -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 15:30:00 up 164 days, 15:03, 3 users, load average: 0.11, 0.31, 0.58 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
