The bug here appears to be in the packaging, not the init script and/or code.
Example, I am using pcnet32/vmxnet with init.d. The upstream wiki says that I need to have the following in my modprobe config (I have it in modprobe.d/open-vm-tools):
install pcnet32 /sbin/modprobe -q --ignore-install vmxnet; /sbin/modprobe -q --ignore-install pcnet32 $CMDLINE_OPTS; /bin/true;
(source: http://open-vm-tools.wiki.sourceforge.net/Packaging)
Without this, rebooting will cause the eth device to fail, as Craig described.
The bug here appears to be in the packaging, not the init script and/or code.
Example, I am using pcnet32/vmxnet with init.d. The upstream wiki says that I need to have the following in my modprobe config (I have it in modprobe. d/open- vm-tools) : open-vm- tools.wiki. sourceforge. net/Packaging)
install pcnet32 /sbin/modprobe -q --ignore-install vmxnet; /sbin/modprobe -q --ignore-install pcnet32 $CMDLINE_OPTS; /bin/true;
(source: http://
Without this, rebooting will cause the eth device to fail, as Craig described.