From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 13 NFS syntax variations
Date: Tue, 23 Jun 2009 00:15:38 -0400 [thread overview]
Message-ID: <4A4056EA.9010102@redhat.com> (raw)
In-Reply-To: <1245709757.13352.20.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
On 06/22/2009 06:29 PM, David Dillow wrote:
>> 3) Support it but print deprecation warnings like Legacy nfsroot.txt.
>
> This would be my choice; the DHCP (BOOTP) root-path=[server:]/root-path
> formats have been around for decades. I seem to recall network booting a
> SunOS 4.1.2 box using that back in 1993, and I'll bet it wasn't a new
> feature then.
>
> Some changes I'm thinking about would benefit from dropping the non nfs:
> formats, as they wouldn't have a clean home otherwise, but I don't think
> that is a good reason to drop them -- they are too easy to support.
root=<server-ip>:/path:nfs-options
Yes, I am aware it has existed for decades. However neither Red Hat nor
Debian's tools supported this method.[1] This seems to make it a good
candidate for chopping.
Harald, what do you think?
[1]
mkinitrd supports it only partially, without nfs-options, and without a
method to auto-load network drivers prior to NFS, meaning nobody used it.
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 prev parent reply other threads:[~2009-06-23 4:15 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 ` 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 [this message]
[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=4A4056EA.9010102@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