From: Fulbert <fulbert@bluewin.ch>
To: help-guix@gnu.org
Subject: guix configuration problem : bootloader "menu-entry"
Date: Fri, 19 Mar 2021 14:53:26 +0100 [thread overview]
Message-ID: <YFSs1gDJcj4FhYO1@bluewin.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
Hello Guixers !
I am adding some `menu-entries` to my bootloader-configuration.
From `$ info "(guix)Bootloader Configuration"`
‘device’ (default: ‘#f’)
The device where the kernel and initrd are to be found—i.e.,
for GRUB, “root” for this menu entry (*note (grub)root::).
This may be a file system label (a string), a file system UUID
(a bytevector, *note File Systems::), or ‘#f’, in which case
the bootloader will search the device containing the file
specified by the ‘linux’ field (*note (grub)search::). It
must _not_ be an OS device name such as ‘/dev/sda1’.
My problem is that `device` (or no device at all) does not seem to
work as expected. Whatever the `device`, guix produces an identical
`search --file…` grub menuentry.
Attached are 3 configuration test entries and their resulting
`menuentry` in grub.cfg. Not sure how to produce a "bytevector"
for the UUID though, but at least the test with a label (literal
string) should produce something like :
"search --label --set debian-stable"
Correct ? Or do I miss something ?!
Thanks for you time !
[-- Attachment #2: configuration.scm.extract --]
[-- Type: text/plain, Size: 752 bytes --]
(menu-entries (list
(menu-entry
(label "TEST LABEL")
(device "debian-stable")
(linux "/boot/vmlinuz-4.19.0-14-amd64")
(linux-arguments '("root=UUID=2b5cc508-e2ea-4c43-a1c4-2532553af654 ro quiet"))
(initrd "/boot/initrd.img-4.19.0-14-amd64"))
(menu-entry
(label "TEST UUID")
(device "2b5cc508-e2ea-4c43-a1c4-2532553af654")
(linux "/boot/vmlinuz-4.19.0-14-amd64")
(linux-arguments '("root=UUID=2b5cc508-e2ea-4c43-a1c4-2532553af654 ro quiet"))
(initrd "/boot/initrd.img-4.19.0-14-amd64"))
(menu-entry
(label "TEST NO DEVICE")
(linux "/boot/vmlinuz-4.19.0-14-amd64")
(linux-arguments '("root=UUID=2b5cc508-e2ea-4c43-a1c4-2532553af654 ro single"))
(initrd "/boot/initrd.img-4.19.0-14-amd64"))))
[-- Attachment #3: grub.cfg.extract --]
[-- Type: text/plain, Size: 649 bytes --]
menuentry "TEST LABEL" {
search --file --set /boot/vmlinuz-4.19.0-14-amd64
linux /boot/vmlinuz-4.19.0-14-amd64 root=UUID=2b5cc508-e2ea-4c43-a1c4-2532553af654 ro quiet
initrd /boot/initrd.img-4.19.0-14-amd64
}
menuentry "TEST UUID" {
search --file --set /boot/vmlinuz-4.19.0-14-amd64
linux /boot/vmlinuz-4.19.0-14-amd64 root=UUID=2b5cc508-e2ea-4c43-a1c4-2532553af654 ro quiet
initrd /boot/initrd.img-4.19.0-14-amd64
}
menuentry "TEST NO DEVICE" {
search --file --set /boot/vmlinuz-4.19.0-14-amd64
linux /boot/vmlinuz-4.19.0-14-amd64 root=UUID=2b5cc508-e2ea-4c43-a1c4-2532553af654 ro single
initrd /boot/initrd.img-4.19.0-14-amd64
}
reply other threads:[~2021-03-19 13:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YFSs1gDJcj4FhYO1@bluewin.ch \
--to=fulbert@bluewin.ch \
--cc=help-guix@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.
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).