4 ms·
The solution to this problem is either dead simple, or impossible (depending on your specific field of work, I guess): You do not buy or deploy hardware that do
by c0l0 6y ago
The solution to this problem is either dead simple, or impossible (depending on your specific field of work, I guess): You do not buy or deploy hardware that doesn't have mainline support at the time of your specific Debian release's kernel version (or its backports variant, if need be).
$prevjobcompany lives by that unwritten rule for more than two very profitable decades by now, and I recommend anyone considering operating a Linux-based OS to adopt it.
- zinekeller 6y ago> You do not buy or deploy hardware that doesn't have mainline support at the time of your specific Debian release's kernel version (or its backports variant, if need be). There are glacial changes, but scientific instruments are often still shy on Debian or even Ubuntu :(
- bgorman 6y agoDo you have the source for these drivers? It probably isn’t too difficult to make them compile for a slightly different kernel
- zinekeller 6y agoHah, I wish! If it has a source, then it will probably already be on mainline and the issue will be moot. These are at least a bit free-er than some other instruments which rely on Windows (and maybe not even 10 or 64-bit at that).
- pabs3 6y agoIf these are Linux kernel drivers then it sounds a bit like they might be GPL violations?