| 1 |
What I ended up doing is put net.eth0 (my built in one) in boot instead |
| 2 |
of default, took net.eth1 (my wireless) from default and just left |
| 3 |
pcmcia in default. I used the settings in /etc/pcmcia/network.opts to |
| 4 |
set up my networking for the wireless card. |
| 5 |
|
| 6 |
For some reason, if net.eth0 is in boot, the system assumes that the net |
| 7 |
dependency is satisfied and never bothers me again, even if eth0 does |
| 8 |
not come up. |
| 9 |
|
| 10 |
Avi |
| 11 |
|
| 12 |
On Tue, 2002-05-07 at 13:04, Sean P. Kane wrote: |
| 13 |
> What is the "right" way to handle this situation. I have two nic cards |
| 14 |
> in my laptop. The built-in one and a wireless PCMCIA card. In my |
| 15 |
> /etc/init.d directory I have: |
| 16 |
> |
| 17 |
> net.eth0 (10/100BaseT) |
| 18 |
> net.lo (loopback) |
| 19 |
> net.wlan0 (wireless) |
| 20 |
> |
| 21 |
> On any given boot eth0 or wlan0 will fail since only one of them is |
| 22 |
> plugged in. However /etc/init.d/netmount has a depend of "need net" and |
| 23 |
> I would think that either of these being up would suffice, yet it seems |
| 24 |
> it wants both of them up. IS there a proper way to configure this so |
| 25 |
> that either on being up meets the needs of "need net"? |
| 26 |
|
| 27 |
-- |
| 28 |
Avi Schwartz |
| 29 |
avi@×××××××××××××××.com |
Archives