From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: guix system init co-existing with other distros
Date: Tue, 23 Feb 2016 14:40:34 +0100 [thread overview]
Message-ID: <87d1rnk0j1.fsf@gnu.org> (raw)
In-Reply-To: <87oab93c9t.fsf@drakenvlieg.flower> (Jan Nieuwenhuizen's message of "Sun, 21 Feb 2016 23:54:22 +0100")
Jan Nieuwenhuizen <janneke@gnu.org> 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 janneke@drakenvlieg:~/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’.
prev parent reply other threads:[~2016-02-23 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 18:26 guix system init co-existing with other distros Jan Nieuwenhuizen
2016-02-18 20:26 ` Andreas Enge
2016-02-18 21:40 ` Jan Nieuwenhuizen
2016-02-21 22:12 ` Ludovic Courtès
2016-02-21 22:54 ` Jan Nieuwenhuizen
2016-02-23 13:40 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1rnk0j1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).