You are not logged in.
Pages: 1
I use Arch on my laptop and depending on where I boot up the network is not always available. Typically this results in 30 seconds to a minute of the Network showing [BUSY] before [FAIL]. This is not surprising since I might be in an airport or somewhere with no wireless network.
So in order to speed boot time I'd like to start as many daemons in the background as possible.. specifically network. However, I'd like very much not to hose my system.
Here's the daemon's section of my rc.conf. Can you tell me if it's ok to start network in the background? Also, any other suggestions as far as starting other services in the background go? Most are pretty fast except Network..
DAEMONS=(syslog-ng !hotplug !pcmcia network acpid portmap fam netfs @cups crond dbus hal @mono @samba avahi-daemon !avahi-dnscond)
Offline
I would prefer a network environment set for each location / situation. Have a look at /etc/rc,conf, there is such a section.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
BTW how one can set up a network profile with only lo enabled ? I let lo in rc.conf and touch an empty network profile named "alone", it works but also gave an error "unable to find interface" or something like this. The one with "home" and eth0 works fine, though.
Excessive showering, grooming, and toothbrushing is not only vain, it wastes valuable coding time.
Offline
I run network in the background. In fact, every daemon I load is backgrounded and it all works fine. But I'm able to do that because I use powersaved, for example, which calls dbus and hal in the right order.
I am a gated community.
Offline
Pages: 1