1. Forum
  2. Usenet
  3. LINUX.DEBIAN.KERNEL

  • Not installing files to /boot

    From =?iso-8859-1?Q?J=F6rg?= Behrmann@21:1/5 to All on Mon Sep 5 11:00:01 2022
    Dear Debian kernel maintainers,

    people wanting to give systemd-boot a try cannot currently follow the upstream recommended setup [1] that mounts a FAT-formatted partition (either the XBOOTLDR
    partition from the spec or ESP [2]) to /boot/, since dpkg requires a lot of things from the underlying filesystem that FAT does not support [3].

    This could be worked around by shipping the files that are currently installed to /boot/ to /usr/lib/ instead, e.g. /usr/lib/modules/$KERNEL_VERSION/ as Arch and Fedora do, and if necessary copy the files into /boot/ in a postinst script and remove them likewise, as Fedora does.

    I know this is probably too late in the cycle for bookworm, but I wanted to get a discussion on this started in time for trixie.

    best regards,
    Jörg Behrmann

    [1] https://systemd.io/BOOT_LOADER_SPECIFICATION/
    Talking with upstream the preference would be having two partitions,
    XBOOTLDR mounted to /boot/ and the ESP mounted to /efi/, which would allow
    for either to be automounted, since neither systemd's automount logic nor
    autofs' one allows for nested automounts.
    [2] It is clear that the ESP needs to be FAT-partitioned. Why then use it for
    yet another partition? Reading FAT comes free with the EFI firmware, so
    putting boot-related things on FAT partitions frees one from implementing
    reading "real" filesystems, no matter what partition setup one uses.
    [3] https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_What_are_the_filesystem_requirements_by_dpkg.3F

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEEW8ff2Z3ec8g+9IMxPFdy1xdIMhgFAmMVuSQACgkQPFdy1xdI Mhhs7RAAr3YIZ9RU/6LWn6Ni47sYHzHC3yBGWFXOpxhenf/NPUwKlXUxda51WSV+ 0JOYFfJN2TokElRxzQ/W45LrbugTOIafQVbrUMEasWDD7Owpt/lolejOYaz2j/gY VZCnEjFpTcXhaa5Wqu/M0t/q2gmxJGAHYTYr76BlLYEuyIhXc1W9PE4S394TyxAF GztssMuZhP/9hKJzbTkK31GVkofB04TNE54bR3cfG/BpZIbDCShqMd/Ht8upcOAW VscVFH3rL1OgafBpMJYuUkgzI8pWc3pemt5ghorXt5nKmgSsUbPQJF2Sxa3hvwRv NAuyZl6608VcsYpqmcgDDIj32AmKnh6YqisAyUbiqXY53Sa1mfuIJ43K4RwdSXVx 5otTtCHErwRjqFgNQT3qiqb7ndAneBVHbfNW6k8DbBHKpR0b4yBtX30LTQnMKgem UpUkpw3Bm2PzY1g8fRtywoBYKDTLoVvm9RjhlCrHZqkc85DG5NhfLdxh76S5YAfT CDTTeeEYjZ9E5MW+MrsIdyQIBTCwqaSW/A5sQ34zAaZR71nWX/UqixmN+QM7+UVq yd75j1cWkWi8EMIIJlpwwa6VMMzltbOSV/s3jZtKUssR2QYLTeCwqns+Jaxs12lU ZQLJGHG5zH2ZNccWb3zURmr/gLliejjpdvDmU4MowSWF+bfchmg=
    =6qAT
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Luca Boccassi@21:1/5 to All on Mon Sep 5 12:20:01 2022
    Dear Debian kernel maintainers,

    people wanting to give systemd-boot a try cannot currently follow the upstream
    recommended setup [1] that mounts a FAT-formatted partition (either
    the XBOOTLDR
    partition from the spec or ESP [2]) to /boot/, since dpkg requires a
    lot of
    things from the underlying filesystem that FAT does not support [3].

    This could be worked around by shipping the files that are currently installed
    to /boot/ to /usr/lib/ instead, e.g.
    /usr/lib/modules/$KERNEL_VERSION/ as Arch
    and Fedora do, and if necessary copy the files into /boot/ in a
    postinst script
    and remove them likewise, as Fedora does.

    I know this is probably too late in the cycle for bookworm, but I
    wanted to get
    a discussion on this started in time for trixie.

    One additional advantage of this would be moving further toward the
    direction of having packages/distro artifacts shipping only files under
    /usr and the rest being determined locally at install/image build time.

    --
    Kind regards,
    Luca Boccassi

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEErCSqx93EIPGOymuRKGv37813JB4FAmMVy/4ACgkQKGv37813 JB4IMw//Up2VqtUbtA/gpgAZwTvcUN1VCVqIPPPpzp2UEPDK60atOC6Gg0Bk+k2N p39TP33Gb814rlnFKVCC8ih5zMfsTOSDEOgYWe8gT4ui0xw5BbMyVssGwvNclw9L Ne0FQZE++oJ9CT1wGMfTeq38mgiPuzPWPz/jWbEG7AhcYdJueVc6nITF01kPeSI1 zGKTd7ZQxkdGT9XGsHaoFw3D5AdRVECbJyPmc3YV0ftaaQzJAqzVRKW2FEQNE5pG cqNl8pKH6br8L0q6kjZJKOXruWzEWW0/tRvJzVm5xRkaDss9ryM2ybRTSGZLPQMj KWrDzF9CTb22SQrwcGdL61fjKMNLO3uKhmG+eCDRouPzwA9/vGgeRJigtlqlOxpM wgYccEc/GTGo7WIqVq1sYuMG6RcvQLb6o9orjbM4HEdTO0cMH6TmQsTQZe0LZC3W QhklNj+NyXhevSjgpI6k2r9/9g5P08oOwoVoEJl9IrlxAR6ghhuVZ0K/WOvCjpkk Qkgavq25aQNtjYm9U90Zr6AmTbRb8z9uZAqkMrg6tVKG8homk5vnjXuJPO09BRa7 Xzlg2zaquDrIU6NilBd50idoRS2VJOqt63JCrKPCOKvbhoYWpU4/n8+e2TY2kSQd 8N3WC+/EcEDt3+diIJKiOmlZ5Gb981TPSKfLDq/cFcSsrKnlRiI=
    =yIeV
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)