If someone tests it without any kernel modules paths (/lib/modules
empty), and with a kernel(not needing an initrd in /boot as well),
apt-get install kernel will fail
I can understand why nobody wants to verify anything here because it
takes time to compile a kernel without "initrd" nor any /lib/modules,
and then boot up with it to see if this error occurs. I doubt anyone
here is using this type of custom kernel with these conditions otherwise
they'd notice the same.
fwiw, the "workaround" output from message 5(first) message is actually
completely a coincidence of wording from program output. the actual
workaround I took can be found in message 12 and 17.
The reason why I said "is a bug or not", is testifying if this is a
"policy" just as the name of the file edited for working around this is
/etc/initramfs-tools/conf.d/driver-policy
There's not much else to this report. If you want me to confirm anything
you'll just have to apply the same condition tests.
1) no /lib/modules << have this directory EMPTY
2) /boot/<kernel> << one kernel nothing else (no initrd)
3) Boot this kernel, and try installing a kernel from the debian repos
using initramfs 0.116
It'll fail, but that workaround works well to getting a kernel
installed. Not rocket science once the same conditions are applied and
should be immediately noticeable once you run a simple apt-get. The only
thing non-debian on this system is that custom kernel which is booted from.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54274ea6.1020...@videotron.ca
