[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: guix system init co-existing with other distros
From: |
Ludovic Courtès |
Subject: |
Re: guix system init co-existing with other distros |
Date: |
Tue, 23 Feb 2016 14:40:34 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Jan Nieuwenhuizen <address@hidden> skribis:
> So what I need is for Guix's Grub to create an extra menu entry
> for Debian, with this text
>
> menuentry 'Debian GNU/Linux' {
> linux /boot/vmlinuz-3.16.0-4-amd64 root=/dev/sda3 ro
> initrd /boot/initrd.img-3.16.0-4-amd64
> }
>
> When you specify extra an extra menu-entry
>
> (list (menu-entry
> (label "debian")
> (linux "<file-name>")
> (initrd "<file-name>))
>
> then grub.scm:(grub-configuration-file) appends "/" "bzImage" to the
> kernel's file-name
>
> (define linux-image-name
> (if (string-prefix? "mips" system)
> "vmlinuz"
> "bzImage"))
>
> So, I setup some symlinks on the Debian side so that I can provide Guix's
> Grub wih a kernel file name that can have "/bzImage" appended.
>
> 23:42:13 address@hidden:~/src/guix
> $ ls -l /debian/boot/latest/
> totaal 0
> lrwxrwxrwx 1 root root 28 6 feb 21:17 bzImage ->
> /boot/vmlinuz-3.16.0-4-amd64
> lrwxrwxrwx 1 root root 31 6 feb 21:17 initrd ->
> /boot/initrd.img-3.16.0-4-amd64
>
> Possibly we'd want to add another keyword
>
> (linux-image "(hd0,msdos3)/boot/vmlinuz-3.16.0-4-amd64")
>
> that gets used literally?
Oh, I see. This is what <http://bugs.gnu.org/20067> is about.
I think the solution would be to not guess file names, indeed.
Until this is fixed, I don’t have any good solution other than hacks
like the one you propose. :-/
Ludo’.