From owner-freebsd-net Wed May 6 12:18:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26905 for freebsd-net-outgoing; Wed, 6 May 1998 12:18:33 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26889 for ; Wed, 6 May 1998 12:18:24 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id MAA07625; Wed, 6 May 1998 12:08:20 -0700 (PDT) Message-Id: <199805061908.MAA07625@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: "Justin T. Gibbs" Cc: freebsd-net@FreeBSD.ORG Subject: Re: ethernet Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 06 May 1998 12:08:19 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 May 1998 12:07:28 -0600 (MDT) "Justin T. Gibbs" wrote: > I'm still waiting to see NetBSD cleanly deal with LKMs in it's > autoconfiguration code. Config.new is not the answer to all > configuration problems, although I will admit that it is much > better than FreeBSD's current config nightmare. Dealing with LKMs really only requires defining a way of specifying the locator arguments. Then, the autoconfiguration code locates the parent node, and attempts to match/probe the device given the new driver/locators. The reason THAT hasn't been done is because the LKM interface sucks rocks (and it's basically the same as FreeBSD's), but that's been known for a while. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 428 6939 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message