17 May 2023 |
@elvishjerricco:matrix.org | mberndt: I'll take a look soon. Been feeling a little ill so I've been avoiding nixpkgs work for a couple of days | 13:34:40 |
@mberndt:matrix.org | In reply to @elvishjerricco:matrix.org mberndt: I'll take a look soon. Been feeling a little ill so I've been avoiding nixpkgs work for a couple of days Oh dear, I hope you get better soon! This isn't in any way urgent, so take whatever time you need | 17:29:33 |
19 May 2023 |
@nikstur:matrix.org | ElvishJerricco: isn't the stage 1 activation initrd-nixos-activation.service and the stage 2 activation nixos-activation.service ? | 13:47:32 |
@elvishjerricco:matrix.org | nikstur: .... yep. Got those names mixed up | 13:47:50 |
@elvishjerricco:matrix.org | you can tell I'm having a foggy week :P | 13:47:59 |
@elvishjerricco:matrix.org | but nixos-activation.service is a user service thing, not a system service thing | 13:48:49 |
@elvishjerricco:matrix.org | not relevant to repart at all | 13:48:54 |
@nikstur:matrix.org | Ah ok | 13:48:58 |
@nikstur:matrix.org | Is /etc set up in initrd-nixos-activation.service ? | 13:49:17 |
@nikstur:matrix.org | or in nixos-activation.service | 13:49:35 |
@nikstur:matrix.org | In reply to @elvishjerricco:matrix.org you can tell I'm having a foggy week :P No worries :D | 13:49:42 |
@elvishjerricco:matrix.org | nikstur: nixos-activation.service is started for each user when that user logs in. Each user has their own systemd instance that runs with their permissions, and that starts user units like nixos-activation.service | 13:52:39 |
@elvishjerricco:matrix.org | initrd-nixos-activation.service is a system service in stage 1 that runs the generation's activation script, which does things like setup /etc | 13:52:57 |
@nikstur:matrix.org | Right thanks | 13:53:46 |
@nikstur:matrix.org | I see how it doesnt make sense to order after nixos-activation.service then :D | 13:56:23 |
@nikstur:matrix.org | https://github.com/NixOS/nixpkgs/pull/232533 should be good to go then | 13:56:45 |
| Charles ⚡️ joined the room. | 22:28:36 |
@uep:matrix.org | Cool.. what's the use-case? Something like netbooting a disposable compute node with local ssd? | 23:58:16 |
20 May 2023 |
colemickens |
where the root partition is dynamically created and how is that achieved? is there an option you pass for the mount and systemd(-repart) will make it?
| 00:00:06 |
colemickens | *
where the root partition is dynamically created
and how is that achieved? is there an option you pass for the mount and systemd(-repart) will make it?
| 00:00:12 |
@elvishjerricco:matrix.org | think of e.g. nixos tests, where the root fs is created on boot | 00:01:07 |
@elvishjerricco:matrix.org | but imagine you want it in an actual partition table, probably with other partitions as well | 00:01:20 |
@elvishjerricco:matrix.org | the systemd folks tend to think of this in terms of an installation process that just creates an ESP and a /usr partition, and then everything else is set up by the boot process | 00:02:11 |
@uep:matrix.org | oh, on the same disk.. so a partially-constructed partition table and set of filesystems vs something like disk when building the disk image, all at once. | 00:18:17 |
@elvishjerricco:matrix.org | There's sort of a lot you can do with it | 00:18:57 |
@elvishjerricco:matrix.org | It's pretty flexible | 00:19:02 |
@uep:matrix.org | hm. It seems to me like shuffling the deck chairs of when things get done, compared to (say) resizing partitions on first boot | 00:20:29 |
@uep:matrix.org | but it is a more general version of that idea, so I suppose allows for more options | 00:20:55 |
@elvishjerricco:matrix.org | I don't really understand that analogy but ok :P | 00:21:31 |
@uep:matrix.org | old and not-really-busted: make a disk image with relevant partitions, as small as you can. Clone that, boot it, and expand the root fs to fill free space on first boot.
new systemd hotness: make a disk image with fewer relevant partitions, and free space. Clone that, boot it, and mkfs the root fs on first boot. | 00:24:55 |