Some notes as I attempt to make the lfs bootscripts more wireless-friendly:
Currently the networking scripts allow only for one default gateway. However, each interface should have it's own. When trying to do that manually with ip, it bombs. Since I still prefer net-tools I decided to try it with route and it works swimmingly. After discussing this with Jim, he said he would send a bug report upstream to fix ip. Once this is done, the code will need to be changed to only grep for a default gateway on the interface that is being setup, not all interfaces. Is it necessary for the scripts to still maintain code to allow it to act as it did long ago? I'm referring specifically to ifconfig.* being a file and not a directory. If we never allow a break from the old ways, the code will get bigger and clunkier. Lastly, I see a need for a user-configurable file to dictate which order interfaces should be brought up. While this probably won't ultimately clean up the code (as we will still need code to reverse the process), it will allow people to bring up interfaces in a non-alphabetical order. I'm toying with some ideas here, but comments and suggestions are most appreciated. -- Archaic Want control, education, and security from your operating system? Hardened Linux From Scratch http://www.linuxfromscratch.org/hlfs -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
