Re: [OpenWrt-Devel] Attitude Adjustment (r36608) Configuration config problems
On 05/15/2013 05:27 AM, Gui Iribarren wrote: On 05/15/2013 02:15 AM, cmsv wrote: I have encountered the following problems while compiling images: The reason being is for example that the network configuration file for a dlink is not fully the same as for example tp-link. Having any of these config files in buildroot dir/files/config/ will eventually brick routers that for example have a different switch configuration; will fail working properly for wireless and have functioning problems with system. These files exist in buildroot dir/package/base-files/files/etc/ and while building the image they get merged with the specifics of the hardware. My question is if we can have the same merging task done while having buildroot dir/files/ . Have you considered either...? a) use ./scripts/env to maintain a different set of /files for each model or b) use an /etc/uci-defaults/smart-template.sh : it can check the hardware model where it is running live, and apply the config based on that information I might that the ./scripts/env approach but right now there are other problems such as for example even using buildroot dir/package/base-files/files/etc/* still overwrites the network file and does not merge the wireless file into the new image. Some other files work as hey should such as the system config file which merges the date in it as it should during compilation. Hope that helps ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel 0x782BF73E.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Attitude Adjustment (r36608) Configuration config problems
On 05/15/2013 02:15 AM, cmsv wrote: I have encountered the following problems while compiling images: The reason being is for example that the network configuration file for a dlink is not fully the same as for example tp-link. Having any of these config files in buildroot dir/files/config/ will eventually brick routers that for example have a different switch configuration; will fail working properly for wireless and have functioning problems with system. These files exist in buildroot dir/package/base-files/files/etc/ and while building the image they get merged with the specifics of the hardware. My question is if we can have the same merging task done while having buildroot dir/files/ . Have you considered either...? a) use ./scripts/env to mantain a different set of /files for each model or b) use an /etc/uci-defaults/smart-template.sh : it can check the hardware model where it is running live, and apply the config based on that information Hope that helps ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Attitude Adjustment (r36608) Configuration config problems
I have encountered the following problems while compiling images: After make kernel menuconfig i was i not able to fully revert the changes with svn revert -R target/linux/ and even tho svn diff target/linux/ does not output anything some previous selected options still persist when doing make menuconfig and i am unable to revert them even after doing make defconfig. Only make distclean solved the issue When adding my own templates to the final image and placing them inside buildroot dir/files/ the only ones the image ends up by being compiled with, are buildroot dir/files/bin. All the other files in buildroot dir/files/etc and so on do not get added. I thought it had to do with file permissions but they are the same as the ones i have with an older buildroot. All files have the shell user's permissions. I also have a question regarding the use of custom templates. By trial and error i noticed that i cannot use the following configuration files for all my images - wireless - network - system The reason being is for example that the network configuration file for a dlink is not fully the same as for example tp-link. Having any of these config files in buildroot dir/files/config/ will eventually brick routers that for example have a different switch configuration; will fail working properly for wireless and have functioning problems with system. These files exist in buildroot dir/package/base-files/files/etc/ and while building the image they get merged with the specifics of the hardware. My question is if we can have the same merging task done while having buildroot dir/files/ . For example; having the network file in buildroot dir/files/config/network with all the settings we need which then will be merged with the switch specifics of the hardware that it is being compiled for. -- Site: http://wirelesspt.net Mesh: http://tinyurl.com/wirelesspt Admin: http://wirelesspt.net/wiki/Cmsv Twitter: http://twitter.com/wirelesspt Suporte técnico via sms: 91 19 11 798 Donativos/Paypal: http://tinyurl.com/doar-verba Chave publica PGP/SSH: http://wirelesspt.net/arquivos/pk Email assinado digitalmente pelo emissor assegurando autenticidade 0x782BF73E.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
