You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Nick Kew <ni...@webthing.com> on 2008/05/28 13:20:59 UTC
Re: svn commit: r660749 - /httpd/httpd/branches/2.2.x/STATUS
On Tue, 27 May 2008 22:26:09 -0000
rpluem@apache.org wrote:
> + rpluem says: Thanks. Sorry for being picky, but after revisiting
> the patch
> + again I ask myself how we can be sure that the chroot function is
> actually
> + present on the platform we compile.
$ man chroot
...
CONFORMING TO
SVr4, SVID, 4.4BSD, X/OPEN.
How many unix platforms support none of the above?
Would #ifdef HAVE_UNISTD_H be an appropriate wrapper for this,
or could you have a unistd without chroot?
--
Nick Kew
Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/
Re: svn commit: r660749 - /httpd/httpd/branches/2.2.x/STATUS
Posted by Ruediger Pluem <rp...@apache.org>.
On 05/28/2008 01:20 PM, Nick Kew wrote:
> On Tue, 27 May 2008 22:26:09 -0000
> rpluem@apache.org wrote:
>
>> + rpluem says: Thanks. Sorry for being picky, but after revisiting
>> the patch
>> + again I ask myself how we can be sure that the chroot function is
>> actually
>> + present on the platform we compile.
>
> $ man chroot
> ...
> CONFORMING TO
> SVr4, SVID, 4.4BSD, X/OPEN.
>
> How many unix platforms support none of the above?
I guess not many. So lets backport it and see if we get a bug report
where this fails to build. This may also help to create a good test
for detecting it correctly
>
> Would #ifdef HAVE_UNISTD_H be an appropriate wrapper for this,
> or could you have a unistd without chroot?
>
I don't know.
Regards
Rüdiger
Re: svn commit: r660749 - /httpd/httpd/branches/2.2.x/STATUS
Posted by Ruediger Pluem <rp...@apache.org>.
On 05/28/2008 01:20 PM, Nick Kew wrote:
> On Tue, 27 May 2008 22:26:09 -0000
> rpluem@apache.org wrote:
>
>> + rpluem says: Thanks. Sorry for being picky, but after revisiting
>> the patch
>> + again I ask myself how we can be sure that the chroot function is
>> actually
>> + present on the platform we compile.
>
> $ man chroot
> ...
> CONFORMING TO
> SVr4, SVID, 4.4BSD, X/OPEN.
>
> How many unix platforms support none of the above?
My man chroot says
CONFORMING TO
SVr4, 4.4BSD, SUSv2 (marked LEGACY). This function is not part of
POSIX.1-2001.
So it does not seem to be part of POSIX. But I have no strong opinion. Maybe
another developer could chime in and push me to one or another side :-).
Regards
Rüdiger