892
edits
Difference between revisions of "Mesh/Firmware/Generating"
Jump to navigation
Jump to search
no edit summary
| Line 1: | Line 1: | ||
= freifunk = | |||
Freifunk has a web app called meshkit for generating images. | |||
*[http://meshkit.freifunk.net/ live web app] | |||
*[https://github.com/freifunk/meshkit source code] | |||
Meshkit takes a strange approach. From the readme file: | |||
<pre> | |||
Meshkit itself just writes a uci config file and stores it in | |||
/etc/config/meshkwizard in the resulting firmware image. The actual | |||
configuration is done by meshwizard, which uses community profiles | |||
and the settings from meshkit to configure the device at first boot after | |||
the device has been flashed. | |||
</pre> | |||
While I understand why community profiles would be a good idea, it seems odd that the configuration would happen on the device. Why not generate all of the required configuration before generating the image? That way you save a bit of space and an extra reboot of the device. | |||
= wlan slovenija = | = wlan slovenija = | ||