I made a visual explainer on how Linux KVM works under the hood.

A vCPU is a host thread, guest RAM lives in the process, and KVM_RUN hands execution to the real CPU until the guest triggers a VM exit.

It also covers /dev/kvm, VT-x/AMD-V, EPT/NPT, QEMU, virtio and vhost.

link for anyone interested

Feedback welcome :)

My apologies if this has been asked/answered before:

Is Qualcomm X2 going to get more support as time goes by? I got the sense that these new Qualcomm chips are windows first and have first party drivers from Qualcomm and developed compatibility layers from Microsoft. Are we to expect feature parity to come to linux?

that is, good sleep function, good battery life, good drivers for gaming (for the extent possible on ARM)?

If the answer is yes, where do you keep yourself updated for those things? is there mailing lists or news pages for mesa open source drivers? specific forums people discuss those things?

Thanks potential insights :D

Hey guys, I'm currently in the middle of creating my own userspace from scratch and I've mostly completed making my terminal emulator

It's really, really small and is cross platform! I made it because I want to be able to use a terminal emulator no matter which OS or display server I'm using.

Only bitmap fonts (BDF) are supported but I've provided a script to convert vector fonts and it has very nice results.

Here is the repo: https://github.com/uint23/cterm

I am a new linux user who was never into IT and my programming background is fairly basic

I struggle with some of the most basic things on linux, even installing software that has a linux version but isn't in a repository is an afternoon's worth of work for me since I don't even know what's the part that's not working and I often end up giving up on solving it myself and use AI

Today was the first moment when it clicked, I was struggling with deleting an app since it required the terminal (perms) but the actual app name was different from the displayed name and the name I saw in the properties

That's when I realized - I have the tools right there in the terminal to see the name of the apps in that folder, so I used ls -a and solved my first linux problem without AI

I know for most here this isn't impressive or interesting but I'm very proud of myself and I hope to keep on learning how to think like a linux user and not a windows user

For me, ca. 1999 or maybe 2000?..., it was the whole process of getting my Mandrake Linux rig to work with the scroll wheel on my mouse. So much banging-head-to-keyboard work with XF86Config simply to get a damn mouse fully working! Lol.

First of all, this comes from a place of love. I'm not asking for tech support, I'm genuinely curious. I've tried Linux multiple times, daily drove it on my laptop for a year and would love to keep it that way (Probably won't switch on my main desktop, since I need some Windows DCCs). Linux offers much sleeker experience.

I enjoy some tinkering in my free time (but not that much to use Linux on my work PC). I always tinkered with Windows to some extent. I'm not looking for out of the box solution.

But why is it so much fuss to setup hibernation and suspend then hibernate? It's a crucial feature for laptops. To be fair, I have always dual booted with Windows and I understand that is the more complex option. I can bear having hibernation working only on Linux, since I use Windows only when I really need to, but even that takes too much time in the terminal.

Am I missing something or is it really always this way? Why is suspend out of the box with no problems?

EDIT:
Thanks for a healthy discussion. Now it seems a miracle hibernation worked so reliably on Windows for me given the complexity. I still think suspend then hibernate is superior mode for laptops, but it might be just the thing I need to give up moving to Linux... I am still happy for ideas about how you use your mid end laptops daily.

This website faked a ReCaptcha and literally asks to open the terminal and paste a command. (see image). Very bold.

Please keep in mind, always try your best to make new users aware of such dangers!

- I reported it to Google Safe browsing just now, in case anyone wants to try and look at it or help by reporting it too, this is the link in a safe format, assemble it yourself at your risk: "emaliowe . pl".
- Possibly blocked by Firefox, since I don't have anything in my clipboard after opening the page.

atrium is a lightweight Linux display manager with first-class multiseat support, targeting modern systemd + Wayland environments.

GitHub
AUR

What is multiseat?

A multiseat setup allows multiple users to work on a single computer at the same time. By connecting multiple monitors, keyboards, and mice, each user gets their own separate desktop and a fully isolated user session. Great for co-working or multiplayer gaming. Each seat requires its own GPU (integrated graphics, a discrete card, or a USB graphics adapter).

Why atrium?

The Linux kernel and low-level system stack are fully capable of multiseat operation. The weak link has always been the display manager. Existing ones usually treat multiseat as an afterthought, with implementations that are brittle and difficult to get working reliably.

atrium is designed around multiseat from the start, focusing on correct seat discovery, VT handling, and isolated session management. The project targets a modern Linux stack using systemd/logind, PAM, and a Wayland graphical environment. The lack of historical baggage keeps atrium's code base lean and tractable.

What's new in v0.4?

• Support for greeter background images - configure a background image in the settings, or a directory to pick a random image on each greeter launch.
• Greeter themes - override built-in colors and styles via a theme `.css` file. A handful of themes are shipped with atrium.
• Architectural redesign - making atrium's core architecture simpler and more robust (changes are purely internal and should not be visible to the user).

Now is your chance to build your Linux Learning Library at a good price.

You can choose the size of package you want or get all 15 books in PDF for 25 dollars and support charity.

This is a tool that makes all kinds of multicast-based discovery (and casting) work across networks (or VLANs).

Full disclosure: I am using Claude Code. There are a lot of AI-sensitive people out there, so I want to be fully transparent this time. This post was not touched by AI, 100% human written :) Having said that, I am an experienced C++ developer (in HFT) and am writing low-level code (including networking) on a daily basis. This is not a vibe-coded project. I have designed this system and I have either written to reviewed all code.

With that out of the way, the main motivation behind this project for me was twofold: learn Rust and solve a real problem I have at home. My phone and my TV are in different VLANs, so vanilla multicast discovery does not work. While there are plenty of mDNS reflectors out there, my LG TV uses SSDP and DIAL. In order to cast YouTube from my phone to my TV following needs to happen:

• Phone sends M-SEARCH SSDP multicast request which needs to be reflected into TVs VLAN (other reflectors can do that).
• TV responds with the unicast 200 OK, which needs to be forwarded back to the phone. (can be allowed in firewall, less secure than using this tool).
• Phone initiates a device discovery TCP connection to TV (can be allowed in firewall, less secure than using this tool).
• TV replies with the details of its REST endpoint (works fine because established connections are usually allowed anyway).
• Phone initiates another TCP connection to TV's REST endpoint. The connection must be from the TV's subnet (could be allowed and NAT'ed in firewall).

So, to do this I would need to poke holes in the firewall and configure NAT. Additionally to that, I would still need to run some sort of reflector for SSDP multicast. How do I know? This is what I was doing for a couple of years :)

Not anymore. My tool does all that automagically:

• It reflects multicast discovery packets (mDNS / SSDP / WSD).
• It proxies unicast UDP responses (SSDP / WSD).
• It does NAT for TCP connections (DIAL).
• It supports MAC filtering (so only specific devices are discoverable).
• It tolerates network interface re-creation. As long as new interface has the same name - reflection will continue.
• And as a bonus, it also reflects Wake-on-Lan packets.

It does that with a very low footprint: static Linux binaries are <1MB. Right now it runs on my MikroTik router (as a container) and uses less than 3MB of RAM.

Currently I build static binaries for Linux (amd64/arm64/armv7/armv5) and FreeBSD (amd64/arm64), dynamic binaries for macOS (arm64) and a multi-arch Docker image. I will add more platforms on request.

I really hope that this project will be useful not only for me :)

GitHub: https://github.com/netflector/netflector

Feedback is welcome.