-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian J. Murrell wrote: | On Wed, 2009-01-21 at 08:51 +0100, Markus Wigge wrote: |> Hello, | | Hi, | |> Have you ever tried "sysupgrade"? | | No. | |> A nice little tool to save your |> config, | | And how does it know where all of the various config is? Are you sure | it's not missing any, now or in the future?
It has a builtin list of important configs like /etc/opkg.conf, /etc/dropbear etc. It also backups the whole /etc/config/ directory which contains 100% of the uci config. | |> flash a new image and restore the config? | | So, I've flashed my new image. Now what? Do I have to connect to the | router using it's factory (or OpenWRT) default IP address? No, since the old network config is restored, you connect to the ip it previously had. | So now I | have to reconfigure other equipment to get back into the router after I | reflash it? See above. | And now I have to go through some kind of "configuration | restore" process? No. | This is _exactly_ the kind of rigmarole I am talking | about. Solved for the platforms which support sysupgrade which are currently the ones that have a unified image format (kernel + rootfs). | With the router's stock firmware, or OpenWRT's WhiteRussian, | this is not necessary. Only if all firmwares agree on the same meaning for the same nvram variables. Minor stuff like wl0_txpwr in dbm for the one and qdbm for the other firmware is what makes this a big mess. Also it's impossible to distinguish between factory, bootloader and custom variables. | You just reflash and when it comes back it's | ready to go. Dito for sysupgrade. | Anyway, this particular annoyance in the whole upgrade thing was a minor | point. | ~ JoW -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJd0GbdputYINPTPMRArHXAKCme0IbW3N6uGFtv4Jcvqe9Qdd7GQCgkR9n 1LNZ9nLLemk+x03HkSQ1jo4= =BsZx -----END PGP SIGNATURE----- _______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
