I think ecc isn’t more required for zfs then for any other file system. But the idea that many people have is that if somebody goes through the trouble of using raid and using zfs then the data must be important and so ecc makes sense.
I think ecc isn’t more required for zfs then for any other file system. But the idea that many people have is that if somebody goes through the trouble of using raid and using zfs then the data must be important and so ecc makes sense.
I love the idea of distrobox/toolbx!
but ive never understood why they by default share the home directory. They still overwrite each others config filesand leave a huge mess in the home dir. And last time i tried it wasn’t possible to really isolate things. Has thisimprovesd?
I’ve been a paying bitwarden customer for years but i through they were moving more towards free software and not away from it… Makes me consider quitting my subscription. Why do they do this?
Ah i see kde has fixed the issue where dropdowns had broken behavior when scrolling https://invent.kde.org/frameworks/kirigami/-/commit/f6ca218607ff7e5d5066eb3224154c3256cb9516 this was my main blocker why i couldn’t use it when i tried it around 2020. Maybe i could give it another try?
What non standard thing are they doing with the power supply? The PSU looks like a regular usb c PD supply to me (even supports 12v, nice!)
Edit: wtf! 5v@5a yeah thats non standard. What were they thinking?
The system tray is the one thing i need to see that/if email/steam/chat is running and if there’s new messages. Otherwise gnome works great for me
There are portals: https://docs.flatpak.org/en/latest/desktop-integration.html#portals . they allow secure access to many features. Also any flatpak app still has access to a private app-specific filesystem, just not to the host.
Doesn’t work for all applications but for many sand boxing is possible without a loss of features.
I get screen tearing when gaming on x11 so i use wayland and I only switch to x11 if i need to screenshare on discord.
yes these are the terms that are not supposed to be used in product naming or by consumers and are just intended for use by people developing USB devices.
Well you have to differentiate somehow and USB 5, 10, 20, 40 or 80 gbps sound like reasonable terms for normal people.
Yes it was never intended that any consumer hears about something like “USB 3.2 Gen 2” that was strictly internal naming for people developing USB devices.
In fact the naming guidelines we’re simplified even further than in the older version you linked: https://cdn.arstechnica.net/wp-content/uploads/2022/09/USB-IF-language-usage-guideliens.pdf
But yea borderline fraudulent manufacturers and uninformed tech journalists are to blame for all this confusion
The v2 part here really just refers to the fact that it’s version 2 of the specification. Consumerrs only need to know the term USB4 and the speed that their device operates at. It’s sort of like complaining that the ietf has terrible naming schemes because HTTP is defined in half a dozen RFCs with 4 digit numbers. This versioning is just meant for people developing USB things.
Actually this article here is one of the few times where even mentioning the version 2 part is reasonable since the details of these specifications actually matter to kernel developerrs. For everybody else it’s just USB4 80 gbps.
How do you do inter-pod communication witg quadlet? I never figured that out with podman kube play and just moved back to staring conatiners and creating networks from a shell script