Randy McMurchy wrote:
But for the BLFS devs to painstakingly go through the book and try and figure out which ones of the almost 400 packages are going to need updates to add an entry to a rules file, and instructions to restart udev is simply such a royal pain in the ass.
I wasn't/we weren't expecting you to. We, as a community, need to coordinate this effort. I was under the impression that BLFS wouldn't be majorly affected by this. Aside from multimedia packages, networking packages, and possibly X, I can't see anything that immediately looks like it requires specific device setup. Admittedly that was at a very brief glance through the BLFS-SVN TOC.
Archaic did actually test this on a BLFS system, which included things like SSH which uncovered the fact we really *do* need /dev/{u,random} configured correctly. Pushing this out to the wider community to test on their particular setups is a great way (IMO) of finding out exactly how much pain this is going to cause everyone (users and developers alike).
It would almost seem that to avoid that huge headache, BLFS will simply migrate all the rules you pull out and stick them into a BLFS rules file and have new BLFS users install this rules file and restart UDEV.
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).
Problem is getting folks to see the instructions to add the rules file and getting them to restart udev.
Do they miss the instructions to install a bootscript? I'm sure if they do, they'd realise why it wasn't working properly.
Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
