You are not logged in.
First of all I want to say a big thanks to the Arch developers. I am new here and really enjoying the distro. Great work guys.
One question: during the Arch boot process (amazingly fast compared to other I might add...) I get about a 5 second delay at:
::Starting Network [BUSY]
And then it begins to boot into my login screen. The network otherwise works fine. I wonder whether this delay is normal or whether I can optimize my eth0 settings?
My relevant rc.conf config:
HOSTNAME="scorpion"
eth0="dhcp"
INTERFACES=(eth0)
gateway="dhcp"
ROUTES=(!gateway)
My /etc/resolv.conf file:
domain uniserve.com
nameserver 192.168.0.2
ifconfig:
eth0 Link encap:Ethernet HWaddr 00:0E:A6:89:A8:F5
inet addr:192.168.0.122 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20e:a6ff:fe89:a8f5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5626 errors:0 dropped:0 overruns:0 frame:0
TX packets:1849 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3040845 (2.8 Mb) TX bytes:274216 (267.7 Kb)
Interrupt:18
Any suggestions or comments greatly appreciated.
Last edited by lagagnon (2009-12-13 13:53:49)
Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.
Offline
Seems normal with DHCP. If you want it to fly by, consider a static IP config described on the wiki.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
You can background it.
Offline
You can background it.
As long as he doesn't have something like ntpd or openntpd, samba, nfs, apache2, etc. that depend on the network being up though, no?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
@graysky
Of course :-)
Offline
If you just put a "@" before network in rc.conf's daemons array, it gets backgrounded so the system continues to boot up before the network is up and running. I do this, and shave off about 3 seconds of boot time, and everything works by the time I'm into the WM. Assuming you don't run any daemons that require the network to be active, it shouldn't cause any problems.
The human being created civilization not because of willingness but of a need to be assimilated into higher orders of structure and meaning.
Offline
karol wrote:You can background it.
As long as he doesn't have something like ntpd or openntpd, samba, nfs, apache2, etc. that depend on the network being up though, no?
At least ntpd can be tricked to work (if you don't use .pool servers) even if you background network (or wicd or anything else you may use to manage your network connections). I can't comment about samba, nfs and apache2 because I don't use them.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
If you just put a "@" before network in rc.conf's daemons array, it gets backgrounded so the system continues to boot up before the network is up and running.
Excellent! I had no idea about that feature. Works a treat!
Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.
Offline
I notice both dhcpcd and dhclient both do this. I'm guessing there is some type of authentification process that makes it take this amount of time. I've used udhcp before though (a lightweight minimalistic dhcp client) and it only takes about a second though, hmm.
Last edited by Gen2ly (2009-12-13 18:41:31)
Setting Up a Scripting Environment | Proud donor to wikipedia - link
Offline
if you dont need dhcp, setup a static IP as suggested. Some routers simply have crappy dhcp servers.
Offline