@sandro@c3d2.social avatar

sandro

@sandro@c3d2.social

Some lefti :AFD:, NixOS :nixos:, Linux :tux:, Chaos :fairydust:

Don't be afraid of colorful flags :progress_pride: 🏳️‍🌈🏳️‍⚧️🚩🏴

This profile is from a federated server and may be incomplete. Browse more on the original instance.

farcaller, to random
@farcaller@hdev.im avatar

, when you can pull any version of a package into your local shell.

How did I survive with debian, again?

sandro,
@sandro@c3d2.social avatar

@farcaller big asterix: any version that was in nixpkgs and the state of it is completely arbitrary. It could be on a completely unusable commit or contain sever CVEs or misconfigurations. Things cannot be fixed because things are frozen in time. You shouldn't use this unless you do testing. It is very risky and irresponsible to use those tools in production. Any issue you encounter is completely unactionable unless it is also happening on a maintained branch.

nomeata, to linux
@nomeata@mastodon.online avatar

Switching from (contributing to) to changed a few things. What it doesn't change is the kind of interaction with upstreams that, well, at least I find strangely hard to work with. Oh well, my strategy is to raise a shield of intense humility and politeness, and else shrug away all the mistrust and misunderstanding that otherwise could wind me up.
(No links needed.)

sandro,
@sandro@c3d2.social avatar

@nomeata at least with overlays you can easily ignore upstream and do whatever yourself pleases with ease

raito, to random
@raito@nixos.paris avatar

Fuck me, I went into the rabbit hole of packaging https://baserow.io/ 1.16.0 with Enterprise and Premium features.

It took me my everything, I had to hack code in https://github.com/nix-community/nix-init because the OpenTelemetry ecosystem in Python is a dumpster fire (pardon for the people working on that, but I have never seen that.)

Instead of using optional-dependencies, they decide to create one wrapper instrumentation package per dependency, and they made micro-packages everywhere.

sandro,
@sandro@c3d2.social avatar

@raito People in the python ecosystem always find ways to do basic things in none standard ways, that's the standard. I am glad they didn't wrote their own package manager.

savanni, to random

Hey, tonight I think I want to spend some time trying to build a toolchain that links together Kifu-core, the wasm binding, and the typescript app.

All of this using .

If any of you want to join me, I'm thinking 11pm, eastern, and I can set up a jitsi room for it.

sandro,
@sandro@c3d2.social avatar

@savanni I would recommend to use buildNpmDependencies to reduce code generation.

ramin_hal9001, to linux
@ramin_hal9001@emacs.ch avatar

Guix maintainers Janneke Nieuwenhuizen @janneke and Ludovic Courtès @civodul have announced just today that their "seed" C compiler "Mes" is now in production in Guix OS. Mes can, after several boostraping stages eventually compile GCC which in turn compiles Linux, Guile, and Guix. The bootstrap program (as I understand it) is written in Guile Scheme, and compiles to a 357 byte binary. Now when you do guix pull you will see that the entirety of the core operating system (some 22,000 expressions) all depend on that single 357-byte bootstrap program. The idea is to eliminate the footprint of trusted binaries that build the software for the OS and compiler toolchain -- the famous "Trusting Trust" problem outlined by Ken Thompson which he presented while receiving his Turing Award. Thanks to their hard work, we now have an operating system for which every stage of the build can be verified by a human. https://guix.gnu.org/blog/2023/the-full-source-bootstrap-building-from-source-all-the-way-down/

Nix OS people do not need to feel left out, a new issue on the Nix OS GitHub page has announced that they will begin a similar project. https://github.com/NixOS/nixpkgs/pull/227914

sandro,
@sandro@c3d2.social avatar

@ramin_hal9001 @janneke @civodul *NixOS

duckunix, to random

I have a question for the crowd. I have a laptop which needs a custom kernel, and I have tried to follow the NixOS wiki and not getting it. Does anyone have some good links I can go read? Thanks!

sandro,
@sandro@c3d2.social avatar

@duckunix custom kernel as in custom config, source or with patches?

sandro,
@sandro@c3d2.social avatar

@duckunix no idea, you could try looking at the full log if something other happened before this

