From owner-freebsd-current Fri Feb 2 18:14:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id D54B337B401 for ; Fri, 2 Feb 2001 18:14:29 -0800 (PST) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id SAA47904 for ; Fri, 2 Feb 2001 18:14:29 -0800 (PST) (envelope-from DougB@gorean.org) Date: Fri, 2 Feb 2001 18:14:29 -0800 (PST) From: Doug Barton X-X-Sender: To: Subject: devfs not making vn devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been using devfs for a long time without problems. I had device vn in my kernel conf since the pre-devfs days, and today I needed to use a vn device to build picobsd. Lo and behold, I don't have any vn devices of any sort in /dev. I tried 'vnconfig -c /dev/vn0' but it also complained that the device didn't exist. I know that the goal is for vn to be phased out (at least that's my impression) but what do we do in the meantime? Doug -- "Pain heals. Chicks dig scars. Glory . . . lasts forever." -- Keanu Reeves as Shane Falco in "The Replacements" Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message