From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 06:00:14 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B99116A41F for ; Thu, 5 Jan 2006 06:00:14 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA8143D5E for ; Thu, 5 Jan 2006 06:00:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id DEED81FFACF; Thu, 5 Jan 2006 07:00:08 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 423151FFACE; Thu, 5 Jan 2006 07:00:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 78F4044487E; Thu, 5 Jan 2006 05:58:24 +0000 (UTC) Date: Thu, 5 Jan 2006 05:58:24 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Robert Huff In-Reply-To: <17340.38546.880801.123738@jerusalem.litteratus.org> Message-ID: <20060105055731.Q24703@maildrop.int.zabbadoz.net> References: <17340.38546.880801.123738@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: FreeBSD current mailing list Subject: Re: sk(4) ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 06:00:14 -0000 On Wed, 4 Jan 2006, Robert Huff wrote: > > Is there anyone currently in charge of the sk driver? Bill > Paul has disclaimed any further connection (never mind lack of time) > and I have a NIC which is not being recognized. And it's a PCI-E one? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT