On Fri, 27 Oct 2000, Donald G. Knecht,KR4JX wrote:

# while watching /var/log/messages on the server i see the classic connect
# to tftp, but nothing happens on the classic, after about 5 minutes
# classic reports it can't find file.
# i've tested tftp as the HOWTO suggests and find that i have to enter
# "get /tftpboot/AC100007.SUN4M" or else i get an "Access Error" from
# tftp. The HOWTO explains that the full path to the file may need to be
# entered into bootparams file.?
# client root=nfsserver:/export/client/root
# tftboot=/tftboot/AC100007.SUN4M
# 
# would that be what is meant?
# i tried setting boot-file in the classic PROM to
# /tftpboot/AC100007.SUN4M........didn't work

It means that you need to have a tftpboot directory set up somewhere,
such as /tftpboot.  Within /tftpboot, you need a symlink to "."
named "tftpboot" (i.e.

	mkdir /tftpboot		# or wherever you want to put it
	cd /tftpboot
	ln -s . tftpboot
)

You need to enable tftp in your /etc/inetd.conf file.  If you put
your tftpboot directory somewhere else besides /tftpboot, you need
to change the "-s /tftpboot" to be "-s /wherever/else/you/put/it".

_In that tftpboot area_, you need to have the file named
AC100007.SUN4M, which will probably be a symlink to AC100007,
which will probably be a symlink to boot.net.  If you're doing
anything tricky, such as booting more than one architecture from
that directory, the bootfile proper should be called boot.net.$arch,
where $arch expands to "sun4m", "i386", etc., and NNNNNNNN.$ARCH
and NNNNNNNN should both be links to boot.net.$arch.

# --
# LINUX - Because time is money.....
# and rebooting is a waste of time.

				--*greywolf;

Resident UNIX Wizard (not saying much)
SiteROCK Corporation
Phone: 3847CFEA3
greywolf@siteROCK.com