From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: David Dillow <dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org>
Cc: "<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>"
<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Netroot cmdline arguments
Date: Thu, 11 Jun 2009 09:20:51 +0200 [thread overview]
Message-ID: <4A30B053.9030308@bfh.ch> (raw)
In-Reply-To: <1244638667.16191.57.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
With input from the current discussion and ignorance of upcoming
netroot patches the current documentation would/should look like
the following:
DHCP
----
Format:
root=dhcp
Get IP from dhcp, use dhcp root-path option to specify root location.
Contents according to formats below.
Please note: Specifying root=dhcp will ignore further netroot options
NFS
---
Preferred format:
root=nfs[4]:[server:]path[:options]
Legacy formats:
root=[[/dev/]nfs[4]] nfsroot=[server:]path[,options]
root=[[/dev/]nfs[4]] nfsroot=[server:]path[:options]
If the 'nfsroot' parameter is not given on the command line or is empty,
the dhcp root-path is used as [server:]path[:options] or the default
"/tftpboot/%s" will be used.
If server is unspecified it will be pulled from one of the following
sources, in order:
static ip= option on kernel command line
DHCP next-server option
DHCP server-id option
DHCP root-path option
NFSv4 is only used if explicitly requested; default is NFSv2 or NFSv3
depending on kernel configuration
iSCSI
-----
Preferred format:
root=iscsi:[<servername>]:[<protocol>]:[<port>]:[<LUN>]:<targetname>
Legacy formats:
root=[iscsi] iscsiroot=[<servername>]:[<protocol>]:[<port>]:[<LUN>]:<targetname>
root=[iscsi] iscsi_firmware
NBD
---
Preferred format:
root=nbd:srv:port[:fstype[:rootflags[:nbdopts]]]
Legacy formats:
root=[nbd] nbdroot=srv,port
root=[nbd] nbdroot=srv:port[:fstype[:rootflags[:nbdopts]]]
nbdopts is a comma seperated list of options to give to nbd-client
--
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
prev parent reply other threads:[~2009-06-11 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:35 Netroot cmdline arguments Seewer Philippe
[not found] ` <4A2E8130.2050305-omB+W0Dpw2o@public.gmane.org>
2009-06-10 4:26 ` David Dillow
[not found] ` <1244607992.16191.33.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-10 7:41 ` Seewer Philippe
[not found] ` <4A2F63C6.2020504-omB+W0Dpw2o@public.gmane.org>
2009-06-10 12:57 ` David Dillow
[not found] ` <1244638667.16191.57.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-11 7:20 ` Seewer Philippe [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=4A30B053.9030308@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=dave-i1Mk8JYDVaaSihdK6806/g@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.