[OpenWrt-Devel] [PATCH] config/Config-images.in: Fix wrong handling of ROOTFS_INCLUDE default options

Jan Čermák jan.cermak at nic.cz
Thu Nov 19 03:48:30 EST 2015


Hello,

currently I think the best option for us is an ext4fs image with /boot in the
same partition, no squashfs+jfss2 or separated /boot partition. I saw that a few
targets are making ext4fs image, but is any of them following the current best
practices?

Cheers,
Jan

On 11.11.2015 17:31, Felix Fietkau wrote:
> On 2015-11-11 16:04, Jan Čermák wrote:
>> Hello Felix,
>>
>> On 11.11.2015 15:00, Felix Fietkau wrote:
>>> This option is apparently supported for ext4 and ubifs only. Also, the
>>> code enabled by these options is one big design flaw, and I'd like to
>>> get rid of it as soon as possible by converting all devices that need it
>>> over to the new image building code.
>>
>> because I was planning to use these options for a new target, can you give me a
>> hint what's now the correct way to create an image of ext4 FS with kernel
>> included within it?
> Do you need to keep the kernel in the same filesystem as the rest of the
> system, or can you make a small kernel partition and use the normal
> squashfs+jffs2 overlay, or does it use something else?
> 
> - Felix
> 
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


More information about the openwrt-devel mailing list