A year or so ago, I was working on getting Gnome-system-tools to support BLFS (https://bugzilla.gnome.org/show_bug.cgi?id=624299). While I was doing that, I ran into roadblocks when trying to implement the network functions. They were:
* The configuration files. Instead of a single file, there were multiple files for each service, and what service runs is controlled by the ONBOOT variable (which is normally supposed to control whenever to initialize the device or not), and this made it a mess to implement in the backends. * The fact that both DHCPCD and dhclient had very similar comfiguration files, which made it hard to implement DHCP support in the backends. Dissecting the scripts further yielded more problems: * Absolutely no Wifi support in the network scripts. This is a real problem for people who use a laptop (like me), and who don't want to lug around a ethernet cable every time they want the internet. You can't set the SSID of a network on boot, and those who want to connect to a secure network are left out. * Zilch IPv6 support. There really aren't many address to go around, and a lack of support for IPv6 worries me. And since we are doing major changes to the bootscripts, I suggest that we fix the above mentioned issues. We should start with only using one configuration file per interface, using SERVICE to set which program to use for setting up the network. If you have any questions, I am open to replies. -- William Immendorf The ultimate in free computing. Messages in plain text, please, no HTML. GPG key ID: 1697BE98 If it's not signed, it's not from me. -- "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- Are you a Gmail user? Please read this important notice: http://www.fsf.org/campaigns/jstrap/gmail?31450. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
