Dirk Heinrichs <dirk.heinri...@online.de> writes: > Am Sonntag, 28. Dezember 2008 12:38:37 schrieb Harry Putnam: >> Still, on a shutdown I can't get past this output: >> >> hwclock waiting for localmount > > I mentioned it in your other thread. Try masking openrc >=0.4.0.
I've masked >=sys-apps/openrc-0.4.0 and downlgraded to sys-apps/openrc (0.3.0...@12/28/08) Bootup seems normal except for the fact that something is still trying to start eth1. Other things seem to have started normally and no hwclock on shutdown. So why are there entities beyond /etc/conf.d/net and the controls used in rc-udpate that can even start things in /etc/init.d? Aren't those two controls the time honored places to handle that sort of stuff? What else is capable of attempting to start services? Have I been hacked (.. hehe)
