Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!news.cerf.net!pagesat!decwrl!spool.mu.edu!howland.reston.ans.net!agate!library.ucla.edu!news.mic.ucla.edu!pita.cns.ucla.edu!scott From: scott@pita.cns.ucla.edu (Scott Burris) Newsgroups: comp.os.386bsd.questions Subject: [NetBSD 0.9] panic: init died, Windows NT coexistence Date: 14 Sep 1993 23:53:15 GMT Organization: UCLA Campus Network Services Lines: 23 Distribution: world Message-ID: <275lhb$otg@news.mic.ucla.edu> NNTP-Posting-Host: pita.cns.ucla.edu I compiled up a new kernel to run on a 386/33 system and whenever I try to run it instead of the distributed kernel, the system panic's with init died. Any words of wisdom here? I checked to make sure that it's compiled for a 386 with the math emulator. Another new kernel works just fine on a 486/33. (I needed a kernel with some strategically placed printf's so I could figure out why my port of color_xterm failed to become the controlling terminal of the PTY it ran on -- needed color for Seyon). I've finally made 0.9 NetBSD and Windows NT exist peacefully on a system, but I'm having trouble selecting which of them should boot. I thought os-bs would work, and it does allow me to select which system to boot, but Windows NT no longer reconizes a striped volume set when booted from os-bs; 0.9 works fine. I was forced to revert back to the normal MBR and use fdisk to twiddle active partitions (bleh!). Anyone know of another partition selector to try? I'm thinking of trying to figure out how to boot NetBSD from within the Windows NT boot selector as a last resort. -- ---------- Scott Burris UCLA Campus Network Services cnetslb@oac.ucla.edu (310) 206-4860 - OR - scott@pita.cns.ucla.edu