| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Roy Marples wrote: |
| 5 |
> One issue with that is there is no automatic way of doing that. We just |
| 6 |
> pass the array elements onto the various programs |
| 7 |
> |
| 8 |
> config_eth0=( "1.2.3.4/24" "some voodoo" ) |
| 9 |
> becomes |
| 10 |
> ifconfig eth0 1.2.3.4/24 |
| 11 |
> ifconfig eth0 some voodoo |
| 12 |
> |
| 13 |
> We also do the same for iproute2 which has a very comples language |
| 14 |
> structure. We also do this for most of the helper programs that we use - |
| 15 |
> vlan, bridging, wireless just to name a few. |
| 16 |
> |
| 17 |
> Do we want variables for every single possibility? |
| 18 |
> |
| 19 |
> The beauty with the array structure is that it allows the user to define |
| 20 |
> a sequence of commands to send to a helper. The issue with the array |
| 21 |
> structure is that it is bash and we strive to support non bash shells |
| 22 |
> hence the discussion. |
| 23 |
> |
| 24 |
|
| 25 |
Thanks for clarifying this - I can see the where you're coming from a |
| 26 |
bit better in light of this explanation. I think that as long as the |
| 27 |
documentation is clear and well-commented we should be in good shape - |
| 28 |
the goal is of course to make things fairly transparent to the |
| 29 |
less-educated among us - especially when we're talking about something |
| 30 |
simple like setting up a static IP network or DHCP. At the same time, |
| 31 |
if we can accomplish that while also allowing for folks using |
| 32 |
multi-homed systems with all kinds of bridges and cost-based routing and |
| 33 |
all that so much the better... |
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 36 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 37 |
|
| 38 |
iD8DBQFHIqooG4/rWKZmVWkRAlo2AKCmJy98UKFngz/PuHQwbJ9X4LKsxACgo+TS |
| 39 |
Ze5HKc9YgqvIJr9Y29gSn5E= |
| 40 |
=WPAf |
| 41 |
-----END PGP SIGNATURE----- |
Archives