From owner-freebsd-current Sun Sep 3 23:14:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA17690 for current-outgoing; Sun, 3 Sep 1995 23:14:15 -0700 Received: from linux.csie.nctu.edu.tw (linux.csie.nctu.edu.tw [140.113.235.252]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id XAA17668 for ; Sun, 3 Sep 1995 23:13:26 -0700 Received: (from jdli@localhost) by linux.csie.nctu.edu.tw (8.6.9/8.6.9) id OAA28971; Mon, 4 Sep 1995 14:09:54 +0800 From: Chien-Ta Lee Message-Id: <199509040609.OAA28971@linux.csie.nctu.edu.tw> Subject: Re: Making a release problem : bootfd To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 4 Sep 1995 14:09:53 +0800 (CST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <10926.810137971@time.cdrom.com> from "Jordan K. Hubbard" at Sep 3, 95 07:19:31 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 989 Sender: current-owner@FreeBSD.ORG Precedence: bulk > > > when making release.8 (bootfd), it died due to disklabel failure. > > How to solve it ? (I am using 2.2-CURRENT, kernel supports MFS) > > Thanks. > > You need to have the `vn' device in your kernel to make releases. > Stick this line somewhere near the end of your kernel config file: > > pseudo-device vn 1 > I had "pseudo-device vn 4" configured already ..... What Bruce said is right, stuffs get larger in 2.2-CURRENT, I increase the image size from 1075 to 1200 and continue the bootfd procedure. (solved the disk full problem) (the BOOTMFS kernel is too large, and the /stand is too large in 2.2-current if the image size is the default - 1075) But the disklabel still failed, I tried "vn0 rvn0 vn0c rvn0c vn0s1 rvn0s1" but all filed...without disklabeling, what will be effected ? Can't boot ? -- 李 建 達 (Adonis) 交大資工 Mail: jdli@csie.nctu.edu.tw