From owner-freebsd-current Mon Jul 17 10:10: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43]) by hub.freebsd.org (Postfix) with ESMTP id DE8AE37BAEB for ; Mon, 17 Jul 2000 10:10:00 -0700 (PDT) (envelope-from gjohnson@gs.verio.net) Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net) by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7) id 13EENs-000104-00 for current@freebsd.org; Mon, 17 Jul 2000 17:08:48 +0000 Received: from [204.1.124.74] (helo=power) by dfw-mmp1.email.verio.net with smtp (Exim 3.15 #4) id 13EENr-0007LV-00 for current@freebsd.org; Mon, 17 Jul 2000 17:08:47 +0000 Received: by localhost with Microsoft MAPI; Mon, 17 Jul 2000 12:08:46 -0500 Message-ID: <01BFEFE7.C21FC8D0.gjohnson@gs.verio.net> From: Tony Johnson To: "'current@freebsd.org'" Subject: nic cards Date: Mon, 17 Jul 2000 12:08:45 -0500 Organization: Expert Solutions, L.L.C. X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One thing that I just noticed on the python mailing list is a portable way of retrieving an ip addy. Why not start using eth0 (unfortunately as they do in Linuxland) eth1 ... For nic cards instead of fxp0 for an intel, etc... The fxp0 way is too hardware and implementation dependant. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message