Fix examples of names the Sun PROM looks for in /tftpboot (PR#804)
This commit is contained in:
parent
8894b953f7
commit
b80cb1aea6
|
@ -1,4 +1,4 @@
|
||||||
.\" $NetBSD: diskless.8,v 1.3 1995/04/12 00:32:27 jtc Exp $
|
.\" $NetBSD: diskless.8,v 1.4 1995/08/08 20:34:05 gwr Exp $
|
||||||
.\"
|
.\"
|
||||||
.\"
|
.\"
|
||||||
.\" Copyright (c) 1994 Gordon W. Ross, Theo de Raadt
|
.\" Copyright (c) 1994 Gordon W. Ross, Theo de Raadt
|
||||||
|
@ -184,12 +184,13 @@ in HEX, a dot, and the architecture name (all upper case).
|
||||||
For example:
|
For example:
|
||||||
.Bd -literal -offset indent -compact
|
.Bd -literal -offset indent -compact
|
||||||
# cd /tftpboot
|
# cd /tftpboot
|
||||||
# ln -s boot.sun3.sunos.4.1.1 C0C5600C.SUN3
|
# ln -s boot.sun4.sunos.4.1.1 C0C5600C.SUN4
|
||||||
.Ed
|
.Ed
|
||||||
.Pp
|
.Pp
|
||||||
For a Sun4C machine, the name would be C0C5600C.SUN4C. The name
|
For a Sun3 machine, the name would be just C0C5600C
|
||||||
|
(the sun3 PROM does not append the architecture name). The name
|
||||||
used is architecture dependent, it simply has to match what the
|
used is architecture dependent, it simply has to match what the
|
||||||
booting client's rom wishes to it to be.
|
booting client's PROM wishes to it to be.
|
||||||
If the client's PROM fails to fetch the expected file,
|
If the client's PROM fails to fetch the expected file,
|
||||||
.Xr tcpdump 8
|
.Xr tcpdump 8
|
||||||
can be used to discover which filename the client is trying to read.
|
can be used to discover which filename the client is trying to read.
|
||||||
|
|
Loading…
Reference in New Issue