-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roy Marples wrote: > One issue with that is there is no automatic way of doing that. We just > pass the array elements onto the various programs > > config_eth0=( "1.2.3.4/24" "some voodoo" ) > becomes > ifconfig eth0 1.2.3.4/24 > ifconfig eth0 some voodoo > > We also do the same for iproute2 which has a very comples language > structure. We also do this for most of the helper programs that we use - > vlan, bridging, wireless just to name a few. > > Do we want variables for every single possibility? > > The beauty with the array structure is that it allows the user to define > a sequence of commands to send to a helper. The issue with the array > structure is that it is bash and we strive to support non bash shells > hence the discussion. >
Thanks for clarifying this - I can see the where you're coming from a bit better in light of this explanation. I think that as long as the documentation is clear and well-commented we should be in good shape - the goal is of course to make things fairly transparent to the less-educated among us - especially when we're talking about something simple like setting up a static IP network or DHCP. At the same time, if we can accomplish that while also allowing for folks using multi-homed systems with all kinds of bridges and cost-based routing and all that so much the better... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHIqooG4/rWKZmVWkRAlo2AKCmJy98UKFngz/PuHQwbJ9X4LKsxACgo+TS Ze5HKc9YgqvIJr9Y29gSn5E= =WPAf -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
