On 2026-02-16, Eduardo Mercovich wrote: > The path to guixdom I choose was -thanks to Ekaitz great suggestion- to > have a dual boot installation for a while. So used the weekend for that > and after doing a backup I used 'parted' to resize my current Debian > partition, made 200 Gb of space for guix, followed the installation and > could boot on guix. Congratulations! Except that along with these great > news I found that the new grub ignored the other, existing and already > working partition that could be booted (an old Debian).
As a one-off, you can also probably enter the grub shell and run something like (from memory, may need adjustment to work): configfile (hd0,0)/boot/grub/grub.cfg Where hd0,0 is has the /boot partition of your Debian installation. If everything worked right, it should bring up the same menu entries as your Debian installation. This may not work if you have esoteric grub module needs, but if you're using the same sorts of disks and filesystems and such, it has generally worked ok for me on a few systems... It would be nice to be able to add that or something like it to a guix system configuration, but I am not sure it is currently possible; the current customization options, as far as I am aware, are far too sophisticated to add a single-line menu entry. :) The approach of adding menu entries to your Guix System configuration basically requires you to update your guix configuration every time you update the kernel or some other relevent thing in Debian... which could quickly become tedius, error-prone and possible you get to a state where you have the wrong kernel versions or something and the guix menu refers to non-existent files... I know in Debian there is (was?) os-prober to do this thing automatically, but not sure how to hook that into guix... live well, vagrant
signature.asc
Description: PGP signature
