This is in response to having the /etc/init.d/networking script call ifrename. Marco said/asked "No, why?"
I'm hoping that Marco will reconsider his answer...
The reason why is that network adapters are not guaranteed to always come up in the same order between reboots.
It is important to map the network devices from the init script because it must be done before they are bought up with an IP address.
This problem bit me the other day, where previously my e1000 card was eth0, and my 8139too card was eth1, but on reboot they had swapped over and networking no longer worked.
This is a real problem, that affects permanent ethernet cards and not just hot pluggable ones.
I solved the problem by mapping the names onto the MAC addresses using nameif, since that's included in the netbase package.
I still had to to edit the /etc/init.d/networking script to call nameif though.
Marco, I understand that ifrename was designed to superscede ifrename, but I would like to propose that you consider the option of supporting both in the /etc/init.d/networking script.
I'd imagine that the code would work something along the lines of looking for ifrename and it's config file first, and if not found then use the older nameif.
The code in it's basic form (minus comments and console messages) would look something like:
if [ -r /etc/iftab ] && [ -x /sbin/ifrename ]; then
/sbin/ifrename -p -d
elif [ -r /etc/mactab ] && [ -x /sbin/nameif ]; then
/sbin/nameif
fiApart from adding support for nameif which is part of the netbase package, this version also passes the -d parameter to iferename.
The documentation for ifrename specifies that the -d option should be used on Debian systems to parse the /etc/network/interfaces file to determine which devices to load modules for.
Regards,
-- Jim Barber
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
