I need to generate a number of scripts in my configuration and make them into a single package (for ease of reference, because there are a lot of them).

So far, I'm creating the scripts via writeShellApplication, making them into packages via an overlay, merging them with buildEnv and then adding the resulting package to `systemPackages.

Something like:

````nix nixpkgs.overlays = [ (final: prev: { my-hello-1 = final.writeShellApplication { name = "my-hello-1-script"; text = "echo my hello wolrd 1"; }; my-hello-2 = final.writeShellApplication { name = "my-hello-2-script"; text = "echo my hello wolrd 1"; }; my-hello-scripts = final.buildEnv { name = "my-hello-scripts"; paths = [ final.my-hello-1 final.my-hello-2 ]; }; }) ];

environment.systemPackages = [ pkgs.my-hello-scripts ]; ````

This works, but I don't really need the my-hello-1 and my-hello-2 packages... can you think of a way to make do without needing them?

I'm migrating my NAS to nixos, and I got to the point of setting up my restic backups.

services.restic.backups is great, but -- on top of the systemd timers/services -- I also want some helper scripts (eg. one to easily mount the backups, stuff that with ansible I currently generate into /usr/local/sbin).

These scripts would be entirely generated from the services.restic.backups config and would reference sops secrets also from configuration.nix, so... I don't think it would make sense to make a package out of them?

What should I use to make these scripts? Should I use nixpkgs.writeShellApplication and then alter the PATH?

I've been searching for a way to do this, but I haven't found anything. After I have refactored my Home Manager configuration is there a way I can test the changes in a shell before I switch?

From what I understand the next-best option is to switch, and then find and run the activate script of the previous generation to switch back.

I was configuring DWM, among other things, for the last 3-4 days, and every single rebuild switch caused a new generation to appear. There were too many Systemd-boot entries so they couldn't even fit on the screen and continued down to Gen 41. It's just crazy.

Edit: This post: https://feddit.uk/post/1454174 shows the rest of the boot entries

Im just starting out in my nixos journey. This thought came to me in the shower: would nixOS lend itself for a phone OS?

I couldn't find a nix community, so I'm hoping it is ok that I'm posting on the nixos one instead. I'll switch to mailing list/discord if necessary, but I have a lemmy app on my phone, and it is much easier to have an ongoing conversation from here, so I decided to give it a shot. Here goes!

While I have a NixOS laptop, I primarily use other systems (e.g. OpenSuse Tumbleweed) as of now.

I love the ability to define the packages I want installed, with home-manager managing my command line utilities (e.g mtr, dig, protobuf etc).

I've been playing around a bit with protobuf recently, and after generating some c++ code using protoc, I loaded up the generated code in vscode, which understandably wasn't able to find the development headers for protobuf (since they are in the nix store - /nix/store/h2h5fs8iv2a8rmlkfhr6id6y4jxwd5i1-protobuf-3.21.12/include/google/protobuf/io)

I tried to compile the code anyways on the command line, and got some errors.

I might need an OS specific protobuf install just for the development headers, but I'm pretty sure I should be able to, and just don't know how. Here's what I get when I try to compile:

$ g++ searchReq.pb.cc In file included from searchReq.pb.cc:4: searchReq.pb.h:10:10: fatal error: google/protobuf/port_def.inc: No such file or directory 10 | #include | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated.

Any tips/pointers would be appreciated. Thanks in advance!

===========================================

Edit: Thank you all, particularly @Xephopiqua@lemmy.ml and @chayleaf@lemmy.ml for the help. After setting the include path (compile) and LD_LIBRARY_PATH (link), things work great.

I ended up writing a small Makefile for convenience in the short run:

```Makefile INC_FLAGS:=-I$(HOME)/.nix-profile/include -Icpp LD_FLAGS:=-L$(HOME)/.nix-profile/lib -l protobuf

run: task LD_LIBRARY_PATH=$(HOME)/.nix-profile/lib ./task

task: g++ $(LD_FLAGS) $(INC_FLAGS) main.cpp cpp/searchReq.pb.cc -o task

regen: protoc --python_out=python --cpp_out=cpp searchReq.proto ```

That's enough to get me going for now.

TODO - read up the NIXOs Wiki C page in more detail

I have a personal source project I created a shell.nix file for. However, in the project I have also scripts I want to execute periodically non-interactively. Could I use the nix-shell shebang pointing to shell.nix file in order to have the same programs when I use nix-shell interactively and when I launch the scripts?

