On Thursday 16 December 2004 4:16 am, Giacomo Mulas wrote: > for some reason, autodiscovery (whether you run discover1 or discover2) > detected eth1394 before sk98lin, while previously it used to do the other > way around. As to why this is so, I have no idea. However, regardless of > why this happened, it is definitely a Bad Thing (TM) to rely on the order > of autodetection of devices for something as critical as deciding which > phisical device gets bound to a given network interface, when you have > more than one. I did not notice this problem because I _always_ put such > critical devices in /etc/modules, in the order in which I want them > loaded.
Fair enough, and I have done just that. Now though, my question is why are the nfs filesystems not being mounted at boot time like they used to, or rather, why is the network unreachable at boot time? I can see the messages where the mount attempts fail because there is no route to host. John -- John C. Martin - http://www.cs.utk.edu/~jomartin * Use my gpg key to ensure privacy - http://www.cs.utk.edu/~jomartin/John.gpg * You seal an envelope before you mail it - why treat your email differently?
pgpvhYxn9w5JJ.pgp
Description: PGP signature
