€•       Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ+/translations/zh_CN/admin-guide/nfs/nfsroot”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/zh_TW/admin-guide/nfs/nfsroot”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/it_IT/admin-guide/nfs/nfsroot”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/ja_JP/admin-guide/nfs/nfsroot”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/ko_KR/admin-guide/nfs/nfsroot”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/pt_BR/admin-guide/nfs/nfsroot”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ+/translations/sp_SP/admin-guide/nfs/nfsroot”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ.Mounting the root filesystem via NFS (nfsroot)”h]”hŒ.Mounting the root filesystem via NFS (nfsroot)”…””}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³ŒE/var/lib/git/docbuild/linux/Documentation/admin-guide/nfs/nfsroot.rst”h´KubhŒ
field_list”“”)”}”(hhh]”hŒfield”“”)”}”(hhh]”(hŒ
field_name”“”)”}”(hŒAuthors”h]”hŒAuthors”…””}”(hh×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÕhhÒh³hÊh´K ubhŒ
field_body”“”)”}”(hX  Written 1996 by Gero Kuhlmann <gero@gkminix.han.de>

Updated 1997 by Martin Mares <mj@atrey.karlin.mff.cuni.cz>

Updated 2006 by Nico Schottelius <nico-kernel-nfsroot@schottelius.org>

Updated 2006 by Horms <horms@verge.net.au>

Updated 2018 by Chris Novakovic <chris@chrisn.me.uk>


”h]”(hŒ	paragraph”“”)”}”(hŒ3Written 1996 by Gero Kuhlmann <gero@gkminix.han.de>”h]”(hŒWritten 1996 by Gero Kuhlmann <”…””}”(hhíh²hh³Nh´NubhŒ	reference”“”)”}”(hŒgero@gkminix.han.de”h]”hŒgero@gkminix.han.de”…””}”(hh÷h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:gero@gkminix.han.de”uh1hõhhíubhŒ>”…””}”(hhíh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Khhçubhì)”}”(hŒ:Updated 1997 by Martin Mares <mj@atrey.karlin.mff.cuni.cz>”h]”(hŒUpdated 1997 by Martin Mares <”…””}”(hj  h²hh³Nh´Nubhö)”}”(hŒmj@atrey.karlin.mff.cuni.cz”h]”hŒmj@atrey.karlin.mff.cuni.cz”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ"mailto:mj@atrey.karlin.mff.cuni.cz”uh1hõhj  ubhŒ>”…””}”(hj  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Khhçubhì)”}”(hŒFUpdated 2006 by Nico Schottelius <nico-kernel-nfsroot@schottelius.org>”h]”(hŒ"Updated 2006 by Nico Schottelius <”…””}”(hj3  h²hh³Nh´Nubhö)”}”(hŒ#nico-kernel-nfsroot@schottelius.org”h]”hŒ#nico-kernel-nfsroot@schottelius.org”…””}”(hj;  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ*mailto:nico-kernel-nfsroot@schottelius.org”uh1hõhj3  ubhŒ>”…””}”(hj3  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K
hhçubhì)”}”(hŒ*Updated 2006 by Horms <horms@verge.net.au>”h]”(hŒUpdated 2006 by Horms <”…””}”(hjU  h²hh³Nh´Nubhö)”}”(hŒhorms@verge.net.au”h]”hŒhorms@verge.net.au”…””}”(hj]  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:horms@verge.net.au”uh1hõhjU  ubhŒ>”…””}”(hjU  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Khhçubhì)”}”(hŒ4Updated 2018 by Chris Novakovic <chris@chrisn.me.uk>”h]”(hŒ!Updated 2018 by Chris Novakovic <”…””}”(hjw  h²hh³Nh´Nubhö)”}”(hŒchris@chrisn.me.uk”h]”hŒchris@chrisn.me.uk”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:chris@chrisn.me.uk”uh1hõhjw  ubhŒ>”…””}”(hjw  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Khhçubeh}”(h]”h ]”h"]”h$]”h&]”uh1håhhÒubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÐh³hÊh´KhhÍh²hubah}”(h]”h ]”h"]”h$]”h&]”uh1hËhh·h²hh³hÊh´Kubhì)”}”(hX÷  In order to use a diskless system, such as an X-terminal or printer server for
example, it is necessary for the root filesystem to be present on a non-disk
device. This may be an initramfs (see
Documentation/filesystems/ramfs-rootfs-initramfs.rst), a ramdisk (see
Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The
following text describes on how to use NFS for the root filesystem. For the rest
of this text 'client' means the diskless system, and 'server' means the NFS
server.”h]”hXÿ  In order to use a diskless system, such as an X-terminal or printer server for
example, it is necessary for the root filesystem to be present on a non-disk
device. This may be an initramfs (see
Documentation/filesystems/ramfs-rootfs-initramfs.rst), a ramdisk (see
Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The
following text describes on how to use NFS for the root filesystem. For the rest
of this text â€˜clientâ€™ means the diskless system, and â€˜serverâ€™ means the NFS
server.”…””}”(hj«  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Khh·h²hubh¶)”}”(hhh]”(h»)”}”(hŒEnabling nfsroot capabilities”h]”hŒEnabling nfsroot capabilities”…””}”(hj¼  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj¹  h²hh³hÊh´Kubhì)”}”(hŒÈIn order to use nfsroot, NFS client support needs to be selected as
built-in during configuration. Once this has been selected, the nfsroot
option will become available, which should also be selected.”h]”hŒÈIn order to use nfsroot, NFS client support needs to be selected as
built-in during configuration. Once this has been selected, the nfsroot
option will become available, which should also be selected.”…””}”(hjÊ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K!hj¹  h²hubhì)”}”(hŒ¯In the networking options, kernel level autoconfiguration can be selected,
along with the types of autoconfiguration to support. Selecting all of
DHCP, BOOTP and RARP is safe.”h]”hŒ¯In the networking options, kernel level autoconfiguration can be selected,
along with the types of autoconfiguration to support. Selecting all of
DHCP, BOOTP and RARP is safe.”…””}”(hjØ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K%hj¹  h²hubeh}”(h]”Œenabling-nfsroot-capabilities”ah ]”h"]”Œenabling nfsroot capabilities”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)”}”(hhh]”(h»)”}”(hŒKernel command line”h]”hŒKernel command line”…””}”(hjñ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjî  h²hh³hÊh´K-ubhì)”}”(hX0  When the kernel has been loaded by a boot loader (see below) it needs to be
told what root fs device to use. And in the case of nfsroot, where to find
both the server and the name of the directory on the server to mount as root.
This can be established using the following kernel command line parameters:”h]”hX0  When the kernel has been loaded by a boot loader (see below) it needs to be
told what root fs device to use. And in the case of nfsroot, where to find
both the server and the name of the directory on the server to mount as root.
This can be established using the following kernel command line parameters:”…””}”(hjÿ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K/hjî  h²hubhŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hŒ®root=/dev/nfs
This is necessary to enable the pseudo-NFS-device. Note that it's not a
real device but just a synonym to tell the kernel to use NFS instead of
a real device.

”h]”(hŒterm”“”)”}”(hŒroot=/dev/nfs”h]”hŒroot=/dev/nfs”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K9hj  ubhŒ
definition”“”)”}”(hhh]”hì)”}”(hŒžThis is necessary to enable the pseudo-NFS-device. Note that it's not a
real device but just a synonym to tell the kernel to use NFS instead of
a real device.”h]”hŒ This is necessary to enable the pseudo-NFS-device. Note that itâ€™s not a
real device but just a synonym to tell the kernel to use NFS instead of
a real device.”…””}”(hj-  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K6hj*  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K9hj  ubj  )”}”(hXá  nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
If the `nfsroot' parameter is NOT given on the command line,
the default ``"/tftpboot/%s"`` will be used.

<server-ip>   Specifies the IP address of the NFS server.
              The default address is determined by the ip parameter
              (see below). This parameter allows the use of different
              servers for IP autoconfiguration and NFS.

<root-dir>    Name of the directory on the server to mount as root.
              If there is a "%s" token in the string, it will be
              replaced by the ASCII-representation of the client's
              IP address.

<nfs-options> Standard NFS options. All options are separated by commas.
              The following defaults are used::

                      port            = as given by server portmap daemon
                      rsize           = 4096
                      wsize           = 4096
                      timeo           = 7
                      retrans         = 3
                      acregmin        = 3
                      acregmax        = 60
                      acdirmin        = 30
                      acdirmax        = 60
                      flags           = hard, nointr, noposix, cto, ac

”h]”(j  )”}”(hŒ0nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]”h]”hŒ0nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]”…””}”(hjK  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KVhjG  ubj)  )”}”(hhh]”(hì)”}”(hŒiIf the `nfsroot' parameter is NOT given on the command line,
the default ``"/tftpboot/%s"`` will be used.”h]”(hŒIf the ”…””}”(hj\  h²hh³Nh´NubhŒtitle_reference”“”)”}”(hŒD`nfsroot' parameter is NOT given on the command line,
the default ``”h]”hŒDnfsrootâ€™ parameter is NOT given on the command line,
the default `”…””}”(hjf  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  hj\  ubhŒ"â€/tftpboot/%sâ€`` will be used.”…””}”(hj\  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K<hjY  ubj  )”}”(hhh]”(j  )”}”(hŒÒ<server-ip>   Specifies the IP address of the NFS server.
The default address is determined by the ip parameter
(see below). This parameter allows the use of different
servers for IP autoconfiguration and NFS.
”h]”(j  )”}”(hŒ9<server-ip>   Specifies the IP address of the NFS server.”h]”hŒ9<server-ip>   Specifies the IP address of the NFS server.”…””}”(hj…  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KBhj  ubj)  )”}”(hhh]”hì)”}”(hŒ—The default address is determined by the ip parameter
(see below). This parameter allows the use of different
servers for IP autoconfiguration and NFS.”h]”hŒ—The default address is determined by the ip parameter
(see below). This parameter allows the use of different
servers for IP autoconfiguration and NFS.”…””}”(hj–  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K@hj“  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KBhj~  ubj  )”}”(hŒ¸<root-dir>    Name of the directory on the server to mount as root.
If there is a "%s" token in the string, it will be
replaced by the ASCII-representation of the client's
IP address.
”h]”(j  )”}”(hŒC<root-dir>    Name of the directory on the server to mount as root.”h]”hŒC<root-dir>    Name of the directory on the server to mount as root.”…””}”(hj´  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KGhj°  ubj)  )”}”(hhh]”hì)”}”(hŒsIf there is a "%s" token in the string, it will be
replaced by the ASCII-representation of the client's
IP address.”h]”hŒyIf there is a â€œ%sâ€ token in the string, it will be
replaced by the ASCII-representation of the clientâ€™s
IP address.”…””}”(hjÅ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KEhjÂ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj°  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KGhj~  ubj  )”}”(hXË  <nfs-options> Standard NFS options. All options are separated by commas.
The following defaults are used::

        port            = as given by server portmap daemon
        rsize           = 4096
        wsize           = 4096
        timeo           = 7
        retrans         = 3
        acregmin        = 3
        acregmax        = 60
        acdirmin        = 30
        acdirmax        = 60
        flags           = hard, nointr, noposix, cto, ac

”h]”(j  )”}”(hŒH<nfs-options> Standard NFS options. All options are separated by commas.”h]”hŒH<nfs-options> Standard NFS options. All options are separated by commas.”…””}”(hjã  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KVhjß  ubj)  )”}”(hhh]”(hì)”}”(hŒ!The following defaults are used::”h]”hŒ The following defaults are used:”…””}”(hjô  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KJhjñ  ubhŒliteral_block”“”)”}”(hX  port            = as given by server portmap daemon
rsize           = 4096
wsize           = 4096
timeo           = 7
retrans         = 3
acregmin        = 3
acregmax        = 60
acdirmin        = 30
acdirmax        = 60
flags           = hard, nointr, noposix, cto, ac”h]”hX  port            = as given by server portmap daemon
rsize           = 4096
wsize           = 4096
timeo           = 7
retrans         = 3
acregmin        = 3
acregmax        = 60
acdirmin        = 30
acdirmax        = 60
flags           = hard, nointr, noposix, cto, ac”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j  h³hÊh´KLhjñ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjß  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KVhj~  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjY  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjG  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KVhj  h²hubj  )”}”(hXî  ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<ntp0-ip>
This parameter tells the kernel how to configure IP addresses of devices
and also how to set up the IP routing table. It was originally called
nfsaddrs, but now the boot-time IP configuration works independently of
NFS, so it was renamed to ip and the old name remained as an alias for
compatibility reasons.

If this parameter is missing from the kernel command line, all fields are
assumed to be empty, and the defaults mentioned below apply. In general
this means that the kernel tries to configure everything using
autoconfiguration.

The <autoconf> parameter can appear alone as the value to the ip
parameter (without all the ':' characters before).  If the value is
"ip=off" or "ip=none", no autoconfiguration will take place, otherwise
autoconfiguration will take place.  The most common way to use this
is "ip=dhcp".

<client-ip>   IP address of the client.
              Default:  Determined using autoconfiguration.

<server-ip>   IP address of the NFS server.
              If RARP is used to determine
              the client address and this parameter is NOT empty only
              replies from the specified server are accepted.

              Only required for NFS root. That is autoconfiguration
              will not be triggered if it is missing and NFS root is not
              in operation.

              Value is exported to /proc/net/pnp with the prefix "bootserver "
              (see below).

              Default: Determined using autoconfiguration.
              The address of the autoconfiguration server is used.

<gw-ip>       IP address of a gateway if the server is on a different subnet.
              Default: Determined using autoconfiguration.

<netmask>     Netmask for local network interface.
              If unspecified the netmask is derived from the client IP address
              assuming classful addressing.

              Default:  Determined using autoconfiguration.

<hostname>    Name of the client.
              If a '.' character is present, anything
              before the first '.' is used as the client's hostname, and anything
              after it is used as its NIS domain name. May be supplied by
              autoconfiguration, but its absence will not trigger autoconfiguration.
              If specified and DHCP is used, the user-provided hostname (and NIS
              domain name, if present) will be carried in the DHCP request; this
              may cause a DNS record to be created or updated for the client.

              Default: Client IP address is used in ASCII notation.

<device>      Name of network device to use.
              Default: If the host only has one device, it is used.
              Otherwise the device is determined using
              autoconfiguration. This is done by sending
              autoconfiguration requests out of all devices,
              and using the device that received the first reply.

<autoconf>    Method to use for autoconfiguration.
              In the case of options
              which specify multiple autoconfiguration protocols,
              requests are sent using all protocols, and the first one
              to reply is used.

              Only autoconfiguration protocols that have been compiled
              into the kernel will be used, regardless of the value of
              this option::

                off or none: don't use autoconfiguration
                              (do static IP assignment instead)
                on or any:   use any protocol available in the kernel
                             (default)
                dhcp:        use DHCP
                bootp:       use BOOTP
                rarp:        use RARP
                both:        use both BOOTP and RARP but not DHCP
                             (old option kept for backwards compatibility)

              if dhcp is used, the client identifier can be used by following
              format "ip=dhcp,client-id-type,client-id-value"

              Default: any

<dns0-ip>     IP address of primary nameserver.
              Value is exported to /proc/net/pnp with the prefix "nameserver "
              (see below).

              Default: None if not using autoconfiguration; determined
              automatically if using autoconfiguration.

<dns1-ip>     IP address of secondary nameserver.
              See <dns0-ip>.

<ntp0-ip>     IP address of a Network Time Protocol (NTP) server.
              Value is exported to /proc/net/ipconfig/ntp_servers, but is
              otherwise unused (see below).

              Default: None if not using autoconfiguration; determined
              automatically if using autoconfiguration.

After configuration (whether manual or automatic) is complete, two files
are created in the following format; lines are omitted if their respective
value is empty following configuration:

- /proc/net/pnp:

      #PROTO: <DHCP|BOOTP|RARP|MANUAL>        (depending on configuration method)
      domain <dns-domain>                     (if autoconfigured, the DNS domain)
      nameserver <dns0-ip>                    (primary name server IP)
      nameserver <dns1-ip>                    (secondary name server IP)
      nameserver <dns2-ip>                    (tertiary name server IP)
      bootserver <server-ip>                  (NFS server IP)

- /proc/net/ipconfig/ntp_servers:

      <ntp0-ip>                               (NTP server IP)
      <ntp1-ip>                               (NTP server IP)
      <ntp2-ip>                               (NTP server IP)

<dns-domain> and <dns2-ip> (in /proc/net/pnp) and <ntp1-ip> and <ntp2-ip>
(in /proc/net/ipconfig/ntp_servers) are requested during autoconfiguration;
they cannot be specified as part of the "ip=" kernel command line parameter.

Because the "domain" and "nameserver" options are recognised by DNS
resolvers, /etc/resolv.conf is often linked to /proc/net/pnp on systems
that use an NFS root filesystem.

Note that the kernel will not synchronise the system time with any NTP
servers it discovers; this is the responsibility of a user space process
(e.g. an initrd/initramfs script that passes the IP addresses listed in
/proc/net/ipconfig/ntp_servers to an NTP client before mounting the real
root filesystem if it is on NFS).

”h]”(j  )”}”(hŒiip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<ntp0-ip>”h]”hŒiip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<ntp0-ip>”…””}”(hj6  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Káhj2  ubj)  )”}”(hhh]”(hì)”}”(hX4  This parameter tells the kernel how to configure IP addresses of devices
and also how to set up the IP routing table. It was originally called
nfsaddrs, but now the boot-time IP configuration works independently of
NFS, so it was renamed to ip and the old name remained as an alias for
compatibility reasons.”h]”hX4  This parameter tells the kernel how to configure IP addresses of devices
and also how to set up the IP routing table. It was originally called
nfsaddrs, but now the boot-time IP configuration works independently of
NFS, so it was renamed to ip and the old name remained as an alias for
compatibility reasons.”…””}”(hjG  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KYhjD  ubhì)”}”(hŒãIf this parameter is missing from the kernel command line, all fields are
assumed to be empty, and the defaults mentioned below apply. In general
this means that the kernel tries to configure everything using
autoconfiguration.”h]”hŒãIf this parameter is missing from the kernel command line, all fields are
assumed to be empty, and the defaults mentioned below apply. In general
this means that the kernel tries to configure everything using
autoconfiguration.”…””}”(hjU  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K_hjD  ubhì)”}”(hX  The <autoconf> parameter can appear alone as the value to the ip
parameter (without all the ':' characters before).  If the value is
"ip=off" or "ip=none", no autoconfiguration will take place, otherwise
autoconfiguration will take place.  The most common way to use this
is "ip=dhcp".”h]”hX-  The <autoconf> parameter can appear alone as the value to the ip
parameter (without all the â€˜:â€™ characters before).  If the value is
â€œip=offâ€ or â€œip=noneâ€, no autoconfiguration will take place, otherwise
autoconfiguration will take place.  The most common way to use this
is â€œip=dhcpâ€.”…””}”(hjc  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KdhjD  ubj  )”}”(hhh]”(j  )”}”(hŒV<client-ip>   IP address of the client.
Default:  Determined using autoconfiguration.
”h]”(j  )”}”(hŒ'<client-ip>   IP address of the client.”h]”hŒ'<client-ip>   IP address of the client.”…””}”(hjx  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kkhjt  ubj)  )”}”(hhh]”hì)”}”(hŒ-Default:  Determined using autoconfiguration.”h]”hŒ-Default:  Determined using autoconfiguration.”…””}”(hj‰  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Kkhj†  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjt  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kkhjq  ubj  )”}”(hXã  <server-ip>   IP address of the NFS server.
If RARP is used to determine
the client address and this parameter is NOT empty only
replies from the specified server are accepted.

Only required for NFS root. That is autoconfiguration
will not be triggered if it is missing and NFS root is not
in operation.

Value is exported to /proc/net/pnp with the prefix "bootserver "
(see below).

Default: Determined using autoconfiguration.
The address of the autoconfiguration server is used.
”h]”(j  )”}”(hŒ+<server-ip>   IP address of the NFS server.”h]”hŒ+<server-ip>   IP address of the NFS server.”…””}”(hj§  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kzhj£  ubj)  )”}”(hhh]”(hì)”}”(hŒ„If RARP is used to determine
the client address and this parameter is NOT empty only
replies from the specified server are accepted.”h]”hŒ„If RARP is used to determine
the client address and this parameter is NOT empty only
replies from the specified server are accepted.”…””}”(hj¸  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Knhjµ  ubhì)”}”(hŒ~Only required for NFS root. That is autoconfiguration
will not be triggered if it is missing and NFS root is not
in operation.”h]”hŒ~Only required for NFS root. That is autoconfiguration
will not be triggered if it is missing and NFS root is not
in operation.”…””}”(hjÆ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Krhjµ  ubhì)”}”(hŒMValue is exported to /proc/net/pnp with the prefix "bootserver "
(see below).”h]”hŒQValue is exported to /proc/net/pnp with the prefix â€œbootserver â€
(see below).”…””}”(hjÔ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Kvhjµ  ubhì)”}”(hŒaDefault: Determined using autoconfiguration.
The address of the autoconfiguration server is used.”h]”hŒaDefault: Determined using autoconfiguration.
The address of the autoconfiguration server is used.”…””}”(hjâ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Kyhjµ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj£  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kzhjq  ubj  )”}”(hŒ{<gw-ip>       IP address of a gateway if the server is on a different subnet.
Default: Determined using autoconfiguration.
”h]”(j  )”}”(hŒM<gw-ip>       IP address of a gateway if the server is on a different subnet.”h]”hŒM<gw-ip>       IP address of a gateway if the server is on a different subnet.”…””}”(hj   h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K}hjü  ubj)  )”}”(hhh]”hì)”}”(hŒ,Default: Determined using autoconfiguration.”h]”hŒ,Default: Determined using autoconfiguration.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K}hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjü  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K}hjq  ubj  )”}”(hŒÁ<netmask>     Netmask for local network interface.
If unspecified the netmask is derived from the client IP address
assuming classful addressing.

Default:  Determined using autoconfiguration.
”h]”(j  )”}”(hŒ2<netmask>     Netmask for local network interface.”h]”hŒ2<netmask>     Netmask for local network interface.”…””}”(hj/  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kƒhj+  ubj)  )”}”(hhh]”(hì)”}”(hŒ^If unspecified the netmask is derived from the client IP address
assuming classful addressing.”h]”hŒ^If unspecified the netmask is derived from the client IP address
assuming classful addressing.”…””}”(hj@  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K€hj=  ubhì)”}”(hŒ-Default:  Determined using autoconfiguration.”h]”hŒ-Default:  Determined using autoconfiguration.”…””}”(hjN  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Kƒhj=  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj+  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kƒhjq  ubj  )”}”(hX  <hostname>    Name of the client.
If a '.' character is present, anything
before the first '.' is used as the client's hostname, and anything
after it is used as its NIS domain name. May be supplied by
autoconfiguration, but its absence will not trigger autoconfiguration.
If specified and DHCP is used, the user-provided hostname (and NIS
domain name, if present) will be carried in the DHCP request; this
may cause a DNS record to be created or updated for the client.

Default: Client IP address is used in ASCII notation.
”h]”(j  )”}”(hŒ!<hostname>    Name of the client.”h]”hŒ!<hostname>    Name of the client.”…””}”(hjl  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KŽhjh  ubj)  )”}”(hhh]”(hì)”}”(hX´  If a '.' character is present, anything
before the first '.' is used as the client's hostname, and anything
after it is used as its NIS domain name. May be supplied by
autoconfiguration, but its absence will not trigger autoconfiguration.
If specified and DHCP is used, the user-provided hostname (and NIS
domain name, if present) will be carried in the DHCP request; this
may cause a DNS record to be created or updated for the client.”h]”hX¾  If a â€˜.â€™ character is present, anything
before the first â€˜.â€™ is used as the clientâ€™s hostname, and anything
after it is used as its NIS domain name. May be supplied by
autoconfiguration, but its absence will not trigger autoconfiguration.
If specified and DHCP is used, the user-provided hostname (and NIS
domain name, if present) will be carried in the DHCP request; this
may cause a DNS record to be created or updated for the client.”…””}”(hj}  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K†hjz  ubhì)”}”(hŒ5Default: Client IP address is used in ASCII notation.”h]”hŒ5Default: Client IP address is used in ASCII notation.”…””}”(hj‹  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KŽhjz  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjh  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KŽhjq  ubj  )”}”(hX  <device>      Name of network device to use.
Default: If the host only has one device, it is used.
Otherwise the device is determined using
autoconfiguration. This is done by sending
autoconfiguration requests out of all devices,
and using the device that received the first reply.
”h]”(j  )”}”(hŒ,<device>      Name of network device to use.”h]”hŒ,<device>      Name of network device to use.”…””}”(hj©  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K•hj¥  ubj)  )”}”(hhh]”hì)”}”(hŒìDefault: If the host only has one device, it is used.
Otherwise the device is determined using
autoconfiguration. This is done by sending
autoconfiguration requests out of all devices,
and using the device that received the first reply.”h]”hŒìDefault: If the host only has one device, it is used.
Otherwise the device is determined using
autoconfiguration. This is done by sending
autoconfiguration requests out of all devices,
and using the device that received the first reply.”…””}”(hjº  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K‘hj·  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj¥  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K•hjq  ubj  )”}”(hX2  <autoconf>    Method to use for autoconfiguration.
In the case of options
which specify multiple autoconfiguration protocols,
requests are sent using all protocols, and the first one
to reply is used.

Only autoconfiguration protocols that have been compiled
into the kernel will be used, regardless of the value of
this option::

  off or none: don't use autoconfiguration
                (do static IP assignment instead)
  on or any:   use any protocol available in the kernel
               (default)
  dhcp:        use DHCP
  bootp:       use BOOTP
  rarp:        use RARP
  both:        use both BOOTP and RARP but not DHCP
               (old option kept for backwards compatibility)

if dhcp is used, the client identifier can be used by following
format "ip=dhcp,client-id-type,client-id-value"

Default: any
”h]”(j  )”}”(hŒ2<autoconf>    Method to use for autoconfiguration.”h]”hŒ2<autoconf>    Method to use for autoconfiguration.”…””}”(hjØ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K®hjÔ  ubj)  )”}”(hhh]”(hì)”}”(hŒ•In the case of options
which specify multiple autoconfiguration protocols,
requests are sent using all protocols, and the first one
to reply is used.”h]”hŒ•In the case of options
which specify multiple autoconfiguration protocols,
requests are sent using all protocols, and the first one
to reply is used.”…””}”(hjé  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K˜hjæ  ubhì)”}”(hŒOnly autoconfiguration protocols that have been compiled
into the kernel will be used, regardless of the value of
this option::”h]”hŒ~Only autoconfiguration protocols that have been compiled
into the kernel will be used, regardless of the value of
this option:”…””}”(hj÷  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Khjæ  ubj  )”}”(hXU  off or none: don't use autoconfiguration
              (do static IP assignment instead)
on or any:   use any protocol available in the kernel
             (default)
dhcp:        use DHCP
bootp:       use BOOTP
rarp:        use RARP
both:        use both BOOTP and RARP but not DHCP
             (old option kept for backwards compatibility)”h]”hXU  off or none: don't use autoconfiguration
              (do static IP assignment instead)
