Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!spool.mu.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD 2.0: Custom kernel problems Date: 3 Dec 1994 19:01:50 GMT Organization: Montana State University, Bozeman Montana Lines: 31 Message-ID: <3bqfau$4cd@pdq.coe.montana.edu> References: <D03nwu.39M@news.unr.edu> <3bl7qf$s3s@pdq.coe.montana.edu> <D07JAE.AL0@news.unr.edu> NNTP-Posting-Host: bsd.coe.montana.edu In article <D07JAE.AL0@news.unr.edu>, Eric V. Blood <eblood@pogonip.scs.unr.edu> wrote: >In article <3bl7qf$s3s@pdq.coe.montana.edu>, >Nate Williams <nate@bsd.coe.montana.edu> wrote: >>Is the new kernel named kernel? > >The kernel configuration was named WINKY. I would make it, and move >the kernel file in the WINKY directory to /kernel.test or something. >Then I would reboot passing kernel.test at the boot prompt. Ahh, that's the problem. Many of the functions get their information from the file /kernel. Even when you booted from kernel.test, the functions themselves were trying to get information from kernel. So, try doing this: # cp /kernel /kernel.old # cp /kernel.test /kernel # reboot And see if your problems go away. Nate -- nate@bsd.coe.montana.edu | FreeBSD dude and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | Unemployed, looking for permanant work in home #: (406) 586-0579 | CS/EE field.