Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!swrinde!emory!europa.eng.gtefsd.com!news.ans.net!cmcl2!sbcs.sunysb.edu!stark.UUCP!gene From: gene@stark.uucp (Gene Stark) Newsgroups: comp.os.386bsd.questions Subject: Re: patchkit 0.2.2 kernel and crypt() problems Date: 30 Mar 93 09:24:30 Organization: Gene Stark's home system Lines: 25 Message-ID: <GENE.93Mar30092430@stark.stark.uucp> References: <12689@vtserf.cc.vt.edu> NNTP-Posting-Host: stark.uucp In-reply-to: mmead@meadmc.async.vt.edu's message of 28 Mar 93 17:34:47 GMT In article <12689@vtserf.cc.vt.edu> mmead@meadmc.async.vt.edu (Matthew C. Mead) writes: I grabbed the patchkit 0.2.2 with some anticipation and just a little bit of excitement and followed its directions. When I finally got the new kernel built...and moved it to /386bsd, I attempted a reboot. Unfortunately, that wasn't as easy as patchkit 0.2.1, the computer told me that the 386bsd kernel was too large to read in.....thank god I moved the old one to 386bsd.old. So I examined the files when I got back running again under my old kernel, noticing that the new one was only a measly 100 bytes larger (457822 as compared to 457722) ... Right now I'm truly baffled so I remove all patches except for 1 - 82, what my old patchkit had included. Remake the kernel, etc. The file size is back to the smaller, older kernel's size, yet when I reboot, no dice, the system says it is too big to load. Got me ... any suggestions? I think there is a problem where if you don't do a "make clean" and remake the entire kernel, then it screws up on the size of the bss segment, making it too large. This is all I know, but I suggest doing the full make clean make depend make - Gene Stark -- stark@cs.sunysb.edu