on or any:   use any protocol available in the kernel
             (default)
dhcp:        use DHCP
bootp:       use BOOTP
rarp:        use RARP
both:        use both BOOTP and RARP but not DHCP
             (old option kept for backwards compatibility)”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j  h³hÊh´K¡hjæ  ubhì)”}”(hŒoif dhcp is used, the client identifier can be used by following
format "ip=dhcp,client-id-type,client-id-value"”h]”hŒsif dhcp is used, the client identifier can be used by following
format â€œip=dhcp,client-id-type,client-id-valueâ€”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K«hjæ  ubhì)”}”(hŒDefault: any”h]”hŒDefault: any”…””}”(hj!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K®hjæ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjÔ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K®hjq  ubj  )”}”(hŒâ<dns0-ip>     IP address of primary nameserver.
Value is exported to /proc/net/pnp with the prefix "nameserver "
(see below).

Default: None if not using autoconfiguration; determined
automatically if using autoconfiguration.
”h]”(j  )”}”(hŒ/<dns0-ip>     IP address of primary nameserver.”h]”hŒ/<dns0-ip>     IP address of primary nameserver.”…””}”(hj?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kµhj;  ubj)  )”}”(hhh]”(hì)”}”(hŒMValue is exported to /proc/net/pnp with the prefix "nameserver "
(see below).”h]”hŒQValue is exported to /proc/net/pnp with the prefix â€œnameserver â€
(see below).”…””}”(hjP  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K±hjM  ubhì)”}”(hŒbDefault: None if not using autoconfiguration; determined
automatically if using autoconfiguration.”h]”hŒbDefault: None if not using autoconfiguration; determined
automatically if using autoconfiguration.”…””}”(hj^  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K´hjM  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj;  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kµhjq  ubj  )”}”(hŒA<dns1-ip>     IP address of secondary nameserver.
See <dns0-ip>.
”h]”(j  )”}”(hŒ1<dns1-ip>     IP address of secondary nameserver.”h]”hŒ1<dns1-ip>     IP address of secondary nameserver.”…””}”(hj|  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K¸hjx  ubj)  )”}”(hhh]”hì)”}”(hŒSee <dns0-ip>.”h]”hŒSee <dns0-ip>.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K¸hjŠ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjx  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K¸hjq  ubj  )”}”(hX   <ntp0-ip>     IP address of a Network Time Protocol (NTP) server.
Value is exported to /proc/net/ipconfig/ntp_servers, but is
otherwise unused (see below).

Default: None if not using autoconfiguration; determined
automatically if using autoconfiguration.
”h]”(j  )”}”(hŒA<ntp0-ip>     IP address of a Network Time Protocol (NTP) server.”h]”hŒA<ntp0-ip>     IP address of a Network Time Protocol (NTP) server.”…””}”(hj«  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K¿hj§  ubj)  )”}”(hhh]”(hì)”}”(hŒYValue is exported to /proc/net/ipconfig/ntp_servers, but is
otherwise unused (see below).”h]”hŒYValue is exported to /proc/net/ipconfig/ntp_servers, but is
otherwise unused (see below).”…””}”(hj¼  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K»hj¹  ubhì)”}”(hŒbDefault: None if not using autoconfiguration; determined
automatically if using autoconfiguration.”h]”hŒbDefault: None if not using autoconfiguration; determined
automatically if using autoconfiguration.”…””}”(hjÊ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´K¾hj¹  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj§  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´K¿hjq  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjD  ubhì)”}”(hŒ»After configuration (whether manual or automatic) is complete, two files
are created in the following format; lines are omitted if their respective
value is empty following configuration:”h]”hŒ»After configuration (whether manual or automatic) is complete, two files
are created in the following format; lines are omitted if their respective
value is empty following configuration:”…””}”(hjê  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KÁhjD  ubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hX¾  /proc/net/pnp:

    #PROTO: <DHCP|BOOTP|RARP|MANUAL>        (depending on configuration method)
    domain <dns-domain>                     (if autoconfigured, the DNS domain)
    nameserver <dns0-ip>                    (primary name server IP)
    nameserver <dns1-ip>                    (secondary name server IP)
    nameserver <dns2-ip>                    (tertiary name server IP)
    bootserver <server-ip>                  (NFS server IP)
”h]”(hì)”}”(hŒ/proc/net/pnp:”h]”hŒ/proc/net/pnp:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KÅhjÿ  ubhŒblock_quote”“”)”}”(hX–  #PROTO: <DHCP|BOOTP|RARP|MANUAL>        (depending on configuration method)
domain <dns-domain>                     (if autoconfigured, the DNS domain)
nameserver <dns0-ip>                    (primary name server IP)
nameserver <dns1-ip>                    (secondary name server IP)
nameserver <dns2-ip>                    (tertiary name server IP)
bootserver <server-ip>                  (NFS server IP)
”h]”hì)”}”(hX•  #PROTO: <DHCP|BOOTP|RARP|MANUAL>        (depending on configuration method)
domain <dns-domain>                     (if autoconfigured, the DNS domain)
nameserver <dns0-ip>                    (primary name server IP)
nameserver <dns1-ip>                    (secondary name server IP)
nameserver <dns2-ip>                    (tertiary name server IP)
bootserver <server-ip>                  (NFS server IP)”h]”hX•  #PROTO: <DHCP|BOOTP|RARP|MANUAL>        (depending on configuration method)
domain <dns-domain>                     (if autoconfigured, the DNS domain)
nameserver <dns0-ip>                    (primary name server IP)
nameserver <dns1-ip>                    (secondary name server IP)
nameserver <dns2-ip>                    (tertiary name server IP)
bootserver <server-ip>                  (NFS server IP)”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KÇhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KÇhjÿ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hjú  ubjþ  )”}”(hŒÕ/proc/net/ipconfig/ntp_servers:

    <ntp0-ip>                               (NTP server IP)
    <ntp1-ip>                               (NTP server IP)
    <ntp2-ip>                               (NTP server IP)
”h]”(hì)”}”(hŒ/proc/net/ipconfig/ntp_servers:”h]”hŒ/proc/net/ipconfig/ntp_servers:”…””}”(hj5  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KÎhj1  ubj  )”}”(hŒ¨<ntp0-ip>                               (NTP server IP)
<ntp1-ip>                               (NTP server IP)
<ntp2-ip>                               (NTP server IP)
”h]”hì)”}”(hŒ§<ntp0-ip>                               (NTP server IP)
<ntp1-ip>                               (NTP server IP)
<ntp2-ip>                               (NTP server IP)”h]”hŒ§<ntp0-ip>                               (NTP server IP)
<ntp1-ip>                               (NTP server IP)
<ntp2-ip>                               (NTP server IP)”…””}”(hjG  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KÐhjC  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KÐhj1  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hjú  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jø  h³hÊh´KÅhjD  ubhì)”}”(hŒâ<dns-domain> and <dns2-ip> (in /proc/net/pnp) and <ntp1-ip> and <ntp2-ip>
(in /proc/net/ipconfig/ntp_servers) are requested during autoconfiguration;
they cannot be specified as part of the "ip=" kernel command line parameter.”h]”hŒæ<dns-domain> and <dns2-ip> (in /proc/net/pnp) and <ntp1-ip> and <ntp2-ip>
(in /proc/net/ipconfig/ntp_servers) are requested during autoconfiguration;
they cannot be specified as part of the â€œip=â€ kernel command line parameter.”…””}”(hji  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KÔhjD  ubhì)”}”(hŒ¬Because the "domain" and "nameserver" options are recognised by DNS
resolvers, /etc/resolv.conf is often linked to /proc/net/pnp on systems
that use an NFS root filesystem.”h]”hŒ´Because the â€œdomainâ€ and â€œnameserverâ€ options are recognised by DNS
resolvers, /etc/resolv.conf is often linked to /proc/net/pnp on systems
that use an NFS root filesystem.”…””}”(hjw  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KØhjD  ubhì)”}”(hXB  Note that the kernel will not synchronise the system time with any NTP
servers it discovers; this is the responsibility of a user space process
(e.g. an initrd/initramfs script that passes the IP addresses listed in
/proc/net/ipconfig/ntp_servers to an NTP client before mounting the real
root filesystem if it is on NFS).”h]”hXB  Note that the kernel will not synchronise the system time with any NTP
servers it discovers; this is the responsibility of a user space process
(e.g. an initrd/initramfs script that passes the IP addresses listed in
/proc/net/ipconfig/ntp_servers to an NTP client before mounting the real
root filesystem if it is on NFS).”…””}”(hj…  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KÜhjD  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hj2  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Káhj  h²hubj  )”}”(hŒãnfsrootdebug
This parameter enables debugging messages to appear in the kernel
log at boot time so that administrators can verify that the correct
NFS mount options, server address, and root path are passed to the
NFS client.

”h]”(j  )”}”(hŒnfsrootdebug”h]”hŒnfsrootdebug”…””}”(hj£  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KèhjŸ  ubj)  )”}”(hhh]”hì)”}”(hŒÔThis parameter enables debugging messages to appear in the kernel
log at boot time so that administrators can verify that the correct
NFS mount options, server address, and root path are passed to the
NFS client.”h]”hŒÔThis parameter enables debugging messages to appear in the kernel
log at boot time so that administrators can verify that the correct
NFS mount options, server address, and root path are passed to the
NFS client.”…””}”(hj´  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Kähj±  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjŸ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kèhj  h²hubj  )”}”(hXø  rdinit=<executable file>
To specify which file contains the program that starts system
initialization, administrators can use this command line parameter.
The default value of this parameter is "/init".  If the specified
file exists and the kernel can execute it, root filesystem related
kernel command line parameters, including 'nfsroot=', are ignored.

A description of the process of mounting the root file system can be
found in Documentation/driver-api/early-userspace/early_userspace_support.rst

”h]”(j  )”}”(hŒrdinit=<executable file>”h]”hŒrdinit=<executable file>”…””}”(hjÒ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´KóhjÎ  ubj)  )”}”(hhh]”(hì)”}”(hXI  To specify which file contains the program that starts system
initialization, administrators can use this command line parameter.
The default value of this parameter is "/init".  If the specified
file exists and the kernel can execute it, root filesystem related
kernel command line parameters, including 'nfsroot=', are ignored.”h]”hXQ  To specify which file contains the program that starts system
initialization, administrators can use this command line parameter.
The default value of this parameter is â€œ/initâ€.  If the specified
file exists and the kernel can execute it, root filesystem related
kernel command line parameters, including â€˜nfsroot=â€™, are ignored.”…””}”(hjã  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Këhjà  ubhì)”}”(hŒ’A description of the process of mounting the root file system can be
found in Documentation/driver-api/early-userspace/early_userspace_support.rst”h]”hŒ’A description of the process of mounting the root file system can be
found in Documentation/driver-api/early-userspace/early_userspace_support.rst”…””}”(hjñ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Kñhjà  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j(  hjÎ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kóhj  h²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjî  h²hh³hÊh´Nubeh}”(h]”Œkernel-command-line”ah ]”h"]”Œkernel command line”ah$]”h&]”uh1hµhh·h²hh³hÊh´K-ubh¶)”}”(hhh]”(h»)”}”(hŒBoot Loader”h]”hŒBoot Loader”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj  h²hh³hÊh´Köubhì)”}”(hŒrTo get the kernel into memory different approaches can be used.
They depend on various facilities being available:”h]”hŒrTo get the kernel into memory different approaches can be used.
They depend on various facilities being available:”…””}”(hj*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Køhj  h²hubjù  )”}”(hhh]”(jþ  )”}”(hX‰  Booting from a floppy using syslinux

      When building kernels, an easy way to create a boot floppy that uses
      syslinux is to use the zdisk or bzdisk make targets which use zimage
      and bzimage images respectively. Both targets accept the
      FDARGS parameter which can be used to set the kernel command line.

      e.g::

         make bzdisk FDARGS="root=/dev/nfs"

      Note that the user running this command will need to have
      access to the floppy drive device, /dev/fd0

      For more information on syslinux, including how to create bootdisks
      for prebuilt kernels, see https://syslinux.zytor.com/

      .. note::
              Previously it was possible to write a kernel directly to
              a floppy using dd, configure the boot device using rdev, and
              boot using the resulting floppy. Linux no longer supports this
              method of booting.
”h]”(hì)”}”(hŒ$Booting from a floppy using syslinux”h]”hŒ$Booting from a floppy using syslinux”…””}”(hj?  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Kühj;  ubj  )”}”(hX	  When building kernels, an easy way to create a boot floppy that uses
syslinux is to use the zdisk or bzdisk make targets which use zimage
and bzimage images respectively. Both targets accept the
FDARGS parameter which can be used to set the kernel command line.

e.g::

   make bzdisk FDARGS="root=/dev/nfs"

Note that the user running this command will need to have
access to the floppy drive device, /dev/fd0

For more information on syslinux, including how to create bootdisks
for prebuilt kernels, see https://syslinux.zytor.com/

.. note::
        Previously it was possible to write a kernel directly to
        a floppy using dd, configure the boot device using rdev, and
        boot using the resulting floppy. Linux no longer supports this
        method of booting.
”h]”(hì)”}”(hX  When building kernels, an easy way to create a boot floppy that uses
syslinux is to use the zdisk or bzdisk make targets which use zimage
and bzimage images respectively. Both targets accept the
FDARGS parameter which can be used to set the kernel command line.”h]”hX  When building kernels, an easy way to create a boot floppy that uses
syslinux is to use the zdisk or bzdisk make targets which use zimage
and bzimage images respectively. Both targets accept the
FDARGS parameter which can be used to set the kernel command line.”…””}”(hjQ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´KþhjM  ubhì)”}”(hŒe.g::”h]”hŒe.g:”…””}”(hj_  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MhjM  ubj  )”}”(hŒ"make bzdisk FDARGS="root=/dev/nfs"”h]”hŒ"make bzdisk FDARGS="root=/dev/nfs"”…””}”hjm  sbah}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j  h³hÊh´MhjM  ubhì)”}”(hŒeNote that the user running this command will need to have
access to the floppy drive device, /dev/fd0”h]”hŒeNote that the user running this command will need to have
access to the floppy drive device, /dev/fd0”…””}”(hj{  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MhjM  ubhì)”}”(hŒyFor more information on syslinux, including how to create bootdisks
for prebuilt kernels, see https://syslinux.zytor.com/”h]”(hŒ^For more information on syslinux, including how to create bootdisks
for prebuilt kernels, see ”…””}”(hj‰  h²hh³Nh´Nubhö)”}”(hŒhttps://syslinux.zytor.com/”h]”hŒhttps://syslinux.zytor.com/”…””}”(hj‘  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j“  uh1hõhj‰  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M
hjM  ubhŒnote”“”)”}”(hŒÇPreviously it was possible to write a kernel directly to
a floppy using dd, configure the boot device using rdev, and
boot using the resulting floppy. Linux no longer supports this
method of booting.”h]”hì)”}”(hŒÇPreviously it was possible to write a kernel directly to
a floppy using dd, configure the boot device using rdev, and
boot using the resulting floppy. Linux no longer supports this
method of booting.”h]”hŒÇPreviously it was possible to write a kernel directly to
a floppy using dd, configure the boot device using rdev, and
boot using the resulting floppy. Linux no longer supports this
method of booting.”…””}”(hj¬  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Mhj¨  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hjM  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´Kþhj;  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj8  h²hh³hÊh´Nubjþ  )”}”(hXÝ  Booting from a cdrom using isolinux

      When building kernels, an easy way to create a bootable cdrom that
      uses isolinux is to use the isoimage target which uses a bzimage
      image. Like zdisk and bzdisk, this target accepts the FDARGS
      parameter which can be used to set the kernel command line.

      e.g::

        make isoimage FDARGS="root=/dev/nfs"

      The resulting iso image will be arch/<ARCH>/boot/image.iso
      This can be written to a cdrom using a variety of tools including
      cdrecord.

      e.g::

        cdrecord dev=ATAPI:1,0,0 arch/x86/boot/image.iso

      For more information on isolinux, including how to create bootdisks
      for prebuilt kernels, see https://syslinux.zytor.com/
”h]”(hì)”}”(hŒ#Booting from a cdrom using isolinux”h]”hŒ#Booting from a cdrom using isolinux”…””}”(hjÐ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MhjÌ  ubj  )”}”(hXj  When building kernels, an easy way to create a bootable cdrom that
uses isolinux is to use the isoimage target which uses a bzimage
image. Like zdisk and bzdisk, this target accepts the FDARGS
parameter which can be used to set the kernel command line.

e.g::

  make isoimage FDARGS="root=/dev/nfs"

The resulting iso image will be arch/<ARCH>/boot/image.iso
This can be written to a cdrom using a variety of tools including
cdrecord.

e.g::

  cdrecord dev=ATAPI:1,0,0 arch/x86/boot/image.iso

For more information on isolinux, including how to create bootdisks
for prebuilt kernels, see https://syslinux.zytor.com/
”h]”(hì)”}”(hŒüWhen building kernels, an easy way to create a bootable cdrom that
uses isolinux is to use the isoimage target which uses a bzimage
image. Like zdisk and bzdisk, this target accepts the FDARGS
parameter which can be used to set the kernel command line.”h]”hŒüWhen building kernels, an easy way to create a bootable cdrom that
uses isolinux is to use the isoimage target which uses a bzimage
image. Like zdisk and bzdisk, this target accepts the FDARGS
parameter which can be used to set the kernel command line.”…””}”(hjâ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MhjÞ  ubhì)”}”(hŒe.g::”h]”hŒe.g:”…””}”(hjð  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MhjÞ  ubj  )”}”(hŒ$make isoimage FDARGS="root=/dev/nfs"”h]”hŒ$make isoimage FDARGS="root=/dev/nfs"”…””}”hjþ  sbah}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j  h³hÊh´MhjÞ  ubhì)”}”(hŒ†The resulting iso image will be arch/<ARCH>/boot/image.iso
This can be written to a cdrom using a variety of tools including
cdrecord.”h]”hŒ†The resulting iso image will be arch/<ARCH>/boot/image.iso
This can be written to a cdrom using a variety of tools including
cdrecord.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MhjÞ  ubhì)”}”(hŒe.g::”h]”hŒe.g:”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M"hjÞ  ubj  )”}”(hŒ0cdrecord dev=ATAPI:1,0,0 arch/x86/boot/image.iso”h]”hŒ0cdrecord dev=ATAPI:1,0,0 arch/x86/boot/image.iso”…””}”hj(  sbah}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j  h³hÊh´M$hjÞ  ubhì)”}”(hŒyFor more information on isolinux, including how to create bootdisks
for prebuilt kernels, see https://syslinux.zytor.com/”h]”(hŒ^For more information on isolinux, including how to create bootdisks
for prebuilt kernels, see ”…””}”(hj6  h²hh³Nh´Nubhö)”}”(hŒhttps://syslinux.zytor.com/”h]”hŒhttps://syslinux.zytor.com/”…””}”(hj>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j@  uh1hõhj6  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M&hjÞ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´MhjÌ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj8  h²hh³hÊh´Nubjþ  )”}”(hX¯  Using LILO

      When using LILO all the necessary command line parameters may be
      specified using the 'append=' directive in the LILO configuration
      file.

      However, to use the 'root=' directive you also need to create
      a dummy root device, which may be removed after LILO is run.

      e.g::

        mknod /dev/boot255 c 0 255

      For information on configuring LILO, please refer to its documentation.
”h]”(hì)”}”(hŒ
Using LILO”h]”hŒ
Using LILO”…””}”(hjc  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M)hj_  ubj  )”}”(hXs  When using LILO all the necessary command line parameters may be
specified using the 'append=' directive in the LILO configuration
file.

However, to use the 'root=' directive you also need to create
a dummy root device, which may be removed after LILO is run.

e.g::

  mknod /dev/boot255 c 0 255

For information on configuring LILO, please refer to its documentation.
”h]”(hì)”}”(hŒˆWhen using LILO all the necessary command line parameters may be
specified using the 'append=' directive in the LILO configuration
file.”h]”hŒŒWhen using LILO all the necessary command line parameters may be
specified using the â€˜append=â€™ directive in the LILO configuration
file.”…””}”(hju  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M+hjq  ubhì)”}”(hŒzHowever, to use the 'root=' directive you also need to create
a dummy root device, which may be removed after LILO is run.”h]”hŒ~However, to use the â€˜root=â€™ directive you also need to create
a dummy root device, which may be removed after LILO is run.”…””}”(hjƒ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M/hjq  ubhì)”}”(hŒe.g::”h]”hŒe.g:”…””}”(hj‘  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M2hjq  ubj  )”}”(hŒmknod /dev/boot255 c 0 255”h]”hŒmknod /dev/boot255 c 0 255”…””}”hjŸ  sbah}”(h]”h ]”h"]”h$]”h&]”j  j  uh1j  h³hÊh´M4hjq  ubhì)”}”(hŒGFor information on configuring LILO, please refer to its documentation.”h]”hŒGFor information on configuring LILO, please refer to its documentation.”…””}”(hj­  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M6hjq  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´M+hj_  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj8  h²hh³hÊh´Nubjþ  )”}”(hŒ‹Using GRUB

      When using GRUB, kernel parameter are simply appended after the kernel
      specification: kernel <kernel> <parameters>
