Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2363 ; Mon, 01 Mar 93 10:55:59 EST Newsgroups: comp.os.386bsd.questions Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: Rebuilding the kernel Message-ID: <1993Feb27.233942.6272@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: Dept. of Computer Science, MSU, Bozeman Mt 59717 References: <001.2miu0.561.930226193741Z.CC-MAIL*/O=DOE/PRMD=GOV+USDOE.G02/ADMD=ATTMAIL/C=US/@mailgw> <1993Feb26.174613.1225@coe.montana.edu> <SHAKER.93Feb27011435@lager.cisco.com> Date: Sat, 27 Feb 1993 23:39:42 GMT Lines: 22 In article <SHAKER.93Feb27011435@lager.cisco.com> shaker@lager.cisco.com (Christopher J. Shaker) writes: > >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! Thanks Julian for this feature. However, this feature only exists using his enhanced boot blocks. Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, work #: (406) 994-4836 | I don't think they'll catch on - home #: (406) 586-0579 | Don Hammerstrom