Date: Fri, 19 Sep 1997 22:39:27 -0700 (PDT) From: Simon Shapiro <Shimon@i-Connect.Net> To: Terry Lambert <tlambert@primenet.com> Cc: hackers@FreeBSD.ORG, (Harlan Stenn) <Harlan.Stenn@pfcs.com> Subject: Re: Higher-level kernel config? Message-ID: <XFMail.970919223927.Shimon@i-Connect.Net> In-Reply-To: <199709192006.NAA29936@usr03.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Terry Lambert; On 19-Sep-97 you wrote: > > I was just noticing that I have 3 or 4 customized config files here for > > various FreeBSD machines, and that stuff changes in the GENERIC and > > LINT > > files *much* more often than I change hardware in my machines. > > > I'm curious: could there ever be a case where you would not want to > include a driver for hardware that was actually in your machine? If > not, then I think dynamic autoconfiguration is the way to go. Absolutely yes. Consider a test bench machine where there is some known to be bad hardware you may want activated only if you choose to. Auto config is still excellent there. I put an entry in /boot.conf that specifies a deny list, as well as an allow list. Then I allow the boot prompt to specify the file name of the ``boot.conf'' I want related to and presto! A truely managable system. Oh, somewhere along the line, we will make a /boot and throw all these kernels, config files, etc. into that directory, so / looks readable again. --- Sincerely Yours, (Sent on 19-Sep-97, 22:30:39 by XF-Mail) Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.643.5559, Emergency: 503.799.2313
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.970919223927.Shimon>