From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] remove files in /srv
Date: Mon, 31 Jan 2005 23:33:25 -0500 [thread overview]
Message-ID: <ee9e417a05013120334ea16313@mail.gmail.com> (raw)
In-Reply-To: <445eefa0258b2da0a9497a5f8be79032@ar.aichi-u.ac.jp>
> Permission bit of files in /srv/* is only formal, I think.
> The meaning of the bit follows by the service program, not OS.
> Service program can do anything what ever the bit is.
That's not true -- the bits are checked when the file is opened.
The real solution is to put directories in /srv and have a common
directory and personal directories. But instead I made a smaller
change and tightened up what can be removed.
Russ
next prev parent reply other threads:[~2005-02-01 4:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 3:48 YAMANASHI Takeshi
2005-02-01 4:06 ` arisawa
2005-02-01 4:33 ` Russ Cox [this message]
2005-02-01 4:49 ` [9fans] allocb question Tim Newsham
2005-02-01 20:31 ` [9fans] remove files in /srv rog
2005-02-02 23:22 ` Bruce Ellis
2005-02-02 23:57 ` Charles Forsyth
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 4:05 YAMANASHI Takeshi
2005-02-01 4:44 ` geoff
2005-02-01 1:11 YAMANASHI Takeshi
2005-02-01 3:21 ` arisawa
2005-02-01 3:56 ` Russ Cox
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=ee9e417a05013120334ea16313@mail.gmail.com \
--to=russcox@gmail.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).