First of all, I'm completely new to Nix and I have no idea what I'm doing. I would like to use it initially as a more general purpose replacement of conda environments for my AI-development workflow. To begin with, I'd like to install nix package manager at my work server where I don't have root access. I tried

sh <(curl -L https://nixos.org/nix/install) --no-daemon

however it tries to create /nix which I cannot do without sudo. I searched everywhere, but I don't seem to find a way to circumvent this.

Thanks!

I've been messing around with nix flakes to configure my NixOS system and to put the final touches on I wanted to write an overlay of Neovim with the plugins and everything configured with Lua and then use this overlay to install neovim-qt. After reading various docs on Overlays, I get the fundamentals but I don't get where to look to find a list of all the configurable options that an overlay provides? Typically I can look in the home-mananger nix decleration of a package for the options exposed or nixpkgs for the options in configuration.nix. Any help that will dive deeper into overlays or where to find their options would be greatly appreciated!

I've been hopping around Gentoo and Void the past few days with musl on both, and I'll be going back to NixOS in a bit due to not having enough time to set up either of them. I've realised how little RAM either systems use on musl, though, and I was wondering if there is any chance of replacing glibc with musl on NixOS?

I've found a few guides but most of them or hard to understand or poorly written, I've done pass trough on proxmox and Arch Linux.

I tries this guide but no luck

https://astrid.tech/2022/09/22/0/nixos-gpu-vfio/

I'm trying to build my first nix package out of the Kana project. My `default.nix' file is below.

When I try to build the application nix tries to fetch https://github.com/ChrisWiegman/kana-cli/archive/v0.10.1.tar.gz which gives a 404. How do I get nix to download the release .tar.gz file to build the application?

``` { lib , buildGoModule , fetchFromGitHub , makeWrapper , go }:

buildGoModule rec { pname = "kana-cli"; version = "0.10.1";

src = fetchFromGitHub { owner = "ChrisWiegman"; repo = "kana-cli"; rev = "v${version}"; hash = ""; };

vendorSha256 = null;

This is required for wrapProgram.

allowGoReference = true;

nativeBuildInputs = [ makeWrapper ];

postFixup = '' wrapProgram $out/bin/kana-cli --prefix PATH : ${lib.makeBinPath [ go ]} '';

meta = with lib; { homepage = "https://github.com/ChrisWiegman/kana-cli"; description = "WordPress Stuff"; license = licenses.gpl3; maintainers = with maintainers; [ curtismchale ]; }; } ```

Is anybody using distrobox on NixOS to develop and run software? What are your thoughts on using it?

I feel like it's a huge time saver and makes the use of NixOS easier for beginners. Instead of spending an afternoon or a few days trying to compile or run something using nix, you can spin up a box and seamlessly do your development there. This makes prototyping and testing things out way easier before investing a bunch of time trying to nixify it.

This is more of a personal dilemma, since I keep finding myself switching back and forth between NixOS and Gentoo every now and then. I've done this twice for each so far ever since I immediately started off my Linux journey with Gentoo, making a quick stop at Arch once when I didn't have enough time to set either of them up properly. Both of them provides a massive amount of control over my system and lets me build my system in weird and interesting ways, e.g. musl, clang, and/or SELinux for Gentoo and impermanence for NixOS (it still kind of blows my mind right now). Personally, I find Gentoo more intuitive, but NixOS is more powerful for managing complex systems, but then again, I don't have any complex systems to manage, only a singular desktop system. I'd love to keep switching back and forth, but I feel like it has become sort of a time sink for me, somewhat hindering my studies, and thus I feel the need to decide which one to settle on, and which one to keep in a VM to mess around with. That brings me to the title of the post, which do you think is better for a simple desktop system? Also, I don't know how viable dual booting is, given that I manage my dotfiles almost entirely with home-manager, and I like to have secure boot.

I was looking at ryan4yin's new NixOS book and stumbled upon nixpak, a neat project that , as far as I understand, acts like a sandbox for Nix packages, similar to Flatpak. I've been wanting to try using it for myself, but haven't found any dotfiles I could steal from use as a references. If anyone uses this, I'd love to hear how, and what your experiences are with it.

I don't quite understand how to set up AppArmor on NixOS, and I can't seem to find anyone's dotfiles which has AppArmor configurations. Is AppArmor support not a thing on NixOS, or is it just configured the regular way and not declaratively?

I've seen a lot more people start to use Lanzaboote for secure boot recently, and I want to try it myself. However, I have a ZFS fiesystem, and I've heard that you can't do secure boot on ZFS, and the ZFS wiki itself says that you need to disable secure boot or the ZFS kernel module won't load. I'm planning on moving my root to tmpfs for impermanence tomorrow anyways, but my home will still be on ZFS. I'm not too knowledgeable in these areas, but I can't see why I can't just sign the ZFS kernel module. Anyone has secure boot on ZFS? I'd like to hear your thoughts on this.

What I've done is installing

xdg-desktop-portal libsForQt5.xdg-desktop-portal-kde libsForQt5.kdialog

and adding

``` xdg.portal.enable = true; xdg.portal.extraPortals = [ pkgs.libsForQt5.xdg-desktop-portal-kde ]; environment.sessionVariables.XDG_CURRENT_DESKTOP = "kde";

```

to my configuration.nix, but while I do get the qt file picker on my web browser, the theming is broken and it looks like this

!

I currently handle my theming through qt5ct with the line environment.sessionVariables.QT_QPA_PLATFORMTHEME = "qt5ct"

GitHub Repository: https://github.com/nix-community/nix-init

Diff: https://github.com/nix-community/nix-init/compare/v0.2.3...v0.2.4

Here is the full changelog for v0.2.4:

Features

• Go: support dependency inference
• Rust: improve dependency inference for the following crates: alsa-sys, curl-sys, gtk-sys, gtk4-sys, librocksdb-sys, llvm-sys
• Go: improve ldflags formatting
• Add nix and nurl to runtime with environment variables instead of relying on a wrapper

Changes

• Drop support for nixpkgs 22.11

Fixes

• Rust: use cargo and rustc instead of rustPlatform.rust.cargo and rustPlatform.rust.rustc
• Python: fix pythonImportsCheck
• Python(pyproject): default build-system.requires to setuptools
• Fix interaction with showAliases = false on nixpkgs 23.11 (#153)

https://github.com/nix-community/nix-init/compare/v0.2.3...v0.2.4

I've been reading some articles regarding impermanence in NixOS, particularly this, this, this, and this, and I want to set up impermanence on my desktop system. Since it involves deleting my entire root, however, I figured I'd ask for advice here to learn what the best practices are for doing this to minimise risk of data loss, though it isn't too critical since it's a new setup. For reference, I have a Flake + home-manager setup on ZFS root, though I didn't think to do a snapshot when the disk was empty since I didn't know about impermanence when I started out. I also have separate ZFS datasets for /, /home, /nix, /var, and /var/lib. I want to set up impermanence for both root and home, with some persistent directories on home, but I'm not sure if I should set it up on both at once or if I should do root first and then home. Any advice or help is appreciated!

My Chromebook is now end of life so I turn to FOSS. I'm excited for the opportunity to shed the crummy Linux VM (crostini) as well. Anybody tried installing NixOS on a Chromebook? Is it possible, how much trouble did it give you?

I've been using NixOS for a year now, and recently switched to flakes,

So after being a long-time Fedora/RHEL/CentOS/Rocky/etc user, I finally decided to give NixOS a try after the recent RHEL news.

And BOY and I blown away. You can do so much more than I thought possible with automation on NixOS. It's incredible!

Since I"m so new, I do have a question for you all: What's your go-to resource for learning Nix/NixOS?

Thanks!

Hi, I'm new to nix and NixOS and would like to try out the package manager first on a different host OS (I use OpenSUSE Tumbleweed). I want to build KDE Plasma desktop in its own nix environment isolated from the rest of the system and be able to launch a graphical desktop session (requires integration from systemd and d-bus). Do you think that should be possible with nix?

I'm new to Nix and wanted to get my feet wet by using the Nix package manager. However, I wasn't sure how these packages were made. Are these packaged by the community? Who do I need to "trust" when installing these packages? In general, I was looking for info on how nix packages are made and maintained.

Example config linked in readme! My ISP doesn't offer IPv6, so it might not fit your use case well, but it's a setup with multiple routing tables (one for vpn, one for direct internet access, one for no internet access)+multiple network namespaces (default namespace has the vpn interface, wan namespace has the vpn socket)+configured dnat/port forwarding which is hard to get right in such setups. It also takes port forwarding rules from another system's config, which was always my dream before even starting this project lol

"framework" is really the right choice of words because while it's well integrated with itself, it forces you to use itself, it doesn't integrate with networking.interfaces because it itself is a more featureful variant of networking.interfaces.

In my experience, this let me focus on writing the router itself, while previously half the time I felt that NixOS just doesn't provide enough customizability for routers. However, I don't offer many features right now, only device config/network namespace management/bridge creation/veth pair creation/dhcp/router advertisement/wireless access point creation. Obviously, there are many cases for which this won't be enough. If this isn't enough for you, open an issue and I'll try to add what you want (or better yet, do it yourself, as I probably wouldn't be able to test it).

I'm trying to set up Lutris to play games with Wine. I don't understand how I am supposed to install wine runners? Can anyone help?

Edit:* It seems the answer is to install runners through the Lutris UI as usual. The Lutris package runs in an FHS which makes everything work even though the runners are not built for NixOS.

It turns out that what I was missing (I think) was 32-bit DRI support. I enabled that with these lines in my NixOS configuration:

```nix

in /etc/nix/configuration.nix

hardware.opengl = { driSupport = true; driSupport32Bit = true; }; ```

Everything below this edit is red herrings.

/end of edit*

I tried installing a runner, lutris-GE-Proton8, through Lutris itself as I do in another distro. That crashed with some sort of error - instead of spending time investigating that I thought I'm probably supposed to install things the Nix way so that dependencies are set up correctly.

I tried installing Wine from nixpkgs like this, and configuring Lutris to use the system Wine:

home.packages = with pkgs; [ (lutris.override { extraPkgs = lutrisPkgs: [ wine ]; }) ];

But when I start up a game I get a warning telling me that I need a version of Wine with esync.

I found a Nix expression for wine-ge in the nix-gaming repo. So I tried building Lutris with that. Here is an excerpt of my Home Manager flake.nix:

{ inputs = { # ... nix-gaming = { url = "github:fufexan/nix-gaming"; inputs.nixpkgs.follows = "nixpkgs"; }; };

outputs = { nixpkgs, home-manager, nix-gaming, ... }: let system = "x86_64-linux"; pkgs = nixpkgs.legacyPackages.${system}; in { homeConfigurations."jesse" = home-manager.lib.homeManagerConfiguration { # ... modules = [ ./home.nix # ... ]; extraSpecialArgs.inputs = { inherit nix-gaming; }; }; }; }

And the my attempt at a Lutris config in home.nix:

home.packages = with pkgs; [ (lutris.override { extraPkgs = lutrisPkgs: [ wine inputs.nix-gaming.packages.${pkgs.system}.wine-ge ]; }) ];

After a great deal of compiling I believe that I have wine-ge installed... somewhere. (I did try to use the nix-gaming binary cache. I probably messed that up by forcing my version of nixpkgs. I'll probably let nix-gaming use its own nixpkgs version next time.)

I've read that the lutris package creates an FHS (Filesystem Hierarchy Standard) environment. That is a filesystem somewhere with the directory layout you see in other distros. I expected that wine-ge would be linked into the FHS somewhere. I had the thought that I would configure Lutris with the path to wine-ge. But the file browser that I get in Lutris seems to show me the host file system, not the FHS.

I thought that maybe I could give Lutris the store path to wine-ge. Then if when I upgrade I'll have to track that down and set the path again. Is there a better way?

i use arch (btw), and i hate how much i depend on the AUR, its very unstable. I switched to flatpak for my gui programs since the cli experience sucks. nix on the other hand works like a native package manager, and thats great for me. but i see that nix also includes stuff like coreutils (because of nixos im guessing). do i install everything with nix? if not what packages do i install with pacman and which with nix?

I use agenix for managing some secrets on my nixos-configs. Agenix deploys the unencrypted secrets in the live system, so the secrets cannot be accesed when evaluating the nixos config.

Do you know any way or hack to have secrets inside of nix expressions?

It would be great if that solution would be pure and compatible with nix flakes.

Thanks :)

Honestly I don't know why I made this, it clearly isn't worth it lol (Jesus, 5000kloc for this), but it was interesting to learn more about nftables (I also found a bug in Nix in the process). I will contribute to nftables docs some time later, as I found many undocumented or poorly documented parts, and some documentation that's flat out wrong.

Currently this can only export rules in json, but it shouldn't be too hard to write a transpiler into the nftables language.

Note: these are not my first impressions, that's just the blog's title. I came across the post and thought it was interesting and you all might too :)

Hello, does anyone know about how to run a kbin instance on NixOS? Will the steps on https://codeberg.org/Kbin/kbin-core/wiki#admin-guide (but replacing the apt installs with adding packages in configuration.nix) just work, or is there a better, more reproducible way?

Thanks.

EDIT: I meant a kbin instance, not lemmy.

I was looking to manage my server through Cockpit project.

I would like to also be able to use cockpit-machines to manage VMs on my server. However, that module is not present in nixpkgs.

I know how to deploy simple-ish packages, however, JS based projects seem a bit complicated.

https://github.com/cockpit-project/cockpit-machines

Could you suggest a starting point with this project? Any similar modules I can refer to?

cross-posted from: https://beehaw.org/post/551377

> Recently my kernel started to panic every time I awoke my monitors from sleep. This seemed to be a regression; it worked one day, then I received a kernel upgrade from upstream, and the next time I was operating my machine it would crash when I came back to it. > > After being annoyed for a bit, I realized this was a great time to learn how to bisect the git kernel, find the problem, and either report it upstream, or, patch it out of my kernel! I thought this would be useful to someone else in the future, so here we are. > > Step #1: Clone the Kernel; I grabbed Linus' tree from https://github.com/torvalds/linux with git clone git@github.com:torvalds/linux.git > > Step #2: Start a bisect. > > If you're not familiar with a bisect, it's a process by which you tell git, "this commit was fine", and "this commit was broken", and it will help you test the commits in-between to find the one that introduced the problem. > > You start this by running git bisect start, and then you provide a tag or commit ID for the good and the bad kernel with git bisect good ... and git bisect bad .... > > I knew my issue didn't occur on the 5.15 kernel series, but did start with my NixOS upgrade to 6.1. But I didn't know precisely where, so I aimed a little broader... I figured an extra test or two would be better than missing the problem. 😬 > > > git bisect start > git bisect good v5.15 > git bisect bad master > > > Step #3: Replace your kernel with that version > > In an ideal world, I would have been able to test this in a VM. But it was a graphics problem with my video card and connected monitors, so I went straight for testing this on my desktop to ensure it was easy to reproduce and accurate. > > Testing a mid-release kernel with NixOS is pretty easy! All you have to do is override your kernel package, and NixOS will handle building it for you... here's an example from my bisect: > > > boot.kernelPackages = pkgs.linuxPackagesFor (pkgs.linux_6_2.override { # (#4) make sure this matches the major version of the kernel as well > argsOverride = rec { > src = pkgs.fetchFromGitHub { > owner = "torvalds"; > repo = "linux"; > # (#1) -> put the bisect revision here > rev = "7484a5bc153e81a1740c06ce037fd55b7638335c"; > # (#2) -> clear the sha; run a build, get the sha, populate the sha > sha256 = "sha256-nr7CbJO6kQiJHJIh7vypDjmUJ5LA9v9VDz6ayzBh7nI="; > }; > dontStrip = true; > # (#3) `head Makefile` from the kernel and put the right version numbers here > version = "6.2.0"; > modDirVersion = "6.2.0-rc2"; > # (#4) `nixos-rebuild boot`, reboot, test. > }; > }); > > > Getting this defined requires a couple intermediate steps... > Step #3.1 -- put the version that git bisect asked me to test in (#1) > Step #3.2 -- clear out sha256 > Step #3.3 -- run a nixos-rebuild boot > Step #3.4 -- grab the sha256 and put it into the sha256 field (#2) > Step #3.5 -- make sure the major version matches at (#3) and (#4) > > Then run nixos-rebuild boot. > > Step #4: Test! > > Reboot into the new kernel, and test whatever is broken. For me I was able to set up a simple test protocol: xset dpms force off to blank my screens, wait 30 seconds, and then wake them. If my kernel panicked then it was a fail. > > Step #5: Repeat the bisect > > Go into the linux source tree and run git bisect good or git bisect bad depending on whether the test succeeded. Return to step #3. > > Step #6: Revert it! > > For my case, I eventually found a single commit that introduced the problem, and I was able to revert it from my local kernel. This involves leaving a kernel patch in my NixOS config like this: > > > boot.kernelPatches = [ > { patch = ./revert-bb2ff6c27b.patch; name = "revert-bb2ff6c27b"; } > ]; > > > This probably isn't the greatest long-term solution, but it gets my desktop stable and I'm happy with that for now. > > Profit! > >