From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] basic question
Date: Thu, 26 Jul 2001 16:10:12 -0400 [thread overview]
Message-ID: <200107262010.QAA19915@augusta.math.psu.edu> (raw)
In-Reply-To: <Pine.GSO.3.96.1010726153618.3315B-100000@sun2.bnl.gov>
In article <Pine.GSO.3.96.1010726153618.3315B-100000@sun2.bnl.gov> you write:
>
>Having played with plan9 in stand alone mode, I am trying to
>install a plan9 system and I am following the various tips found on
>the plan9 Wiki page. The first thing is the CPU/auth server. However
>I have a basic problem: How to edit files such as /adm/users,
>/rc/bin/cpurc etc... I am logged in as glenda. What is the magic
>word?
For the standalone machines with local KFS, the manage word is:
disk/kfscmd allow
Then you should be able to edit files using the text editor of your
choice (eg, sam, acme, ed....). Hope that helps!
- Dan C.
prev parent reply other threads:[~2001-07-26 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 19:40 helio takai
2001-07-26 20:10 ` Dan Cross [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=200107262010.QAA19915@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/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).