From owner-freebsd-current Wed Nov 3 0: 6:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 19BA615086 for ; Wed, 3 Nov 1999 00:06:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA03299; Tue, 2 Nov 1999 23:58:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030758.XAA03299@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@freebsd.org Subject: Re: GENERIC build broken In-reply-to: Your message of "Tue, 02 Nov 1999 23:53:38 PST." <199911030753.XAA55780@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 23:58:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think there is only one thing that will ever allow us to remove > the BOOTP code from the kernel, and that is if a time comes when > the BIOSes for all standard off-the-shelf motherboards all have > the ability to set a boot-from-network option. When/if that ever > occurs, then we will be able to remove the code. Please take a few minutes to go to developer.intel.com and read about PXE. Note that it's card-centric, not board-centric, so it doesn't require any buy-in from motherboard vendors. Also, because it's software only, there are already third-party vendors with software for most cards on the market. The last time I looked, InCom had support for well over 100 different network cards. With the general adoption of PXE in the WfM context for diskless WinTel installs, you can be certain that any network adapter with a bootrom socket is going to have PXE-compliant support available. If you want to participate in this dicussion much futher without dragging us off on these irrelevant tangents, it's quite important that you catch up on your reading. If you've been and looked at PXE more than a few months ago, go back again as they've massively updated the spec for PXE 2.0. Note that PXE 2.0, and UNDI in particular, go so far as to make it quite feasible to write a generic kernel driver that will talk to any PCI or PnP network adapter with a PXE-compliant bootrom. Not that I'm advocating this, you should understand. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message