Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!howland.reston.ans.net!torn!nott!bnrgate!bnr.co.uk!zaphod.axion.bt.co.uk!uknet!warwick!zaphod.crihan.fr!vishnu.jussieu.fr!ensta!bsd10.ensta.fr!bouyer From: bouyer@bsd10.ensta.fr (Manuel Bouyer) Newsgroups: comp.os.386bsd.questions Subject: Re: [NetBSD] Kernel problems... Date: 23 Jun 1993 15:29:00 GMT Organization: Ecole Nationale Superieure de Techniques Avancees, Paris Lines: 24 Distribution: world Message-ID: <209srs$a3s@ensta.ensta.fr> References: <2030vf$ml2@news.ysu.edu> <207cp5INNbvb@bonnie.tcd-dresden.de> NNTP-Posting-Host: bsd10.ensta.fr 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 I had the same problem. Remove the DDB option, and your kernel size will go back to about 500 kb Another solution would be to compile the kernel to adresses upper than 1 Mb, but i don't know how to do this. If anybody has some informations about this, i am interested. --- Manuel Bouyer email: bouyer@ensta.fr --