Hi, Quoting Diederik de Haas (2024-10-19 21:08:37) > > All existing arm* recipes always created a separated ext2 /boot partition, > > so I kept it in the new arm64 recipes. If this is not needed, the arm64 > > recipes can be changed so that they create a separate /boot partition only > > when partitioning with LVM, just like recipes for other architectures. > > I never create a separate /boot partition, which has several advantages > IMO. But the ARM ecosystem is ... let's say ... diverse. > So I don't know if other systems would/could need a separate /boot partition. > But Rockchip devices don't need it.
just some thoughts on the topic of having a separate /boot partition. For the MNT Reform system images we use a separate `/boot` partition by default because: - support encrypted rootfs (luks) - allow bit-by-bit identical rootfs for all supported boards (`/boot` differs because /boot/dtb and /boot/dtb-$(uname -r) symlink contents differ) - kernel, initrd and dtb being at the root of the partition allows for simply mounting it on /boot from another system -- with everything in a single partition, one'd get /boot/boot Thanks! cheers, josch P.S.: eagerly awaiting my own rk3588 to arrive
signature.asc
Description: signature
