I was wondering how possible it were to have an update feature without having to reflash? I thought openwrt had it, so would it just be a matter of typing the correct command into the terminal?
I mean, a lot of the changes are to the shell scripts, right? Shouldn't it be possible to just wget updates or something? I suppose an option is to check out the code from svn and copy them over manually though. I just thought it might allow people to be testing on the latest version a lot easier without having to worry about reflashing so that the data/bug reports would be more consistent
OpenWrt does have a new "sysupgrade" feature, that does re-flash, but saves the configuration files in RAM, and then copies them back. So the router does get re-flashed, but the configuration files are preserved.
I could certainly implement something similar but I'm hesitant to do that, at least now, because some of the configuration files are changing between releases too! I realize that's not really good... it prevents backwards compatibility, but Gargoyle is still in beta, and some changes are to be expected. When it reaches 1.0 (oficial) I may make a change such as this to facilitate upgrading.
Fair enough, though, to be honest, I would argue that it is just as important if not more so, since allowing upgrades without a reflash would encourage more users to upgrade more frequently, giving you better bug reports
Eric wrote:OpenWrt does have a new "sysupgrade" feature, that does re-flash, but saves the configuration files in RAM, and then copies them back. So the router does get re-flashed, but the configuration files are preserved.
I could certainly implement something similar ...
Wouldn't it be more flexible to be able to upload and download the configuration file/s manually rather than have it happen automatically?
I'm thinking of something similar to the facility CoovaAP uses for configuration management: http://www.coova.org/node/229