Return to BSD News archive
Xref: sserve comp.unix.bsd.freebsd.misc:70 comp.os.386bsd.questions:17026
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newshost.marcam.com!news.mathworks.com!solaris.cc.vt.edu!goof.com!mmead
From: mmead@goof.com (matthew c. mead)
Newsgroups: comp.unix.bsd.freebsd.misc,comp.os.386bsd.questions
Subject: Re: FreeBSD boot looks for "386bsd"
Date: 16 Mar 1995 19:20:27 GMT
Organization: Goofs R Us
Lines: 31
Message-ID: <3ka31r$8k7@solaris.cc.vt.edu>
References: <D5Jo35.I8F@mv.mv.com>
NNTP-Posting-Host: goof.com
NNTP-Posting-User: mmead
In article <D5Jo35.I8F@mv.mv.com>, Coranth Gryphon <shaman@mv.mv.com> wrote:
>From the previous installation (1.1.0), the FreeBSD boot said to look for
>the kernel on sd0 at "/386bsd". Now, running 2.0R, it still looks for that
>file. The kernel-building procedure creates the file "kernel" which
>it installs as "/kernel".
Sounds right, except for the 2.0R looking for /386bsd.
>What I had to do was change the Makefile to install it as "/386bsd"
>and it works fine. I just have to make sure that all the things that
>look for the kernel (ex. kvm_mkdb) look at the new path instead.
>
>What I would like to do is tell the boot sequence to look for "/kernel"
>directly, and not muck around.
Hmm.
>Any ideas?
It sounds like somehow you didn't get the 2.0 bootblocks installed
properly. I bet you still have 1.1 bootblocks on your system.
-matt
--
Matthew C. Mead -> Virginia Tech Center for Transportation Research -
-> Multiple Platform System and Network Administration
Work Related -> mmead@ctr.vt.edu | mmead@goof.com <- All Other
---- ------- WWW -> http://www.goof.com/~mmead --- -----