From: Tim Fraser <tfraser@cs.umd.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] admin with fossil?
Date: Fri, 10 Oct 2003 10:06:21 -0400 [thread overview]
Message-ID: <20031010140614.GB2749@tfraser.cs.umd.edu> (raw)
Here's a couple of newbie questions for you all; I apologize in
advance for trying your patience:
I recently installed Plan 9 4th edition off of an installation CD-ROM
downloaded on 29 Sept 2003. Sticking to the defaults, I wound up with
a stand-alone terminal running a local fossil filesystem.
Question 1: What is the proper way to overcome fossil's access
controls in order to perform administrative tasks (such as editing
/rc/bin/termrc)? Is there a means of turning off access control with
fossil as there is with kfs, or does one create a user with
administrative group memberships?
Question 2: Based on the number of helpful examples on the web, kfs
appears to be a well-trodden path. However, it seems that fossil is
the way of the future. Which filesystem is more appropriate for my
stand-alone terminal, fossil or kfs?
Thanks,
Tim Fraser / U. Maryland Institute for Advanced Computer Studies
next reply other threads:[~2003-10-10 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 14:06 Tim Fraser [this message]
2003-10-10 14:20 ` David Presotto
2003-10-10 14:46 ` Charles Forsyth
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=20031010140614.GB2749@tfraser.cs.umd.edu \
--to=tfraser@cs.umd.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).