Re: Fix make release for 4-STABLE

From: Peter Jeremy (PeterJeremy_at_optushome.com.au)
Date: 01/23/04

  • Next message: John Baldwin: "Re: Fix make release for 4-STABLE"
    Date: Sat, 24 Jan 2004 07:50:05 +1100
    To: Dag-Erling Smørgrav <des@des.no>
    
    

    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
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"


  • Next message: John Baldwin: "Re: Fix make release for 4-STABLE"

    Relevant Pages

    • Re: SP3 issues
      ... but clean reinstall is something I'm trying to avoid. ... install SP3 before upping the RAM. ... Non-viral malware is one of the most common causes of slow PCs. ...
      (microsoft.public.windowsxp.general)
    • Re: Brand new Imac suffering frightening kernel panic attacks
      ... You don't have phoney Apple stickers to hide, ... You have room to install more hard drives and components can breathe, ... A real PC is what Mac users call The Missing Link, ... your RAM is not to specifications you may get a kernel panic. ...
      (comp.sys.mac.system)
    • Re: Brand new Imac suffering frightening kernel panic attacks
      ... You don't have phoney Apple stickers to hide, ... You have room to install more hard drives and components can breathe, ... A real PC is what Mac users call The Missing Link, ... your RAM is not to specifications you may get a kernel panic. ...
      (comp.sys.mac.system)
    • Re: Brand new Imac suffering frightening kernel panic attacks
      ... You don't have phoney Apple stickers to hide, ... You have room to install more hard drives and components can breathe, ... A real PC is what Mac users call The Missing Link, ... your RAM is not to specifications you may get a kernel panic. ...
      (comp.sys.mac.system)
    • Re: regretting upgrade from ME to XP Home
      ... Their ValueRAM is the best bargain among their memory types. ... Crucial sells direct....they are a subsidiary of the company that manufactures their RAM. ... How To Install Internal & External Hard Drives ...
      (microsoft.public.windowsxp.newusers)