On Thu, Aug 25, 2016 at 07:40:56AM +0200, Zoltan HERPAI wrote: > Daniel Golle wrote: > > On Wed, Aug 24, 2016 at 11:28:40PM +0200, Zoltan HERPAI wrote: > > > Ralph Sennhauser wrote: > > > > I use kmod-ubi for creating a block device from the squasfs using module > > > > parameters as there is no busybox ubiblock applet yet. If ubi is made > > > > available as module so obvioulsy should ubifs. > > > > > > > > This completes the addition of kmod-fs-squashfs in commit > > > > 5163389b9c3b302a0d53df9a70294da5cbc08ada > > > > > > > > -- > > > > V2: kmod-ubifs -> kmod-fs-ubifs in commit message > > > Hi Ralph, > > > > > > With this configuration, these packages will try to get built on targets > > > where UBI support is not available, and failing those builds due to the > > > missing UBI config symbols. Can you try to make these packages depend on > > > the > > > ubifs feature ? > > > > Well, I reckon on most if not all targets with 'ubifs' feature set, UBI and > > UBIFS is built-in the kernel anyway... > True - there still are a couple config variables need to be taken care of. Are you planning to switch to initramfs and then load the ubi and ubifs modules in order to get a persistent rootfs?! Remember that otherwise, these modules are needed to be built-in to the kernel in order to mount the rootfs during boot.
> > -w- > _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
