Actual Linux news rather than “which distro should I use for gaming and bit torrents?”

Sometimes you gotta let people try to resolve things on their own first.

Sounds like something is broken.

As someone who has seen almost EVERY kernel bugfix and security issue for the past 15+ years (well hopefully all of them end up in the stable trees, we do miss some at times when maintainers/developers forget to mark them as bugfixes), and who sees EVERY kernel CVE issued, I think I can speak on this topic.

The majority of bugs (quantity, not quality/severity) we have are due to the stupid little corner cases in C that are totally gone in Rust. Things like simple overwrites of memory (not that rust can catch all of these by far), error path cleanups, forgetting to check error values, and use-after-free mistakes. That’s why I’m wanting to see Rust get into the kernel, these types of issues just go away, allowing developers and maintainers more time to focus on the REAL bugs that happen (i.e. logic issues, race conditions, etc.)

I assume you’ve configured it for “single” mode?

Making C go away will require major rewrites of projects that have millions upon millions of hours of development.

Yep. And it’ll be done. Yes it’ll take a while, but this is what it means for C to be like COBOL (which also still exists). But the more and more it can be marginalized the better we’ll all be security-wise.

The rewrite-it-in-rust gang arrives in 3, 2 …

Cattle not pets. They’re just computer languages.

It’s mostly about memory access. Modern languages throw errors if, for example, you try to reference an element of an array that is “outside the bounds” of the array. C does not - it gladly returns whatever memory address is past the end of the array. So the programmer has to check that the index is 0 <= x < array_size whenever they access a an array entry. That’s a pain - so they don’t.

Don’t be shitty.

You need the same source code, the same exact build tools, the same exact libraries that it depends on, and the same exact OS. Additionally every single build has to be reproducible - so not including in its output, say, the build date/time or any information about the host that built it. Now you need to repeat that for thousands of packages.

I believe it’s less about the packaging system and more about the build system. You’re building source code from thousands of individual projects, getting a reproducible output is difficult if, for example, some library embeds the build date/time in its output.

Oof, awk…

I consider myself to be very cli proficient, but I’ve never understood awk.

Teams is its own plane of hell. Sorry to hear.

Let’s be honest - in this community NAS means “my do-everything server that may have a RAID and probably also shares storage”.

All my systems are backed up with “rsnapshot” to a file server. File server is backed up to backblaze with duplicacy.

🤣

I have a cron job set to run on Monday and Friday nights, is this too frequent?

Only you can answer that - what is your risk tolerance for data loss?

You’re not going to run deepseek r1 without GPUs (plural).

I’m also considering UnRaid instead of Proxmox for a NAS OS.

NAS just has no meaning anymore?

If they’re not having problems then why investigate?

This is excellent advice. Bash is fantastic but it has a lot of “foot guns” that can cause problems. Especially where spaces are concerned…

Op: good job with the script

Not really. Doesn’t sound like they are having any problems.