Re: [9front] another CPU

[thinktankworkspaces@gmail.com]

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

Okay so the clarification is as follows: 

/rc/bin/cpurc.local only pertains to the intial system that
booted such as the first system which is CPU/Auth. 
However you don't really need that file. Its' just a diff of
/rc/bin/cpurc. So really its also optional

The /cfg/$sysname/cpurc is also optional and no cpurc.local
should exist in that directory. It only pertains to machines
that will boot off the initial server (CPU/Auth). And the
file should be a minimum file of things needed such as
auth/secstore or maybe auth/httpd if you wanted to dedicated
the new cpu to just service httpd as a service right?

As far as a mount point to copy data back and forth. No mount
point exists you still have to mout it directly using commands such as having a listener on the server

server% aux/listen1 -tv tcp!*!9999 /bin/exportfs -R -r /

client% srv tcp!192.168.1.172!9999 servrer /n/server

something like that right?

[-- Attachment #2: Type: message/rfc822, Size: 6597 bytes --]

From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] another CPU
Date: Sat, 08 Aug 2020 09:48:51 +0100
Message-ID: <209c852d-7353-4c6d-b91a-81603faea9d0@www.fastmail.com>

On Sat, Aug 8, 2020, at 6:44 AM, thinktankworkspaces@gmail.com wrote:
> So I have it working. But maybe i'm missing something. Much
> of the documentation talks about
> 
> cd /cfg; mkdir $sysname; dircp example $sysname
> 
> This seems old and deprecated. I'm not really sure what we
> are supposed to have in /cfg/$sysname

It's optional. (The documentation should say so.) If you read /rc/bin/^(term cpu)^rc you'll see files in /cfg/$sysname are sourced only if they exist.