From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <32a656c204111720266056314c@mail.gmail.com> Date: Thu, 18 Nov 2004 13:26:38 +0900 From: Vester Thacker To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] pc boot and ether drivers In-Reply-To: <1285048a44ca7a9d3c339d95924f2745@collyer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1285048a44ca7a9d3c339d95924f2745@collyer.net> Topicbox-Message-UUID: 0646a0d2-eace-11e9-9e20-41e7f4b1d025 On Wed, 17 Nov 2004 18:43:22 -0800, geoff@collyer.net wrote: > The main complication is that the Plan 9 bootstraps also read and > parse plan9.ini and leave the results in a known place for the loaded > kernel. I suppose that code could be moved into the kernels. Couldn't we have a single large kernel with all the drivers for installation purposes? Could we have the user build and/or a kernel during the install process for the type of Plan 9 computer that is desired rather than the current scheme? Would this lessen the need for a plan9.ini during the initial installation bootstrap? I don't advocate plan9.ini being depreciated, only that it should not be required initially. IMHO this might be advantagous considering floppy drives are obsolete. Sorry if this obfuscates the matter a bit. -vester