If worked here - at least for now (I restarted the system a few times without problems).
In my opinion, this work-around also points to a timing issue between starting the ethernet network, starting the samba system and mouting the network shares.
Most of most of the above mentioned suggestions influence the point in time when a specific service is started:
putting smbfs in /etc/modules: early in the boot process
mounting shares in /etc/rc.local: late in the boot process
pre-up sleep 5 in /etc/network/interfaces: give something else more time to finish
This would also be consistent with my observation that the /etc/modules variant sometimes work and sometimes it doesn't.
My guess: This problem is a hick-up in the multi-threaed booting process introduced sometime during the latest Dapper pre-releases.
If worked here - at least for now (I restarted the system a few times without problems).
In my opinion, this work-around also points to a timing issue between starting the ethernet network, starting the samba system and mouting the network shares.
Most of most of the above mentioned suggestions influence the point in time when a specific service is started:
putting smbfs in /etc/modules: early in the boot process
mounting shares in /etc/rc.local: late in the boot process
pre-up sleep 5 in /etc/network/ interfaces: give something else more time to finish
This would also be consistent with my observation that the /etc/modules variant sometimes work and sometimes it doesn't.
My guess: This problem is a hick-up in the multi-threaed booting process introduced sometime during the latest Dapper pre-releases.