First time in my life running Linux with SecureBoot thanks to lanzaboote
![Secure Boot for NixOS [maintainers=@blitz @raitobezarius @nikstur] - nix-community/lanzaboote Secure Boot for NixOS [maintainers=@blitz @raitobezarius @nikstur] - nix-community/lanzaboote](https://mastouille.fr/system/cache/preview_cards/images/001/460/608/original/cadd66f582d41556.png)
First time in my life running Linux with SecureBoot thanks to lanzaboote
Almost in #Zurich for #NixCon2025
And DB was on time so it all went smoothly without having to change trains in Basel.
Are you spontaneous and don't have any plans for tonight? Then come check out our TechTalkThursday! We open the doors at 5:30 p.m., the first talk starts at 6 p.m., and at 7:30 p.m. there's pizza, beer, and a chance to chat with speakers and the community.
For more information, visit https://www.meetup.com/ninetechtalkthursday/events/307715644/ on Meetup, and watch the livestream here https://www.youtube.com/watch?v=eTyDfgJsjGs on YouTube.
#techtalkthursday #technicaldebt #kubernetes #nixos #nine
Jeden Dienstag findet auf der c-base der NixOS-Stammtisch statt.
#c-base | c-base.org/ | @cbase
Rungestraße 20
10179 Berlin
#Linux #NixOS #Stammtisch #Berlin
Ich lerne NixOS
linux.waldstepper.de/ich-lerne…
Today we’re launching Thymis — open source + SaaS for managing IoT device fleets declaratively with NixOS.
Fleet updates, infra‑as‑code style.
Live now → https://www.producthunt.com/products/thymis?launch=thymis-open-source-cloud
It's alive! The #uConsole is a nice piece of hardware but it was missing my favorite operating system #NixOS. Since I am using a Raspberry Pi Compute Module 5 as core, it was not trivial to get NixOS running on it.
After several days of tinkering and learning a lot about the boot process of ARM-based devices, the structure of the Linux kernel source tree and the Nix language in general, the system finally boots up as expected. Yay!
Ah yes, i got the classic `Module lists can't be nested lists` in #NixOS but it does not tell me what lead to this.
Sadly it was during a slightly larger refactor and i don't want to roll back everthing.
`--show-trace` does not help either.
When that 2011 #MacBookPro is pushing 16gig of ram and an SSD, booting #NixOS in 45 seconds
Now that #nixos is no longer accepting new package requests, wonder how we can coordinate creating packages so we don't duplicate efforts, or waste time solving problems that have already been solved?
Also is there any discussion on this decision I can find online?
As usual, of course migrating services is also possible with other distributions, but the experience is very predictable and smooth with #NixOS and I did not have to distinguish between self-packaged custom Go software or distribution-provided standard FOSS software — it can all be moved around easily, including not just services, but also system users/groups, auth keys and other secrets, and PostgreSQL databases (config, not contents).
For two VMs, I could just live-migrate them between hypervisors, but the third one runs Caddy and hence needs DNS updates for each service, so I did a service-by-service migration.
This is where migrating to #NixOS has paid off: I could migrate a setup spanning 4 custom Go services, 17 virtual hosts, totaling 25 .nix files from one server to another in just about 2 hours.
The trivial approach of “move config, deploy dest, stop src, copy state, update DNS, deploy src” worked beautifully :)
I've updated Wombat's Book of Nix
(https://mhwombat.codeberg.page/nix-book/) to show how to use `nix shell` in place of `nix-shell`, and added a few recipes. It's even explain-y-er now, and, freely available online.
Huh, got a whole slew of closed PRs because nixpkgs
is no longer accepting new package requests via issues. Not saying its wrong to look for someone willing to do the PR, but I disagree with closing the ticket because it is useful to know how many other people are interested in a package for someone to step up. Community interest is still important.
Also, more reasoning for creating flakes for the applications I use. I think nixpkgs
is getting too large in general but flakes need a bit more love for playing better with others.
So to search for a package you use search.nixos.org as the CLI tools are considered to be suboptimal.
But if I want to know which package contains a specific file or provides a specific executable (like e.g. fsck.ntfs) I've to first install nix-index, download the entire index and then use nix-locate as there is no website to do that through?
Did I get this right?
Sounds kinda half assed both ways...
Updated android-translation-layer on #NixOS including some patches for upstream https://github.com/NixOS/nixpkgs/pull/439150