https://packages.debian.org/source/stretch/linux
In Devuan we use the exact same kernel(s) as is used in Debian. Probably the rest of the kernels from the list too, but I know about mine.
This is my machine (I grep out 4.9.3 and 4.9.5, such as 4.9.39 and 4.9.51 --soon also 4.9.52-- because I have a few minipli grsecurity-hardened kernels, and the topic is Debian/Devuan kernels compatibility):
Code: Select all
# ls -l /boot/ | grep -vE '4.9.3|4.9.5'
total 195663
...
-rw-r--r-- 1 root root 190055 2017-01-06 20:17 config-4.4.0-59-generic
-rw-r--r-- 1 root root 186386 2017-06-26 15:27 config-4.9.0-3-amd64
drwxr-xr-x 2 root root 1024 2017-07-24 19:19 efi
drwxr-xr-x 6 root root 1024 2017-09-27 19:56 grub
-rw-r--r-- 1 root root 33548826 2017-09-13 12:33 initrd.img-4.4.0-59-generic
-rw-r--r-- 1 root root 19462711 2017-09-15 11:54 initrd.img-4.9.0-3-amd64
...
-rw------- 1 root root 3888958 2017-01-06 20:17 System.map-4.4.0-59-generic
-rw-r--r-- 1 root root 3180497 2017-06-26 15:27 System.map-4.9.0-3-amd64
-rw-r--r-- 1 root root 6969744 2017-01-30 17:03 vmlinuz-4.4.0-59-generic
-rw-r--r-- 1 root root 4204320 2017-06-26 15:27 vmlinuz-4.9.0-3-amd64
#
But 4.9.0.3 is the same kernel in Debian and in Devuan. And I base my 4.9.5x configs on that one, which is actually generic kernel, except that it is described, currently on that page linked above as:
Code: Select all
linux-image-4.9.0-3-amd64
Linux 4.9 for 64-bit PCs
linux-image-4.9.0-3-686-pae
Linux 4.9 for modern PCs
Just saying about clumsy naming . Because the 64-bit PCs on the market are small share AMD64, much greater share Intel (IIUC), and 686:
Code: Select all
linux-image-4.9.0-3-686-pae
Linux 4.9 for modern PCs
(I mean other than Udoo x86, which I'd never recommend to anybody, because I'd very strongly expect Intel owns it, not you, and owns you through it: it's closed source, black box hardware. IIUC.)
But on the question about compatibility, I'd believe Devuan and Debian kernels being same, even my packages should work fine on Debian/Ubuntu as well, and if you go the best way, which is compiling your own kernel and hardening it with the fresh unofficial-grsecurity patches, it can not be in any way incompatible in the, I believe, whole Debian family (but I am not familiar with many other of the Debian family distro-members)!
I also take all the precautions when I compile the packages. For that reason I put fat warnings if I have any marginal doubts of my systems.
I'm compiling, away from this online system, linux-4.9.52 with the new patch:
https://github.com/minipli/linux-unoffi ... cial_grsec
Just as in the script (also been updated, e.g. you could likely also simply just use:
https://github.com/miroR/grsec-dev1-com ... compile.sh
) I run the long, one thread only:
Code: Select all
fakeroot make deb-pkg
For compiling the next kernel the line is fine like this:
Code: Select all
$ grsec-dev1-compile.sh v4.9.52-unofficial_grsec-20170928143206 linux-4.9.52 config-4.9.51-unofficial+grsec170923-22
Regards!