From owner-freebsd-current Sat Feb 3 0:24:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 46B4C37B67D for ; Sat, 3 Feb 2001 00:24:14 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f138OHB11750; Sat, 3 Feb 2001 09:24:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Doug Barton Cc: freebsd-current@FreeBSD.ORG Subject: Re: devfs not making vn devices In-Reply-To: Your message of "Fri, 02 Feb 2001 18:14:29 PST." Date: Sat, 03 Feb 2001 09:24:17 +0100 Message-ID: <11748.981188657@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Doug Barton writes: > 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. Use md instead of vn, it has all the same (and more) functionality. See mdconfig(8). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message