Short-sightedly.

Of course that’s how sanctions work… against nations. Linux isn’t a country, it’s not an American asset. They could have resisted. Linus chose not to.

Do they? They could have just isolated those commits as sanctioned and added a warning. Linux hates Russians as a Finn, so didn’t need much convincing to remove them.

I would be singing a different tune if our allies invading other countries at the moment were also sanctioned, but that’s not the case.

As it stands, let the individuals escape the nation state punishment. They didn’t start this war, and likely don’t support it.

It’s on sa, so ok.

This is what I’m thinking. The file originally overwrote an older one, I muxed in and synced truehd audio into the original and ended up copying it back after forgetting a subtitle track. It definitely went back and forth with the same name a few times. It’s probably something with the Unix ACLs. Still concerning that it crashes the SMB daemon.

Exactly. All the hype and excitement over a locked down arm ecosystem with evaporating battery life advantages. No thank you. Development efforts are better served elsewhere. I would prefer the Linux community ignore it rather than support it over RISC-V.

This is what I was think also. Just let the host rproxy the requests and just map the dns to the host in opnsense.

The only issue is not having a simple backup interface and feature in general. Has this been addressed yet? How are snapshots with ZFS on Incus?

It’s almost like the whole customized apps to fit into the GTK framework concept creates too much added work and needs to be rethought.

I don’t understand why someone should choose any GTK variant when they’ll have to refactor and rewrite their application every few years.

After decades of user interfaces and internet access, we’re making things worse rather than better.

Someone at Microsoft realized that hardware will speed up, hiding the fact that the OS is getting bloated and riddled with code that doesn’t directly benefit the user.

The value Windows provides isn’t great enough to deal with this state any longer. In fact, my experience shows it’s slower and just as buggy.

We have technology available to improve experiences, let’s not mix it with profit incentives for once.

If that were the case, the scientific method would not exist.

The xz backdoor hidden in precooked blobs would like a word with you.

It still might. Redox is a microkernel based around L4 architecture, but not formally verified.

The problem for me is portability. Flatpak, Snap, Appimage, docker, podman, lxc, they all do the same thing, but they’re splitting the market into “servers” and “desktops”.

We need a portable container runtime we can build from a compose file, run cli or gui apps, and migrate to a server with web app capability displaying the UI. There are too many build targets, and too much virtual market segmentation.

Nix tries to solve the issue, but the problem is you have to use Nix.

Just wait for VeganOS to drop.

The difficulty is getting closed source hardware manufacturers to adopt it.

With immutable distros you can try a silverblue and switch to kinoite with a reboot on an already running system and it will just work and run your flatpaks. The base image it runs does not get corrupted. You cannot make changes (easily) to the base to corrupt it. Your apps and files are just an overlay or mounts on top of the system. Your machine lights on fire, if you have a network backup, it will fire up on any hardware and be the same. It’s much cleaner and allows for easy os switching.

You could theoretically make windows work and be switchable.

Linux fragmenting Ike this between distros is a major problem for the future.

Used to use LMDE but moved to Debian to get 12 early.

I’ve been daily driving Debian with cinnamon on top. The only thing keeping my windows partition going is lack of HDR support and horrific Wayland nvidia support.