Thank you for your kindness. I have read all these. But I think that is not enough. Some more work need to be done. I need dig deeper. Ok, let me tell something:
Actually I want to know how the hostapd.conf is produced. Because there is one option that I am interested, channel. This option resides int the /etc/config/wireless. I just want to know how the channle in wireless is piped to hostapd.conf. And I want do some altercation about this option. At the beginning, I thought that the point was the hostapd.sh which resides in /lib/wifi/. But it still works after I deleted this file. mac80211.sh which also resides in the same directory initiates the system for the first time startup. Then I deleted the /sbin/wifi. But the translation from wireless to hostapd.conf still works. Then I found the problem maybe was in /etc/init.d/network. So I commented all the functions except the start_servive() , but everything still was good. Finally I commented the start_service and the pipe was cut off. The translation was down as well as the system. I know the point might be here. Something related to procd which is just a process management application. I am stuck here. I still can't figure how the channel translated from wireless to hostapd.conf is achieved. On Thu, Mar 13, 2014 at 6:08 PM, Damian Kaczkowski < damian.kaczkowski+open...@gmail.com> wrote: > Hello Wandy. > > Read this: > http://wiki.openwrt.org/doc/devel/config-scripting > > and this: > http://wiki.openwrt.org/doc/devel/network-scripting > http://wiki.openwrt.org/doc/start#developing > http://downloads.openwrt.org/docs/openwrt.html#x1-310001.3 > > Should give you a good starting point. > > > On 13 March 2014 10:04, Wandy Lau <xdragon...@gmail.com> wrote: > >> Hi, >> I really appreciate your kind help,guys. Thank you all. I wonder >> the process of uci configuration process is : LuCI makes changes into the >> /etc/config/*, >> then all the file in this directory will be parsed producing the >> configure file of other application such as hostapt, dropbear and so on. >> I have been looking for the parse process for a couple days. Actually, I >> want to do some changes, so I have to figure out this process. Thank you >> zhou for you reminds. Perhaps I miss some points when read the uci.sh and >> function.sh. Thank you. I will try again. >> >> >> On Thu, Mar 13, 2014 at 4:44 PM, Yousong Zhou <yszhou4t...@gmail.com>wrote: >> >>> Hi, >>> >>> On 13 March 2014 16:11, Wandy Lau <xdragon...@gmail.com> wrote: >>> > These files are parsed by shell scripts or some thing else? I really >>> can't >>> > figure it out. Please give me some idea about this. >>> > >>> >>> UCI is really a pearl in OpenWrt. I was surprised by the design and >>> implementation when trying to understand the details. >>> >>> Basically, identifiers like "config", "option" are defined as shell >>> functions, so uci config files can be evaled by the shell when they >>> are parsed, kind of self interpretation. IIRC, you can find the >>> details in /lib/functions.sh, /lib/config/uci.sh. There are a lot of >>> eval statements there, so be warned. :) >>> >>> >>> yousong >>> _______________________________________________ >>> openwrt-devel mailing list >>> openwrt-devel@lists.openwrt.org >>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >>> >> >> >> >> -- >> This is my life,but world of us~~ >> >> _______________________________________________ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> >> > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > -- This is my life,but world of us~~
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
