From owner-freebsd-current Fri Feb 2 20: 6:48 2001 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 0D02837B401 for ; Fri, 2 Feb 2001 20:06:30 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f1346LW35039; Fri, 2 Feb 2001 20:06:23 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200102030406.f1346LW35039@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Doug Barton Cc: freebsd-current@FreeBSD.ORG Subject: Re: devfs not making vn devices In-Reply-To: Date: Fri, 02 Feb 2001 20:06:21 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? In the meantime? besides using mdconfig, try this: mkdir /dev2 cd /dev2 sh /usr/src/etc/MAKEDEV vn0 vnconfig -c /dev2/vn0 .... > Doug Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message