From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] another CPU
Date: Sat, 08 Aug 2020 09:48:51 +0100 [thread overview]
Message-ID: <209c852d-7353-4c6d-b91a-81603faea9d0@www.fastmail.com> (raw)
In-Reply-To: <5E0794B16739F3F6F9FDD99E60189AE1@gmail.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.
next prev parent reply other threads:[~2020-08-08 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 6:13 thinktankworkspaces
2020-08-03 6:47 ` [9front] " hiro
2020-08-08 5:44 ` thinktankworkspaces
2020-08-08 8:48 ` Ethan Gardener [this message]
2020-08-08 17:57 ` thinktankworkspaces
2020-08-08 18:45 ` thinktankworkspaces
2020-08-08 6:04 Romano
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=209c852d-7353-4c6d-b91a-81603faea9d0@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).