From owner-freebsd-current Fri Feb 2 18:28:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 84B2F37B401 for ; Fri, 2 Feb 2001 18:28:34 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f132SC301387; Fri, 2 Feb 2001 18:28:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 02 Feb 2001 18:28:21 -0800 (PST) From: John Baldwin To: Doug Barton Subject: RE: devfs not making vn devices Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Feb-01 Doug Barton wrote: > 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 mdconfig(8) has all of the functionality of vnconfig now, along with all the functionality of the old md(4) driver. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message