Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!darwin.sura.net!jvnc.net!yale.edu!ira.uka.de!rz.uni-karlsruhe.de!stepsun.uni-kl.de!uklirb!posthorn!vier!neuhaus From: neuhaus@vier.informatik.uni-kl.de (Stephan Neuhaus (HiWi Mattern)) Subject: [386BSD] Compiling new kernel (possible FAQ) Message-ID: <neuhaus.720122348@vier> Sender: news@posthorn.informatik.uni-kl.de (News system account) Nntp-Posting-Host: vier.informatik.uni-kl.de Organization: University of Kaiserslautern, Germany Date: Mon, 26 Oct 1992 17:59:08 GMT Lines: 34 Hi. DISCLAIMER: I'm posting this for a relative of mine who does not have Usenet access. I don't have 386BSD, so even *if* this is a FAQ, don't flame me, please. This may be a FAQ: When compiling a new kernel under 386BSD, is there a way to boot with an old kernel that is known to work? Booting from floppy doesn't count. Pretend that it doesn't exist. Background: The PC in question will not boot from drive B: (3.5") and the boot floppy on drive A: (5.25") won't boot. Don't ask me why. Now, my relative is keen on applying all the nice patches. He has compiled a new kernel but is somewhat reluctant to install it without having a method for booting with the old kernel. On Suns this is simple: Rename your old kernel to /vmunix.works, copy the new one to /vmunix, and boot. If the machine hangs, bring the machine down to the boot monitor and "b sd(0,0,0) /vmunix.works". Question: How is it done in 386BSD? Please reply by email, since I don't subscribe to this newsgroup. If you reply, please send mail to neuhaus@informatik.uni-kl.de, not neuhaus@vier.informatik.uni-kl.de. This is a bug in our news software, and I'm not sure when we'll get it fixed. Thank you. -- Stephan <neuhaus@informatik.uni-kl.de> sig closed for inventory. Please leave your pickaxe outside. PGP 2.0 public key available on request. Note the expiration date.