unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan <stefan-guix@vodafonemail.de>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 43219@debbugs.gnu.org
Subject: [bug#43219] [PATCH] gnu: Handle nfs-root device strings.
Date: Mon, 7 Sep 2020 20:44:33 +0200	[thread overview]
Message-ID: <6028D7D4-E880-4E45-8D5B-6FDE196809CD@vodafonemail.de> (raw)
In-Reply-To: <6354A850-CD6B-43EC-8DFA-3B1F172C935B@vodafonemail.de>

Hi Danny!

> However, the grub.cfg is loaded via TFTP as well, so root must be preset to ‘(tftp)’ or even ‘(http)’ due to DHCP options. So omitting the search command could be enough and even allow the use of HTTP.
> 
> It could also be possible to keep the ‘search —file’ command, if it does not produce an error.
> 
> I’ll check that. 

I think we should use that change.

+        ((? (lambda (device)
+              (and (string? device) (string-contains device ":/"))) nfs-uri)
+         "set root=(tftp)")

The point is the following: It is possible that GRUB got loaded from a local storage and that the current system is also on a local storage. Then the root variable is set to some ‘(hd0,1)’ or similar.

If you then select to boot an older system generation or a custom menu entry, which is using TFTP and NFS, then the root variable has to be changed to ‘(tftp)’.


Bye

Stefan




  reply	other threads:[~2020-09-07 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1A001E6C-A2C2-4364-B40D-C88059941CDF@vodafonemail.de>
2020-09-05 11:26 ` [bug#43219] [PATCH] gnu: Handle nfs-root device strings Stefan
2020-09-06 11:52   ` Stefan
2020-09-06 12:21     ` Danny Milosavljevic
2020-09-07  9:05   ` Danny Milosavljevic
2020-09-07 12:50     ` Stefan
2020-09-07 18:44       ` Stefan [this message]
2020-09-07 13:33     ` Danny Milosavljevic
2020-09-13 18:30     ` Stefan
2020-10-05  8:40       ` Ludovic Courtès
2020-10-05 16:31         ` bug#43219: " Stefan
2020-09-07  9:32   ` [bug#43219] Fwd: " Stefan

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=6028D7D4-E880-4E45-8D5B-6FDE196809CD@vodafonemail.de \
    --to=stefan-guix@vodafonemail.de \
    --cc=43219@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).