From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mta01.eonet.ne.jp ([203.140.81.20]) by ttr; Mon Aug  4 21:16:55 EDT 2014
Received: from titan.jitaku.localdomain (112-71-7-162f1.kyt1.eonet.ne.jp [112.71.7.162])
	by mailmsa11.mozu.eo.k-opti.ad.jp  with ESMTP id s751GkaE002822
	for <9front@9front.org>; Tue, 5 Aug 2014 10:16:47 +0900
To: 9front@9front.org
Subject:  Re: [9front] root from 9pi terminal
Date: Tue, 5 Aug 2014 10:16:46 +0900
From: kokamoto@hera.eonet.ne.jp
Message-ID: <578ebf8f40bede17a339e394d6858ced@titan.jitaku.localdomain>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: singleton lifecycle descriptor
In-Reply-To: <159371a00f7aff5fd640f5099b433120@felloff.net>
References: <159371a00f7aff5fd640f5099b433120@felloff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

> its not clear what machine you'r trying to pxe boot here. a 386
> kernel will most likely not work on a arm based raspi. also,
I' using Core2duo machine (ASUS P5Q-pro motherboard).
Ah!  Subject line!

> what (boot) program is on the tftp client end? the pxe bios only downloads
> the boot program over tftp, not the plan9 kernel. the plan9 kernel
> is loaded by the bootloader. what are you using?

Dhcp swerches my machine, this time mars(192.168.11.2), and
found bootf=/386/pcf, and tryes to download this.   Am I wrong?

You mean tftp cliant shoud try to download /boot/boot?
Or something else?


On the cpu command problem, I reached to the problem point.
When I try to auth/factotum on the cpu/auth/file server machie like:
titan: auth/factotum
secstore password:  xxxxx(password in)
secstore
secstore: remote file factotum does not exit
secstore: scstore cmd failed

Then what is 'remote file factotum'?

Kenji