From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 9 Dec 2010 10:39:14 -0500 To: 9fans@9fans.net Message-ID: <0b1b23228086b6f899880da55f0a6ef9@plug.quanstro.net> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] plan9.ini bootfile= syntax for 9pxeload client? Topicbox-Message-UUID: 89e00a48-ead6-11e9-9d60-3106f5b1d025 > dhcp/tftp works to set diskless terminal ethernet ip, fs and auth ip > addresses and downloads 9pxeload to diskless terminal. 9pxeload then > fails with an exception. > > I suspect it fails because I haven't told 9pxeload how to load what > kernel. I have created the /cfg/pxe/ file but have yet to > guess the correct incantation of syntax to specify the kernel location. in addition, you need to add "bootf=/386/9pxeload" in the /lib/ndb/local entry for this machine. > I have included ether0=type=i82557 in this file so 9pxeload knows > which device to use. not necessary. > The 9load man page says that the plan9.ini file attribute > bootfile=device!file or bootfile=device!partition!file specifies what > kernel to load. However it says if you specify ether0 for device, > 'file' is determined by /lib/ndb which just loaded 9pxeload, which is > pretty circular logic (imho). I've tried bootfile=manual to no avail. the kernel is specified in /cfg/pxe/. e.g. nobootprompt=ether0!/386/9pccpu - erik