All of lore.kernel.org
 help / color / mirror / Atom feed
From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: NFS why root=nfs and root=nfs4?
Date: Tue, 23 Jun 2009 00:07:02 -0400	[thread overview]
Message-ID: <4A4054E6.2090700@redhat.com> (raw)
In-Reply-To: <1245728880.13352.106.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>

On 06/22/2009 11:48 PM, David Dillow wrote:
>> This is a difference in design philosophy.  We have a native syntax that
>> seems fully feature capable.  Allowing redundancy and variation in this
>> syntax can confuse people less technically savvy than us who follow
>> documentation and examples.
>
> The people that do "config by example" are going to find the old HOWTOs
> that discuss using nfsroot.txt syntax. A current search for "linux nfs
> root" returns the NFS-root mini-HOWTO (circa 1996) and
> Diskless-root-NFS-other-HOWTO (circa 2001) as the top two results. In
> fact 5 of the top 6 results refer to the nfsroot.txt syntax and the
> sixth one refers one to the NFS-root mini-HOWTO for the kernel command
> line setup.

Isn't arguing over this moot?  I already said this is a reasonable 
compromise because of the upstream kernel and initramfs-tools.

None of those other documents however will have root=nfs, root=nfs4 or 
root=/dev/nfs4 examples.  I object to more confusing variations like 
this redundant to the preferred, full featured native syntax.

> Or is this both of us arguing from our gut and we'll have to disagree
> until Harald lays down the law about syntactic support?
>

Harald was in favor of removing the three "shortcut" variations of 
Legacy nfsroot.txt.  He also said I could go ahead and eliminate the 
netroot= variations if I felt strongly about it.  I do hope he would 
make his own comments on this matter.

I will still push chopping either root= or netroot= NFS variations, but 
only after we see what Harald decides to do for DHCP root-path for 
remote block devices (his iscsi idea).

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

      parent reply	other threads:[~2009-06-23  4:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 21:31 NFS why root=nfs and root=nfs4? Warren Togami
     [not found] ` <4A3FF836.6080208-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-22 22:41   ` David Dillow
     [not found]     ` <1245710475.13352.31.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-23  1:16       ` Warren Togami
     [not found]         ` <4A402CEF.4030506-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-23  3:48           ` David Dillow
     [not found]             ` <1245728880.13352.106.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-23  4:07               ` Warren Togami [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=4A4054E6.2090700@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.