On 26.10.21 17:48, Larry Finger wrote:
On 10/26/21 05:24, Bernhard Held wrote:
On 26.10.21 at 07:31, Andrei Borzenkov wrote:
On 26.10.2021 06:14, Bernhard M. Wiedemann wrote:
On 26/10/2021 02.54, Larry Finger wrote:
With a recent Tumbleweed snapshot (probably 20211023), the utility installkernel was removed from /usr/sbin. Without this code, a kernel 'make install' returns "Cannot find LILO.".
Honestly, I don't get the point of the commit message:
Nowadays, /sbin/installkernel is only used by developers who compile their own kernels on the target system.
Are developers compiling their own kernels no longer welcome or no longer supported? Obviously, a couple of tumbleweed users ("only developers") will now have to dig out the script from github or an old rpm (like I did).
Wouldn't it be possible to keep the source file "dracut-installkernel" e.g. in /usr/lib/dracut/ as a template? Or put it in a devel package, as I understand that development files don't necessarily have to come with the dracut main package.
File "installkernel" does not have to be part of dracut.
You are right here, having it in some separate package (either a sub-package of dracut or elsewhere). Yet the question here for me is: Is the script connected to some high-maintanance burden? If not, i do not see a real reason why this can not stay within dracut. Looking into the git repo for opensuse dracut - https://github.com/openSUSE/dracut.git, the file "dracut-installkernel" was created 2018-04-20 and one line was changed in 2020-02-18.
Putting it in the kernel-devel package would make a lot of sense as you need that one to build your own kernel. That utility is essential on my system.
This would actually make no sense to me, as building a non-opensuse, e.g. a upstream from git (kernel.org) does not require this package. Having a smaller package with only the installkernel around, would be preferable in my eyes.
When a new kernel merge starts, that is the time to start testing the KMP builds for VirtualBox. Some cycles, it requires a lot of time to figure out what API changes are coming so that VB is ready when Kernel_HEAD_standard releases kernel X.Y.0-rc1. Perhaps that is not necessary, but I take great pride in being ready. My experience is that Oracle cannot be trusted to have the necessary patches ready in time.
As was pointed out, installkernel must do real work. A dummy link would still result in the LILO not found message.
Larry
Greetings, Tobias