From owner-freebsd-small Thu Mar 15 14:32:32 2001 Delivered-To: freebsd-small@freebsd.org Received: from online.tmx.com.au (online.tmx.com.au [192.150.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A93837B719 for ; Thu, 15 Mar 2001 14:32:27 -0800 (PST) (envelope-from mtaylor@bytecraft.com.au) Received: from melexc01.bytecraft.com.au ([203.9.250.249]) by online.tmx.com.au (8.9.3/8.8.8) with ESMTP id JAA03308; Fri, 16 Mar 2001 09:32:13 +1100 (EST) Received: by MELEXC01 with Internet Mail Service (5.5.2448.0) id ; Fri, 16 Mar 2001 09:33:56 +1100 Message-ID: <710709BB8B02D311942E006067441810544298@MELEXC01> From: Murray Taylor To: "'Bruce R. Montague'" Cc: "'freebsd-small@freebsd.org'" Subject: RE: odd "MFS Filesystem signature not found" Date: Fri, 16 Mar 2001 09:31:56 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Based on Luigi's comment to reset the MD_ROOT_SIZE=2200 as it was in the bridge PICOBSD file it all built fine I am on 4.3-BETA as at 13/mar Note I am using the regular more(aka less) as the ports stuff isnt available and at present (done when I was using the 1440 MD size) I have commented out tcpdump. I did have to modify the picobsd script and add ' -s labels' to all vnconfig lines and I changed all ${TYPE} to ${THETYPE} as TYPE was never set anywhere As my previous email indicated - all I have to do now is get the floppy disk drive replaced by our IT bloke! mjt > -----Original Message----- > From: Bruce R. Montague [SMTP:brucem@mail.cruzio.com] > Sent: Friday, 16 March 2001 07:07 > To: mtaylor@bytecraft.com.au > Subject: odd "MFS Filesystem signature not found" > > > Here's an odd one. I downloaded the latest 4.3 BETA > this monday and have been building the various > picobsd types. > > I build the "bridge" config w/o seeing the MFS > filesystem signature problem... but I _did_ > see this error when building the vanilla "net" > config. > > I did all my builds w/o any changes, that is, > no dialog alterations to the default, no PICOBSD > config file changes. > > No here's the troublesome thing... the problem > "fixed itself". After a session last night and > one this morning (after a reboot), the problem > just disappeared. I had "forced" a good "net" > build by adding to PICOBSD an: > options MD_ROOT_SIZE=2200 # same as def_sz > > line... not really sure why this build > worked... and after doing this I cant > get any build to fail (well, I dont have > a supported Ethernet device in the final > target, so the final system doesnt usually > run, but the build goes fine). > > I'm wondering if maybe something somewhere > can left over as the result of crash, and > not cleaned, causing confusion until a > good build or complete cleanup, etc. > > > - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message