Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2348 ; Mon, 01 Mar 93 10:55:10 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!cronkite.cisco.com!cronkite.cisco.com!shaker From: shaker@lager.cisco.com (Christopher J. Shaker) Newsgroups: comp.os.386bsd.questions Subject: Re: Rebuilding the kernel Date: 27 Feb 93 01:14:35 Organization: cisco Systems, Inc. Lines: 20 Message-ID: <SHAKER.93Feb27011435@lager.cisco.com> References: <001.2miu0.561.930226193741Z.CC-MAIL*/O=DOE/PRMD=GOV+USDOE.G02/ADMD=ATTMAIL/C=US/@mailgw> <1993Feb26.174613.1225@coe.montana.edu> NNTP-Posting-Host: lager.cisco.com In-reply-to: osyjm@cs.montana.edu's message of Fri, 26 Feb 1993 17:46:13 GMT > Of course, if you muffed the kernel config, you'll have > to boot fixit.fs, mount your root fs, and cp /386bsd.alt to > /386bsd, then reboot and fix whatever's wrong. In case some people don't already know this, some (all?) 386BSD boot blocks let you choose which kernel to boot. When you boot, it prints out the kernel that it thinks it should boot. If you wait, or hit <Return>, it will boot this kernel. Instead, you can tell it to boot another kernel stored in the root directory by typing in the file name and hitting return. Thank you whoever added this feature! I'm not sure of exactly which boot block I'm running. It may be one of Julian's enhanced boot blocks, it might be one from the patchkit 0.2.1, or it could be the one from the 1742 fixit.fs disk that Julian created... Chris Shaker shaker@cisco.com