Matthew Burgess wrote these words on 09/13/05 15:47 CST: > But how can *attempting to* correctly configure the devices when we > don't install the software that exercises those nodes be a good thing? > Surely one should configure the devices when one installs the software > that uses them, just as one would configure the rest of that software at > the same time. Surely it's only at that point that one is fully aware > of the issues involved, and therefore more educated in being able to > correctly configure the hardware?
I will answer your question, then probably bow out of the thread, as I don't want to appear that I need to provide a counter argument to every detail. I'm not trying to dodge the issue, or say that I have nothing more to say, I'm simply trying to be polite and let others have their say as well. There is merit in the knowledge aspect of editing the rules file for every piece of software that may need access to hardware. However, it is my opinion that because Udev is an LFS package, the knowledge should be acquired there. LFS installs the daemon, LFS starts the daemon and provides a mechanism so that it is started and each boot. Folks that want to learn about Udev should have already discovered that knowledge when they installed it in LFS. Having to modify the file and restart a daemon every time a piece of software is installed that needs access to a device node is no longer a learning experience. It is now nothing more than a hassle. -- 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:50:00 up 164 days, 15:23, 3 users, load average: 0.02, 0.06, 0.21 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
