From owner-freebsd-current Thu Jan 14 15:54:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05055 for freebsd-current-outgoing; Thu, 14 Jan 1999 15:54:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05039 for ; Thu, 14 Jan 1999 15:54:45 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id XAA20496; Thu, 14 Jan 1999 23:54:03 GMT Date: Thu, 14 Jan 1999 23:54:03 +0000 (GMT) From: Doug Rabson To: "Eric L. Hernes" cc: Luigi Rizzo , Doug Ambrisko , current@FreeBSD.ORG, erich@jake.lodgenet.com.demon.co.uk Subject: Re: netboot & ELF kernels In-Reply-To: <199901141510.JAA86132@jake.lodgenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Jan 1999, Eric L. Hernes wrote: > Luigi Rizzo writes: > >> > >A few comments on netboot. Recently, erich@lodgenet.com > >contributed netboot support for "fxp" cards. The msg was posted on some > >freebsd list about 1 month ago, and the file to look for is "nbfxp.tgz". > > > >Again, better than nothing, although it does not support ELF i think. > > > > Yea, that's right, although it's the netboot infrastructure, not the > fxp specifics (obviously). I talked to Mike Smith on the future of > netbooting when the 3-stage boot was still in early developoment. There > is some code in the new 3rd stage that looks like it's there for netboot; > but I'm not sure whether it's functional or not. It works well on the alpha. To make life easy, the SRM firmware has good support for low level networking. > > I was kind of figuring that the current bootroms would get the 3rd stage > boot loader, which would in turn fetch the real kernel. > > Supporting any card that has a FreeBSD driver isn't that tough, you don't > really need programming specs other than the driver source (although > it is nice). Tricker is actually burning the flash image. > > >Having tried both the tftp and nfs method, i prefer the latter a lot > >because it means i don't have to cnfigure another service (TFTP) on the > >server: with the current FreeBSD's netboot, you can supply all > >parameters with bootp (which you'd need anyways -- or replace it with > >DHCP i guess) and download the kernel with NFS (which your server > >probably already has). > > I'd have to agree with the bootp/nfs scheme. I use NFS enough that I'm > somewhat familiar with the errors it gives; but everytime something > goes wrong with tftp, I end up groveling through the man-pages and > tcpdump ;-) On the alpha, the firmware uses tftp to load the loader and that uses dhcp and NFS to load the kernel. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message