root from 9pi terminal

root from 9pi terminal

[kokamoto]

I'm now writing this mail on my Richard's 9pi machine.
The root was gotten from A68N-5000 9front file/auth/cpu server.
日本語も入りますね

However if I try to do cpu command from the fossil
based (root from local) 9pi to my titan(cpu server), login
authentication is done, but nothing more, and stalled.
Anyone has any idea what is happening here.

There is a log of:
titan Aug  3 17:45:13 srvauth: auth_proxy short read

I can drawterm to the titan without problems.
What is the difference.

One more:

When I try pxe boot with running ip/dhcpd and ip/tftpd on
titan, I fail TFTPD with Too many packages error message.
However tital logs the following:
------from here----
titan Aug  4 16:51:35 tftp 491 connection from 192.168.11.2!2070 dir /net/udp/2
titan Aug  4 16:51:35 tftpd 491 /386/9pcf tsize is 4,157,439
titan Aug  4 16:51:35 tftpd 491 send file '/386/9pcf' octet to 192.168.11.2!2070
titan Aug  4 16:51:35 tftp 494 connection from 192.168.11.2!2071 dir /net/udp/2
titan Aug  4 16:51:35 tftpd 494 setting blksize to client's 1456
titan Aug  4 16:51:35 tftpd 494 overriding blksize to 1352
titan Aug  4 16:51:35 tftpd 494 send file '/386/9pcf' octet to 192.168.11.2!2071
titan Aug  4 16:51:36 tftpd 494 rexmit 1356 /386/9pcf:408 to 192.168.11.2!2071
titan Aug  4 16:51:37 tftpd 494 rexmit 1356 /386/9pcf:408 to 192.168.11.2!2071
titan Aug  4 16:51:38 tftpd 494 rexmit 1356 /386/9pcf:408 to 192.168.11.2!2071
titan Aug  4 16:51:39 tftpd 494 rexmit 1356 /386/9pcf:408 to 192.168.11.2!2071
titan Aug  4 16:51:40 tftpd 494 rexmit 1356 /386/9pcf:408 to 192.168.11.2!2071
titan Aug  4 16:51:41 tftpd 494 done sending file '/386/9pcf' octet to 192.168.11.2!2071
-----to here----

It seems titan sent the kernel file successfully, which is confrict with above
error message, and yes, it fails tftp actually.

Hmmm, it's not easy to understand.

Kenji

Re: [9front] root from 9pi terminal

[cinap_lenrek]

the log is misleading. from the code, it will try retransmitting
the block 5 times (timeout = 5) and then give up but still write
"done sending file".

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,
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?

--
cinap

Re: [9front] root from 9pi terminal

[kokamoto]

> 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

Re: [9front] root from 9pi terminal

[Nick Owens]

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

On Tue, Aug 05, 2014 at 10:16:46AM +0900, kokamoto@hera.eonet.ne.jp wrote:
> Then what is 'remote file factotum'?
> 
> Kenji
> 

kenji,

in the manual of factotum(4) it says under the heading Control and Key
Management:

          By default when factotum starts it looks for a secstore(1)
          account on $auth for the user and, if one exists, prompts
          for a secstore password in order to fetch the file factotum,
          which should contain control file commands.  An example
          would be
            key dom=x.com proto=p9sk1 user=boyd !hex=26E522ADE2BBB2A229
            key proto=rsa service=ssh size=1024 ek=3B !dk=...

this file in secstore is like your keyring.
i believe you can create it with: ipso factotum

just add your key like the example in the manual above and it will get
loaded into factotum when you authenticate with secstore.

hope this makes it clear.


[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [9front] root from 9pi terminal

[kokamoto]

> On Tue, Aug 05, 2014 at 10:16:46AM +0900, kokamoto@hera.eonet.ne.jp wrote:

> this file in secstore is like your keyring.
> i believe you can create it with: ipso factotum

No, it doen't help.
same error message 'remote file factotum does not exist' appeared.

I did auth/changeuser -n glenda (or other members), and got
changeuser: can't create user xxxxx:
	'/mnt/netkeys/xxxxx' create prohibited

Indeed, ls -l /mnt doen't show /mnt/netkeys directory.
However, if I try to create it, system sat it already exist.

Kenji

Re: [9front] root from 9pi terminal

[Nick Owens]

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

On Tue, Aug 05, 2014 at 04:07:43PM +0900, kokamoto@hera.eonet.ne.jp wrote:
> > On Tue, Aug 05, 2014 at 10:16:46AM +0900, kokamoto@hera.eonet.ne.jp wrote:
> 
> > this file in secstore is like your keyring.
> > i believe you can create it with: ipso factotum
> 
> No, it doen't help.
> same error message 'remote file factotum does not exist' appeared.

sorry. i think you need to make it with the auth/secstore command
directly. ipso is a wrapper script. so:

touch factotum
auth/secstore -p factotum # stores empty file
ipso factotum # opens factotum file into editor

> 
> I did auth/changeuser -n glenda (or other members), and got
> changeuser: can't create user xxxxx:
> 	'/mnt/netkeys/xxxxx' create prohibited

why are you using -n? the manual says -n is for SecureNet database,
which i believe is for hardware security token. see securenet(8).

i think you want just auth/changeuser glenda. make sure you have
keyfs(4) mounted first (which serves /mnt/keys).

> 
> Indeed, ls -l /mnt doen't show /mnt/netkeys directory.
> However, if I try to create it, system sat it already exist.

the program mntgen(4) is used in /n and /mnt. its meant to be used for
automatically creating mount points.


[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [9front] root from 9pi terminal

[kokamoto]

Thanks Nick!

> touch factotum
> auth/secstore -p factotum # stores empty file
> ipso factotum # opens factotum file into editor

It solved the
auth/factotum
problem.

> why are you using -n? the manual says -n is for SecureNet database,
> which i believe is for hardware security token. see securenet(8).

It's my paniccal behaviour caused by ununderstanding things.

> the program mntgen(4) is used in /n and /mnt. its meant to be used for
> automatically creating mount points.

ls -l /mnt showed no netkeys directory, however, if I try
ls -ld /mnt/netkeys
it shows strangely that directory with the timestamp of now like this:

d-r-xr-xr-x M 381 sys sys 0 Aug  6 09:53 /mnt/netkeys


By the way I cannot cpu from labs plan9 box.
If I choose /root from 9front server, I can do cpu command, strange?

Kenji

PS. now writing from drawterm on Ubuntu 12.04 machine, where I can use 日本語.
I have to use ^\ instead of Shift+Space key to trigger the transformation.

Re: [9front] root from 9pi terminal

[kokamoto]

> its not clear what machine you'r trying to pxe boot here. 

I changed the line of /lib/ndb/local file on auth/file/cpu server
from
bootf=/386/9pcf
to
bootf=/386/9bootpxe.

It solved the problem.
Now I can pxe boot the c2d machine(which has lab's Plan9 dist on a disk)
successfully.

Thanks a lot, I'm writing this mail on that pxe booted terminal.

By the way, if I boot a machine with lab's kernel, but /root is from
9front server, something of the kernel device doen't confrict?

Kenji