Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!noc.near.net!howland.reston.ans.net!agate!agate.berkeley.edu!cgd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.questions
Subject: Re: QUESTION: Diff between NetBSD & 386bsd kernel source
Date: 13 Jun 93 13:31:50
Organization: Kernel Hackers 'r' Us
Lines: 39
Message-ID: <CGD.93Jun13133150@eden.CS.Berkeley.EDU>
References: <C8FsBI.1A4@mordor.uucp>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: shane@mordor.uucp's message of Fri, 11 Jun 1993 02:59:41 GMT
In article <C8FsBI.1A4@mordor.uucp> shane@mordor.uucp (Shane Holder) writes:
As I understand it, NetBSD 0.8 is 386bsd 0.1 with the 0.2.2 patches
applied. I just looked on agate and saw that the current patch release
is 0.2.3 and was wondering if this patch may be applied to the NetBSD
kernel source.
don't *even think about it*... not only will you be wasting
your time, you'll be wasting a lot of it... if you'd like
the NetBSD sources, up to the latest patch level,
get the NetBSD-current source.
couldn't find db_symtab symbols
I'm unsure what this message means, but being the cat I am I replaced
my kernel (saving the old I'm not stupid just ignorant) and rebooted.
Things seemed to work properly though I didn't test it to it's full
extent.
yes, that's not an error message, really, just an informational one.
And, what is subr_mcount and is it needed?
it *is* included in the "generic kernel" files list,
and i have no idea why a kernel you were building wanted to
include it, unless you were building said kernel with profiling
support.
if that's the case, there's another bug that i think might
be in 0.8 (i forget when we fixed it, i.e. before or after
the 0.8 release... it's noted in the CHANGES file though)
the caused kernel profiling not to work.
chris
--
Chris G. Demetriou cgd@cs.berkeley.edu
"386bsd as depth first search: whenever you go to fix something you
find that 3 more things are actually broken." -- Adam Glass