Date: Mon, 28 Aug 2000 15:40:38 +0300 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Mike Meyer <mwm@mired.org> Cc: Donn Miller <dmmiller@cvzoom.net>, Brooks Davis <brooks@one-eyed-alien.net>, current@FreeBSD.org Subject: Re: hints static wiring Message-ID: <39AA5DC6.8D73081B@FreeBSD.org> References: <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Meyer wrote: > Donn Miller writes: > > Mike Meyer wrote: > > > I do read cvs-all, and I missed it. Not did I find device.hints in the > > > relevant Makefiles. Can you provide a pointer to details on how > > > /boot/device.hints is used in the build process, or how having an > > > empty one keeps you from shooting yourself in the foot? > > Actually, device.hints isn't used in the build process. > > In that case, why does the kernel build process fail if it doesn't > exist? Probably because you have `hints "BLABLA.hints"' line in your kernel config file. > > KERNEL.hints file is hard-coded into the kernel when your kernel is > > built (assuming you use one). /boot/device.hints is used to override > > the "hardcoded" values of hints, KERNEL.hints, at boot time. Sometimes, > > people can make a mistake in KERNEL.hints, and it's necessary to > > override those hints with /boot/device.hints. So, device.hints is > > created after-the-fact, and not part of the kernel build. Of course, if > > you don't have any hints to override, then just install an empty > > device.hints file. > > Will the system fail to boot if there isn't an empty device.hints > file? No, it will boot, but some devices (like keyboard, console etc) would not work. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39AA5DC6.8D73081B>