On Sat, Jan 02, 2016 at 04:02:58PM +0100, Felix Fietkau wrote: > On 2016-01-02 15:11, RhoYounJae wrote: > > Currently, the devices which actually uses ubifs filesystem uses squashfs > > filesystem > > Thus openwrt binary image have a wrong squashfs- prefix not ubifs- which > > gives user confusion > > This patch add ubifs filesystem for image building system but not for > > legacy system > You're right about one thing: These images do use ubifs, however only as > an overlay. The base filesystem is squashfs, just like on all those NOR > flash based devices (which use jffs2 as overlay). > > I might accept a patch that adds ubifs as an option, if you can convince > me that it's actually useful, but replacing the squashfs images with > ubifs ones is not an option.
Similar to having a JFFS2 read-write-mounted rootfs without any overlay can make sense in certain (rare) scenaria. I intended to use a ubifs rootfs in those situations on devices which need UBI. There already is a way to generate images having ubifs rootfs, see e.g. https://dev.openwrt.org/browser/trunk/target/linux/oxnas/image/Makefile#L90 UBI and UBIFS image generation is still kind of a mess because not all targets have been migrated to the 'new way' (using SysupgradeNAND and UbinizeImage) yet. Once this is done, include/image.mk can be cleaned up and the old stuff (still needed on targets relying on a static ubinize.cfg) can be removed... Cheers Daniel _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
