Finally had a go at solving one of my biggest pet peeves with booting up Linux, having to add console=ttyS0 or console=hvc0 or console=<god-knows-what> to the kernel command line to get output on the serial console. With https://github.com/systemd/systemd/pull/41387, systemd-stub will now try to auto-detect whether a single virtconsole or serial console is attached without graphics output and append console= to the kernel command line automatically so you get output on the serial console automatically.
@daandemeyer
- 210 Followers
- 16 Following
- 128 Posts
@agowa338 I have no clue how I would even test this unfortunately.
@samueldr So I'm already reworking this to pick the right index on x86 since they're statically allocated there. You're right that on arm we can't really know for sure. I kept it for now to pick ttyAMA0 if we find a single serial console.
As for the graphical console, you're of course right that this breaks if the uefi firmware can't detect the graphics output. I guess I could make it opt-in to avoid breaking existing use cases.
Michael VogtWhile work on the varlink-http-bridge for systemd I had this idea that a lot of the tech could be used to build an #MCP for systemd via #varlink. So here it it is: https://github.com/mvo5/systemd-mcp - it auto-discovers systemd's varlink sockets, introspects the IDL, and exposes every method as a typed tool. On a typical system that's 50-80+ tools: units, journals, credentials, factory reset, you name it. What could possibly go wrong :) ? (requires systemd v260+)
Christian Brauner đĻđēAge verification clearly doesn't belong into #systemd. We should have never merged this. Instead this should be incrementally added to the kernel itself. I'm doing my part:
https://lore.kernel.org/all/20260401-i-hope-someone-believes-this-is-real-04f24e03944e@brauner
LWN.net[$] Objections to systemd age-attestation changes go overboard
In early March, Dylan M. Taylor submitted a pull request to add a field to store a user's birth date in systemd's JSON user records. This was done to allow applications to store th [...]
https://lwn.net/Articles/1064706/ #LWN #Linux #Debian #systemd
All Systems Go!đŖ The CFP for All Systems Go! 2026 is now open!
Submit your talk about foundational user-space Linux technologies now đ https://cfp.all-systems-go.io/all-systems-go-2026/cfp
âšī¸ More info here: https://all-systems-go.io/
đĢ Tickets go on sale in April.
@Valentin Awesome! Finally we'll be able to support ISOs.
@cwebber the AI contributions will happen regardless. It's trivial to have e.g. opus 4.6 spit out prs that we would not be able to classify as being written by AI. In fact, by adding an AGENTS.md that instructs AIs to add disclosure, we probably make AI written prs more obvious. Anyway, if we know people are going to use AI to contribute in ways we cannot reliably detect, we may as well add instructions to make those prs as good as possible.
@cwebber @trentmichael_reznor It's not just that, the ai part of the review workflow runs with only read-only access to the repository. All it does is produce some json that is processed by another step further in the workflow which does have permission to write the comments from the json to prs.
I did put a little thought into making the risk of prompt injection is minimal. The review workflow can also only be triggered by repository members and is not triggered automatically yet.