| 5 Oct 2024 |
 K900 | The kernel would consider it an out of memory condition if it can't find a page to swap out | 15:41:05 |
| K900 | Which is why you can't just throw swap at your OOM problems and expect them to go away | 15:42:23 |
 ElvishJerricco | Philip: Huh, that's extremely odd; @rosscomputerguy:matrix.org was having a very similar issue in #users:nixos.org the other day | 15:43:30 |
| ElvishJerricco | OOMs on processes that weren't using much memory when the total used wasn't very high | 15:43:46 |
| ElvishJerricco | I think they found out it was some kernel tuning they had done that was the problem. But maybe that was wrong and the problem is somewhere in nixos? | 15:44:44 |
| ElvishJerricco | (also, that is an unbelievable amount of swap. Absolutely a waste lol) | 15:47:56 |
 Philip | In reply to @elvishjerricco:matrix.org
(also, that is an unbelievable amount of swap. Absolutely a waste lol) Yes, totally obscene... I have a 1 TB NVMe drive that I am not using for anything right now, so I thought I'd dedicate it to swap. But that'll be the first to go when I need more storage. | 17:24:41 |
 theelevated | I need to duplicate the same system over 30 school laptops with the same setup and settings everywhere. Would nixos be feaseable also considering every laptop need to be a little unique with hostname? | 21:43:56 |
 Scrumplex | In reply to @theelevated:matrix.org
I need to duplicate the same system over 30 school laptops with the same setup and settings everywhere. Would nixos be feaseable also considering every laptop need to be a little unique with hostname? I think it could be a great option here. Basically you could configure everything once and then just set different hostnames for different machines in separate configurations. You could then generate small disk images that you can then dd onto the drives while using the option boot.growPartition to expand the rootfs to the remaining size. | 21:51:51 |
| theelevated | In reply to @scrumplex:duckhub.io
I think it could be a great option here. Basically you could configure everything once and then just set different hostnames for different machines in separate configurations. You could then generate small disk images that you can then dd onto the drives while using the option boot.growPartition to expand the rootfs to the remaining size. does nix also shell bin commands? if I need want to have a elevated listener for a root ssh session and in the global file. | 21:53:56 |
| theelevated | In reply to @scrumplex:duckhub.io
I think it could be a great option here. Basically you could configure everything once and then just set different hostnames for different machines in separate configurations. You could then generate small disk images that you can then dd onto the drives while using the option boot.growPartition to expand the rootfs to the remaining size. * does nix also shell bin commands? if I need want to have a elevated listener for a root ssh session in the global file. | 21:54:12 |
|  magic_rb changed their profile picture. | 22:16:52 |
| 6 Oct 2024 |
|  raf joined the room. | 12:43:02 |
|  DerivationDingus changed their display name from bytebandit to DerivationDingus. | 19:43:20 |
| 7 Oct 2024 |
|  @memegames99:matrix.org removed their profile picture. | 00:05:36 |
| @memegames99:matrix.org removed their display name memegames99. | 00:05:47 |
| @memegames99:matrix.org left the room. | 00:06:01 |
 ˈt͡sɛːzaɐ̯ | In reply to @scrumplex:duckhub.io
I think it could be a great option here. Basically you could configure everything once and then just set different hostnames for different machines in separate configurations. You could then generate small disk images that you can then dd onto the drives while using the option boot.growPartition to expand the rootfs to the remaining size. I wonder, is there a more elegant way of doing this? If you build an image per system, you'll be compressing the same content a lot of times. I'd rather have one image, and an activation script that checks what mac addresses it can find on the system and then pics the hostname / activation script for the correct system. But that sounds brittle to set up. Are there any examples of doing this in a sane way? | 05:47:17 |
| ˈt͡sɛːzaɐ̯ | In reply to @theelevated:matrix.org
does nix also shell bin commands? if I need want to have a elevated listener for a root ssh session and in the global file. Your question is a little bit gibberish. Are you using some translation software? In any case: Yes, you can run sshd and add something to users.users.root.openssh.authorizedKeys.keys on all hosts, so you'll be able to ssh in as root and e.g. execute nixos-rebuild. | 05:48:39 |
|  @thunder:kotiboksi.xyz joined the room. | 08:28:15 |
|  mabh joined the room. | 10:19:59 |
 steveej | does anyone here happen to have a disko config for EFI boot with raid0 over two drives? | 11:34:23 |
| steveej | interesting, hetzner puts the EFI partition on a mdadm raid1 with their default debian installations. it seems they're doing something non-standard which is using "EFI System" as a partition type for a mdadm member:
/dev/nvme0n1p1 4096 528383 524288 256M EFI System
i'll see if disko supports creating such a layout
| 12:07:49 |
| steveej | snippet from lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 1.7T 0 disk
├─nvme0n1p1 259:2 0 256M 0 part
│ └─md0 9:0 0 255.9M 0 raid1 /boot/efi
| 12:08:23 |
 @adam:robins.wtf | Raid zero for efi? I hope you mean one, because what in the world…. | 13:23:48 |
| @adam:robins.wtf | Anyway there’s `boot.loader.grub.mirroredBoots` . I haven’t used it but would investigate if I was trying to have boot redundancy | 13:25:22 |
|  Sam Lehman changed their profile picture. | 14:24:40 |
| Scrumplex | I noticed today that one file in my Nix store was off. It is a YAML config file for frigate. I mounted the config file into an oci-container (using Docker, not Podman) using the following snippet:
virtualisation.oci-containers.containers."frigate".volumes = [ "${configFile}:/config/config.yml" ];
When comparing the contents of this store file with the store file I built locally it has version: 0.14 at the end of it. I assume this was added by Frigate.
I created a root shell in this container, installed a text editor but was unable to edit the file in anyway, as I would expect, so I am wondering if I am missing something here
| 16:54:48 |
| Scrumplex | I ran these inside of the container:
# ls -la /config/config.yml
-r--r--r-- 2 root root 2250 Sep 30 20:48 /config/config.yml
# chmod 644 /config/config.yml
chmod: changing permissions of '/config/config.yml': Read-only file system
| 16:56:05 |
| 8 Oct 2024 |
|  MonkCanatella joined the room. | 00:24:02 |
