From: Nikita Danilov <nikita@clusterfs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17219.55937.27499.495968@gargle.gargle.HOWL>
Date: Wed, 5 Oct 2005 17:52:01 +0400
To: Marc Perkel <marc@perkel.com>
Cc: Luke Kenneth Casson Leighton <lkcl@lkcl.net>, linux-kernel@vger.kernel.org
Subject: Re: what's next for the linux kernel?
In-Reply-To: <4343D367.5030608@perkel.com>
References: <20051002204703.GG6290@lkcl.net>
	<4342DC4D.8090908@perkel.com>
	<200510050122.39307.dhazelton@enter.net>
	<4343694F.5000709@perkel.com>
	<17219.39868.493728.141642@gargle.gargle.HOWL>
	<4343D367.5030608@perkel.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1279
Lines: 36

Marc Perkel writes:
 > 

[...]

 > Now of you think "outside" the Linux box" you can see where people in 
 > the real world would expect that if you have no rights to a file to read 
 > or write to it that you shouldn't be able to delete it. In the outside 
 > world it's "duh - of course"! but for thouse that are in the "Unix Cult" 
 > you can't think past inodes.

Deleting files without read/write access to them is exactly what happens
in the real world of classified information: people who physically burn
paper folders have no right to open them. :-)

Please understand one simple thing: unlink(2) system call does not
_remove_ file. It just removes one of possibly many references to this
file from an index. To erase (a part of) a file body, one uses
truncate(2) system call that --wonders!-- requires write access to the
file.

[...]

 > 
 > Once you'be had Netware permissions - even 1990 Netware permission - you 
 > are spoiled and everything else isn't even close.
 > 

Repeating "sugar" doesn't make it sweet.

Nikita.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/