Stable package > back port package > flatpak/snap.

Basically I want everything as stable as possible unless I have a particular need for a newer feature.

The main things I run from flatpak/snap are browsers and the Minecraft launcher because they are both regularly updated.

When it comes to export controls and sanctioned entities it doesn’t really matter what Red Hat would like to do - they have to comply with the law in the jurisdictions they work in. Even if it was purely a community project individual contributors face a similar liability if based in those jurisdictions.

When it comes to sanction lists there is a fair amount of commonalty between the US and Europe. This is really something to complain to government about.

I guess somewhere between 6 and 7…urm 6/7 👐 (and my kids say I don’t understand memes 😅).

The year of Linux on the desktop is whatever year you personally switched over.

mu4e inside my Emacs session.

Things like Tianaman square aren’t Western propaganda, it was a thing that happened. There is a difference between alignment fine tuning and straight up wiping things from the models knowledge base.

It’s not like totalitarian regimes don’t have form on censoring inconvenient facts including various revolutions, the Nazis and the Catholic church.

Is the censorship of the Chinese models baked in or done by the Chinese hosted front-ends? I’ve seen some of the Llama models have de-censored versions on Huggingface so I wonder if the same is true for the Chinese versions?

Are you using open drivers or the binary proprietary ones? As I understand it with open drivers most of the work is in the Mesa user space and trying hand built versions of that is a lot easier.

I didn’t know who Kirk was until the assassination I have better things to do with my limited time than go on a deep dive into their history before posting any comment on the news. I kinda got the vibe when I realised that was who Cartman was based on in the recent South Park.

Yeah I don’t think this is an ncdu issue but something is broken with the OPs system.

I’ve moved to using Rama Lama mainly because it promises to do the probing to get the best acceleration possible for whatever model you launch.

I’ve got an Ampere workstation (AVA( which from a firmware point works fine. They may even fix the PCIe bus on later versions.

Asahi is a powerful example of what a small well motivated team can achieve. However they are still face the sisyphean task of reverse engineering entirely undocumented hardware and getting that upstream.

If you love Apples hardware then great. Personally when I have Apple hardware I just tweak the keys to make it a little more like a Linux system and use brew for the tools I’m used to. If I need to I can always spin up a much more hackable VM.

Arm has been slowly pushing standardisation for the firmware which solves a lot of the problems. On the server side we are pretty much there. For workstations I’m still waiting for someone to ship hardware with non-broken PCIe. On laptops the remaining challenge is power usage parity with Windows and the insistance of some manufacturers to try and lock off EL2 which makes virtualization a pain.

Sorry to hear that. Good luck finding a new gig without needing to interact with Teams again.

I used to update my tickets from Emacs org-mode where I kept my working set off knowledge. The org export functions dealt with whatever format Jira expects. Nowadays I’m mostly tracking stuff so my comments are generally never more than a “thanks”, 👍 or occasionally a link to the patch series or pull requests.

Jira is alright, not great, not terrible. You need something to track projects and break down work and say least being ubiquitous a lot of people are familiar with it.

Teams is a dumpster fire of excrement though.

What do the inputs and configuration drop down menus say?

I remember the old ADSL modems where effectively winmodems. I had to keep a Windows ME machine as my household router until the point the community had reversed engineered them enough to get them working on Linux.

At least they where usb based rather than some random card. I think the whole driver could work in user space.

VirtIO was originally developed as a device para-virtualization as part of KVM but it is now an OASIS standard: https://docs.oasis-open.org/virtio/virtio/v1.3/virtio-v1.3.html which a number of hypervisors/VMM’s support.

The line between what a hypervisor (like KVM) does and what is delegated to a Virtual Machine Monitor - VMM (like QEMU) is fairly blurry. There is always an additional cost to leaving the hypervisor to the VMM so it tends to be for configuration and lifetime management. However VirtIO is fairly well designed so the bulk of VirtIO data transactions can be processed by a dedicated thread which just gets nudged by the kernel when it needs to do stuff leaving the VM cores to just continue running.

I should add HVF tends to delegate most things to the VMM rather than deal with things in the hypervisor. It makes for a simpler hypervisor interface although not quite as performance tuned as KVM can be for big servers.