From: Tim Wright <timw@splhi.com>
To: Justin Carlson <carlson@sibyte.com>
Cc: Xavier Ordoquy <xordoquy@aurora-linux.com>, linux-kernel@vger.kernel.org
Subject: Re: Bug in the file attributes ?
Date: Thu, 29 Mar 2001 18:34:04 -0800 [thread overview]
Message-ID: <20010329183404.B4053@kochanski> (raw)
In-Reply-To: <Pine.LNX.4.21.0103292011480.20805-100000@ilaws.aurora-linux.net> <0103291053110G.04063@plugh.sibyte.com>
In-Reply-To: <0103291053110G.04063@plugh.sibyte.com>; from carlson@sibyte.com on Thu, Mar 29, 2001 at 10:51:18AM -0800
On Thu, Mar 29, 2001 at 10:51:18AM -0800, Justin Carlson wrote:
> You don't need write perms on a file to remove it, you need write perms on the
> directory. If you've got write permissions on the directory, you can remove
> any file in the directory, regardless of the permissions.
>
> -Justin
Except when the "sticky" bit is set. This is useful for shared temporary
directories. Files can be created by anyone, but they can only be unlinked
by the owner or by the superuser. Take a look at the permissions of /var/tmp.
Tim
--
Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI
next prev parent reply other threads:[~2001-03-30 2:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 20:20 Bug in the file attributes ? Xavier Ordoquy
2001-03-29 18:44 ` Andreas Dilger
2001-03-29 20:56 ` Xavier Ordoquy
2001-03-29 19:04 ` John Jasen
2001-03-29 22:57 ` Brian Beattie
2001-03-29 18:45 ` Stephen Clouse
2001-03-29 18:51 ` Justin Carlson
2001-03-30 2:34 ` Tim Wright [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 19:25 Jesse Pollard
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=20010329183404.B4053@kochanski \
--to=timw@splhi.com \
--cc=carlson@sibyte.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xordoquy@aurora-linux.com \
/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