From owner-freebsd-small Thu Dec 3 00:21:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16558 for freebsd-small-outgoing; Thu, 3 Dec 1998 00:21:54 -0800 (PST) (envelope-from owner-freebsd-small@FreeBSD.ORG) Received: from pixar.com (pixar.pixar.com [138.72.10.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16553 for ; Thu, 3 Dec 1998 00:21:51 -0800 (PST) (envelope-from markv@pixar.com) Received: from omnipotus.pixar.com (omnipotus.pixar.com [138.72.40.61]) by pixar.com (8.8.6/8.8.6) with SMTP id AAA09281 for ; Thu, 3 Dec 1998 00:21:36 -0800 (PST) Received: by omnipotus.pixar.com (Smail3.1.29.1 #2) id m0zlU0p-00HwReC; Thu, 3 Dec 98 00:21 PST From: "Mark VandeWettering" Message-Id: <9812030021.ZM16818@omnipotus> Date: Thu, 3 Dec 1998 00:21:23 -0800 Reply-To: markv@pixar.com X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: freebsd-small@FreeBSD.ORG Subject: Building PicoBSD on 2.2.x systems... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I understand that the primary problem with building PicoBSD on pre-3.0 systems is the behavior of the disklabel command, but even when I use the build scripts included in the 2.2.5 version, I get a problem during the stage3 part of the build process. In particular, I get the following messages: ====================== stage3 started ===================== -> Preparing 1.44 floppy filesystem... disklabel: ioctl DIOCWLABEL: Operation not supported by device -> Copying language dependent files... -> Populating floppy filesystem... 130 blocks Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/vn0c 1387 1133 254 82% 34 156 18% /mnt Press any key to continue... ==================== stage3 completed ===================== which would seem to indicate some problem with doing the disklabel on the vn device. Is something else supposed to be done here? The resulting floppy does boot, but bombs out when it tries to load the /etc filesystem into the MFS, claiming a corrupt superblock. Any hints? As a teaser, I am trying to create a version of FreeBSD that boots and serves a dedicated webcam using a simple cgi program that interfaces to the brooktree capture devices. My 3.0 CD is probably in the mail, so perhaps all this is moot, but I'd like to know the answer. Mark -- Mark T. VandeWettering Telescope Information (and more) Email: http://www.idle.com/~markv/ No Code International Member #1173 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message