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: Sun, 13 Sep 2020 20:30:02 +0200	[thread overview]
Message-ID: <9ED0EFDA-8A93-4243-9644-BD4DEBE93353@vodafonemail.de> (raw)
In-Reply-To: <20200907110552.0bdef27e@scratchpost.org>

Hi Danny!

> Why does having a NFS root "device" imply using TFTP?
> 
> I can see that it would be nice--but I've been using NFS for many years without
> using TFTP.
> 
>> +        ((? (lambda (device)
>> +              (and (string? device) (string-contains device ":/"))) nfs-uri)
>> +         "set root=(tftp)")
> 
> What is that required for in practice?

One more remark to this.

If you used an NFS root file system without using TFTP during boot, then certainly your bootloader, the initrd and the kernel where stored locally and have been loaded from disk, not over the network.

In Guix the initrd and the kernel are loaded from the store. If the store is located on a local device, then (grub-root-search) will still load them from that local device, even if the root file system is on an NFS share.

But in Guix its likely that the store is on the same device as the root file system. And if the root file system containing the store is mounted via NFS, then GRUB needs to access the initrd and kernel via network.


Bye

Stefan



  parent reply	other threads:[~2020-09-13 18:31 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
2020-09-07 13:33     ` Danny Milosavljevic
2020-09-13 18:30     ` Stefan [this message]
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=9ED0EFDA-8A93-4243-9644-BD4DEBE93353@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).