From owner-freebsd-current Tue Nov 2 23:24:45 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 DF738154F7 for ; Tue, 2 Nov 1999 23:24:43 -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 XAA03050; Tue, 2 Nov 1999 23:16:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199911030716.XAA03050@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:03:07 PST." <199911030703.XAA55313@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Nov 1999 23:16:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've settled Matt's qualms in private, since this was getting a little off track. Needless to say I'm quite on top of the current set of issues, and Matt's just a bit confused about what I'm trying to say. > :> great deal of work required to support this we're stuck with BOOTP > :> in the kernel. > : > :Er, hello? It's _already_been_done_, even. See above inre: netboot. > > Good god, you are talking about netboot? Hello? Mike, I get the feeling > that you've never actually tried to use netboot. You seem to believe > that it is direct replacement for BOOTP. It isn't even close. netboot > only works with a very small number of ethernet cards while the BOOTP > code in the kernel works with *all* ethernet cards that the kernel > supports. > > netboot doesn't work with a single one of my machines. > > -Matt > -- \\ 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