Is OpenBSD seriously still using CVS for development?
Is OpenBSD seriously still using CVS for development?
“Squeezes”, “20%”. Interesting word choice. Feels almost like downplaying. When, in reality, 20% is massive, especially on a CPU like the Threadripper.
Rimworld for me.
(I have never tried Dwarf Fortress.)
Honorable mention goes to War Thunder, while it isn’t on of my favorites, I was still a bit blown away to find out it runs natively on Linux.
This is something that has been occasionally happening in Europe (at least in Germany, don’t know about France) for well over 10 years now. Probably more like 15.
What’s sorely needed at this point is much more storage to make this energy available when it is needed instead of when it isn’t. Before that happens, you cannot really decommission any gas or coal power plants, because you still need them during times of much less renewable production.
Going by what OP thinks “Chaotic Evil” means for sysadmins, they have clearly never heard of BOFH.
Writing good comments is an art form, and beginner programmers often struggle with it. They know comments mostly from their text books, where the comments explain what is happening to someone who doesn’t yet know programming, and nobody has told them yet that that is not at all a useful commenting style outside of education. So that’s how they use them. It usually ends up making the code harder to read, not easier.
Later on, programmers will need to learn a few rules about comments, like:
The KDE team has already determined that this is not a bug and that both you and me must just be imagining it:
About 20 years ago, Microsoft was found guilty and convicted, because they forced their browser on their users, driving out competitors by abusing their de facto monopoly on PC operating systems. These days, they are doing the exact same thing again, just on an even broader base. I don’t even understand how this verdict took so long.
Smartctl works on nvme drives. Use it.
btop for bling
htop for practical utility
top for minimalism, availability, reliability
Batteries take “rare earth metals” like cobalt.
Some Lithium-Ion batteries use Cobalt, but many don’t. Lithium-Iron-Phosphate, for example, is a popular variant without any Cobalt. There is a push going on to move to battery chemistries without Cobalt or to reduce the actual amount of Cobalt where it is still required.
Several years ago now. On at least two of those tries, after maybe a month or some of daily driving, suddenly the fs goes totally unresponsive and because it’s the entire system, could only reboot. FS is corrupted and won’t recover. There is no fsck. There is no recovery. Total data loss.
Could you narrow it down to just how long ago? BTRFS took a very long time to stabilise, so that could possibly make a difference here. Also, do you remember if you were using any special features, especially RAID, and if RAID, which level?
Out of interest, since I’ve not used the “recommended partion setup” for any install for a while now, is ext4 still the default on most distros?
I recently installed Nobara Linux on an additional drive, because after 20 years, I wanted to give Linux gaming another shot (works a lot better than I had hopes for, btw), and it defaulted to btrfs. I’ll assume so does Fedora, because I cannot imagine Nobara changed that part over the Fedora base for gaming purposes.
Well passwordless.
Same thing in this context. But sure, an encrypted partition would work.
Dunno about ideal, but it should work.
It does have quite a bit of overhead, meaning it’s not the fastest out there, but as long as it’s fast enough to serve the media you need, that shouldn’t matter.
Also, you need to either mount it manually on the command line whenever you need it or be comfortable with leaving your SSH private key in your media server unencrypted. Since you are already concerned with needing to encrypt file share access even in the local network, the latter might not be a good option to you.
The good part about it is, as long as you can ssh from your media server to your NAS, this should just work with no additional setup needed.
Interesting. Though it does seem to to require your private key to be unencrypted…
Is sshfs an option? Unfortunately, I don’t think you can put that into /etc/fstab, though…
This is on Ubuntu 22.04.3 LTS, so well within the 5 year window. I’m complaining because I kept getting frantic calls from people using that who didn’t know what was going on.
The rules explicitly say “No AI art”.