mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 13 NFS syntax variations
Date: Mon, 22 Jun 2009 16:56:07 -0400	[thread overview]
Message-ID: <4A3FEFE7.7080907@redhat.com> (raw)
In-Reply-To: <4A3A13A8.6050100-omB+W0Dpw2o@public.gmane.org>

On 06/18/2009 06:15 AM, Seewer Philippe wrote:
>> 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.
>
> If I understand David Dillow correctly they were meant as shortcuts.
> Removing them doesn't break anything, so I agree.

Soon pushing this.  This removes 3 variations of the nfsroot.txt syntax 
that are new inventions of dracut.

>>
>> 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.
>
> Reduntant: Yes. But it keeps the argument scheme consistent. And dracut
> is allowed to introduce new syntaxes if they make sense.

root= and netroot= redundant syntaxes with redundant tests make sense how?

* netroot= NFS variation adds to confusion understanding the 
documentation and examples.
* Complaints about the tests taking too long?  Remove all the redundant 
tests that do identical root= and netroot=.
* Separate netroot= only exists for remote block devices, useless for NFS.

This would remove 3 redundant new syntaxes.

>> 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.

Alternatively, how do people feel about removing the NFS syntax that is 
missing the nfs: prefix?  It was poorly supported (did not support 
nfs-options) in mkinitrd, lacked DHCP support, and non-existent in 
Debian's initramfs-tools.

root=[<server-ip>:]<root-dir>[:<nfs-options>]
root=dhcp
	root-path=[<server-ip>:]<root-dir>[:<nfs-options>]

RHEL5 supported the former without nfs-options, but without the ability 
to load network drivers it was almost useless.
Fedora 10+ supported the latter with root=dhcp but without nfs-options.

Options:
1) Leave it as-is.
2) Remove it.
3) Support it but print deprecation warnings like Legacy nfsroot.txt.

Opinions?

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-22 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  2:42 13 NFS syntax variations Warren Togami
     [not found] ` <4A39A9AF.6070009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18 10:15   ` 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       ` Warren Togami [this message]
     [not found]         ` <4A3FEFE7.7080907-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-22 22:29           ` 13 NFS syntax variations 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=4A3FEFE7.7080907@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox