@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.

jwildeboer, (edited ) to opensource
@jwildeboer@social.wildeboer.net avatar

You know why I like @forgejo so much? I just did a "fly-by" patch on the documentation because I was annoyed with how complicated that one page was written. So I forked the repo, cleaned up that page and submitted a Pull Request. And guess what? No discussions, no back and forth, it just got merged! Now THAT is how you attract new contributors to your Open Source project. Thank you! My first contribution!

https://codeberg.org/forgejo/docs/commit/784e395e977c5a3d0ca6892501f7216939f3b955

#Forgejo #OpenSource #MergeFast #FirstContribution #FeelsGood

sandro,
@sandro@c3d2.social avatar

@jwildeboer I mean, it also just straight up copied from GitHub/GitLab

sandro,
@sandro@c3d2.social avatar

@doomsdayrs @jwildeboer @forgejo Because people have different ideas about how things should look and if you want to have somewhat coherent code/docs, not every other person can write a different style, tone and structure.

sandro,
@sandro@c3d2.social avatar

@fink @jwildeboer You shouldn't really give to much credit for good ideas if they are all straight up copied from somewhere else

chrism, to NixOS
@chrism@chattingdarkly.org avatar

Report on NixOS Governance Discussions

https://chrismcdonough.substack.com/p/report-on-nixos-governance-discussions

#nix #nixos

sandro,
@sandro@c3d2.social avatar

@yisraeldov @chrism NixOS is not deeply embedded into GitHub. Many CI checks are just executing shell code in the end which can be early run locally and be adopted and everything specific to GitHub would need to find a replacement, like the labeler.

The main problem is scalability. Running your own infrastructure on that level of size, complexity and availability is a major undertaking and eg. Gitea couldn't even handle the amount of forks.

squirrelroad, to NixOS
@squirrelroad@mas.to avatar

why is there https://lix.systems and https://aux.computer ?
Why not just merge them together ?

sandro,
@sandro@c3d2.social avatar

@dwagenk @squirrelroad I don't see how replacing nix with different 3 letters in all terms would solve the naming quirk.

Also IMO that's not such a big issue. Most languages have a language and compiler/interpreter which is named the same.

sandro,
@sandro@c3d2.social avatar

@squirrelroad 🤷
Also aux seems to be just a community which primary goal is rebranding?

zperk13, to NixOS
@zperk13@mastodon.sdf.org avatar

Trying out

I am getting very annoyed with the way it just imports everything

There's a reason we don't do "using namespace" or "use library::*" or "from library import *".

Ok I see a function here. Is it built in or imported? I have no idea.

Or if you somehow know it's not builtin, ok, but which of the 20 imported things is it from?

sandro,
@sandro@c3d2.social avatar

@zperk13 It's not weird, it's a run of the mill functional language and for most beginner things it doesn't even matter that it is functional.

The file doesn't know anything. Nix looks everything up through channels, flakes and then you have a high level wrapper which pulls everything together.

lib comes all from the lib directory in nixpkgs.

sandro,
@sandro@c3d2.social avatar

@zperk13 Even if it would have a FHS layout, things wouldn't always work out of the box and if you really need one, it can be emulated with a fhs env.

sandro,
@sandro@c3d2.social avatar

@zperk13 It doesn't. There a few keywords and everything else is either in builtins or in lib. lib is split into multiple sections but everything is also directly available under lib. and mostly those sections are not used and implementation details.

That people overuse with lib is slowly worked on to be removed.

xenya52, to NixOS German
@xenya52@chaos.social avatar

Für mich persönlich ist schwer verständlich…

sandro,
@sandro@c3d2.social avatar

@xenya52 Was genau?

Häufig ist man mit fd und rg gut beraten und findet sehr schnell was man sucht, weil es eben nicht über tausende kleine repos verteilt ist und man wissen muss in welchem man jetzt genau suchen muss.

