> Mm, that's interesting. However, in the present case, the mounts > should > really be backgrounded, and then come up as soon as the network is properly > available. I won't guarantee that this can deal with not having a DNS > server, but correct backgrounding behavior should make your original scenario > "just work". If it doesn't, we'll need to figure out what goes wrong.
I think the issue that is even though the mount is in the background, it fails and the mount process exits. In case 1, where eth1 isn't available, mount exits with a 'network unreachable' error. And after swapping the order the mount fails with 'unable to resolve hostname error' I'll test with etch,lenny and sid and provide more information Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
