Lines Matching +full:nfs +full:- +full:kernel +full:- +full:server
1 .\"-
2 .\" SPDX-License-Identifier: BSD-3-Clause
42 re-installing file systems on a local disk.
44 a client and its server when a client is booting over the network.
47 phases of interaction between client and server:
48 .Bl -enum
50 The stage-1 bootstrap, typically PXE built into your Ethernet
51 card, loads a second-stage boot program.
53 The second-stage boot program, typically
56 the kernel, and boots the kernel.
58 The kernel
59 .Tn NFS
65 First, the stage-1 bootstrap loads the stage-2 boot program over
67 The stage-1 bootstrap typically uses
80 directory on the server, which is typically
83 The stage-2 boot program then loads additional modules and the kernel.
88 server.
90 .Ic next-server
93 configurations to specify the server holding
94 the second stage boot files and kernel.
95 The stage-2 program uses
96 .Tn NFS
101 .Tn NFS
116 here so you can place a custom kernel
120 .Tn NFS
123 client, the stage-2 boot will load your server's kernel as the kernel for
127 .Bd -literal -offset indent
133 In phase 3, the kernel acquires IP networking configuration in one
137 kernel using the kernel environment, then the kernel will configure
159 .Bl -bullet
162 .Tn NFS
163 server which exports a root and
168 scripts work with read-only partitions, as long as root is exported with
174 .Bd -literal -offset indent
175 <ROOT> -ro -maproot=0 -alldirs <list of diskless clients>
176 /usr -ro -alldirs <list of diskless clients>
181 is the mount point on the server of the root partition.
184 can be used to create a shared read-only root partition,
186 (again as read-only) the root directory used by
187 the server itself.
193 server.
203 .Bd -literal -offset indent
207 :sa=<SERVER>:\\
209 :rp="<SERVER>:<ROOT>":
215 .Aq SERVER ,
224 can help in creating it, using the server's root partition
227 simply use the server's own root directory,
237 boot as you do on the server.
261 .Pa /conf/<broadcast-ip> ,
263 .Pa /conf/<machine-ip> .
266 which will entirely replace the server's
271 You can clone the server's
276 to remount the server's
290 Alternatively, if the server contains several independent roots, the file
293 .Dl 10.0.0.1:/usr/diskless/4.7-RELEASE/etc
296 .Pa /usr/diskless/4.7-RELEASE
298 .Pa /usr/diskless/4.8-RELEASE
323 You then typically provide file-by-file overrides in the
336 You can supply network-specific defaults
358 Since you normally clone the server's
364 if the server has a firewall but you do not, you might wish
377 .Bd -literal -offset indent
378 <SERVER>:<ROOT> / nfs ro 0 0
379 <SERVER>:/usr /usr nfs ro 0 0
389 which could be empty but prevents the server's own
407 as the switch variable to do machine-specific configuration
413 The kernel for the
416 .Tn NFS
419 must include support for the NFS client:
425 to the kernel using the kernel environment, you will also need to include
437 booting environment relies on memory-backed file systems to
439 is mounted read-only; as such, it is necessary to add the following
440 to the device section of the kernel configuration:
446 or your kernel
453 .Tn NFS