All of lore.kernel.org
 help / color / mirror / Atom feed
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: Redundant nfsroot cmdline options
Date: Wed, 17 Jun 2009 09:18:56 +0200	[thread overview]
Message-ID: <4A3898E0.8090700@bfh.ch> (raw)
In-Reply-To: <4A386B20.9010205-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Warren Togami wrote:
> On 06/16/2009 11:48 PM, Dave Dillow wrote:
>> On Mon, Jun 15, 2009 at 03:46:24PM -0400, Warren Togami wrote:
>>> I am concerned about the proliferation of too many redundant ways of
>>> configuring netboot.  We should clearly document each supported method
>>> on this Wiki page and figure out which methods should be cut.  The most
>>> obvious methods to cut are NEW inventions of dracut that are redundant
>>> to other methods.
>>
>>> root=nfs       nfsroot=...
>>> root=nfs4      nfsroot=...
>>> root=/dev/nfs4 nfsroot=...
>>>
>>> These are all new inventions in dracut, redundant to the following
>>> native methods already supported.
>>
>> These short cuts are simple, and fall naturally out of the current 
>> command
>> line parsing. I don't expect validating them to be any harder than the
>> translation I already do into the canoncical nfs[4]:IP:/path:options
>> format -- you validate the canonical. Documenting them is not very
>> difficult, either. Maybe there is a potential of user confusion, but you
>> hide them away in the "Legacy support" or "Non-recommended" appendix.
>>
>> I simply don't see the problem.
>>
>> But, I'm tired of having this same coversation every few days and I
>> don't care enough to continue it now. I'm not going to lose sleep if 
>> these
>> options are gone, so rip them out if that's your fancy.
> 
> I have great respect for the work and effort you've put into this, but 
> it just doesn't make sense to add multiple redundant syntaxes of doing 
> exactly the same thing.  I accepted it earlier because I was under the 
> impression that all of the above were Legacy syntax from kernel's 
> nfsroot.txt.  But now I realize it is invented for dracut.

Same here, only I though the syntaxes not involving /dev/ (and nfs4) 
were a redhattish invention. Which they aren't as Warren's already 
pointed out.

> 
> Furthermore it makes less sense to add redundant syntaxes immediately 
> for them to be classified as Legacy.

For parsing it doesn't actually really matter much how many 
[net]root=*nfs* variants we have. As long as nfsroot stays in for 
compatibility all is well.

> Also,
> 
> root=/dev/nfs4 nfsroot=...
> 
> How is this a shortcut for
> 
> root=nfs4:...

For one root=/dev/nfs[4] nfsroot=server:/path[:,]options is translated
to netroot=nfs[4]:server:/patch:options. This is not really a shortcut, 
but simplifies transition to a newer syntax or let's people try out nfs 
without changing much.

And then there's the option (as documented in kernel nfsroot.txt) of 
leaving nfsroot= away, forcing us to use a rather special variant of 
dhcp root-path.

If it's really that important I suggest we rip out the mentioned 
[net]root=[nfs,nfs4,/dev/nfs4]. root=/dev/nfs is required for kernel 
legacy support. If someone wants nfs4, they should use the preferred 
syntax [net]root=nfs4:server...

Regards,
Philippe
--
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-17  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 19:46 Redundant nfsroot cmdline options Warren Togami
     [not found] ` <4A36A510.5010709-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-17  3:48   ` Dave Dillow
     [not found]     ` <20090617034849.GA22705-i1Mk8JYDVaaSihdK6806/g@public.gmane.org>
2009-06-17  4:03       ` Warren Togami
     [not found]         ` <4A386B20.9010205-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-17  7:18           ` Seewer Philippe [this message]
     [not found]             ` <4A3898E0.8090700-omB+W0Dpw2o@public.gmane.org>
2009-06-17 19:26               ` Warren Togami
     [not found]                 ` <4A394352.1010007-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-17 20:38                   ` Warren Togami
     [not found]                     ` <4A39543D.9040206-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18  7:07                       ` Seewer Philippe
2009-06-18  7:23                   ` Seewer Philippe

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=4A3898E0.8090700@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 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.