Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sun-barr!olivea!uunet!vtserf!meadmc.async.vt.edu!mmead From: mmead@meadmc.async.vt.edu (Matthew C. Mead) Newsgroups: comp.os.386bsd.questions Subject: patchkit 0.2.2 kernel and crypt() problems Summary: resulting kernel too large Message-ID: <12689@vtserf.cc.vt.edu> Date: 28 Mar 93 17:34:47 GMT Sender: news@vtserf.cc.vt.edu Organization: Institute of Yesterday Lines: 25 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? My second problem is with the installation of a real crypt.c...I did this per the instructions in /usr/386bsd.errata/crypt.instructions, but no go with this either...once I rebuild everything and begin to use it, I notice the message about crypt not being installed....odd...I _did_ mod that Makefile.inc file so that dummy_crypt wasn't use....and ideas? Thanks! Matt