9front - general discussion about 9front
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] root from 9pi terminal
Date: Tue, 5 Aug 2014 10:16:46 +0900	[thread overview]
Message-ID: <578ebf8f40bede17a339e394d6858ced@titan.jitaku.localdomain> (raw)
In-Reply-To: <159371a00f7aff5fd640f5099b433120@felloff.net>

> 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



  reply	other threads:[~2014-08-05  1:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 12:10 kokamoto
2014-08-04 12:46 ` [9front] " cinap_lenrek
2014-08-05  1:16   ` kokamoto [this message]
2014-08-05  6:08     ` Nick Owens
2014-08-05  7:07       ` kokamoto
2014-08-05  7:27         ` Nick Owens
2014-08-06  0:57           ` kokamoto
2014-08-06  2:48   ` kokamoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=578ebf8f40bede17a339e394d6858ced@titan.jitaku.localdomain \
    --to=kokamoto@hera.eonet.ne.jp \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).