Currently I have this similar use case, I have a PCI-E NVMe that is not
detected by BIOS (KGPE-D16 motherboard) so my plan was had a partition
for /boot in my SSD and the root system in the NVMe, so could be great
have support to that user case that I think is pretty common in old
board that
Ludovic Courtès skribis:
> It goes OK until building
> /gnu/store/6rfaqfq693vda59a55asc4wjjg52ilns-guix-package-cache.drv, which
> consumes memory until it gets OOM-killed.
The culprit is easily found (here on just the 22K packages of ‘guix’, so
less than half of what you get with
i turn off some services using `herd disable`. then i do a `guix system
reconfigure`, and these services get enabled and started.
i would expect the enabled/disabled state to be preserved across reconfigures.
if it's not easily feasible in the current architecture, then feel free to
close
$ sudo guix system reconfigure ...
[...]
building
/gnu/store/8by5a6wqlxm3fw27xh3a6zzzwfczjpcm-install-bootloader.scm.drv...
guix system: bootloader successfully installed on '(/boot/efi)'
guix system: warning: exception caught while executing 'eval' on service 'root':
error: remove: unbound
