Open redtux opened 3 years ago
/proc/cmdline
is read-only file that shows cmdline of currently running kernel therefore it doesn't make sense to symlink it as /etc/kernel/cmdline
.
Alright, but the installer cannot expect a file that is not there, and then just fail instead of creating it. In case the format is the same it could just be copied from proc or extracted from grub, or just provide an example file with all options commented out.
I thin the better solution is to fallback to /proc/cmdline
in case /etc/kernel/cmdline
doesn't exist. In fact this is what manpage of kernel-install says:
/etc/kernel/cmdline /proc/cmdline
Read by 90-loaderentry.install. The content of the file /etc/kernel/cmdline specifies the kernel command line to use. If that file does not exist, /proc/cmdline is used.
I think it shouldn't be complicated to fix this.
As described in https://bugs.launchpad.net/ubuntu/+source/sicherboot/+bug/1883345 (and replied to by @julian-klode), there is a bug with the Ubuntu package, requiring the non-existent file
/etc/kernel/cmdline
. The installer needs to create the file (e.g. by creating a symlink to/proc/cmdline
- in case the format is the same), or it needs to depend on a package that creates this file.