> > <soapbox>Personally, I think there's something fundamentally wrong > > with managing a firewall/router through a web-based interface, but it > > seems that I'm the only one who feels this way...</soapbox> > > Nope, your not alone. _Many_ of us feel exactly that way, but may don't > and this limits the user base. If this config weblet is loaded as a > package, you are only as unhappy as you make yourself :)
IMHO, there's nothing inherently wrong with GUI config tools (properly secured). I would like to see a consistent configuration system for the next generation LEAF that allows text-based menu configiguration via scripts on the default system, with the option of adding a web GUI if desired (sort of a light-weight linuxconf that actually works). It should also be possible to edit config files by hand without confusing the config menu front-end. The ease of use this provides would help widen the user base, and I think the discipline of maintaining a consistent configuration scheme will add to both understandability and ease of administration. As long as the power to manually edit the config-files directly is still available (w/o completely confusing the GUI tools), I don't see where this has any big negatives (other than the obvious time/effort involved in building the configuration framework in the first place). Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
