After performing a new 2006.1 install I get the following message: "Cannot start netmount as net.eth0 could not start" during the the init stripts startup. I have installet kde with xdm added to the default runlevel. Note that my net.eth0 afterwards starts and I can use net with no problem. Any ideas My rc-update output: czuba@mithrandir ~ $ /sbin/rc-update show bootmisc | boot checkfs | boot checkroot | boot clock | boot consolefont | boot hostname | boot keymaps | boot local | default nonetwork localmount | boot modules | boot net.eth0 | default net.lo | boot netmount | default rmnologin | boot syslog-ng | default urandom | boot vixie-cron | default xdm | default
Please attach your /etc/conf.d/net and /etc/conf.d/rc files.
Created attachment 96036 [details] /etc/conf.d.net
Created attachment 96037 [details] /etc/conf.d/rc
I'm seeing this as well with an existing install. So it's a recent change in something. Portmap, netmount, kdm, and syslog-ng all startup before eth0.
(In reply to comment #4) > I'm seeing this as well with an existing install. So it's a recent change in > something. > > Portmap, netmount, kdm, and syslog-ng all startup before eth0. > I get the same thing, fresh Gentoo 2006.1 (networked) install. My rc-update output: aphax hans # rc-update show bootmisc | boot checkfs | boot checkroot | boot clock | boot consolefont | boot hald | default hostname | boot keymaps | boot local | default nonetwork localmount | boot modules | boot net.eth0 | default net.lo | boot netmount | default rmnologin | boot sshd | default syslog-ng | default urandom | boot vixie-cron | default xdm | default conf.d/net and rc are untouched. Could this be caused by bug#143928 ?
I'm suffering from this one too. I have to do a console login, stop xdm, start each of the failed services by hand (netmount, ypbind, and autofs), and then I start xdm again so I can log into X as an NIS user. I've tried adding "need net.lo" to /etc/init.d/portmap, thinking lo was not quite up. No help. I also tried lengthening the "sleep 1" in the portmap rc script to three seconds, thinking it needed more time to become responsive, but that didn't help either. By the time I reach the console command prompt, portmap is running. The services that depend on it are able to start without a problem.
same problem.
This should be fixed in baselayout-1.13.0_alpha11. Re-open if you disagree.