jbzfn, to NixOS
@jbzfn@mastodon.social avatar

:owi: Lix, a community run fork of CppNix and an implementation of the Nix language
➥ @lix_project

「 Lix is developed by a diverse group of users – and accordingly is committed to providing a space that’s safe for users and developers typically underrepresented in technical projects. We take moderation seriously, and are committed to preventing bad actors from driving out marginalized groups 」

https://lix.systems/

#lix #nix #nixos #opensource

sandro,
@sandro@c3d2.social avatar

@jbzfn it's a fork, not an implementation. Tvix is an implementation.

mir, to random

NixOS use lisp for config files [search]

sandro,
@sandro@c3d2.social avatar

@mir that's guix

sandro, to NixOS
@sandro@c3d2.social avatar

If you are testing all the experimental features, you also need to create PRs from time to time.
https://github.com/NixOS/hydra/pull/1377 fixes .doi resolution in hydra on the latest version.

#NixOS

baer, to NixOS

can someone help me with what i should expect from the
services.xserver.virtualScreen option.
From the source code I gather that it just appends

"Virtual ${toString cfg.virtualScreen.x} ${toString cfg.virtualScreen.y}"}

to the monitor section
but what does that do? I don't know enough about x11 and the docs are not really helping me...
thanks

sandro,
@sandro@c3d2.social avatar

@baer That's the x and y of the virtual screen.
The example will turn into

"Virtual 2048 2048"

tcurdt, to NixOS
@tcurdt@mastodon.social avatar

After using NixOS, the whole container ecosystem feels like holding it wrong.

I can no longer un-see it 🫣
I am doomed.

sandro,
@sandro@c3d2.social avatar

@tcurdt same

publicvoit, to ubuntu
@publicvoit@graz.social avatar

I AM SO DISAPPOINTED WITH UBUNTU 24.04 😡
https://news.itsfoss.com/ubuntu-24-04-disappointment/

I'm so glad that I got rid of (actually ) and .

Now, I need to get rid of as well, despite having invested (too) much effort. 😞

is my true and only safe heaven, as it seems.

sandro,
@sandro@c3d2.social avatar

@publicvoit Debian doesn't offer that majority of software I use out of the box and using out of tree sources is usually up for upgrade disaster.

And if I need to use containers, then I might as well use something which focuses on that.

jakehamilton, to NixOS
@jakehamilton@hachyderm.io avatar

I like , I do not like what has happened to it. is an incredible technology and it deserves better. Nobody else has started the process so I guess I have to be the one to do it. We are forking. I would rather try and fail alongside all the people who love Nix but were pushed away from the project than give up.

https://aux.computer/

sandro,
@sandro@c3d2.social avatar

@soupglasses @jakehamilton Well, technically there is already a loose grouping. Everything going into the stdenv is absolute core and anything requiring to go to staging could also be classified important. All packages that are just one rebuild, are leaf packages and sometimes can be considered for fun.

18+ hexa, to NixOS
@hexa@chaos.social avatar

What a week, huh?

sandro,
@sandro@c3d2.social avatar

@hexa It's only Wednesday Monday captain.

pimeys, to NixOS
@pimeys@social.nauk.io avatar

Thank you for the TPM2 article @jnsgruk. I decided to give it a go last weekend, and it was a bit longer process than 10 minutes. For anybody who struggle to get rid of the password prompt for the LUKS volume, this setting is essential:

boot.initrd.systemd.enable = true;

The initrd must have systemd installed, so the settings defined with systemd-cryptenroll are available during the boot. Alternative way is to use Clevis to encrypt the LUKS password using the TPM module, and invoke it during boot. This is not super complex either, but I kind of like the systemd approach more.

Also the article didn’t mention much about the different PCR ids you can use with TPM. These define the system state when a secret key can be accessed from the TPM module. If any of the policies trigger, the TPM module will not output any secrets and the user needs to enter the LUKS password. The article uses three policies:

  • 0: firmware updates
  • 2: extended ROMs from pluggable hardware (e.g. USB)
  • 7: secure boot disabled, or firmware certificates update

