MX Linux Forum

Not sure what more you need for confirmation.. that catalog ARE exploited issues.
Actually, I found the website so painful to use as to be worthless. With no assurance it would be topical, as the point under discussion was kernel exploits, not exploits generally. What I spent some time searching ...

The stupid and potential loss of time and energy for almost nothing.
The primary function of the kernel is the interface between operating system and hardware. Testing how well it does that job isn't nothing. It's already been explained that's why Debian takes longer to turn around kernel updates ...

Probably just a glitch. Might be a failing drive. Perhaps gremlins. Make sure your backups are current. Don't worry much, unless and until something similar happens again.

... summarize the problem
What problem? I've never heard of a malware attack in the real world coming in through a Linux kernel vulnerability, not even a zero day never mind a patch in the works. Have you?

Anyhoo, if you don't like the Debian kernel update schedule, use something else. The ...

When I started using Linux, I would read change logs for kernel updates, mainly to get a sense of what zero day vulnerabilities might look like. Was a bit amused to discover how low the bar for what counts as a "security update" (e.g., someone with physical access might be able to stop a process ...

Not what you asked for, but the best solution (imho) would be to buy a USB hard drive, copy the flash drives to it, and have everything in one place. Actually, buy two drives, so you can back up one to the other.

What a bunch of FUD. Anyhoo, 0x6A7232 , consistent with your comment in the other thread, if you want to use systemd, there's a lot to be said for running a distro which supports it. Debian is very good, provided you're comfortable with CLI for system management. If you want GUI system apps, take a ...

This probably belongs in chat rather than support. FWIW, I've always found persuasive a comment I read years ago, the first time I ran into the issue. It's a computer, not a religion. Use whichever option works best for you.

Glad you found a solution, well done.

For the benefit of others, there were several ways this could have been done. Charlie Brown's suggestion was one of them. Switching the system to UEFI, as the OP has done, is another. For the latter, it wasn't necessary to reinstall the system. Would have been ...

The EFI partition is useless in legacy mode and much too small anyway. My advice would be to replace that with a BIOS boot partition - the name for the thing Charlie describes - rather than try to shoe horn it in somewhere else. If you go this route, be sure to edit /etc/fstab to remove or comment ...