From: Stefan <stefan-guix@vodafonemail.de>
To: 43219@debbugs.gnu.org
Cc: Mathieu Othacehe <othacehe@gnu.org>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Danny Milosavljevic <dannym@scratchpost.org>
Subject: [bug#43219] [PATCH] gnu: Handle nfs-root device strings.
Date: Sun, 6 Sep 2020 13:52:28 +0200 [thread overview]
Message-ID: <AF7EB79E-4418-4FBF-8DBD-3EC937ADBC8B@vodafonemail.de> (raw)
In-Reply-To: <4D0B1280-3FB5-48E5-B985-24773F966618@vodafonemail.de>
Hi!
I’d like to propose these minimal changes to support an NFS as a root file system.
Currently there are three ways to define the root file system:
• (file-system (device (label …)) …),
• (file-system (device (union …)) …),
• (file-system (device "<string>") …).
The manual does not mention that an NFS is currently not supported as a root file system. However, NFS mounts are possible already with (file-system (type "nfs") (device "<string>") …).
This patch enables users to use an NFS also as a root file system without introducing a new syntax.
I was asked before to introduce an <nfs-share> record to achieve the same. And I did so, see <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41820#20>. But due to some other PXE efforts – for which I don’t see progress – that patch got on hold.
However, that <nfs-share> record would brake with the compatibility of how an NFS mount is defined today, and it makes the code much more complex without having a real gain.
I think this minimal patch will not conflict with that other PXE effort. Its only purpose is to enable the use of an NFS as a root file system already today.
Bye
Stefan
next prev parent reply other threads:[~2020-09-06 12:28 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 [this message]
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
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=AF7EB79E-4418-4FBF-8DBD-3EC937ADBC8B@vodafonemail.de \
--to=stefan-guix@vodafonemail.de \
--cc=43219@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=maxim.cournoyer@gmail.com \
--cc=othacehe@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.
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).