joshthetechie, to linux
@joshthetechie@fosstodon.org avatar

No matter how many times I distro hop, I always feel back at home on .

sandro,
@sandro@c3d2.social avatar

@joshthetechie distro hopping is pretty much dead for me with nixos

eisfunke, to random
@eisfunke@inductive.space avatar

Talked to @davebloggt today, he told me he worked with some colleagues on a machine someone else (who doesn't work there anymore) set up at his workplace. I think this is an interesting case study on the new-to-NixOS-experience, which is why I'm writing this down.

They tried to change something in the sway config. Searching "sway nixos" led them to the NixOS wiki, which said something about if sway is enabled in the NixOS config at /etc/nixos/configuration.nix, which it was, it overwrites any home-manager config for sway. However, the sway config file was a symlink to a home-manager path in the store, even after running nixos-rebuild switch.

Searching "home-manager" led them to the NixOS wiki again, which said something about the home-manager config being in ~/.config/nixpkgs/home.nix or a NixOS module. This file however didn't exist, and theconfiguration.nix` didn't contain anything mentioning home-manager.

This ended in confusion, them not being able to determine where the home-manager stuff came from, and finally them simply deleting the symlink and changing stuff manually.

The solution we worked out together was that the system was built from a flake in some repo. The file in /etc/nixos/configuration.nix was probably just a leftover, which is why it contained stuff that didn't make sense. When they ran nixos-rebuild without --flake it took the old config file, which didn't contain any home-manager stuff. That left the system in an inconsistent state.

Some learnings we might take from this:

  • If you google something about NixOS, in most cases, the wiki will be the first thing to pop up, because it's the only place that really contains the kind of "you want X? do Y" instructions for practical stuff.
  • I think the NixOS wiki isn't really up to that task as de-facto landing page for novices. It's neither really comprehensive nor up-to-date and seemingly not even official anymore and now now operated independently because of... some stuff that happened?
  • The flake/non-flake split of the ecosystem doesn't make things easier.
  • The person who set up that machine probably should have documented their deployment.
  • His company should really hire me as a consultant!
sandro,
@sandro@c3d2.social avatar

@eisfunke @davebloggt the answer to flakes is: just do flakes

All the custom brewed solutions before flakes have shortfalls and no common interface. Flakes greatly contains the amount of shenanigans possible while evaluating your system.

sandro,
@sandro@c3d2.social avatar

@eisfunke @davebloggt for someone like me that is not often reading the nix docs and has so many settings that enabling flakes is just one of many thousand lines, I don't even notice that they are not mentioned.

terrorjack, to random
@terrorjack@functional.cafe avatar

sysadmins: do you use btrfs/zfs snapshots as another line of defense in addition to nixos's own system generations? if so, why?

sandro,
@sandro@c3d2.social avatar

@terrorjack never snapshoting or backing up /nix, only other directories

sandro,
@sandro@c3d2.social avatar

@mangoiv @terrorjack I have a hydra which has it cached, so for a single machine it has zero value and even without that it takes at most an hour.

sandro,
@sandro@c3d2.social avatar

@mangoiv @terrorjack also the amount of data that goes through my nix store is in the 100s of GBs a week. Snapshoting that would take a lot of data.

tyil, to random

I think I'm getting attracted to 😫

sandro,
@sandro@c3d2.social avatar

@tyil you either use something like sops-nix or supply an absolute path to the private key which can be in many places.

trystimuli, to random

how many things will i break if i set my computer's time zone to TAI? (currently UTC+37 seconds)

sandro,
@sandro@c3d2.social avatar

@trystimuli if you have recently build your system it should be pretty fast. If you changed a bunch of things and then added another thing on top, you either undo things or get all of them at once.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • megavids
  • kavyap
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • osvaldo12
  • everett
  • Youngstown
  • khanakhh
  • slotface
  • rosin
  • thenastyranch
  • ngwrru68w68
  • Durango
  • JUstTest
  • normalnudes
  • ethstaker
  • GTA5RPClips
  • modclub
  • cisconetworking
  • mdbf
  • tacticalgear
  • cubers
  • provamag3
  • tester
  • anitta
  • Leos
  • lostlight
  • All magazines
    •