From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: 13 NFS syntax variations
Date: Wed, 17 Jun 2009 22:42:55 -0400 [thread overview]
Message-ID: <4A39A9AF.6070009@redhat.com> (raw)
I ask the contributors again, please consider that we should reduce
redundant ways of configuring dracut as much as possible. Please
consider that this code will ship in various products for the next
decade. Is it really a good idea to confuse people by having
documentation and examples floating around be in several different
formats? Sure we developers can understand 13 different syntax
variations, but this is a lot more complicated to users trying to
understand examples they find.
Here seems to be every possible dracut NFS syntax variation.
Group A
root=[<server-ip>:]<root-dir>[:<nfs-options>]
root=nfs:[<server-ip>:]<root-dir>[:<nfs-options>]
root=nfs4:[<server-ip>:]<root-dir>[:<nfs-options>]
Group B
netroot=[<server-ip>:]<root-dir>[:<nfs-options>]
netroot=nfs:[<server-ip>:]<root-dir>[:<nfs-options>]
netroot=nfs4:[<server-ip>:]<root-dir>[:<nfs-options>]
Group C
root=dhcp
DHCP root-path=[<server-ip>:]<root-dir>[:<nfs-options>]
DHCP root-path=nfs:[<server-ip>:]<root-dir>[:<nfs-options>]
DHCP root-path=nfs4:[<server-ip>:]<root-dir>[:<nfs-options>]
Legacy nfsroot.txt
root=/dev/nfs nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
Legacy Variations
root=/dev/nfs4 nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
root=nfs nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
root=nfs4 nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
DHCP Fallbacks
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/filesystems/nfsroot.txt
Seewer's code seems to implement various DHCP-derived fallbacks as
documented from this ancient method. I suppose this is OK, except:
* The fallbacks should kick-in only if server-ip is blank from root= or
DHCP root-path.
> 54 If the `nfsroot' parameter is NOT given on the command line,
> 55 the default "/tftpboot/%s" will be used.
* We should do this only in the case where root=/dev/nfs, or not do it
at all. A hard-coded "/tftpboot" root-dir override in the modern
syntaxes makes no sense.
* We should however support the %s substitution in exactly the same way
as the kernel. Looking at our current code though, it seems we don't.
The docs don't do hostname.
What should we cut?
1) The most obvious to cut are the Legacy Variations. Why should
dracut invent three new syntaxes and immediately declare them Legacy?
Removing these would be the simplest.
2) Harald and I think we should cut Group B. The netroot= syntax is
necessary only for remote block device protocols like iscsci and nbd
when you want to use LVM or crypto on those block devices. For NFS it
is only redundant.
Removing these would be a bit complex surgery because netroot= is
tightly ingrained into the current code.
3) I personally think we should cut the "nfs:" prefixed syntaxes from
Group A, B and C because they have no precedent and we're better off
with fewer variations. Others have disagreed though.
Any further thoughts on this?
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
next reply other threads:[~2009-06-18 2:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 2:42 Warren Togami [this message]
[not found] ` <4A39A9AF.6070009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18 10:15 ` 13 NFS syntax variations Seewer Philippe
[not found] ` <4A3A13A8.6050100-omB+W0Dpw2o@public.gmane.org>
2009-06-18 17:48 ` %s substitution Warren Togami
[not found] ` <4A3A7DE0.4060801-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-19 2:48 ` David Dillow
[not found] ` <1245379718.28792.3.camel-FqX9LgGZnHWDB2HL1qBt2PIbXMQ5te18@public.gmane.org>
2009-06-19 8:18 ` Seewer Philippe
2009-06-22 20:56 ` 13 NFS syntax variations Warren Togami
[not found] ` <4A3FEFE7.7080907-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-22 22:29 ` David Dillow
[not found] ` <1245709757.13352.20.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-23 1:24 ` Warren Togami
2009-06-23 4:15 ` Warren Togami
[not found] ` <4A4056EA.9010102-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-23 4:34 ` David Dillow
2009-06-23 6:09 ` Harald Hoyer
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=4A39A9AF.6070009@redhat.com \
--to=wtogami-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.