From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] fossil permission checking
Date: Wed, 6 Aug 2008 20:18:46 -0600 [thread overview]
Message-ID: <14ec7b180808061918t9e5ab94jbd1b0e1f1261a109@mail.gmail.com> (raw)
In-Reply-To: <621112A569DAE948AD25CCDCF1C075331AB324@dolly.ntdom.cupdx>
> However, permissions are still wrong somewhere, as I can't:
> cp /adm/timezone/US_Pacific /adm/timezone/local
/adm/timezone files are owned by the user/group 'adm', so if you want
to modify them you should add the user you're doing this as to that
group.
i believe the issue comes from the instructions assuming that one is
either serving fossil with the "don't check permissions" flag, or has
done a "disk/kfs allow" (remember that command, anybody? :)
having no user who can circumvent the file permissions is a very good
thing, i believe.
next prev parent reply other threads:[~2008-08-07 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 0:10 Benjamin Huntsman
2008-08-07 0:24 ` andrey mirtchovski
2008-08-07 1:01 ` Benjamin Huntsman
2008-08-07 1:36 ` Uriel
2008-08-07 2:18 ` andrey mirtchovski [this message]
2008-08-07 3:07 ` erik quanstrom
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=14ec7b180808061918t9e5ab94jbd1b0e1f1261a109@mail.gmail.com \
--to=mirtchovski@gmail.com \
--cc=9fans@9fans.net \
/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).