Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!nntp-hub2.barrnet.net!news.Stanford.EDU!microunity!usenet From: deborah@gallifrey.microunity.com (Deborah Gronke Bennett) Subject: Re: kernel compile failure In-Reply-To: Charles Reese's message of 20 Apr 1996 02:25:59 GMT Message-ID: <oq91fj955k.fsf@gallifrey.microunity.com> Sender: deborah@gallifrey.microunity.com Organization: MicroUnity Systems Engineering, Inc. X-Newsreader: Gnus v5.1 References: <4l9hvn$hv2@news.duke.edu> Date: Fri, 26 Apr 1996 00:53:59 GMT Lines: 39 In article <4l9hvn$hv2@news.duke.edu> Charles Reese <reese@chem.duke.edu> writes: I am trying to compile a custom kernel (ATHOS) and all seems to be well untill I do the make install at which point it says: chf etc. mv etc. install -c -m 555 -o root -g wheel -fschg kernel/ install: kernel: No such file or directory ***Error code 1 Stop . . . . Any ideas how to recover? Yup. All the make install does is to move the kernel image from the build directory into the root directory. An alternate way to do this is to cd to the build directory <somewhere>/sys/compile/<YOUR_CONFIG> and run these commands: # chflags noschg /kernel # mv /kernel /kernel.backup-name <--- this is optional but recommended # cp kernel /kernel After this you could run chflags to set the flags again, but I usually don't bother. Now your newly-built kernel is the kernel which will boot when you reboot the machine and choose the FreeBSD boot slice. If the new kernel doesn't work, you can boot kernel.backup-name at the second boot prompt (just type in the name). -- ---------- Deborah Gronke Bennett (WD5HJH) kernel and device drivers engineer deborah@microunity.com (408)-734-8100 MicroUnity Systems Eng., 255 Caspian Drive, Sunnyvale, CA 94089-1015 USA