Joost Roeleveld wrote:
On Tuesday 17 May 2011 20:48:54 Dale wrote:
The emerge -e world finished. It still doesn't work like it did a few
weeks ago. So, I tried the nonetwork option. That starts about every
service except the GUI, my UPS thingy and a couple others. Get this, it
even starts the freaking network. Why is it called nonetwork if it
starts the network too. Seeing the list of services it started, it
didn't miss many.
Did it start as part of "Hey, there is a network card, lets use it"?
I believe the default configuration auto-starts network devices if any are
found.
There is something not right here. It appears that openrc or whatever
is not working the way it should. The funniest part about this, it
worked fine the other day and it works just fine from a console. It
just doesn't work right when passed from grub.
Anyone have any ideas on how to fix this?
Try disabling auto-starting services? :)
--
Joost
It's been a while since I rebooted. Built a new kernel so here we go
again. Round two.
Disabled that, still started the network and a WHOLE lot of other
things. This is what is in the nonetwork runlevel:
root@fireball / # ls -al /etc/runlevels/nonetwork/
total 0
drwxr-xr-x 2 root root 72 Nov 17 2010 .
drwxr-xr-x 8 root root 200 May 10 18:19 ..
lrwxrwxrwx 1 root root 17 Dec 9 05:12 local -> /etc/init.d/local
root@fireball / #
I'm going to create a runlevel myself and let it mirror the boot
runlevel. Let's see what that does. I'll post results here shortly.
Dale
:-) :-)
