Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Mar 2001 09:31:56 +1100
From:      Murray Taylor <mtaylor@bytecraft.com.au>
To:        "'Bruce R. Montague'" <brucem@mail.cruzio.com>
Cc:        "'freebsd-small@freebsd.org'" <freebsd-small@freebsd.org>
Subject:   RE: odd "MFS Filesystem signature not found"
Message-ID:  <710709BB8B02D311942E006067441810544298@MELEXC01>

next in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?710709BB8B02D311942E006067441810544298>