News for hackers. Stuff that matters.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by ada-h00k on Monday November 16, 2026 @05:36AM (#50516099)
Can't you just put that in a container with an old version of Java?
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by burnt-resistor on Monday November 16, 2026 @05:59AM (#50516231)
Containers !~= VMs (except Kata Containers and similar). VMs ensure specific, isolated, supported compatible kernel versions in controlled environments because what's supported isn't the same as what's technically possible.

Containers seem lightweight and magical until the tyranny of the quirks of the kernel matters with some gotchas of supported configurations as opposed to unsupported gremlins running custom stuff that other vendors refuse to touch.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by natebc on Monday November 16, 2026 @06:28AM (#50516381)
sometimes, sure but

> "lose the ability for commercial support / you're on your own if shit happens"

is not something you can clever your way into. It's the vendors choice what support characteristics look like.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by pjmlp on Monday November 16, 2026 @06:44AM (#50516518)
Older Java versions aren't container aware, thus it might not run as expected, depending on which version it is.
Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by roryirvine on Monday November 16, 2026 @08:23AM (#50517360)
If you really need a JRE from before they became container aware by default then you're in luck!

Both bookworm and trixie contain the obsolete OpenJDK v8 JRE for both amd64 and ppc64el as it's needed for nvidia-visual-profiler.

Re:Debian Becomes Unresponsive after 6.1.0-55 Kernel Update by pjmlp on Monday November 16, 2026 @09:22AM (#50517882)
Thankfully I have long moved away from Java 8.