Date: Mon, 28 Aug 2000 08:24:50 -0500 (CDT) From: Mike Meyer <mwm@mired.org> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: Donn Miller <dmmiller@cvzoom.net>, Brooks Davis <brooks@one-eyed-alien.net>, current@FreeBSD.org Subject: Re: hints static wiring Message-ID: <14762.26659.335.344828@guru.mired.org> In-Reply-To: <39AA6699.41E12730@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> <39AA5DC6.8D73081B@FreeBSD.org> <14762.24829.363032.115605@guru.mired.org> <39AA6699.41E12730@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev writes: > Mike Meyer wrote: > > > > 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. > > > > That's clearly not true - I just removed an empty /boot/device.hints > > and rebooted, and all those things work fine. I can believe that such > > things won't work if they aren't specified in some hints file, but an > > empty /boot/device.hints doesn't do anything more to specify them than > > one that isn't there. > That's probably because you have hints compiled into your kernel. Try to compile > kernel w/o hints and use it with empty/unexistent /boot/device.hints and you will see > what I mean. Well, yeah, I'd expect that. I'm still trying to figure out what *good* failing to compile unless there's an empty /boot/device.hints does. I mean, if I didn't provide kernel hints, it would make some sense if the build process could determine that it was building on the machine it was running on. <mike 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?14762.26659.335.344828>