From owner-freebsd-fs@FreeBSD.ORG Tue Aug 5 15:32:29 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06EAE10656E4 for ; Tue, 5 Aug 2008 15:32:29 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id A1D088FC1C for ; Tue, 5 Aug 2008 15:32:26 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.2/8.14.2) with ESMTP id m75FX5Pk062580; Tue, 5 Aug 2008 10:33:05 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.2/8.14.2/Submit) id m75FX5Tg062579; Tue, 5 Aug 2008 10:33:05 -0500 (CDT) (envelope-from brooks) Date: Tue, 5 Aug 2008 10:33:05 -0500 From: Brooks Davis To: freebsd-fs@freebsd.org, pfgshield-freebsd@yahoo.com Message-ID: <20080805153305.GB55735@lor.one-eyed-alien.net> References: <370602.32048.qm@web32704.mail.mud.yahoo.com> <200808051430.m75EUQkK037117@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK" Content-Disposition: inline In-Reply-To: <200808051430.m75EUQkK037117@lurza.secnetix.de> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Subject: Re: Should we change dirent for 64 bit directory cookies ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2008 15:32:29 -0000 --/NkBOFFp2J2Af1nK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 05, 2008 at 04:30:26PM +0200, Oliver Fromme wrote: > Pedro Giffuni wrote: > > Oliver Fromme wrote: > > > One of the problems with that is that our PXE boot loader > > > requires NFSv2 support, AFAIK. If you drop NFSv2 server > > > support from the kernel, you can't boot PXE clients from > > > it anymore, unless someone adds NFSv3 support to the boot > > > loader. > >=20 > > I see, thanks for the explanation... yes, it sounds like this will > > have to wait a while then. I am looking at the Intel PXE spec and > > there is no mention about NFS. I will investigate a bit more but I > > guess there is a new wish for the PXE guys ;-). >=20 > The PXE spec is rather low-level, i.e. bascially it allows > for handling raw packets only. It does not implement a > real TCP/IP stack. So if you want to use any higher-level > protocols, you have to implement them yourself on top of > the PXE interface. >=20 > Note that our bootlaoder uses libstand for the actual > protocol implementations that are needed (BOOTP, NFS, RPC, > TFTP). You'll find the sources in /usr/src/lib/libstand. A summer of code project last year implemented TCP and HTTP support. -- Brooks --/NkBOFFp2J2Af1nK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFImHKxXY6L6fI4GtQRAgJHAKDZulAEa5vyykEZ+NcDBXeAeXFwGwCgh6+f q9eH+ADikrcS8gOdQKiA4eA= =N+x5 -----END PGP SIGNATURE----- --/NkBOFFp2J2Af1nK--