From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: NFS cleaned up, one TODO
Date: Wed, 1 Jul 2009 18:04:11 +0200 [thread overview]
Message-ID: <4A4B88FB.1030605@bfh.ch> (raw)
In-Reply-To: <4A4A923E.5020406-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Warren Togami wrote:
> The following are now the valid syntaxes for NFS.
>
> root=[<server-ip>:]<root-dir>[:<nfs-options>]
> root=nfs:[<server-ip>:]<root-dir>[:<nfs-options>]
> root=nfs4:[<server-ip>:]<root-dir>[:<nfs-options>]
> root=dhcp
> root-path=<server-ip>:<root-dir>[,<nfs-options>]
> root-path=nfs:<server-ip>:<root-dir>[,<nfs-options>]
> root-path=nfs4:<server-ip>:<root-dir>[,<nfs-options>]
> root=/dev/nfs [nfsroot=...]
>
> TODO:
> I managed to fix the root=/dev/nfs case that specifies nfsroot=, but I
> don't understand why it doesn't work if you lack nfsroot=. Two NFS
> tests are commenteed out until that is fixed. Any ideas?
The Problem is here:
# LEGACY convert root=<server-ip>:/<path
case "$netroot" in
[0-9]*:/*|[0-9]*\.[0-9]*\.[0-9]*[!:]|/*)
netroot=nfs:$netroot;;
esac
After this part netroot looks like "netroot=nfs:/dev/nfs" if
root=/dev/nfs. This is later interpreted as path.
Patch below fixes this.
diff --git a/modules.d/95nfs/parse-nfsroot.sh b/modules.d/95nfs/parse-nfsroot.sh
index f05fb2a..9e41335 100755
--- a/modules.d/95nfs/parse-nfsroot.sh
+++ b/modules.d/95nfs/parse-nfsroot.sh
@@ -95,6 +95,7 @@ fi
# LEGACY convert root=<server-ip>:/<path
case "$netroot" in
+ /dev/nfs) netroot=nfs;;
[0-9]*:/*|[0-9]*\.[0-9]*\.[0-9]*[!:]|/*)
netroot=nfs:$netroot;;
esac
diff --git a/test/TEST-20-NFS/test.sh b/test/TEST-20-NFS/test.sh
/dev/nfs)netroot=nfs;;
>
> Warren Togami
> wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
>
> --
> To unsubscribe from this list: send the line "unsubscribe initramfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-07-01 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 22:31 NFS cleaned up, one TODO Warren Togami
[not found] ` <4A4A923E.5020406-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-07-01 16:04 ` Seewer Philippe [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4B88FB.1030605@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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