I had that, and many other problems, about a week ago and I am not sure but i
think that I ended up doing an rm -rf /usr/sys/modules/* , cvsuped made world
and built new kernel with no problem. I remember that I had to erase all the
modules directory but I'm not comeletely sure that it was this problem. Sorry,
it's old age.
ed
Quoting Leif Neland <[EMAIL PROTECTED]>:
>
>
> On Tue, 27 Feb 2001, Gary Jennejohn wrote:
>
> > John Baldwin writes:
> > >
> > > On 27-Feb-01 Leif Neland wrote:
> > > > This happens with both my custom and GENERIC kernel.
> > > >
> > > > It has failed for some days, and also with source cvsup'ed today.
> > > > A kernel built with "make buildkernel -k" works...
> > > >
> > > > Leif
> > >
> > > Have you tried running make depend?
> > >
> >
> >
> > Failing that, trying deleting your /sys/compile/<NAME> directory
> > and re-config'ing your kernel. This has always worked for me.
> >
> I'm building the kernel "the new way", ie cd /usr/src
> make buildkernel KERNCONF=<kernelname>
>
> So the kernel is build in /usr/obj/usr/src/sys/GENERIC
>
> I deleted this, which buildkernel does itself, and config'ing it does too,
> and as I expected, it didn't make any difference.
>
> Leif
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
--
EnContacto.Net - InternetSalon.Org - CafeMania.Net
-------------------------------------------------
EnContacto.Net - CafeMania.Net - InternetSalon.Org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
