From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] who can write venti archives?
Date: Thu, 11 Dec 2003 22:19:10 -0500 [thread overview]
Message-ID: <E1AUdpi-0000Fy-O7@t40.swtch.com> (raw)
In-Reply-To: Your message of "Fri, 12 Dec 2003 11:03:22 +0900." <975130bb0250dfb92da710652c7cc57c@granite.cias.osakafu-u.ac.jp>
> Thanks Charles and nemo.
>
> I prefer nemo's suggestion, but I have only very limited
> knowledge on this region, and forget my feeling.
>
> Anyway, now I have a right sight for venti+fossil.
>
> Then, I have one more question.
>
> The user who make the fossil run is the host owner of that machine,
> and then have read/write permission to the disk(s). It's Ok, however,
> s/he has no read permission of some files or directories. Nevertheless,
> fossil can manage all the files of the server. How s/he can do it?
The file server enforces permissions when serving the file system
to other users. The file server itself can look at anything, because
it can look at the raw disk.
It's the same reason that the old worm file server (or any file server!)
can access any of the files -- it just works on the disk blocks.
Russ
next prev parent reply other threads:[~2003-12-12 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 10:44 okamoto
2003-12-11 13:23 ` Charles Forsyth
2003-12-11 14:20 ` Fco.J.Ballesteros
2003-12-12 2:03 ` okamoto
2003-12-12 3:19 ` Russ Cox [this message]
2003-12-12 4:03 ` okamoto
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=E1AUdpi-0000Fy-O7@t40.swtch.com \
--to=rsc@swtch.com \
--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).