There was one on Reddit - I came to see if someone linked one

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

Yeah, that’s bizarre. I’d never have guessed /home was created by tmpfiles

Starting with the iPhone 14, they put the last generation processor in the non-pro and the current generation processor in the pro

The weird thing here is that the 15 non-pro (the new processor from the 14 gen - A16) has a faster NPU than the M1 processor that does support the AI feature

The only possible technical reason is because they put such an anemic amount of RAM in their phones. Otherwise it’s entirely an artificial limitation

Running top of the line models does require a lot of RAM, so it’s not an entirely ridiculous theory.

The one I run on my desktop needs at least 12 gigs of VRAM

There are reasonably frequent rebuilds of basically all packages as new versions of the compiler, gcc, come in

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 :)

To expand - DirectX is a proprietary Windows solution. Any time you pick it on Linux, it will run through a translation layer

OpenGL/Vulkan are cross-platform

OpenGL is to DirectX 11 as Vulkan is to DirectX 12

Microsoft kept the same branding, but also followed in Vulkans/Metals footsteps of using lower level calls to the hardware. This makes the graphics drivers simpler, and can be way more performant because the CPU doesn’t have to do as much

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 😅

When I check out the ISO for microOS, it lists microOS Kalpa as “alpha”

Is it ready to be used as a primary install?

The developer image, dx, includes rocm-hip and rocm-opencl:

https://github.com/ublue-os/bluefin/blob/main/packages.json

The packages under “dx” are the main reason I’m considering it over stock Fedora

How does bluefin fit in the dependency chain here - is this just the repository that builds official uBlue images?

Part of my confusion is trying to understand how these projects are related to each other

Edit - oh, I guess bluefin is the Gnome variant

The RK3588 is pretty nifty, and is the first Mali GPU (610) where ARM themselves have contributed the firmware upstream and have helped with Collabora with Panfrost development

Bleeding edge, still, but kernel 6.10 and Mesa 24.1 have GPU support

HDMI TX and DSI/CSI are still in-progress

Sure. I just think this might be the first time that the current iPhone would be missing a feature on the next iOS update

I’d guess most iPhone 15 owners would have assumed their phone was new enough for the feature

One thing to note is that they announced Apple intelligence is only coming to the iPhone 15 Pro/Pro Max for their iOS release

Browsers do have their own sandboxing, trying to prevent things like a JavaScript overflow on one website affecting other tabs, etc

Flatpaks use user namespaces and run each program in their own filesystem snapshot

Chromium in flathub has been patched to support its own sandboxing inside of the Flatpak sandbox

Firefox only loses its user namespace, but Flatpak has already put it in its own user namespace

The only reduction in the browsers own sandboxing is if they’re creating separate user namespaces per remote process, but in about:support, Firefox still lists itself as having the max sandbox level even in the Flatpak

The nice thing about Flatpak is that you can restrict it even more - e.g. my browser is only allowed to touch files in ~/Downloads/firefox

I don’t use webcams/mics through Firefox, so it also has no access to those, etc

You can set fine grained permissions easily with a program called Flatseal to decide what your browser should be able to touch on your machine

I’m working off the assumption you are using one GPU for the host and one for the guest

The guest one is permanently blacklisted on the host, and you can select the passthrough settings in the GUI

If you’re dynamically detaching the GPU, my statement was incorrect

Wow! I didn’t expect sched_ext to be accepted based off historical precedent of not allowing multiple schedulers

I thought the focus would be on optimizing EEVDF now

Not to mention that even in the 60’s Nixon’s cabinet has stated he specifically started the war on drugs and marijuana in order to imprison black people and anyone against the war.

“We could arrest their leaders. raid their homes, break up their meetings, and vilify them night after night on the evening news”

https://www.cnn.com/2016/03/23/politics/john-ehrlichman-richard-nixon-drug-war-blacks-hippie/index.html