OpenWRT branches i work with
3c4165a305
hi Another version, in this one the enable_server option is in the timeserver ntp part of the "system" config file You can patch trunk and bacfire (tested both) You can put busybox ntpd in client mode (if you put server), in client & server (by putting enable_server to 1, ntpd listen to udp 123), and also in server mode only (if you didn't put any servers in the config and still put enable_server 1, ntpd will answer with the time of the router) I've replaced "config_foreach getpeers timeserver" with "config_get peers ntp server" because we want ntp timeserver, not random ones (to pre-answer if someone want to say that it's intrusive ...) Signed-off-by: Etienne CHAMPETIER <etienne.champetier@free.fr> Le 27/03/2012 20:41, Etienne Champetier a écrit : > I've now tested my trunk patch and it works fine > But I still can't find were $PROG is defined (is this a mistake, or some sort of built in variable???) > (I've made some grep and nothing) > > Le 23/03/2012 02:19, Philip Prindeville a écrit : >> Maybe: >> >> [ -n "$PROG" -a -x "$PROG" ] || return 1 >> >> instead? >> >> >> On 3/22/12 4:34 PM, Etienne Champetier wrote: >>> Hi >>> >>> The 2 attached patchs (trunk & bacfire) add busybox ntpd enable_server option, as busybox ntpd server is compiled by default. >>> We only need 1 client/server daemon (olipro patch was launching 2 daemons) >>> I've fully tested the bacfire patch, and as i don't have a running openwrt trunk i'm not sure for the trunk patch (i'm sure about my modifications, but i'm not sure about "[ -x $PROG ] || return 1", as "$PROG" isn't defined ?!) >>> >>> Signed-off-by: Etienne CHAMPETIER <etienne.champetier@free.fr> >>> >>> >>> Le 16/01/2012 01:57, Philip Prindeville a écrit : >>>> On 1/14/12 11:37 AM, Olipro wrote: >>>>> On Saturday 14 Jan 2012 02:45:59 Philip Prindeville wrote: >>>>>> Don't we already have a 'disabled' option? Now we're adding an >>>>>> 'enable_server' option? >>>>>> >>>>>> That seems confusing for no useful reason. >>>>>> >>>>> have you bothered to read what I originally wrote? your response would make >>>>> me inclined to believe that you didn't. >>>>> >>>>> currently the ntpd initscript only runs it as a CLIENT - this patch enables >>>>> you to have one instance running as a client and another as a SERVER that >>>>> other hosts can synchronise with. >>>>> >>>>> Or perhaps I'm misunderstanding, what would you propose for allowing the >>>>> built-in busybox ntpd to be utilised as a server? a separate init script >>>>> entirely perhaps? >>>> Or separate config sections... instead of 'config ntp' have 'config ntp-server' and 'config ntp-client'. >>>> >>>> -Philip >>>> >>>> >>>> _______________________________________________ >>>> openwrt-devel mailing list >>>> openwrt-devel@lists.openwrt.org >>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel >> _______________________________________________ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel SVN-Revision: 31374 |
||
|---|---|---|
| docs | ||
| include | ||
| package | ||
| scripts | ||
| target | ||
| toolchain | ||
| tools | ||
| .gitignore | ||
| BSDmakefile | ||
| Config.in | ||
| feeds.conf.default | ||
| LICENSE | ||
| Makefile | ||
| README | ||
| rules.mk | ||
This is the buildsystem for the OpenWrt Linux distribution. Please use "make menuconfig" to configure your appreciated configuration for the toolchain and firmware. You need to have installed gcc, binutils, patch, bzip2, flex, make, gettext, pkg-config, unzip, libz-dev and libc headers. Run "./scripts/feeds update" to get the latest package definitions defined in feeds.conf / feeds.conf.default respectively and "./scripts/feeds install" to install symlinks into "package/feeds/*". Use "make menuconfig" to configure your image. Simply running "make" will build your firmware. It will download all sources, build the cross-compile toolchain, the kernel and all choosen applications. You can use "scripts/flashing/flash.sh" for remotely updating your embedded system via tftp. The OpenWrt system is documented in docs/. You will need a LaTeX distribution and the tex4ht package to build the documentation. Type "make -C docs/" to build it. To build your own firmware you need to have access to a Linux, BSD or MacOSX system (case-sensitive filesystem required). Cygwin will not be supported because of the lack of case sensitiveness in the file system. Sunshine! Your OpenWrt Project http://openwrt.org