| 18 Nov 2024 |
|  Jean joined the room. | 16:27:00 |
| 19 Nov 2024 |
|  LEGO® Worm™ changed their display name from Federico Damián Schonborn to LEGO® Worm™. | 01:05:56 |
|  khartahk joined the room. | 17:57:22 |
|  Diamond (it/she) changed their profile picture. | 21:15:57 |
| 20 Nov 2024 |
|  inayet removed their profile picture. | 00:59:18 |
|  Kamilla 'ova joined the room. | 12:53:34 |
| 21 Nov 2024 |
|  NikolayTach changed their profile picture. | 01:23:12 |
|  Jason Odoom changed their profile picture. | 02:51:38 |
|  howlymowly joined the room. | 22:18:56 |
| khartahk | Hey, if anyone can point me to some docs that would explain to me how can I trim the NixOS installation to as little as possible I'd really appreciate it. Or if someone can share a configuration.nix that basicaly just installs the bare minimum. I'm trying to see if it's possible to install and run NixOS (as a server so no GUI) on 512MB. Any help would be greatly appreciated. | 23:46:04 |
 emily | 512 MB is not likely to be a pleasant experience, I would recommend using something else. | 23:49:43 |
| 22 Nov 2024 |
|  ice9 joined the room. | 00:39:39 |
|  Noa joined the room. | 06:41:07 |
| khartahk | The other option is to swap the drive that's embedded with a larger USB Stick. Which is doable but I'm just trying to see what can be done. It would probably not run much perhaps a SAMBA/NFS share or even that perhaps could utilize zfs to do that. Unless zfs would consume to much space then I'd opt for a mdadm style raid or something like that. Is there a way I could perhaps just boot NixOS from the drive then run it all from memory? | 08:38:33 |
 K900 | Wait | 08:40:08 |
| K900 | 512MB disk | 08:40:11 |
| K900 | Or 512MB memory | 08:40:13 |
| K900 | If it's 512MB disk, and you have a network, just netboot? | 08:40:26 |
| khartahk | It's disk and I want this to be a self sufficient NAS for backups which won't have a network drive available to boot from that. | 08:56:10 |
| khartahk | Memory is 2GB | 08:56:27 |
| K900 | Uhh | 08:58:02 |
| K900 | And you can't use anything bigger than 512MB? | 08:58:08 |
| K900 | Maybe you can do some sort of squashfs thing then | 08:58:14 |
| K900 | Because like, if you're going to be updating it, ever, you'll need double the disk space in case of staging merges | 08:58:31 |
| K900 | Which means 256MB per config | 08:58:40 |
| K900 | Not accounting for any data | 08:58:44 |
| khartahk | data would live on 2 hdds. It's just the OS and the services required for it that would live on that drive. I'm guessing someone has done something like this before. My duckduckfoo is just to week to find it :) And yes you are right. I guess the best approach would be:
- minize the install as much as possible
- use squashfs to compress it
- set it up to boot and uncompress that (perhaps even set it to me ran directly from memory)
- ...
Not sure how to achieve all that seems quite daunting as I haven't dabbled in doing something this complex. I guess I need to start at step 1. and first figure out how to make the size as small as possible. Let's for now just say that is my objective. How to change configuration.nix to use as little space as possible.
| 09:04:46 |
| K900 | It really depends on how badly you want to fuck things up | 09:06:41 |
| K900 | You can override basically anything | 09:06:45 |
| K900 | But the more you override, the further from a supported configuration you are | 09:07:40 |
