Date: Wed, 28 Jan 2009 13:08:26 -0500 From: Garance A Drosehn <gad@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com>, jhb@FreeBSD.org Cc: arch@FreeBSD.org Subject: Re: Trimming the default /boot/device.hints Message-ID: <p06240807c5a64df6e188@[128.113.24.47]> In-Reply-To: <20090127.233903.-432839944.imp@bsdimp.com> References: <200901260947.32870.jhb@freebsd.org> <20090127.233903.-432839944.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:39 PM -0700 1/27/09, M. Warner Losh wrote: >I don't like this change. However, you've hit on part of the reason I >don't like the change. I don't think it goes far enough, and at the >same time loses valuable history. > >To address the latter, I'd do a cp GENERIC.hints LEGACY.hints and add >comments to the top that this is for systems that don't have PNPBIOS >or ACPI or that there's problems with those. Admittedly I know almost nothing about the hints themselves, but I like this idea. We already supply multiple kernel files, even though everything is documented in NOTES. We do it because it's convenient and it costs us nothing. We could even install the LEGACY.hints file as /boot/legacy.hints, and then if someone has a problem we can say "go into the boot loader, and type 'include /boot/legacy.hints'. If that doesn't solve your problem, then your problem is not related to this big change to /boot/device.hints". And if it *does* solve their problem, they can just look at 'dmesg' after they boot up, and get a good idea of what lines they need to add to /boot/device.hints. I don't see how this would cost us much (compared to *not* having a legacy.hints file), and yet it might make things much easier if it turns out that too many hints had been removed. -- Garance Alistair Drosehn = drosehn@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06240807c5a64df6e188>