From owner-freebsd-hackers Tue Jul 13 8:19:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id C289B14EEE for ; Tue, 13 Jul 1999 08:19:31 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id 9EF2FF818; Tue, 13 Jul 1999 11:19:25 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 9229F9B15; Tue, 13 Jul 1999 11:19:25 -0400 (EDT) Date: Tue, 13 Jul 1999 11:19:25 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: eT Cc: hackers@freebsd.org Subject: Re: Which device should I make with this error? In-Reply-To: <378B549C.4C511A98@post.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Jul 1999, eT wrote: > During a make release for 3.2-RELEASE I get the following error: > > Making the regular boot floppy. > Compressing doc files... > sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 > /R/stage/m > fsfd 8000 minimum2 > vnconfig: open: Device not configured > *** Error code 1 > > Stop. > *** Error code 1 > > What does this mean and how do I fix it? > According to http://www.freebsd.org/FAQ/FAQ244.html#247 : 13.2. How do I make my own custom release? To make a release you need to do three things: First, you need to be running a kernel with the vn driver configured in. Add this to your kernel config file and build a new kernel: pseudo-device vn #Vnode driver (turns a file into a device) Hence the 'vn' in 'vnconfig'... ...or, checking the manpage for vnconfig(8), it references vn(4) (aka pseudo-device vn). ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message