On Wed, 2009-01-21 at 16:39 +0100, Jo-Philipp Wich wrote: > > It has a builtin list of important configs like /etc/opkg.conf, /etc/dropbear > etc.
Right. But that's a list that will continually need updating as new packages are brought in. As I said in a previous message, having package maintainers identify config files within their packaging is still error-prone but probably less so than them having to know/remember to upgrade the "sysupgrade list". > It also > backups the whole /etc/config/ directory which contains 100% of the uci > config. Yes. That one seems quite obvious. Unfortunately, not all packages are uci driven [yet]. > No, since the old network config is restored, you connect to the ip it > previously had. So sysupgrade also takes care to restore the saved config, automatically? Does it do this on reboot? I might have to go investigate this sysupgrade more closely. I think the last time I looked at it though it didn't support much outside of x86 based systems though. > Solved for the platforms which support sysupgrade which are currently the > ones that have a > unified image format (kernel + rootfs). So how do I know which ones specifically that is? > Only if all firmwares agree on the same meaning for the same nvram variables. Yes, absolutely. They all should though, where there is common functionality. > Dito for sysupgrade. Well, this is good news then. Maybe time to look at that again. Thanx for the clarification. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
