Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!fauern!news.tu-chemnitz.de!irz401!uriah!not-for-mail
From: j@bonnie.tcd-dresden.de (J Wunsch)
Newsgroups: comp.os.386bsd.questions
Subject: Re: [NetBSD] Kernel problems...
Date: 22 Jun 1993 18:42:13 +0200
Organization: Textil Computer Design GmbH, Dresden, Germany
Lines: 26
Message-ID: <207cp5INNbvb@bonnie.tcd-dresden.de>
References: <2030vf$ml2@news.ysu.edu>
NNTP-Posting-Host: bonnie.tcd-dresden.de
In article <2030vf$ml2@news.ysu.edu> ak793@yfn.ysu.edu (Scott E. Derby) writes:
>
> I recently grabed the tar'ed kernel soruce from sun-lamp
>and when to compile a new kernel, supporting lpt/lpa's. After
>the compile (config GENERICISA), it generated a 618K kernel.
>knowing that it wouldn't work, I figured I'll cut the SCSI
>support out of it, being I have no SCSI devices. That generated
>a kernel of 586K. It too, wouldn't work..
> I'm currently still working with the origional compiler
>to NetBSD (GCCv1.39). Anything I'm donig wrong here, that would
>cause the generic configuration to compile such HUGE kernels
Maybe your kernels really wouldn't load, but: don't care too
much for the size values you see on ls -l. Always have a look
at the `size 386bsd', for two reasons: your kernel always has
a symbol table. Beware of stripping it, some programs (ps, w)
rely on it. If you don't compile with -g, there are only global
symbols, they take space in the file, but aren't loaded.
On the other hand, the bss section isn't part of the file but
requires memory when the kernel loads. (Though i'm not aware
whether the bss will count into the 640 k limit.)
--
in real life: J"org Wunsch | ) o o | primary: joerg_wunsch@tcd-dresden.de
above 1.8 MHz: DL 8 DTL | ) | | private: joerg_wunsch@uriah.sax.de
| . * ) == |
``An elephant is a mouse with an operating system.''