« Return to Thread: [Cooker] [2009.1] What is errcode: 13 when trying to allocate files as root

Re: [Cooker] [2009.1] What is errcode: 13 when trying to allocate files as root

by Steve Morris-5 :: Rate this Message:

Reply to Author | View in Thread

On 02/07/09 06:46, Pascal Terjan wrote:

> On Wed, Jul 1, 2009 at 10:41 PM, Steve Morris<samorris@...>  wrote:
>    
>> If that is the case I am now confused about the inconsistencies is 2009.1.
>> An out of the box install of 2009.1 installs /home not user writeable, but
>> normal users have no issue writing to /home/&uid when /home is left with the
>> default allocations, so what's the difference and why this inconsistency.
>>      
> To read or write to a file, you need the rights to read or right it,
> and you need the right to execute it's parents to be able to "walk
> through them"
>
> I suggest that you read a Unix/Linux tutorial about rights management
>
>    
Sorry Pascal, you haven't understood my question. The information
supplied says that a normal user cannot write to the /root/tmp directory
even if it is world writable because a normal user cannot read or cd to
/root, which I understand. But an out of the box install of 2009.1, when
/home is a separate partition, puts the same attributes on /home, a
normal user cannot read or cd to /home, but a normal user has no issues
writing to their &uid directory under /home, so what is the difference
and why?

regards,
Steve


[samorris.vcf]

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard


 « Return to Thread: [Cooker] [2009.1] What is errcode: 13 when trying to allocate files as root