Even if it’s subjective and reliant on the used hardware, if we had enough of these reports, they would become very valuable as patterns would inevitably show up.
But, I’m afraid we’re past the point in which you can reliably and vividly recollect the whole experience 😅.




Definitely the latter.
FWIW, you don’t have to choose the distro’s package manager. While it makes sense in most cases, it’s definitely not a requirement. And that’s where the
nixpackage manager comes in. Unbeknownst to some, you don’t have to be on NixOS to access it, simply because it’s probably already found in the repository of the distro you’re using. So, frankly, you can even expect that it’s well-supported.FWIW, containerfiles used in conjuction with
bootcto boot your OS from, do allow differentiation within a single containerfile; i.e. specific changes are only applied for the designated target. This is accomplished by virtue of a single containerfile being able to produce many (very) different container images to boot from. So, in short, other avenues exist andbootchappens to be one I know. Note thatbootcdoesn’t (necessarily) push you towards Fedora(-derivatives). Despite being very new (and perhaps somewhat experimental), Bootcrew does provide container images for other distros; some of which have already spawned multiple derivatives of their own. See e.g. Tartaria and XeniaOS.My 2 cents: if you’re interested in NixOS, just start out with installing
nixon any distro. And see where that takes you ;) !