Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Jan 2004 07:50:05 +1100
From:      Peter Jeremy <PeterJeremy@optushome.com.au>
To:        Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no>
Cc:        John Baldwin <jhb@freebsd.org>
Subject:   Re: Fix make release for 4-STABLE
Message-ID:  <20040123205005.GB4759@cirb503493.alcatel.com.au>
In-Reply-To: <xzpk73loiip.fsf@dwp.des.no>
References:  <20040118235148M.matusita@jp.FreeBSD.org> <20040119095453.GA43280@pc5.i.0x5.de> <20040119195826X.matusita@jp.FreeBSD.org> <200401201502.18549.jhb@FreeBSD.org> <xzpk73loiip.fsf@dwp.des.no>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 21, 2004 at 08:41:50AM +0100, Dag-Erling Smørgrav wrote:
>John Baldwin <jhb@FreeBSD.org> writes:
>>                                                       [...]  I have this bad
>> feeling that there is some kind of memory corruption bug in the loader and
>> that the problem goes away if you use a loader that has forth in it.

I presume this was the trying-to-DMA-across-a-64k-boundary problem
that was fixed recently.

>why use a loader w/o forth?  a complete loader with all 4th and conf
>files takes about 250k, which will definitely fit on the boot floppy,
>and with splitfs we don't need to worry about there being enough room
>for the kernel.

"goes away" doesn't mean that the problem isn't there.  It just means
that there's no obvious problem in John's particular splitfs test case.
A proper fix is far preferable to masking the problem and finding the
bug is far easier when it clearly manifests itself.

FORTH in the install loader is an interesting question.  Do the
benefits of FORTH in the initial install justify its size?  (I don't
know the answer to this).  I agree that we can do it (with the aid of
splitfs) but we don't want to unnecessarily bloat the install image.

Firstly, writing and reading floppies is painfully slow, though not
slow enough that you can usefully do something else whilst waiting.

Secondly, install image bloat translates to a higher minimum RAM
requirement and the floppy install is likely to be mostly used in
older systems which are likely to have less RAM.  The last figure I
can remember is 16MB RAM (it doesn't seem to be documented in the
-RELEASE Hardware notes).  The current 16MB limit means that it is
non-trivial to install FreeBSD on any normal 386-based system and
increasing it further will start biting 486-based systems.  I agree
that these systems are obsolete but they are still useful as SOHO-
grade routers, simple firewalls, printservers etc.

Peter



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