”h]”(hì)”}”(hŒ
Using GRUB”h]”hŒ
Using GRUB”…””}”(hjË  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M8hjÇ  ubj  )”}”(hŒsWhen using GRUB, kernel parameter are simply appended after the kernel
specification: kernel <kernel> <parameters>
”h]”hì)”}”(hŒrWhen using GRUB, kernel parameter are simply appended after the kernel
specification: kernel <kernel> <parameters>”h]”hŒrWhen using GRUB, kernel parameter are simply appended after the kernel
specification: kernel <kernel> <parameters>”…””}”(hjÝ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M:hjÙ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´M:hjÇ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj8  h²hh³hÊh´Nubjþ  )”}”(hX  Using loadlin

      loadlin may be used to boot Linux from a DOS command prompt without
      requiring a local hard disk to mount as root. This has not been
      thoroughly tested by the authors of this document, but in general
      it should be possible configure the kernel command line similarly
      to the configuration of LILO.

      Please refer to the loadlin documentation for further information.
”h]”(hì)”}”(hŒUsing loadlin”h]”hŒUsing loadlin”…””}”(hjû  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M=hj÷  ubj  )”}”(hXj  loadlin may be used to boot Linux from a DOS command prompt without
requiring a local hard disk to mount as root. This has not been
thoroughly tested by the authors of this document, but in general
it should be possible configure the kernel command line similarly
to the configuration of LILO.

Please refer to the loadlin documentation for further information.
”h]”(hì)”}”(hX%  loadlin may be used to boot Linux from a DOS command prompt without
requiring a local hard disk to mount as root. This has not been
thoroughly tested by the authors of this document, but in general
it should be possible configure the kernel command line similarly
to the configuration of LILO.”h]”hX%  loadlin may be used to boot Linux from a DOS command prompt without
requiring a local hard disk to mount as root. This has not been
thoroughly tested by the authors of this document, but in general
it should be possible configure the kernel command line similarly
to the configuration of LILO.”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M?hj		  ubhì)”}”(hŒBPlease refer to the loadlin documentation for further information.”h]”hŒBPlease refer to the loadlin documentation for further information.”…””}”(hj	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MEhj		  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´M?hj÷  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj8  h²hh³hÊh´Nubjþ  )”}”(hX
  Using a boot ROM

      This is probably the most elegant way of booting a diskless client.
      With a boot ROM the kernel is loaded using the TFTP protocol. The
      authors of this document are not aware of any no commercial boot
      ROMs that support booting Linux over the network. However, there
      are two free implementations of a boot ROM, netboot-nfs and
      etherboot, both of which are available on sunsite.unc.edu, and both
      of which contain everything you need to boot a diskless Linux client.
”h]”(hì)”}”(hŒUsing a boot ROM”h]”hŒUsing a boot ROM”…””}”(hj9	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MGhj5	  ubj  )”}”(hXÎ  This is probably the most elegant way of booting a diskless client.
With a boot ROM the kernel is loaded using the TFTP protocol. The
authors of this document are not aware of any no commercial boot
ROMs that support booting Linux over the network. However, there
are two free implementations of a boot ROM, netboot-nfs and
etherboot, both of which are available on sunsite.unc.edu, and both
of which contain everything you need to boot a diskless Linux client.
”h]”hì)”}”(hXÍ  This is probably the most elegant way of booting a diskless client.
With a boot ROM the kernel is loaded using the TFTP protocol. The
authors of this document are not aware of any no commercial boot
ROMs that support booting Linux over the network. However, there
are two free implementations of a boot ROM, netboot-nfs and
etherboot, both of which are available on sunsite.unc.edu, and both
of which contain everything you need to boot a diskless Linux client.”h]”hXÍ  This is probably the most elegant way of booting a diskless client.
With a boot ROM the kernel is loaded using the TFTP protocol. The
authors of this document are not aware of any no commercial boot
ROMs that support booting Linux over the network. However, there
are two free implementations of a boot ROM, netboot-nfs and
etherboot, both of which are available on sunsite.unc.edu, and both
of which contain everything you need to boot a diskless Linux client.”…””}”(hjK	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MIhjG	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´MIhj5	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj8  h²hh³hÊh´Nubjþ  )”}”(hXq  Using pxelinux

      Pxelinux may be used to boot linux using the PXE boot loader
      which is present on many modern network cards.

      When using pxelinux, the kernel image is specified using
      "kernel <relative-path-below /tftpboot>". The nfsroot parameters
      are passed to the kernel by adding them to the "append" line.
      It is common to use serial console in conjunction with pxelinux,
      see Documentation/admin-guide/serial-console.rst for more information.

      For more information on isolinux, including how to create bootdisks
      for prebuilt kernels, see https://syslinux.zytor.com/


”h]”(hì)”}”(hŒUsing pxelinux”h]”hŒUsing pxelinux”…””}”(hji	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MQhje	  ubj  )”}”(hX+  Pxelinux may be used to boot linux using the PXE boot loader
which is present on many modern network cards.

When using pxelinux, the kernel image is specified using
"kernel <relative-path-below /tftpboot>". The nfsroot parameters
are passed to the kernel by adding them to the "append" line.
It is common to use serial console in conjunction with pxelinux,
see Documentation/admin-guide/serial-console.rst for more information.

For more information on isolinux, including how to create bootdisks
for prebuilt kernels, see https://syslinux.zytor.com/


”h]”(hì)”}”(hŒkPxelinux may be used to boot linux using the PXE boot loader
which is present on many modern network cards.”h]”hŒkPxelinux may be used to boot linux using the PXE boot loader
which is present on many modern network cards.”…””}”(hj{	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MShjw	  ubhì)”}”(hX?  When using pxelinux, the kernel image is specified using
"kernel <relative-path-below /tftpboot>". The nfsroot parameters
are passed to the kernel by adding them to the "append" line.
It is common to use serial console in conjunction with pxelinux,
see Documentation/admin-guide/serial-console.rst for more information.”h]”hXG  When using pxelinux, the kernel image is specified using
â€œkernel <relative-path-below /tftpboot>â€. The nfsroot parameters
are passed to the kernel by adding them to the â€œappendâ€ line.
It is common to use serial console in conjunction with pxelinux,
see Documentation/admin-guide/serial-console.rst for more information.”…””}”(hj‰	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´MVhjw	  ubhì)”}”(hŒyFor more information on isolinux, including how to create bootdisks
for prebuilt kernels, see https://syslinux.zytor.com/”h]”(hŒ^For more information on isolinux, including how to create bootdisks
for prebuilt kernels, see ”…””}”(hj—	  h²hh³Nh´Nubhö)”}”(hŒhttps://syslinux.zytor.com/”h]”hŒhttps://syslinux.zytor.com/”…””}”(hjŸ	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j¡	  uh1hõhj—	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´M\hjw	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´MShje	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jý  hj8  h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jg  jh  uh1jø  h³hÊh´Kühj  h²hubeh}”(h]”Œboot-loader”ah ]”h"]”Œboot loader”ah$]”h&]”uh1hµhh·h²hh³hÊh´Köubh¶)”}”(hhh]”(h»)”}”(hŒCredits”h]”hŒCredits”…””}”(hjÑ	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÎ	  h²hh³hÊh´Mcubj  )”}”(hXW  The nfsroot code in the kernel and the RARP support have been written
by Gero Kuhlmann <gero@gkminix.han.de>.

The rest of the IP layer autoconfiguration code has been written
by Martin Mares <mj@atrey.karlin.mff.cuni.cz>.

In order to write the initial version of nfsroot I would like to thank
Jens-Uwe Mager <jum@anubis.han.de> for his help.”h]”(hì)”}”(hŒmThe nfsroot code in the kernel and the RARP support have been written
by Gero Kuhlmann <gero@gkminix.han.de>.”h]”(hŒXThe nfsroot code in the kernel and the RARP support have been written
by Gero Kuhlmann <”…””}”(hjã	  h²hh³Nh´Nubhö)”}”(hŒgero@gkminix.han.de”h]”hŒgero@gkminix.han.de”…””}”(hjë	  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:gero@gkminix.han.de”uh1hõhjã	  ubhŒ>.”…””}”(hjã	  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊ•;      h´Mehjß	  ubhì)”}”(hŒoThe rest of the IP layer autoconfiguration code has been written
by Martin Mares <mj@atrey.karlin.mff.cuni.cz>.”h]”(hŒRThe rest of the IP layer autoconfiguration code has been written
by Martin Mares <”…””}”(hj
  h²hh³Nh´Nubhö)”}”(hŒmj@atrey.karlin.mff.cuni.cz”h]”hŒmj@atrey.karlin.mff.cuni.cz”…””}”(hj
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ"mailto:mj@atrey.karlin.mff.cuni.cz”uh1hõhj
  ubhŒ>.”…””}”(hj
  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Mhhjß	  ubhì)”}”(hŒwIn order to write the initial version of nfsroot I would like to thank
Jens-Uwe Mager <jum@anubis.han.de> for his help.”h]”(hŒWIn order to write the initial version of nfsroot I would like to thank
Jens-Uwe Mager <”…””}”(hj'
  h²hh³Nh´Nubhö)”}”(hŒjum@anubis.han.de”h]”hŒjum@anubis.han.de”…””}”(hj/
  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:jum@anubis.han.de”uh1hõhj'
  ubhŒ> for his help.”…””}”(hj'
  h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hëh³hÊh´Mkhjß	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  h³hÊh´MehjÎ	  h²hubeh}”(h]”Œcredits”ah ]”h"]”Œcredits”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mcubeh}”(h]”Œ,mounting-the-root-filesystem-via-nfs-nfsroot”ah ]”h"]”Œ.mounting the root filesystem via nfs (nfsroot)”ah$]”h&]”uh1hµhhh²hh³hÊh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÊuh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hºNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j‚
  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÊŒ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j\
  jY
  jë  jè  j  j  jË	  jÈ	  jT
  jQ
  uŒ	nametypes”}”(j\
  ‰jë  ‰j  ‰jË	  ‰jT
  ‰uh}”(jY
  h·jè  j¹  j  jî  jÈ	  j  jQ
  jÎ	  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nh²hub.