From owner-freebsd-questions@FreeBSD.ORG Thu Aug 30 16:10:06 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC93616A41A for ; Thu, 30 Aug 2007 16:10:06 +0000 (UTC) (envelope-from fatman@crackmonkey.us) Received: from crackmonkey.us (crackmonkey.us [70.58.166.197]) by mx1.freebsd.org (Postfix) with ESMTP id A454F13C46A for ; Thu, 30 Aug 2007 16:10:06 +0000 (UTC) (envelope-from fatman@crackmonkey.us) Received: from tarani-bosatsu.dreamtrack.dnsalias.com (cpc1-swin7-0-0-cust216.brhm.cable.ntl.com [::ffff:86.18.88.217]) (AUTH: PLAIN fatman, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by crackmonkey.us with esmtp; Thu, 30 Aug 2007 10:09:54 -0600 id 0018805E.46D6EBD8.00000D0F Message-ID: <46D6EB34.5010000@crackmonkey.us> Date: Thu, 30 Aug 2007 17:07:16 +0100 From: Adam J Richardson User-Agent: Thunderbird 2.0.0.6 (X11/20070830) MIME-Version: 1.0 To: Wojciech Puchar References: <46D6DF26.5010600@crackmonkey.us> <20070830172230.W1947@wojtek.tensor.gdynia.pl> In-Reply-To: <20070830172230.W1947@wojtek.tensor.gdynia.pl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: King Wong , FreeBSD Mailing List Subject: Re: Ethernet controllers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2007 16:10:06 -0000 Wojciech Puchar wrote: >> I think most ethernet cards are fine with FreeBSD, if you're prepared >> to consider Project Evil aka ndisgen. [Warning: It's painful. Don't do >> it if you > > the project evil works fine on one machine which motherboard has > completely unknown ethernet card. and it works fine :) I've had the same experience. What a tool! To be able to take a part of one OS and cram it into another and have it work seamlessly! Amazing. One thing I have learned though is to go through the whole ndisgen process again after a kernel/world update. Obvious when you think about it, because ndisgen requires the kernel source, but not so obvious at the time. Actually finding the right XP driver for any given NIC can be a fearsome quest, so it's not a tool for any but the most adventurous new sysadmins, or those like me who are used to hunting down obscure .sys files across the trackless plains of the web. Regards, Adam J Richardson