hi Vaidhy, i also got the same error as u guys did, that is, i got it after i upgraded from 2.0.36 to 2.2.4. do u think that same fix'll still work for me ? i dont feel too comfortable removing some lines from my init.d/network because though i get those error messages, my box is still working perfectly. and i dont get any error messages on my syslog also. could this be something w/ 2.2.4's new design ? TIA, Chad
On Fri, Apr 16, 1999 at 09:32:18PM -0400, Alec Smith wrote: > Got the same error... The cure is to remove the route -add parameters in > /etc/init.d/network for eth0, lo, and any other adapters... It is not > necessary to remove the route -add default gw parameter if you have a > gateway. > > > > On Fri, 16 Apr 1999, Vaidhyanathan G Mayilrangam wrote: > > > Hi Chris, > > > > I generally get the message during network initialization when something is > > missing or wrong.. Can you post the relevant boot message. (Use dmesg). > > > > Regards, > > Vaidhy > > > > On Fri, Apr 16, 1999 at 09:15:37PM -0400, Chris Brown wrote: > > > Greetings, > > > I'm cleaning up the boot messages of a system we're moving to > > > another location, and I ran into a funny message. When the system > > > boots everything looks OK until It mounts the local filesystems. I > > > get this weird error, > > > "SIOCADDRT: Invalid argument" > > > twice, and then it moves on. I've looked at the > > > /etc/init.d/mountall.sh script, /etc/fstab, and /proc/filesystems > > > and I still don't have a clue. What do I need to change to kill this > > > error? > > > Thanks, > > > Chris > > >
