From owner-freebsd-doc@FreeBSD.ORG  Tue Sep  5 22:33:14 2006
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
X-Original-To: doc@FreeBSD.org
Delivered-To: freebsd-doc@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7891816A4DF;
	Tue,  5 Sep 2006 22:33:14 +0000 (UTC)
	(envelope-from bseklecki@collaborativefusion.com)
Received: from mx02.pub.collaborativefusion.com
	(mx02.pub.collaborativefusion.com [206.210.72.73])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5EE7543D69;
	Tue,  5 Sep 2006 22:33:13 +0000 (GMT)
	(envelope-from bseklecki@collaborativefusion.com)
Received: from soundwave.pgh.priv.collaborativefusion.com
	(pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested) (Authenticated sender: seklecki)
	by mx02.pub.collaborativefusion.com (Postfix) with ESMTP id 07D80AC81F; 
	Tue,  5 Sep 2006 18:32:54 -0400 (EDT)
From: "Brian A. Seklecki" <bseklecki@collaborativefusion.com>
To: doc@FreeBSD.org, alfred@FreeBSD.org
Content-Type: text/plain
Organization: Collaborative Fusion, Inc.
Date: Tue, 05 Sep 2006 18:33:12 -0400
Message-Id: <1157495592.83171.49.camel@soundwave.pgh.priv.collaborativefusion.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Cc: 
Subject: FreeBSD Jumpstart Guide / PXE Docs (TFTP ONLY)
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
	<mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2006 22:33:14 -0000

These docs should probably more-clearly identify how pxeboot(8) makes
its decision regarding the file retrieval mechanisms. The man page is
ambiguous.

Right now the assumption is that the user wants to use NFS to provide
"/boot".  However TFTP can be used.  I.e., for users who just want to
load kernel+MFS Install image (i.e., install-only, no live system VIA
NFS):

As best I can tell, it has to do with the variables contained with the
DHCP lease offer.  Examples of TFTP-file-retrieval:


I.e.,w e need instructions on:

*) Compiling pxeboot w/o NFS and w/ TFTP support:

   make LOADER_TFTP_SUPPORT=yes

*) Explain troubleshooting inetd(8)/tfpd(8):

  server$ inetd -dl & tail -f /var/log/xfer

*) Explain troubleshooting FTP and NFS:

  server$ tcpdump -n "port tftp"

*) dhcpd(8)/dhcpd.conf(5) examples:


host web00 {
          hardware ethernet c0:ff:33:c0:ff:33;
          fixed-address 192.168.0.100;
          option host-name "web00";
          option routers 192.168.0.1;
          # These get PXE Loaded (read by the hardware)
          filename "/pxeboot";
          option bootfile-name "/pxeboot";
          # These are read by PXE itself to move on to 2nd stage
          option tftp-server-name "192.168.0.50";
          #option root-path "192.168.0.50:/tftpboot";
          server-name "192.168.0.50";
          next-server 192.168.0.50;
}


The strange thing is that even with the proper config pxeboot(8) still
attempts to init NFS using "NFS MOUNT RPC error: 60", then gracefully
fails and continues to TFTP load...

~BAS


-- 
Brian A. Seklecki <bseklecki@collaborativefusion.com>
Collaborative Fusion, Inc.