[pve-devel] applied: [PATCH kernel-meta] boot-tool: fix whitespace in generated loader configuration
Thomas Lamprecht
t.lamprecht at proxmox.com
Thu Nov 11 11:20:56 CET 2021
On 10.11.21 14:07, Oguz Bektas wrote:
> issue reported in forum [0]
>
> seems like it came in with 2a8a4b5e37e87a0a994fe3820b015e051e6259fb
>
> [0]: https://forum.proxmox.com/threads/problem-with-proxmox-boot-tool.99043/
>
> before:
> ========
> $ cat /mnt/foo/loader/entries/proxmox-5.11.22-7-pve.conf
> title Proxmox Virtual Environment
> version 5.11.22-7-pve
> options root=ZFS=rpool/ROOT/pve-1 boot=zfs iommu=pt
> linux /EFI/proxmox/5.11.22-7-pve/vmlinuz-5.11.22-7-pve
> initrd /EFI/proxmox/5.11.22-7-pve/initrd.img-5.11.22-7-pve
>
> after:
> ========
> $ proxmox-boot-tool refresh
> $ cat /mnt/foo/loader/entries/proxmox-5.11.22-7-pve.conf
> title Proxmox Virtual Environment
> version 5.11.22-7-pve
> options root=ZFS=rpool/ROOT/pve-1 boot=zfs iommu=pt
> linux /EFI/proxmox/5.11.22-7-pve/vmlinuz-5.11.22-7-pve
> initrd /EFI/proxmox/5.11.22-7-pve/initrd.img-5.11.22-7-pve
>
> Signed-off-by: Oguz Bektas <o.bektas at proxmox.com>
> ---
> proxmox-boot/zz-proxmox-boot | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
applied, but reworked the commit message to clarify that this has no actual functional
impact (but still good to have to avoid confusion), thanks!
More information about the pve-devel
mailing list