Hi, On Sun Oct 20, 2024 at 2:24 AM CEST, Johannes Schauer Marin Rodrigues wrote: > Quoting Diederik de Haas (2024-10-19 21:08:37) > > 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 IIRC having a separate `/boot` means that the dtb files need to be copied over (via a kernel hook?), while that isn't needed when there is no separate `/boot`. But I haven't had much time to fully work those parts out; my image creation project hasn't seen any activity for 6 months now. Maybe during the Forky cycle? > P.S.: eagerly awaiting my own rk3588 to arrive I (still) don't have an rk3588 device, but I did recently receive a PineNote \o/ and I'm *really* excited about that :-D Hopefully in Forky with full upstream and Debian support for it :) Cheers, Diederik
Attachment:
signature.asc
Description: PGP signature