Re: RFC: move kernels out of /boot

[CtrlC-Root <CtrlC-Root@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]

New comment by CtrlC-Root on void-packages repository

https://github.com/void-linux/void-packages/issues/48024#issuecomment-1938812385

Comment:
I think this would be valuable especially if there is an easy way to make local changes to or extend the hooks in order to implement custom behavior.

Background context:

I have been attempting to use Void Linux on embedded systems with fairly limited disk space. These systems typically have a separate `/boot` partition and one challenge I've run into has been sizing it appropriately; if it's too large you end up wasting precious space but if it's too small you risk breaking system updates (or requiring manual intervention). This is made more complicated by the fact that it's difficult to predict the size of generated initramfs images ahead of time (since they occasionally increase). Right now I have solved this with a script that wraps `xbps-install` and makes sure you end up with the right things in `/boot` (it's not 100% full and it has files necessary to boot) after it's done running. I have seen the warnings printed during `xbps-install` that mention the system may not be bootable due to low disk space in `/boot` but (1) assuming I've sized it appropriately it should be mostly full all of the time and (2) I know what the right thing to do is in my situation and I'd like to have it done automatically so I can run `xbps-install` unattended.