![](/static/61a827a1/assets/icons/icon-96x96.png)
![](https://lemmy.dbzer0.com/pictrs/image/92564b48-6f2d-47b6-a0d0-41a16c5e7830.webp)
Gandalf is easily older than anyone else there, and if he can pull it off…
Gandalf is easily older than anyone else there, and if he can pull it off…
While I half agree that having these warnings there for a glass of wine is annoying, the context here is that people will genuinely believe alcohol consumption to be just a harmless passtime, but nobody will think this about getting body parts cut off.
IMHO, it was a mistake to make USB block storage use the same line of names also used for local hard disks. Sure, the block device drivers for USB mass storage internally hook into the SCSI subsystem to provide block level access, and that’s why the drives are called sd[something], but why should I as an end user have to care about that? A USB drive is very much not the same thing for me as a SCSI harddisk. A NVMe drive on the other hand, kinda sorta is, at least from a practical purpose point of view, yet NVMe drives get a completely different naming scheme.
That aside, suggest you use lsblk before dd.
Is OpenBSD seriously still using CVS for development?
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.
MacOS is basically a different world.
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.
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.
Is sshfs an option? Unfortunately, I don’t think you can put that into /etc/fstab, though…
In F/OSS, it is not unusual for software to stay below 1.0 version for a long time yet still get a lot of use. Just look at how long OpenSSL, for example, was at 0.9.something, while already being of crucial importance to a lot of internet infrastructure.
The reasons for this are varied, but the most important is probably simply that free software developers don’t feel the pressure to call a product 1.0 when they don’t believe it is ready to be called that.
Pipewire makes me feel like I’m a bit stupid. I keep reading about it, I read the introduction and FAQ on their website, yet I still couldn’t tell you what that thing even does. All I know is it’s a slightly less buggy drop-in replacement for pulseaudio, and pulseaudio is something I use because Firefox forces me to. (I would still be on plain old ALSA if it weren’t for Firefox.)
Also, it definitely did not “just work” for me out of the box, I had to do quite some digging and some very non-obvious stuff to get it to a) start up and b) let me use my microphone. I still don’t even know what “starting up” really means for pipewire (is there a daemon or something?), the website likes to pretend that isn’t a thing, but without doing some stuff to start it up, audio just won’t work for pulseaudio and pipewire applications…
AMD and nVidia on Windows: So your GPU is still very capable and useful for almost everything including most gaming tasks, but it’s a couple years old and not making us money any more? Sucks to be you, have fun hunting for unmaintained legacy drivers with likely security holes from questionable sources.
Linux: Your video card is from a long bygone era of computing, before the term “GPU” was a thing, and basically a museum piece by now? We’ll maintain a long-term support version for you for the next ten years.
Some of those Cons sound pretty bad, especially the graphics problems. A lot of those I figure I could live with, but some, like the constant noise on the graphics or a low-quality touchpad would be just too much to tolerate.
I am currently awaiting my (pretty damn expensive) Framework 16 at this time, and I can only hope my experience will be a bit better than yours…
Nothing is affected. The headline is largely bullshit. A minor optimization for high core-count systems did not go as far as originally planned, and that may or may not have made a barely noticable difference.
Did you know that “invidia” is one of the seven capital vices, also know as deadly sins?