On Apr 8, 2014, at 8:00 PM, xinglp wrote: >> Wouldn't it be the easiest way to let systemd configure the network >> interfaces? > It works well for my problemed vmware. I think we don't need ifup > ifdown script for systemd now.
It's best to let systemd's networkd deal with all of the network. You can change interface names, setup bonds, and all kinds of other configurations and settings. The only reason a person will not want to use systemd networkd is when: the dhcp server requires more information from a dhcp client which systemd networkd's dhcp client can't provide (such as a hostname) wireless is to be used with encryption and probably some others. When having both systemd and sysvinit in the LFS Book, the network section would be best written so that if a user is using systemd, do this if using sysvinit, do this. Sincerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
