udhcp and busybox

[Jason Schoon]

Agreed, whether it is in a script, or in a .conf file, this is a very common
way of specifying options for a server application.  Trying to make them all
available as command parameters will end up not suiting all users and/or
bloating the code.

On 3/26/06, Paul Fox <pgf at brightstareng.com> wrote:
>
> >
> > Hello Rob.  If you are working on shrinking udhcp, I have a feature
> > request.  Could it be made to not require a shell script.  I imagine
> > 90% of people using it just need to set the gateway, IP address, and
> > DNS servers. So it could have a few new options:
> >
> >      -g     set the gateway if no gateway is set on another interface
> >      -o     delete any other gateways first
> >      -d     edit /etc/resolv.conf
> >      -V     be verbose
> >
> > And if people need to do fancy stuff with it, they can make it
> > verbose and parse the output which can supply the information
> > currently supplied to the script.
> >
> > If you think this is a good idea, but not worth your time, I could
> > probably supply a patch.
>
> what's wrong with needing the script?  all it seems you're doing is
> hard-coding a bunch of actions that may or may not be suitable or
> complete for all users.
>
> paul
> =---------------------
> paul fox, pgf at brightstareng.com
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20060326/e2e2216b/attachment.htm