That is the fourth solution I see now in a raw... after Yocto, Buildroot and OpenWrt...
This is what I was referring to. It is inconsistent across projects. :) That being said, it seems that Harald is objecting to this heavily for some reason (may be miscommunication between us). Thereby, I will not insist on this. If the developers feel happier without that feature, let it be so. On Tue, Mar 18, 2014 at 2:32 PM, Cristian Ionescu-Idbohrn <cristian.ionescu-idbo...@axis.com> wrote: > On Tue, 18 Mar 2014, Bryan Evenson wrote: >> >> How about a set of ntpd menuconfig options to build the command >> line? We could configure the default ntpd settings at build time, >> it wouldn't add anything to the size of the final ntpd binary. > > How about using a resource file the initscript would source: > > ---[ rc-file ]--- > NTPD_OPT1='-f foo' > NTPD_OPT2='-b bar' > NTPD_OPT3= > ----------------- > > ---[ initscript ]--- > #!/bin/sh > > . /path/to/rc-file > ... > <command line to start> ntpd $NTPD_OPT1 $NTPD_OPT2 $NTPD_OPT3 > ... > -------------------- > > > Cheers, > > -- > Cristian > _______________________________________________ > busybox mailing list > busybox@busybox.net > http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox