unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 27735@debbugs.gnu.org
Subject: bug#27735: Lookup by UUID
Date: Thu, 20 Jul 2017 22:32:29 +0200	[thread overview]
Message-ID: <87379qn92a.fsf@gnu.org> (raw)
In-Reply-To: <20170720193801.131a59c7@scratchpost.org> (Danny Milosavljevic's message of "Thu, 20 Jul 2017 19:38:01 +0200")

Heya,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

>> With iso9660, it works… by chance, because GRUB’s “search --fs-uuid”
>> fails.  Guess why?  Because it compares UUIDs as strings, and we format
>> it as a DCE UUID instead of an ISO UUID.  Sounds familiar no?  :-)
>
> Yeah :)
>
>> So that’s where we are.  Thoughts on how to address it?
>
> https://www.gnu.org/software/grub/manual/grub.html#Making-a-GRUB-bootable-CD_002dROM says:
>
>>...grub-mkrescue
>>This produces a file named grub.iso, which then can be burned into a CD (or a DVD), or written to a USB mass storage device.
>>The root device will be set up appropriately on entering your grub.cfg configuration file, so you can refer to file names on the CD without needing to use an explicit device name. This makes it easier to produce rescue images that will work on both optical drives and USB mass storage devices. 
>
> So... just leave the entire "search" instruction off if it's created by grub-mkrescue ?  That's how one could interpret thir "root device" sentence...

Oooh, interesting, that comes in handy.  :-)

Now, how can we pass the information to ‘grub-configuration-file’ so
that it doesn’t emit that “search” command?

It seems that the bootloader API doesn’t leave room to pass
bootloader-specific options.

Thoughts?

Ludo’.

  reply	other threads:[~2017-07-20 20:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 14:40 bug#27735: Unbootable images with GuixSD on... "GuixSD" Tobias Geerinckx-Rice
2017-07-17 14:51 ` bug#27735: [PATCH 1/2] build, vm: Use a slightly less generic label Tobias Geerinckx-Rice
2017-07-17 17:20   ` Danny Milosavljevic
2017-07-17 17:58     ` Tobias Geerinckx-Rice
2017-07-18 10:09     ` Ludovic Courtès
2017-07-18 12:30       ` Tobias Geerinckx-Rice
2017-07-18 13:48         ` Danny Milosavljevic
2017-07-17 17:17 ` bug#27735: Unbootable images with GuixSD on... "GuixSD" Danny Milosavljevic
2017-07-17 18:12   ` Tobias Geerinckx-Rice
2017-07-17 18:37     ` Tobias Geerinckx-Rice
2017-07-18 11:49   ` Ludovic Courtès
2017-07-18 15:09     ` Tobias Geerinckx-Rice
2017-07-18 18:59       ` Ludovic Courtès
2017-07-18 20:42         ` Tobias Geerinckx-Rice
2017-07-19 19:11     ` Danny Milosavljevic
2017-07-19 22:32       ` bug#27735: Lookup by UUID Ludovic Courtès
2017-07-20 17:38         ` Danny Milosavljevic
2017-07-20 20:32           ` Ludovic Courtès [this message]
2017-07-20 21:51             ` Danny Milosavljevic
2017-08-05 17:50             ` Danny Milosavljevic

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=87379qn92a.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27735@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).