-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 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".

Yes. For squashfs + jffs based systems you could also investigate the contents 
of /jffs,
which contains only files that where modified compared to the initial rom file 
system.

> Yes.  That one seems quite obvious.  Unfortunately, not all packages are
> uci driven [yet].

Right, maybe the approach above is a solution for this.

> So sysupgrade also takes care to restore the saved config,
> automatically?  Does it do this on reboot?

It builds a temporary ramdisk, chroots to it, flashes the image from there and
reinitalizes the jffs2 partition from within the yet running system.

> 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.

It works pretty well now.

> So how do I know which ones specifically that is?

Basically all platforms that utilize squashfs + jffs2 in only one single image 
file for
flashing. Examples for that are bcm47xx, bcm63xx, x86 (not for ext2) and 
others. One
platform that does not work is the Atheros port for Fonera and Ubiquity devices 
as the
kernel and rootfs images are separate there.

> Well, this is good news then.  Maybe time to look at that again.

Yes, I'd suggest to try it out. If it supports your platform then it might be a 
suitable
solution for you.

> Thanx for the clarification.

You're welcome.


~ JoW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkl3Ru0ACgkQdputYINPTPNK0ACeOSTnTogwpiADarRWR06p9dLX
exgAnikR2KcwgSnw8RC466LxY9fTdR4N
=Rn3e
-----END PGP SIGNATURE-----
_______________________________________________
openwrt-devel mailing list
[email protected]
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to