From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <419C222B.2070902@comcast.net>
Date: Wed, 17 Nov 2004 23:16:43 -0500
From: bs <balajis@comcast.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] pc boot and ether drivers
References: <6b8af63a9aff0dbdbf3f1a2166f9943e@collyer.net>
In-Reply-To: <6b8af63a9aff0dbdbf3f1a2166f9943e@collyer.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 06408634-eace-11e9-9e20-41e7f4b1d025

geoff@collyer.net wrote:
> Command line to what?  The kernels don't have command lines.
> 
> The other platforms generally are much better defined.  The PC just
> happened, and so there's all sorts of ad hocery to cope with, such as
> the lack of a proper boot prom capable of bootp/dhcp/tftp loading and
> of accepting console configuration commands.  The alphapc port
> actually does read a plan9.ini file from /alpha/conf, much like the
> newer /cfg/pxe.  Of course you have to be able to find your main
> Ethernet interface in order to load those files...
in the case of PXE boot why not get it from a DHCPREQUEST?