1 |
Or perhaps, |
2 |
Something a little more explicit might work? In instances such as the |
3 |
ifconfig lines, it's to create eth0 aliases (such as eth0:0), so perhaps |
4 |
that could look like: |
5 |
|
6 |
ifconfig_eth0:0 = "10.1.1.1 netmask 255.255.255.0" |
7 |
ifconfig_eth0:1 = "10.1.1.2 netmask 255.255.255.0" |
8 |
|
9 |
For uses that really do require a list (such as modules), something like: |
10 |
|
11 |
modules = "wpa_supplicant", "ifconfig" |
12 |
|
13 |
or redefinition: |
14 |
|
15 |
modules = "wpa_supplicant" |
16 |
modules = "ifconfig" |
17 |
|
18 |
might work? If the comma separated syntax is acceptable, it may be that |
19 |
brackets around it are acceptable too, in which case the bash syntax is |
20 |
fine. |
21 |
If the normal shells will still require *some* form of processing to |
22 |
deal with the list, could they not be given processing to deal with |
23 |
lists that bash already has builtin? |
24 |
Mike 5:) |
25 |
-- |
26 |
gentoo-dev@g.o mailing list |