lkml.org 
[lkml]   [2007]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: sys_chroot+sys_fchdir Fix
Alan Cox wrote:
> On Wed, 26 Sep 2007 20:04:14 +0930
> David Newall <david@davidnewall.com> wrote:
>
>> Al Viro wrote:
>>
>>> Oh, for fsck sake... Folks, it's standard-required behaviour. Ability
>>> to chroot() implies the ability to break out of it. Could we please
>>> add that (along with reference to SuS) to l-k FAQ and be done with that
>>> nonsense?
>>>
>> I'm pretty confident that it's only standard behavior for Linux. Every
>> other unix says it's not allowed.
>>
>
> Go try them, then come back and admit your error
>

I've made no error. The documentation says what it says, and what it
doesn't say, other than for Linux, is that there is an unspecified way
of breaking out.

If you're so keen on trying things, then I challenge you to try it on,
oh, say, BSD, and then admit your error. (Such hostile words.)
-
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/

\
 
 \ /
  Last update: 2007-09-26 13:25    [W:0.148 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site