1.\" $NetBSD: diskless.8,v 1.11 1997/06/16 07:50:35 mrg Exp $
2.\"
3.\" Copyright (c) 1994 Gordon W. Ross, Theo de Raadt
4.\" All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
--- 11 unchanged lines hidden (view full) ---
20.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
21.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
22.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
23.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
24.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
25.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
26.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
27.\"
28.\" $FreeBSD: head/share/man/man8/diskless.8 70466 2000-12-29 09:18:45Z ru $
29.\"
30.Dd October 2, 1994
31.Dt DISKLESS 8
32.Os
33.Sh NAME
34.Nm diskless
35.Nd booting a system over the network
36.Sh DESCRIPTION
--- 6 unchanged lines hidden (view full) ---
43This file provides a general description of the interactions between
44a client and its server when a client is booting over the network.
45The general description is followed by specific instructions for
46configuring a server for diskless Sun clients.
47.Sh OPERATION
48When booting a system over the network, there are three
49phases of interaction between client and server:
50.Pp
51.Bl -enum -compact
52.It
53The PROM (or stage-1 bootstrap) loads a boot program.
54.It
55The boot program loads a kernel.
56.It
57The kernel does NFS mounts for root.
58.El
59.Pp
60Each of these phases are described in further detail below.
61.Pp
62In phase 1, the PROM loads a boot program. PROM designs
63vary widely, so this phase is inherently machine-specific.
64Sun machines use
--- 11 unchanged lines hidden (view full) ---
76network boot program either from diskette or
77using a special PROM on the network card.
78.Pp
79In phase 2, the boot program loads a kernel. Operation in
80this phase depends on the design of the boot program.
81(The design described here is the one used by Sun and NetBSD/hp300.)
82The boot program:
83.Pp
84.Bl -tag -width \&2.2 -compact
85.It 2.1
86gets the client IP address using
87.Tn RARP .
88.It 2.2
89gets the client name and server
90.Tn IP
91address by broadcasting an
92.Tn RPC / BOOTPARAMS / WHOAMI
--- 20 unchanged lines hidden (view full) ---
113.El
114.Pp
115In phase 3, the kernel does NFS mounts for root.
116The kernel repeats much of the work done by the boot program
117because there is no standard way for the boot program to pass
118the information it gathered on to the kernel.
119The procedure used by the kernel is as follows:
120.Pp
121.Bl -tag -width \&2.2 -compact
122.It 3.1
123The kernel finds a boot server using the same procedure
124as described in steps 2.1 and 2.2 above.
125.It 3.2
126The kernel gets the
127.Tn NFS
128file handle for root using the same procedure
129as described in steps 2.3 through 2.5 above.
--- 7 unchanged lines hidden (view full) ---
137Before a client can boot over the network,
138its server must be configured correctly.
139This example will demonstrate how a Sun client
140might be configured -- other clients should be similar.
141.Pp
142Assuming the client's hostname is to be
143"myclient",
144.Pp
145.Bl -enum
146.It
147Add an entry to
148.Pa /etc/ethers
149corresponding to the client's ethernet address:
150.Bd -literal -offset indent -compact
1518:0:20:7:c5:c7 myclient
152.Ed
153This will be used by
154.Xr rarpd 8 .
155.It
156Assign an IP address for myclient in your
157.Pa /etc/hosts
158or DNS database:
159.Bd -literal -offset indent -compact
160192.197.96.12 myclient
161.Ed
162.It
163If booting a Sun machine, ensure that
164.Pa /etc/inetd.conf
165is configured to run
166.Xr tftpd 8
167in the directory
168.Pa /tftpboot .
169.Pp
170If booting an HP 300-series machine, ensure that
171.Pa /etc/rbootd.conf
172is configured properly to transfer the boot program to the client.
173An entry might look like this:
174.Bd -literal -offset indent -compact
17508:00:09:01:23:E6 SYS_UBOOT # myclient
176.Ed
177.Pp
178See the
179.Xr rbootd 8
180manual page for more information.
181.It
182If booting a SPARC machine, install a copy of the appropriate diskless boot
183loader (such as
184.Pa /usr/mdec/boot )
185in the
186.Pa /tftpboot
187directory.
188Make a link such that the boot program is
189accessible by a file name composed of the client's IP address
--- 14 unchanged lines hidden (view full) ---
204.Pp
205If booting an HP 300-series machine, ensure that the network boot program
206.Pa SYS_UBOOT
207(which may be called
208.Pa uboot.lif
209before installation)
210is installed in the directory
211.Pa /usr/mdec/rbootd .
212.It
213Add myclient to the bootparams database
214.Pa /etc/bootparams :
215.Bd -literal -offset indent -compact
216myclient root=server:/export/myclient/root
217.Ed
218.Pp
219Note: For the swap file to be mountable, you have to make sure that mountd is
220started with the
221.Fl r
222flag.
223.It
224Build the swap file for myclient:
225.Bd -literal -offset indent -compact
226# mkdir /export/myclient
227# cd /export/myclient
228# dd if=/dev/zero of=swap bs=16k count=1024
229.Ed
230This creates a 16 Megabyte swap file.
231.It
232Populate myclient's
233.Pa /
234filesystem on the server. How this is done depends on the
235client architecture and the version of the NetBSD distribution.
236It can be as simple as copying and modifying the server's root
237filesystem, or perhaps you need to get those files out of the
238standard binary distribution.
239.Pp
240Note that, unlike SunOS, you need to create a mount point for the
241client's swap:
242.Bd -literal -offset indent -compact
243# mkdir /export/myclient/root/swap
244.Ed
245.It
246Export the required filesystems in
247.Pa /etc/exports :
248.Bd -literal -offset indent -compact
249/usr -ro myclient
250# for SunOS:
251# /export/myclient -rw=myclient,root=myclient
252# for NetBSD:
253/export/myclient -maproot=root -alldirs myclient
--- 12 unchanged lines hidden (view full) ---
266.Pa /export/usr.sun3
267and then use the following
268.Pa /etc/exports
269lines:
270.Bd -literal -offset indent -compact
271/export/usr.sun3 -ro myclient
272/export/myclient -rw=myclient,root=myclient
273.Ed
274.It
275Copy and customize at least the following files in
276.Pa /export/myclient/root :
277.Bd -literal -offset indent -compact
278# cd /export/myclient/root/etc
279# cp fstab.nfs fstab
280# cp /etc/hosts hosts
281# echo myclient > myname
282# echo 192.197.96.12 > hostname.le0
283.Ed
284.Pp
285Note that "le0" above should be replaced with the name of
286the network interface that the client will use for booting.
287.It
288Correct the critical mount points and the swap file in the client's
289.Pa /etc/fstab
290(which will be
291.Pa /export/myclient/root/etc/fstab )
292ie.
293.Bd -literal -offset indent -compact
294myserver:/export/myclient/root / nfs rw 0 0
295myserver:/usr /usr nfs rw 0 0
--- 33 unchanged lines hidden ---
2.\"
3.\" Copyright (c) 1994 Gordon W. Ross, Theo de Raadt
4.\" All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
--- 11 unchanged lines hidden (view full) ---
20.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
21.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
22.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
23.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
24.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
25.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
26.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
27.\"
28.\" $FreeBSD: head/share/man/man8/diskless.8 70466 2000-12-29 09:18:45Z ru $
29.\"
30.Dd October 2, 1994
31.Dt DISKLESS 8
32.Os
33.Sh NAME
34.Nm diskless
35.Nd booting a system over the network
36.Sh DESCRIPTION
--- 6 unchanged lines hidden (view full) ---
43This file provides a general description of the interactions between
44a client and its server when a client is booting over the network.
45The general description is followed by specific instructions for
46configuring a server for diskless Sun clients.
47.Sh OPERATION
48When booting a system over the network, there are three
49phases of interaction between client and server:
50.Pp
51.Bl -enum -compact
52.It
53The PROM (or stage-1 bootstrap) loads a boot program.
54.It
55The boot program loads a kernel.
56.It
57The kernel does NFS mounts for root.
58.El
59.Pp
60Each of these phases are described in further detail below.
61.Pp
62In phase 1, the PROM loads a boot program. PROM designs
63vary widely, so this phase is inherently machine-specific.
64Sun machines use
--- 11 unchanged lines hidden (view full) ---
76network boot program either from diskette or
77using a special PROM on the network card.
78.Pp
79In phase 2, the boot program loads a kernel. Operation in
80this phase depends on the design of the boot program.
81(The design described here is the one used by Sun and NetBSD/hp300.)
82The boot program:
83.Pp
84.Bl -tag -width \&2.2 -compact
85.It 2.1
86gets the client IP address using
87.Tn RARP .
88.It 2.2
89gets the client name and server
90.Tn IP
91address by broadcasting an
92.Tn RPC / BOOTPARAMS / WHOAMI
--- 20 unchanged lines hidden (view full) ---
113.El
114.Pp
115In phase 3, the kernel does NFS mounts for root.
116The kernel repeats much of the work done by the boot program
117because there is no standard way for the boot program to pass
118the information it gathered on to the kernel.
119The procedure used by the kernel is as follows:
120.Pp
121.Bl -tag -width \&2.2 -compact
122.It 3.1
123The kernel finds a boot server using the same procedure
124as described in steps 2.1 and 2.2 above.
125.It 3.2
126The kernel gets the
127.Tn NFS
128file handle for root using the same procedure
129as described in steps 2.3 through 2.5 above.
--- 7 unchanged lines hidden (view full) ---
137Before a client can boot over the network,
138its server must be configured correctly.
139This example will demonstrate how a Sun client
140might be configured -- other clients should be similar.
141.Pp
142Assuming the client's hostname is to be
143"myclient",
144.Pp
145.Bl -enum
146.It
147Add an entry to
148.Pa /etc/ethers
149corresponding to the client's ethernet address:
150.Bd -literal -offset indent -compact
1518:0:20:7:c5:c7 myclient
152.Ed
153This will be used by
154.Xr rarpd 8 .
155.It
156Assign an IP address for myclient in your
157.Pa /etc/hosts
158or DNS database:
159.Bd -literal -offset indent -compact
160192.197.96.12 myclient
161.Ed
162.It
163If booting a Sun machine, ensure that
164.Pa /etc/inetd.conf
165is configured to run
166.Xr tftpd 8
167in the directory
168.Pa /tftpboot .
169.Pp
170If booting an HP 300-series machine, ensure that
171.Pa /etc/rbootd.conf
172is configured properly to transfer the boot program to the client.
173An entry might look like this:
174.Bd -literal -offset indent -compact
17508:00:09:01:23:E6 SYS_UBOOT # myclient
176.Ed
177.Pp
178See the
179.Xr rbootd 8
180manual page for more information.
181.It
182If booting a SPARC machine, install a copy of the appropriate diskless boot
183loader (such as
184.Pa /usr/mdec/boot )
185in the
186.Pa /tftpboot
187directory.
188Make a link such that the boot program is
189accessible by a file name composed of the client's IP address
--- 14 unchanged lines hidden (view full) ---
204.Pp
205If booting an HP 300-series machine, ensure that the network boot program
206.Pa SYS_UBOOT
207(which may be called
208.Pa uboot.lif
209before installation)
210is installed in the directory
211.Pa /usr/mdec/rbootd .
212.It
213Add myclient to the bootparams database
214.Pa /etc/bootparams :
215.Bd -literal -offset indent -compact
216myclient root=server:/export/myclient/root
217.Ed
218.Pp
219Note: For the swap file to be mountable, you have to make sure that mountd is
220started with the
221.Fl r
222flag.
223.It
224Build the swap file for myclient:
225.Bd -literal -offset indent -compact
226# mkdir /export/myclient
227# cd /export/myclient
228# dd if=/dev/zero of=swap bs=16k count=1024
229.Ed
230This creates a 16 Megabyte swap file.
231.It
232Populate myclient's
233.Pa /
234filesystem on the server. How this is done depends on the
235client architecture and the version of the NetBSD distribution.
236It can be as simple as copying and modifying the server's root
237filesystem, or perhaps you need to get those files out of the
238standard binary distribution.
239.Pp
240Note that, unlike SunOS, you need to create a mount point for the
241client's swap:
242.Bd -literal -offset indent -compact
243# mkdir /export/myclient/root/swap
244.Ed
245.It
246Export the required filesystems in
247.Pa /etc/exports :
248.Bd -literal -offset indent -compact
249/usr -ro myclient
250# for SunOS:
251# /export/myclient -rw=myclient,root=myclient
252# for NetBSD:
253/export/myclient -maproot=root -alldirs myclient
--- 12 unchanged lines hidden (view full) ---
266.Pa /export/usr.sun3
267and then use the following
268.Pa /etc/exports
269lines:
270.Bd -literal -offset indent -compact
271/export/usr.sun3 -ro myclient
272/export/myclient -rw=myclient,root=myclient
273.Ed
274.It
275Copy and customize at least the following files in
276.Pa /export/myclient/root :
277.Bd -literal -offset indent -compact
278# cd /export/myclient/root/etc
279# cp fstab.nfs fstab
280# cp /etc/hosts hosts
281# echo myclient > myname
282# echo 192.197.96.12 > hostname.le0
283.Ed
284.Pp
285Note that "le0" above should be replaced with the name of
286the network interface that the client will use for booting.
287.It
288Correct the critical mount points and the swap file in the client's
289.Pa /etc/fstab
290(which will be
291.Pa /export/myclient/root/etc/fstab )
292ie.
293.Bd -literal -offset indent -compact
294myserver:/export/myclient/root / nfs rw 0 0
295myserver:/usr /usr nfs rw 0 0
--- 33 unchanged lines hidden ---