9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] disk/kfscmd allow fails
Date: Wed,  7 Apr 2004 13:49:30 -0600	[thread overview]
Message-ID: <cc969814538e0eca6337af90c6b5f451@plan9.ucalgary.ca> (raw)
In-Reply-To: <20040407214157.187d067d.scusi@xs4all.nl>

> Hi 9fans,
> 
> after i had my first conntact with plan9 around 2 years i now installed it 
> again :-). 
> 
> Installation went fine, i rebooted and loged in as "glenda" to start
> setting up my system (at least try how far i gonna get this time).
> 
> My problem is that i can not change important config files since
> "disk-kfscmd allow" gives back: "kfscmd: can't find commands file"
> 
> Any ideas, what is wrong here ?
> Where is the commandsfile normally ?
> Can i somehow put one where it belongs to ?
> 
> Thanks /~scusi

kfs isn't the default filesystem anymore -- we've moved to fossil.

to perform normal maintenance operations you can add your user to the
'sys' group, which will be enough for almost all maintenance
operations.  if you want something non-trivial (like changing the
permissions of a file not owned by you or sys) you can use 'wstat' on
the fossil console, or do serve a console allowing everyone to write
to it (the replica script does that trick -- see
/dist/replica/network).

to connect to the fossil console do 'con -l /srv/fscons'; the commands
are in fossilcons(8).

here's how you may mount a write-allow fossil partition:

% con -l /srv/fscons
prompt: fsys main
main: srv -AWP fsallow
main: ^\
>>> q
% mount /srv/fsallow /n/fossil
% cd /n/fossil # and edit whatever you want there...

hth: andrey



      reply	other threads:[~2004-04-07 19:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 19:41 Scusi
2004-04-07 19:49 ` andrey mirtchovski [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=cc969814538e0eca6337af90c6b5f451@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).