Re: hints static wiring

2000-08-29 Thread Warner Losh
In message [EMAIL PROTECTED] Greg Lehey writes: : 2. You must have a /boot/device.hints file, and it must contain at : least some entries Add "unless you compile the hints statically into the kernel, in which case it may be empty." and you will be correct. There's plenty of potential for

Re: hints static wiring

2000-08-29 Thread Warner Losh
In message [EMAIL PROTECTED] Brooks Davis writes: : Which begs the question: when should the hints file be updated? : : When you add new devices which require hints to work. Since GENERIC.hints : covers the defaults for most of those devices and I don't see too many : new isa drivers going in

Re: hints static wiring

2000-08-29 Thread Mike Meyer
First, I want to thank everyone for taking the time to explain what was going on. It's now clear that I was confused, and things aren't as bad as I thought. I'd like to see the Makefile changes so that if there wasn't an empty /boot/device.hints, one was created, but that's relatively minor.

Re: hints static wiring

2000-08-29 Thread Brooks Davis
On Tue, Aug 29, 2000 at 04:15:09AM -0500, Mike Meyer wrote: Brooks Davis writes: This is more correct. The new world order says that hints are not in the kernel, instead they are loaded by the loader at boot time. By default they are loaded from /boot/device.hints. Without hints in some

Re: hints static wiring

2000-08-29 Thread David O'Brien
On Mon, Aug 28, 2000 at 06:29:21PM -0700, Brooks Davis wrote: On Tue, Aug 29, 2000 at 10:25:26AM +0930, Greg Lehey wrote: At the very least, there appears to be confusion about how to use the hints. I can see two conflicting views here: 1. You must have a /boot/device.hints file, but

Re: hints static wiring

2000-08-29 Thread Brooks Davis
On Tue, Aug 29, 2000 at 10:30:24AM -0700, David O'Brien wrote: On Mon, Aug 28, 2000 at 06:29:21PM -0700, Brooks Davis wrote: This is minimally correct. I.e. that's what the build system requires. This works if you build static hints into your kernel. Please stop saying FUD. The

Re: hints static wiring

2000-08-29 Thread Warner Losh
In message [EMAIL PROTECTED] Brooks Davis writes: : On Tue, Aug 29, 2000 at 10:30:24AM -0700, David O'Brien wrote: : On Mon, Aug 28, 2000 at 06:29:21PM -0700, Brooks Davis wrote: : This is minimally correct. I.e. that's what the build system requires. : This works if you build static hints

Re: hints static wiring

2000-08-29 Thread Mike Meyer
David O'Brien writes: On Mon, Aug 28, 2000 at 06:29:21PM -0700, Brooks Davis wrote: On Tue, Aug 29, 2000 at 10:25:26AM +0930, Greg Lehey wrote: At the very least, there appears to be confusion about how to use the 2. You must have a /boot/device.hints file, and it must contain at

Re: hints static wiring

2000-08-29 Thread Warner Losh
In message [EMAIL PROTECTED] Mike Meyer writes: : I suspect I'm going to be one of those people, but let's ask the next : question. How do the two approaches compare from a performance : standpoint? Completely identical. One loads the table from a file, the other reads it from the kernel. :

Re: hints static wiring

2000-08-28 Thread Mike Meyer
Brooks Davis writes: On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsuzaki wrote: Doing 'make install' without /boot/device.hints is failed, saying "You must set up a /boot/device.hints file first." Is this right? You should read cvs-all. There was a commit by Peter which forces

Re: hints static wiring

2000-08-28 Thread Matthew Jacob
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? cvs-all is not appropriate. I am

Re: hints static wiring

2000-08-28 Thread Donn Miller
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,

Re: hints static wiring

2000-08-28 Thread Mike Meyer
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

Re: hints static wiring

2000-08-28 Thread Maxim Sobolev
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

Re: hints static wiring

2000-08-28 Thread Mike Meyer
Maxim Sobolev writes: 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

Re: hints static wiring

2000-08-28 Thread Maxim Sobolev
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.

Re: hints static wiring

2000-08-28 Thread Mike Meyer
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

Re: hints static wiring

2000-08-28 Thread Motomichi Matsuzaki
Ahh..., I tried to summarize my opinion. If you find any misunderstandings of me, please correct them. *** What's happen if there's no /boot/device.hints? case A kernel has no built-in hints ... some devices would not work, system would stall! You can tell whole hints to the kernel

Re: hints static wiring

2000-08-28 Thread Brooks Davis
On Mon, Aug 28, 2000 at 03:19:15AM -0500, 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

Re: hints static wiring

2000-08-28 Thread David O'Brien
On Mon, Aug 28, 2000 at 08:24:50AM -0500, Mike Meyer wrote: 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 The kernel does not fail to *BUILD*. ``make install'' is what fails. I agree that the requirement

Re: hints static wiring

2000-08-28 Thread Warner Losh
In message [EMAIL PROTECTED] Tony Fleisher writes: : Just a suggestion, but isn't this the type of thing that : should be added to UPDATING? Quoting from the UPDATING file: ... 2825: /boot/device.hints is now required for installkernel to succeed. ... 2612:

Re: hints static wiring

2000-08-28 Thread Warner Losh
In message [EMAIL PROTECTED] Matthew Jacob writes: : 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

Re: hints static wiring

2000-08-28 Thread Matthew Jacob
In message [EMAIL PROTECTED] Matthew Jacob writes: : 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

Re: hints static wiring

2000-08-28 Thread Warner Losh
In message [EMAIL PROTECTED] Mike Meyer writes: : Will the system fail to boot if there isn't an empty device.hints : file? If the kernel doesn't have a hints file compiled into it, then you will have problems. However, you may not have a video console. I've been able to boot my laptop with a

Re: hints static wiring

2000-08-28 Thread Warner Losh
In message [EMAIL PROTECTED] Matthew Jacob writes: : In my opinion, people making major changes that require something in : UPDATING, should coordinate with you *before* the commit. Only 5 or : 6 brain cells are needed for this- I sure wish some of my fellow : committers weren't such skinflints

Re: hints static wiring

2000-08-28 Thread Warner Losh
In message [EMAIL PROTECTED] Mike Meyer writes: : Maxim Sobolev writes: : 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 :

Re: hints static wiring

2000-08-28 Thread Greg Lehey
On Monday, 28 August 2000 at 8:24:50 -0500, Mike Meyer wrote: 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

Re: hints static wiring

2000-08-28 Thread Brooks Davis
On Tue, Aug 29, 2000 at 10:25:26AM +0930, Greg Lehey wrote: At the very least, there appears to be confusion about how to use the hints. I can see two conflicting views here: 1. You must have a /boot/device.hints file, but it may be empty. This is minimally correct. I.e. that's what the

Re: hints static wiring

2000-08-27 Thread Brooks Davis
On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsuzaki wrote: When kernel is built with static device wiring (i.e. 'hints' line is enabled in the config file), is /boot/device.hints required? Doing 'make install' without /boot/device.hints is failed, saying "You must set up a

Re: hints static wiring

2000-08-27 Thread Tony Fleisher
Just a suggestion, but isn't this the type of thing that should be added to UPDATING? "This file contains a list, in reverse chronologocal order, of major breakages in tracking -current." TOny. On Sun, 27 Aug 2000, Brooks Davis wrote: On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi