

So now we’ve lost a very good developer, and the question of rust in the kernel remains unresolved. This is the worst possible outcome.
So now we’ve lost a very good developer, and the question of rust in the kernel remains unresolved. This is the worst possible outcome.
I’m not familiar with that program. How does it determine “throttling”?
I don’t personally use tape, but I get most of my stuff from eBay. Tape drives are surprising expensive, even LTO-6 is going to run you a few hundred. But you still can’t beat the density and longevity.
Tape. Amazon glacier if you’re okay with that.
And regular test restores. An untested backup is not a backup.
But when considering what I need to back up, I usually overestimate how much I or other people will care if it’s lost. Family photos are great, but what are the odds of someone saying “damn I wish we still had two dozen photos of that one barbecue?”
…but still fails to answer the question of “should we continue implementing kernel things in rust”.
Probably none. This is a MITM attack, so they need to be between you and the device. Usually that’s done by being on the local network, though it could also be someone who has compromised your router/firewall appliance.
Of course, you should never expose services like this to the Internet. If you need remote access, use a VPN.
Not all providers let you use your own domain.
Or Qemu if you want a similar interface.
Docker: ouroboros. Linux: unattended-upgrades or dnf-automatic. Windows: MECM.
I know those FOSS ones aren’t centralized, but I find it a lot easier for them to just update themselves as necessary.
I have automatic updates on everything. If it breaks, I fix it when I have time. If I don’t, it remains broken.
I could also just not do updates, but I like new features.
You might need to lower your expectations
Is it feasible to self host websites
yes
for small businesses
NOPE
Well, you say your business sites, so I assume you’re okay with downtime. I would absolutely not self-host sites for someone else’s business, because if something happens to the hosting (ISP outage, power outage, bad update, hardware failure, accidental deletion, misconfiguration, ISP block, flood/fire/storm, theft, I can go on) then it’s my ass on the line. Simple hosting is cheap, spend the few bucks for a lot more peace of mind.
Either this means you won’t get future updates, or future updates will still overwrite your change. The proper way to do this would be to mount your own config over the one in the container, though this may have negative effects if the container config changes in the future. You might be able to mount /dev/null over the log file if you don’t care about the logs at all.
I don’t believe there’s any way to specify modifications to someone else’s containers without making your own image, unfortunately.
Well this code would be maintained by developers who know rust, so it sounds like a good merge to me!
The name of the community should make that obvious.
Is rust more maintainable than C?
It’s okay to let things go when they’re not useful any more.
Or, turn it into art.
Access point?
You might be able to configure it as a DNS server with block lists like pihole, but I don’t think it would be very productive.
I have never gotten WoL to work reliably in any condition. I would just assume it’s not going to, and use other power controls.
Sure, and part of being a good manager is to, you know, manage. It shouldn’t have gotten to the point that marcan is going outside the list to try to get something done. Linus (or someone else with authority, I’m not familiar with who else is managing it) should have stepped in much earlier to head off the drama. It was a very simple question.
Rust in the kernel is already established and part of the mainline kernel. It’s extremely pretty and wholly inappropriate to reject code just because it’s written in rust.