I will try to add more details tomorrow if needed but here is what happened: Did emerge rsync and emerge update world. (I don't know how long it has been since updating last time but was likely early January.) Rebooted. The scripts in boot and default runlevels did not complete. There were several messages that complained about dolisting command not found. I traced this to /sbin/rc but did not see exact problem there. So I started the services in boot and default manually. This allowed me to connect to the network. I tried emergeing sys-apps/baseutils to a previous version and then rebooted. This did fix the problem with the "dolisting" error message and all my runlevel scripts seemed to finish as usual... But... This apparently clobbered my network settings in /etc. My computers IP address had been setup to be 10.0.128.100 and it was now set to something else, which would explain it not talking to my router. After fixing the /etc files for the network settings, ifconfig looked fine, and the network is still unreachable. I am entering this from a separate site, and can get more details if needed and come back here to update this tracker. I want to run update world on this box as well, but if I loose network connectivity on this one as well I will be in a bind. I am still new to portage and haven't been able to track down the cause any more than this.
I have researched in cvs and found some info: on 3/10/2002 functions.sh v1.16 and /sbin/rc v1.17 were modified to use a bash function called dolisting(). When I did my "emerge rsync; emerge update world" yesterday I got the new /sbin/rc but I still had my <v.16 functions.sh. So when I rebooted, /sbin/rc was making a call to dolisting() that I didn't have in the functions.sh file. It treated it as a bad command or file name and aborted. The network connectivity issue is separate; but there must be a problem in one of the dependencies for me to not have updated functions.sh to the latest version and wound up in this mess. I will be a bit more hesitant to use "update world" in the future.
Well I don't know what dependency issues were created in the original update world but, AHAH I found why the network is unreachable. The new net.eth0 script in /etc/init.d was never actually running the line to add the default gateway! I commented all that out in mine and just added: /sbin/route add -net default gw ${gateway} netmask 0.0.0.0 metric 1 And it works! But I'm not sure but it seems from line 61 of net.eth0 that the default gateway will only be added if ${gateway} has a value and does not have a value at the same time. Please help. I've been reading the cvs documentation but do not know for sure how to update this file other than the kludge I am using locally.
I havn't seen this on any system I have access to. It sounds like you didn't merge over all your new config files... see 'emerge --help config' for more information.
Yes, you need to update your config files. "emerge --help config"
