From b80cb1aea673d21155fcd1f2d6d40c2ce116a1bb Mon Sep 17 00:00:00 2001
From: gwr <gwr@NetBSD.org>
Date: Tue, 8 Aug 1995 20:34:05 +0000
Subject: [PATCH] Fix examples of names the Sun PROM looks for in /tftpboot 
 (PR#804)

---
 share/man/man8/diskless.8 | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/share/man/man8/diskless.8 b/share/man/man8/diskless.8
index a0eaf88236e6..a77ab035d1c8 100644
--- a/share/man/man8/diskless.8
+++ b/share/man/man8/diskless.8
@@ -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
@@ -184,12 +184,13 @@ in HEX, a dot, and the architecture name (all upper case).
 For example:
 .Bd -literal -offset indent -compact
 # cd /tftpboot
-# ln -s boot.sun3.sunos.4.1.1 C0C5600C.SUN3
+# ln -s boot.sun4.sunos.4.1.1 C0C5600C.SUN4
 .Ed
 .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
-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,
 .Xr tcpdump 8
 can be used to discover which filename the client is trying to read.