As I said, it's enterprise environments where it fails. Sure, simple home users with a cable
or DSL modem serving DHCP, or connecting to your local Starbucks wifi or whatever, have no
problems: everyone uses that model and of course it works properly.
It's when you start needing lots of OTHER network services, like NIS, autofs, etc. etc. that
we hit the "there be dragons" areas where Ubuntu has not done the due diligence to make sure
their super-cool new features don't break traditional, long-standing, it-just-works
BTW, adding a script to if-up.d won't work: the problem is not that autofs starts before the
network interface comes up: autofs actually doesn't need the network interface to be up IIRC.
The problem is that autofs starts before NIS binds to its server, so when autofs starts and
asks NIS for its maps, NIS doesn't give it any maps, so autofs doesn't set up any automounts.
What needs to happen is autofs cannot start until AFTER NIS has finished binding to its server.
I don't know of any way to do that in the current Ubuntu LTS release, short of creating some
script that runs in the background and queries NIS to see when it has maps available, then
(re-)starts autofs when it is.