If your speedometer/tachometer is a screen instead of dials, it’s extremely likely it’s running Linux, too
So still somewhat useful in the auto space
If your speedometer/tachometer is a screen instead of dials, it’s extremely likely it’s running Linux, too
So still somewhat useful in the auto space
It’s not just betas - it’s in the main release, too
We’re still using them on machines where performance doesn’t matter
On build machines, they’re on a special VLAN and don’t have endpoint protection, but they only download from a protected mirror
Their ftrace hooks caused all disk usage to be serialized, making your multi-core processor single-core when doing anything I/O bound
We saw between 500% - 800% increases in build times with their software installed
without any distro or configuration caveats.
In those cases, they generally have the Ubuntu version that’s supported in the specs section
Oh god. Sentinel one is horrible. If they’re taking issue with your testing, you’ve really screwed the pooch
Somewhere around 0,0 or 1,1
There are amazing possibilities in the theoretical space, but there hasn’t been enough of a breakthrough on how to practically make stable qubits on a scale to create widespread hype
I’d used Linux a bit out of curiosity in the Windows XP era
Windows Vista came out and was completely unusable on the computers I or anyone around me owned. It was also harder to configure than Linux and the new UI looked worse than the Linux UIs at the time
So I switched and haven’t been back to Windows since
How does one flash a ROM without unlocking the bootloader these days?
Shouldn’t that break Android Verified Boot?
A pure GSI image could use a Google key, I suppose, but others shouldn’t, right?
The summary here and in the paper isn’t very helpful to check what CVEs are relevant
The kernels referenced aren’t supported, and it says the issues were reported upstream
Checking some of the references of the paper, it says
By the time we posted this writeup, all the distros have patched this vulnerability.
Do you know what CVEs users should check against?
Isn’t #2 the only option?
Websites specifying color for foreground (or background) and assuming browsers will use whatever color they’re expecting for the other has always existed, and still exists
If you’re getting fancy and specifying colors, you can’t cheap out and not specify all colors
If the browser ignores all your colors at that point, then it’s displaying as the user intended
If you only specified some of the colors, it’s a bug of the website
The even crazier part to me is some chip makers we were working with pulled out of guaranteed projects with reasonably decent revenue to chase AI instead
We had to redesign our boards and they paid us the penalties in our contract for not delivering so they could put more of their fab time towards AI
It’s a strange suggestion after very recently working closely with openSUSE to ensure Leap can use the same binaries as SLE, though
Separated over the PCIe bus with an IOMMU between it and system memory, as well as hardware switches to disable it if I’m not reachable
I haven’t found a way to remove it entirely. It’s the only option I’ve found so far, but if you know of a better designed option, I’m certainly interested
You have to enable developer mode and install with --bypass-low-target-sdk-block
now.
Dunno if they’ll remove that eventually
For the Steam Folders, you can use Flatseal to declare other folders any Flatpak you install is allowed to access
Google is certainly planning on it being viable.
They’ve been merging RISC-V support in Android and have documented the minimum extensions over the base ISA that must be implemented for Android certification
Thanks! That sounds like exactly what I’d want to run mpd. I’ll check it out
For virtualization, I’m all good since I went with uBlue instead of Silverblue for now - the developer images come with lxc/lxd/qemu/libvirt :)
Hey! Thanks!
I’ve installed Aurora to my new drive based off the comments here so far, and it’s been pretty smooth bringing my configs over :)
Immutable is new to me, so I’m wondering how you manage host daemons and cli applications, such as mpd for music and password-store for password management
Is the best practice to keep one Fedora <current release> distrobox with them?
Also, are there any issues with upgrading a distrobox to a new major release over time?
So far my mindset has been make sure I don’t layer anything, but maybe some things like mpd do make sense to layer?
I also see brew
as another option. Perhaps that’s the preferred way for those types of tools? However, it seems like the system upgrade script updates distrobox and not brew?
Sorry for the rambling question - just trying to understand best practices with an immutable distro 😅
I mean, it’s internally consistent with the inbetween too, for the first three:
They went Xbox, did a 360 to face the same direction, and re-released the Xbox 1