From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil write protection
Date: Sun, 2 May 2004 12:58:49 -0600 [thread overview]
Message-ID: <55652dd415b37c70c383a891d1b2179d@plan9.ucalgary.ca> (raw)
In-Reply-To: <ed59f2a84c.michael@privat.utfors.se>
> Hi
>
> I have done a fossil installation from cd. How do I remove the write
> protection ,disk/kfscmd allow doesnt work ?
>
> /Michael Grunditz
connect to the fossil console and do a new srv with -AWP arguments
(see the fossilcons man page):
% con -l /srv/fscons
main: srv -AWP fs2
main: [ctrl+\]
>>> q
% mount /srv/fs2 /n/boot
....
this step is performed automatically by the /dist/replica/network
script whenever you do a 'replica/pull', in fact there may be a
-AWP-ed console left over in /srv/replica -- try mounting that.
add your username (or a special one) to the 'sys' group for trivial
system administration edits. almost everything in Plan 9 has group
writable permissions.
andrey
prev parent reply other threads:[~2004-05-02 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 20:48 Michael Grunditz
2004-05-02 18:58 ` 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=55652dd415b37c70c383a891d1b2179d@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).