From owner-freebsd-questions Thu Nov 16 18: 1:55 2000 Delivered-To: freebsd-questions@freebsd.org Received: from c000.snv.cp.net (c000-h001.c000.snv.cp.net [209.228.32.65]) by hub.freebsd.org (Postfix) with SMTP id 91F2237B479 for ; Thu, 16 Nov 2000 18:01:53 -0800 (PST) Received: (cpmta 10572 invoked from network); 16 Nov 2000 18:01:52 -0800 Received: from tlgw1.turbolinux.co.jp (HELO ken.jp.tlan) (210.171.55.80) by smtp.smith.net (209.228.32.65) with SMTP; 16 Nov 2000 18:01:52 -0800 X-Sent: 17 Nov 2000 02:01:52 GMT Received: by ken.jp.tlan (sSMTP sendmail emulation); Fri, 17 Nov 2000 11:01:51 +0900 Date: Fri, 17 Nov 2000 11:01:51 +0900 From: Ken Smith To: questions@freebsd.org Subject: 3Com Megahertz 10/100 PCMCIA Message-ID: <20001117110151.A433@turbolinux.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Disposition: inline User-Agent: Mutt/1.3.11i-ja0-beta0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that the supported hardware document does not list support for the 3Com Megahertz 10/100 ethernet card. The model number for this card is 3CXFE575CT (or ...BT for the dongle version.) Is anyone planning to support this PCMCIA ethernet adapter? I have also read that OpenBSD 2.7 does support this adapter. Are OpenBSD and FreeBSD different enough that porting the driver would be difficult? I looked for a mail archive for this list but couldn't find one. If there's one out there, please let me know so I can verify that my questions have not already been answered before posting again. Also,I'm not currently subscribed to this mailing list, so please cc: me when responding. While I'm at it, can anyone give me a good argument for choosing [Open|Free|Net]BSD over any of the others? I've never used any of them but from my installation attempts Free goes down a easier than Open. However, the security saaviness of the Open guys is attractive. Many thanks for any answers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message