Additionally, one policy is needed to ensure an attacker cannot boot the system to a single user mode from the bootloader:

  • 12: kernel config change, e.g. changing the boot parameters.

It is important to wipe the old slots with systemd-cryptenroll when changing the PCRs. Changing them is additional, and doesn’t modify the existing policies.

Edit: and do not wipe the password slot! This will render your disk unbootable.

sandro,
@sandro@c3d2.social avatar

@pimeys @jnsgruk Did you find documention on the numbers you can turn on and off? I briefly looked and didn't find anything.

Having to enter the password with almost any configuration change, including plugged in USBs makes me almost want to try it.

sandro, to random
@sandro@c3d2.social avatar

It is always DNS 😅

One of the domains I manage has flaky results with Quad 9 because one of the nameservers it uses has a wrong glue record set for its own nameservers.

astrid, to random
@astrid@fedi.astrid.tech avatar

what nix fork projects currently exist, im curious

sandro,
@sandro@c3d2.social avatar

@dieweltist @astrid Guix has it's roots in NixOS but I would consider it a standalone project by now.

danvolchek, to linux
@danvolchek@mastodon.social avatar

Declarative operating systems sound really neat - I'd love to be able to configure my system + applications through files.

Unfortunately, I'm not interested in Nix because of how Dolstra is handling the current community outcry. Ideally I'd like to stay on Arch, too.

Does anyone know what the current options are? Are any of them as maintained/supported/documented as Arch itself?

Arch has been great, btw!

sandro,
@sandro@c3d2.social avatar

@danvolchek I think I am to knee deep into NixOS to be able to use an imperative distro in large scale again.

soupglasses, to NixOS
@soupglasses@hachyderm.io avatar

I think the most hurtful thing with seeing in flames and people leaving for other immutable distros is...

NixOS was strong for its module system, not so much its immutable nature.

The rapid development you could do, and test that locally, sewing together an entire fleet in a matter of hours, without much of a thought to the minor details was amazing.

Lets remember to take the NixOS module system with us.

sandro,
@sandro@c3d2.social avatar

@soupglasses I am not sure if there is anything like it for the module system though.

ivan, to random
@ivan@hachyderm.io avatar

Maintaining software sometimes feels like rolling a rock up a hill for all eternity.

Other times, the rock is actually a pile of sand

sandro,
@sandro@c3d2.social avatar

@ivan I mean if you're at least get paid well to push up the sand. It kinda makes it bearable for some time.

And eventually you find a way to automate at least something

mart_w, to php German
@mart_w@chaos.social avatar

As fixes for the current and are not reliably available yet, keep in mind that a workaround exists for those of you who don’t need support for the ISO-2022-CN-EXT character set: https://rockylinux.org/news/glibc-vulnerability-april-2024/

This should be quite straightforward to apply on most machines – except those running . If you do use NixOS, my solution might help you bridge the gap until the proper fix is upstream: https://git.brokentech.cloud/mart-w/nixos-workaround-cve-2024-2961

Thanks @hexa for pointing me in the right direction!

sandro,
@sandro@c3d2.social avatar

@mart_w No, not really. Maybe we could supply Hydra with the configuration without this setting and only apply it when deploying. This should easily be possible.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • Leos
  • tsrsr
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • hgfsjryuu7
  • Youngstown
  • InstantRegret
  • slotface
  • khanakhh
  • rosin
  • ngwrru68w68
  • kavyap
  • PowerRangers
  • normalnudes
  • tacticalgear
  • cisconetworking
  • everett
  • vwfavf
  • GTA5RPClips
  • osvaldo12
  • Durango
  • mdbf
  • modclub
  • tester
  • cubers
  • ethstaker
  • anitta
  • All magazines
    •