From: Romano <unobe@cpan.org>
To: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] another CPU
Date: Fri, 7 Aug 2020 23:04:06 -0700 [thread overview]
Message-ID: <5AB869F12585EAFC1D2EAAA1C4BAFC7A@smtp.pobox.com> (raw)
> 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
>
> I tried copying cpurc and termrc and booting with each of them
> the results were strange and buggy. However I made not changes
> to those files as well.
> ...
>
> Any thoughts?
I don't think you want to copy cpurc(8) to /cfg/$sysname/ : see the
man pages for init(8) and cpurc(8): cpurc is started by init, and then
/cfg/$sysname/cpurc runs. So what you're effectively doing, if I am
reading you correctly, is running cpurc(8) twice. This is all I have in my config:
cpu% cat /cfg/$sysname/cpurc
auth/secstored
cpu%
next reply other threads:[~2020-08-08 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 6:04 Romano [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2020-08-08 17:57 ` thinktankworkspaces
2020-08-08 18:45 ` thinktankworkspaces
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=5AB869F12585EAFC1D2EAAA1C4BAFC7A@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=thinktankworkspaces@gmail.com \
/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).