That’s a really good idea! So good in fact that that is actually what they did call it! https://www.usb.org/document-library/usb4r-specification-v20
That’s a really good idea! So good in fact that that is actually what they did call it! https://www.usb.org/document-library/usb4r-specification-v20
That is very very explicitly just the name of technical the specification. Its a documents for people who design usb devices. The tech media failed us by reporting on it like they did.
The spec also explicitly tells us that we should refer to the usb cables/ports/devices as e.g. “USB4 40Gib” or “USB 3 20GiB”. So in fact we have easy to understand names but only a few manufacturers actually print that on the boxes or cables.
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
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.
Maybe it’s a u.2 or u.3 nvme Enterprise drive?
I love USB-C for charging and data and display. But it does not replace 3.5mm. Aside from the things mentioned so far in the comments here, a fundamental problem is that now headphones need DACs in them.
The engineering specification states that an analog headset shall not use a USB-C plug instead of a 3.5 mm plug. In other words, headsets with a USB-C plug should always support digital audio (and optionally the accessory mode)
https://en.wikipedia.org/wiki/USB-C#Audio_Adapter_Accessory_Mode
That increases the cost of headphones and introduces a point of failure and makes things more complicated for the end user. It’s just not worth it.
Did setting OnCalendar to the empty string not work? https://unix.stackexchange.com/a/479745