1 |
Hi Jorge, |
2 |
|
3 |
On Thu, May 12, 2011 at 11:49:22PM +0000, Jorge Manuel B. S. Vicetto wrote: |
4 |
> On 12-05-2011 14:34, William Hubbs wrote: |
5 |
> > I'm not sure I follow. would you rather keep the config_* variable? |
6 |
> |
7 |
> I think we should try to keep them. |
8 |
> |
9 |
> > If so, how do you feel about requiring the syntax of the variable to |
10 |
> > match the tool you are using? |
11 |
> |
12 |
> That's exactly what I meant. |
13 |
> By choosing the module one would get tied to its syntax. That should |
14 |
> make it simpler to parse the data. |
15 |
|
16 |
Ok, cool, this was actually my first choice, but I wasn't sure how it |
17 |
would go over. |
18 |
|
19 |
> I would also suggest making the |
20 |
> declaration of modules mandatory or for you to pick a default tool to be |
21 |
> used when someone doesn't declare modules. |
22 |
|
23 |
We already do this. iproute2 is preferred if you have it installed; |
24 |
otherwise ifconfig is used. |
25 |
|
26 |
I believe the order of preference is discussed in the net.example file. |
27 |
|
28 |
The only time you really need the modules= or modules_iface= lines is if |
29 |
you want to force a specific module to be preferred for an interface. |
30 |
|
31 |
William |