GNU bug report logs - #20067
File name of initrd and kernel image in 'menu-entry' should not be forced

Previous Next

Package: guix;

Reported by: Tomáš Čech <sleep_walker <at> suse.cz>

Date: Mon, 9 Mar 2015 20:36:01 UTC

Severity: normal

Tags: fixed

Fixed in version 0.11.1

Done: ludo <at> gnu.org (Ludovic Courtès)

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: ludo <at> gnu.org (Ludovic Courtès)
To: 20067 <at> debbugs.gnu.org
Subject: bug#20067: fix interpretation of grub configuration
Date: Tue, 23 Feb 2016 14:45:36 +0100
Tomáš Čech <sleep_walker <at> suse.cz> skribis:

> Grub configuration interpretes `linux' as directory where is located
> bzImage. If I enter file name instead, result configuration will be
> wrong.

The solution will be to not automatically append “/bzImage” (and
likewise for the initrd.)

We could change places where ‘menu-entry’ is instantiated to:

  #~(string-append #$kernel "/bzImage")

However, there’s the problem that the image name appears in the
‘parameters’ file of the system (as seen in the output of ‘guix system
build foo.scm’), where it is unevaluated.  If we use ‘string-append’ as
above, a raw (string-append …) sexp will appear in there, which is not
nice.

To address this, an idea is to add “expanders” for gexps: gexps already
have “compilers”, and expanders would be similar except that they would
produce something possibly different from just the derivation’s output
file name.  For instance, we could write:

  (file-append kernel "/bzImage")

and that would expand directly to:

  "/gnu/store/…/bzImage"

Ludo’.




This bug report was last modified 8 years and 243 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.