1 |
On Sat, 2005-09-24 at 20:52 -0700, michael@×××××××××××××.com wrote: |
2 |
> I have a computer with both a wired and wireless network card. At home I |
3 |
> use the wired connection, but when out I use the wireless. |
4 |
[snip] |
5 |
> Is there some way I can have dhcpcd to run in the background, and to |
6 |
> provide an IP address to my interface when it gets a response from the |
7 |
> server? I seem to remember busybox had script that did this; is there a |
8 |
> general solution? |
9 |
|
10 |
The first thing that comes to mind is to set |
11 |
RC_PARALLEL_STARTUP="yes" |
12 |
in /etc/conf.d/rc |
13 |
|
14 |
However, lots of things rely on the net.* scripts before they start. |
15 |
Have a look at the output of |
16 |
`egrep need.*net /etc/init.d/*` |
17 |
and you'll see every service that will wait for your network script to |
18 |
start (which means waiting for a dhcp response) |
19 |
|
20 |
The second thing that came to my mind, and this would probably rely on |
21 |
you only getting a dhcp for the wireless, and not the wired lan, would |
22 |
be to "roll your own" /etc/init.d/net.eth1 script. Make it exactly the |
23 |
same as /etc/init.d/net.lo, but in the depend() function, add something |
24 |
like "provide mywireless". This, coupled with parallel startup, should |
25 |
mean that no other init script will require your net.eth1 connection and |
26 |
it can take time without holding other scripts up. |
27 |
|
28 |
I've never tried this idea, so it could be fundamentally flawed, but its |
29 |
just a thought! |
30 |
|
31 |
HTH, |
32 |
-- |
33 |
Iain Buchanan <iaindb@××××××××××××.au> |
34 |
|
35 |
-- |
36 |
gentoo-user@g.o mailing list |