From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Initial experience with Plan9 on Raspberry Pi
Date: Thu, 23 Mar 2017 09:39:29 +0000 [thread overview]
Message-ID: <bbbeeeffc9bbd7299881e7c9733e8a80@hamnavoe.com> (raw)
In-Reply-To: <CACo5X5jtMRy0KvapndO4FMMLJOWHxvDOHSSzPKSCGoQp8p-Swg@mail.gmail.com>
> Does anyone know why the fscons prompt changes from 'prompt:' to 'main:'
> for second and subsequent commands.
A single fossil may be serving more than one file system. The prompt
is to remind you which is the "current" one (ie the one which will be
acted on by commands which are not prefixed by "fsys <name>").
The 9pi image has only one fossil partition, which is called main.
To see its configuration:
fossil/conf /dev/sdM0/fossil
> Any
> corrections/suggestions or pointers to useful alternative notes on this
> would be much appreciated.
Have you studied http://plan9.bell-labs.com/wiki/plan9/documentation/index.html
particularly the "Installation" and "Configuration" sections? Most of it applies
to the raspberry pi exactly as for any other Plan 9 platform.
> changeuser: can't create user digbyt: '/mnt/keys/digbyt' permission denied
> term%
>
> So I am wondering if there is something I need to start to make my Pi an
> authentication server?
The "permission denied" occurs because you haven't mounted keyfs(4), and
you need to use fossilcons(8) to add your username to group "adm" before
you can do that.
Have a look at http://plan9.bell-labs.com/wiki/plan9/Configuring_a_standalone_CPU_server
for a more complete picture.
prev parent reply other threads:[~2017-03-23 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 3:53 Digby R.S. Tarvin
2017-03-23 9:39 ` Richard Miller [this message]
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=bbbeeeffc9bbd7299881e7c9733e8a80@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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).