From: Nick Owens <mischief@9.offblast.org>
To: 9front@9front.org
Subject: Re: [9front] root from 9pi terminal
Date: Tue, 5 Aug 2014 00:27:35 -0700 [thread overview]
Message-ID: <20140805072735.GD13158@iota.offblast.org> (raw)
In-Reply-To: <d532ffd326fd4703b1bad3a8fa9b9b33@titan.jitaku.localdomain>
[-- 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 --]
next prev parent reply other threads:[~2014-08-05 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 12:10 kokamoto
2014-08-04 12:46 ` [9front] " cinap_lenrek
2014-08-05 1:16 ` kokamoto
2014-08-05 6:08 ` Nick Owens
2014-08-05 7:07 ` kokamoto
2014-08-05 7:27 ` Nick Owens [this message]
2014-08-06 0:57 ` kokamoto
2014-08-06 2:48 ` kokamoto
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=20140805072735.GD13158@iota.offblast.org \
--to=mischief@9.offblast.org \
--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).