| 22 Nov 2024 |
 Gerd Flaig | Having a slice with the OS on the drives doesn't hurt - you can still put the disk into another box to recover the data. Should have backups anyway. ;) | 16:45:13 |
| Gerd Flaig | * Having a slice with the OS on the drives doesn't hurt - you can still put the disks into another box to recover the data. Should have backups anyway. ;) | 16:45:28 |
| Gerd Flaig | Since you mentioned it's a Qnap box - IIRC they're doing exactly like this. That's why they can get away with such a tiny boot device. | 16:46:27 |
| Gerd Flaig | * Since you mentioned it's a Qnap box - IIRC they're doing it exactly like this. That's why they can get away with such a tiny boot device. | 16:46:40 |
 khartahk | That is also true, I just prefer it that way. Probably coz of something I read regarding ZFS and that it need the entire drive etc ... which I know is not true but I kinda just stuck with that as it mitigates the chance of me accidentaly format the wrong drive. Especialy if the OS drive has a totaly different naming schema like nvme or something :) | 16:47:08 |
| Gerd Flaig | Fair :) | 16:47:56 |
| Gerd Flaig | At this time, it seems mostly a trade-off between requirements and time-to-working-solution. | 16:49:01 |
| khartahk | The time I have - it can wait a bit, the problem I think is I try to over-complicate things that I want to simplify. I want to move as much stuff as I can to nix because of it's declarative nature and that way I don't have to have some special backup for the config. Perhaps for this device it's easier and more cost efective to just use Unraid and have the config be backed up in another manner. Coz Unraid does everything I need: boots from usb 2 quite fast, runs in memory and does not use a lot of it so even those 2GB of ram available in here are mostly free for me to deploy some services. | 16:56:00 |
| Gerd Flaig | Side note: Since you mentioned using ZFS, IIRC that can use a lot of memory, especially when enabling deduplication. | 17:00:52 |
 ryantrinkle | Yeah generally deduplication is not recommended unless you are in a very special circumstance | 17:02:05 |
 magic_rb | Zfs without dedup eats memory because of ARC, the solution there is to tel zfs to keep minimum of X GB free, so that other software doesnt think its under constant memory pressure | 17:04:12 |
| magic_rb | (ARC is the zfs equivalent of the page cache on linux) | 17:04:38 |
|  Jakob Schöttl set their display name to Jakob Schöttl. | 18:10:33 |
|  BigBabyThor joined the room. | 18:47:46 |
|  @tanvir:hackliberty.org joined the room. | 20:14:30 |
| 23 Nov 2024 |
|  earthwalker31 joined the room. | 09:45:24 |
 ehrenschwan | Hi, I'm working on an automated update of my flake inputs and then remote switch of all my servers. I'm using a systemd service with a timer to run a script on my desktop workstation which i always leave on to update the input, test the builds using build-vm and then switching the config on the servers. I would also like to switch the config of my workstation but the switch stops the systemd service which then stops the switch, does anyone here have a similar setup and a solution to that problem? I'm thinking a cron job instead of systemd timer would maybe do it, but the wiki says it's recommended to use a systemd timer and I would prefer this for the journalctl logs. | 12:25:57 |
|  startswithbalint joined the room. | 20:48:52 |
| 24 Nov 2024 |
|  Lzebulon joined the room. | 00:41:11 |
| 25 Nov 2024 |
|  Sefodopo joined the room. | 07:12:52 |
|  Noa changed their display name from Noa Aarts to Noa. | 07:44:04 |
|  soywod joined the room. | 08:54:54 |
| soywod | Hi 👋
How reliable is Nix for building release binaries targeting non-Nix systems?
I try to use Nix inside my CI for building (and cross-building) release binaries. People who download such binaries are mostly non-Nix users. I'm facing issues and dilemna with both static and dynamic linking:
- Static builds improve portability, but only on Linux. On MacOS it looks like it's not possible to fully statically link, and on Windows (via cross-compilation) it's a pain to make it work.
- Dynamic builds need to be ELF-patched due to interpreter pointing to
/nix/store, but I'm not sure how reliable it is for MacOS and Windows (versus native builds). If the CI builds a dynamically-linked release for MacOS, does a non-Nix user will be able to use it properly?
| 09:06:58 |
 elikoga (@38c3 📞488{0,1}) | https://github.com/hsjobeki/nixpkgs/blob/migrate-doc-comments/pkgs/build-support/release/debian-build.nix
https://noogle.dev/f/pkgs/releaseTools/debBuild
https://wiki.nixos.org/wiki/Nixpkgs/Building_RPM_DEB_with_nixpkgs
This one gets you pretty far in one direction, not sure if it's the direction you want to go to | 09:11:38 |
 emily | we have static-enough linking for macOS | 09:13:43 |
| emily | libSystem will be dynamically linked, but that is true of all macOS binaries | 09:13:55 |
| emily | in general system frameworks are part of the OS and don't get statically linked | 09:14:05 |
| emily | as long as you use a deployment target corresponding to the minimum macOS version you support, pkgsStatic should work just fine (if there aren't packages it's broken with that you use) | 09:14:35 |
| emily | (current default minimum is 10.12 on x86_64-darwin and 11.0 on aarch64-darwin; in 25.05 it will be 11.3 across the board; in 25.11 it will be 14.x across the board) | 09:15:05 |
| emily | with macOS you can do relative rpaths and stuff, but generally we use absolute ones. it's possible that install_name_tool will let you patch them up enough for it to work. there's various scripts out there for copying dylibs into .app bundles and rewriting the paths appropriately; perhaps you could use one of them | 09:15:57 |
