On 6/1/07, Andrew Beverley <[EMAIL PROTECTED]> wrote: > > Thanks! After some research yesterday I worked out that the 'new' method > just means that 'ip' doesn't deal with aliased interface names (it only > deals with 'real' interfaces), whereas 'ifconfig' deals with both. > Therefore, if using 'ip' to configure the interfaces instead of ifconfig > (as LFS now does) then using an interface name of eth0:n no longer > works. As you rightly identified, ip uses the 'label' option instead. > > However, I hadn't got round to editing the script or replying to the > list, so thanks for sending the patch! > > I think this would be a worthwhile inclusion to LFS. Have you emailed > lfs-dev or would you like me to?
The right way to do this is to add a new service in /etc/sysconfig/network-devices/services. You could call it ipv4-alias or something. Copy ipv4-static for a template. It would be really simple since it's just one call to ip. Then you'd enable that service in /etc/sysconfig/network-devices/ifconfig.eth0 just like you do with dhcp or any other service. As for getting it in LFS, I would be find adding it to the contrib directory in lfs-bootscripts. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
