Hi! Generally, instead of having many duplicates of ubinize.cfg for each board and/or filesystem setup, imho it'd be better to mirgrate platforms to use scripts/ubinize-image.sh introduced by https://dev.openwrt.org/changeset/41121
This would allow nuking all ubinize*.cfg files, thus reducing unnecessary redundancy and making ubinize'd image generation more maintainable. I don't have any lantiq, kirkwood, octeon, ... boards for testing, however, migration should be straight forward and I'm happy to help if needed. see https://gitorious.org/openwrt-oxnas/openwrt-oxnas/source/target/linux/oxnas/image/Makefile for my current use of SysupgradeNAND and ubinize-image.sh (which should maybe also become a make target similar to SysupgradeNAND). Cheers Daniel On 06/22/2014 01:25 PM, Ben Mulvihill wrote: > Setting this flag allows rootfs_data to expand on first boot > to fill remaining free space on nand. > > Signed-off-by: Ben Mulvihill <ben.mulvih...@gmail.com> > --- > --- a/target/linux/lantiq/image/ubinize-overlay.cfg 2014-06-22 > 13:06:07.165906341 +0200 > +++ b/target/linux/lantiq/image/ubinize-overlay.cfg 2014-06-22 > 13:06:26.754362400 +0200 > @@ -19,3 +19,5 @@ vol_type=dynamic > # Volume name > vol_name=rootfs_data > vol_size=1MiB > +# Autoresize volume at first mount > +vol_flags=autoresize > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
