Chad David wrote:
> Problem solved.
>
> cp GENERIC.hints DEBUG.hints
>
> Without them it isn't very happy... did I miss this as a requirement
> somewhere, or is my hardware/timing just a little funky?
Yes, you were not reading the commit messages or UPDATING or -current.
You should have a /boot/device.hints for your machine. You dont need
GENERIC.hints or DEBUG.hints if you have this set up correctly. As a head
start, you can cp GENERIC.hints to /boot/device.hints and you're done.
config and 'make install' will not let you forget this.. Were you installing
your kernel by hand or something?
> Chad
>
> On Tue, Jan 30, 2001 at 04:03:10PM +0100, Rogier R. Mulhuijzen wrote:
> >
> > >None of this has any bearing on the problem, which was caused by a bug
> > >in gensetdefs.pl. Please update your source tree and rebuild your
> > >kernel.
> >
> > Eek. I had the gensetdefs.pl problem too, but my machine just seemed to
> > lock. He says his machine does go on running.
> >
> > I have been pretty tied up lately, so maybe I read his post a bit too quick
ly.
> >
> > DocWilco
> >
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
