Thank you for the fast response. For sake of clarification: When you mention 'network configuration scripts' are you talking about scripts like the old brcm-2.4 init.d netconfig script and things like target profile specific network configuration defaults stored in target/linux/atheros/base-files/etc/uci-defaults/network and target/linux/ar71xx/base-files/etc/defconfig/* for example?
Please advise Regards Hanno -----Original Message----- From: Felix Fietkau [mailto:n...@openwrt.org] Sent: Saturday, 22 October 2011 12:08 p.m. To: OpenWrt Development List Cc: Hanno Schupp Subject: Re: [OpenWrt-Devel] Netifd and ubus in trunk - Please provide some details On 2011-10-22 12:59 AM, Hanno Schupp wrote: > Hi Felix, > > What is this netifd and ubus business appearing in trunk? What is it > implementing or replacing? Will it affect all platforms and be > included firmware images by default or does it have to be specifically > compiled into an image? How can we help you testing this new package, > what should we be looking for in terms of regression testing? ubus simply implements an RPC service, making it easy for C programs to export an API that can easily be accessed from other C code or even shell scripts. netifd is going to replace the network configuration scripts at some point. right now it's experimental and disabled by default, as not all network proto handlers have been converted yet (so far, static, ppp, pppoe, pppoa, dhcp are supported). What would be useful is not just testing what has been ported, but also review of the code and porting more of our protocol handler scripts. When all the existing features have been ported over, this will be enabled by default and the old scripts will be removed. - Felix _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
