Brian Masinick
@andyprough that’s some good information about memory utilization that systemd-journald uses.
Do you also have expertise on the methods that Debian uses with the boot loader?
As we know, the majority of distributions use the GRUB boot loader, but there’s a LOT of
latitude in the way that it’s used.
When I have antiX 23.2 in control of the primary EFI/UEFI aspects of the boot loader,
I’ve been able to use a fairly small 100 MB boot partition.
When I tested out Debian as they approached the release, I found it attempted to put ALL
of it’s boot loader contents within the /boot/efi filesystem, and as a result, it required
several hundred MB. Needless to say, I didn’t keep it, though I’m tempted to increase
the boot partition size the next time I reorganize my system.
Anyway, do you have any specific insight into why the Debian approach wants SO MUCH more –
nearly five times as much – boot partition resources – as antiX 23.2 needs?
I’m certain that it involves a LOT more of their boot related content being placed directly
in that partition; what I don’t know is whether their configuration has some flexibility in
changing that, or if it has to be entirely re-engineered and reconfigured, as we clearly do
in our very efficient implementation of antiX.
I’m sure if I did a deep dive I could eventually find the answer. I don’t expect you or anyone
to go out and do the research; if you happen to already know the details as you did concerning
the memory utilization that systemd-journald uses, that specific knowledge would be much appreciated.
Otherwise, I’ll by default simply keep antiX managing my boot loader, and if time, fortunate choices
in my reading and research, or stumbling across the answer, or a light bulb illuminating my mind suddenly
emerge, I’ll have that “a ha” moment!
--
Brian Masinick
Alternate "Search B":
This search page