Date: Wed, 12 Sep 2001 22:16:30 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Doug Ambrisko <ambrisko@ambrisko.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Anyone experience problems with the "tap" device in current? Message-ID: <20010912221630.A60181@dhcp01.pn.xcllnt.net> In-Reply-To: <200109122359.f8CNxHg59969@ambrisko.com> References: <200109122359.f8CNxHg59969@ambrisko.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 12, 2001 at 04:59:16PM -0700, Doug Ambrisko wrote: > I just tried using tap in current. In both cases I don't see the > /dev/tapX devices with devfs and accessing it without devfs doesn't > work reporting "Device not configured". I tried it as a module and > built into the kernel. Does anyone have this working? My guess is that the breakage is related to the recent commits that were made to if_tap. VMWare doesn't work anymore on -current because the NG modules aren't loaded. These, AFAICT, depend on the device. So, at this time I can only acknowledge the breakage. I probably won't have the time to suggest or implement fixes. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010912221630.A60181>