So basically my box stopped supporting SSH on boot. I'd have to take a keyboard out to the living room and connect it and start ssh by hand. Looking through the logs I saw that ssh was being killed by signal 15. So I noticed on boot it said starting eth0.. starting netplug... backgrounding... the next thing was starting sshd which failed. (the signal 15 error) and so I unmerged netplug and everything worked magically fine. Basically it looked like netscripts bring up the interface, then hand it over to netplug... which cycles the interface down/up when it starts up. netscripts basically should not bring up the interface, they should leave that to netplug and then move on to the next item... but give netplug enough time to bring the interface up.
*** This bug has been marked as a duplicate of 112088 ***
