Hi Ben
On Tue, Feb 01, 2022 at 12:29:08AM +0100, Ben Hutchings wrote:
> On Thu, 2021-11-11 at 11:47 +0100, Bastian Blank wrote:
> > - A lot of bootloaders require special filesystems or other settings.
> > Now this more and more clashs with dpkg, as dpkg can't write data on
> > those filesyste
Likely not important for the broader discussion, but a small note which may
help with the solution space.
On Tuesday, 1 February 2022 00:29:08 CET Ben Hutchings wrote:
> I'm not sure how common it is to make the EFI boot partition be /boot.
I make images for my Pine64 Rock64 which has its EFI pa
Bastian, thanks for pinging me about your message that I missed in
November.
On Thu, 2021-11-11 at 11:47 +0100, Bastian Blank wrote:
> Hi folks
>
> I'd like to propose some pretty drastic reshaping of the way kernels,
> initrd and bootloaders interact with each other and with dpkg.
>
> Tradition
Hi folks
I'd like to propose some pretty drastic reshaping of the way kernels,
initrd and bootloaders interact with each other and with dpkg.
Traditionaly we install kernel images and configs into /boot. During
installation we generate files in /boot (and housekeeping in /var/lib).
Setup symlink
4 matches
Mail list logo
