On Thu, Feb 5, 2009 at 12:28 PM, Timo Sirainen wrote:
> On Wed, 2009-02-04 at 17:37 +1300, Michael Kerrisk wrote:
>> > The test program in my previous mail did the chrooting. Just compile it,
>> > mkdir -p /tmp/foo/proc, mount --bind /proc /tmp/foo/proc and run it.
>>
>> So, I did some experimenti
On Wed, 2009-02-04 at 17:37 +1300, Michael Kerrisk wrote:
> > The test program in my previous mail did the chrooting. Just compile it,
> > mkdir -p /tmp/foo/proc, mount --bind /proc /tmp/foo/proc and run it.
>
> So, I did some experimenting. It looks like the title of your report
> has things wro
tags 514043 fixed-upstream
thanks
> To prevent other people from wasting their time with fexecve(), I suggest
> adding something like this to the description:
>
> Linux implements fexecve() by executing the binary via proc filesystem,
> so /proc needs to be mounted and available during the fexecve
Hi Timo,
On Wed, Feb 4, 2009 at 10:07 AM, Timo Sirainen wrote:
> On Wed, 2009-02-04 at 09:47 +1300, Michael Kerrisk wrote:
>> > In my real
>> > program I got ENOENT for some reason. Anyway ENOENT still happens
>> > if /proc is mounted but the executed file is outside the chroot.
>>
>> Yes. The e
On Wed, 2009-02-04 at 09:47 +1300, Michael Kerrisk wrote:
> > In my real
> > program I got ENOENT for some reason. Anyway ENOENT still happens
> > if /proc is mounted but the executed file is outside the chroot.
>
> Yes. The entries in /proc/self/fd are symlinks, and these would refer
> to paths
On Wed, Feb 4, 2009 at 9:22 AM, Timo Sirainen wrote:
> On Wed, 2009-02-04 at 09:17 +1300, Michael Kerrisk wrote:
>> >> > And for ERRORS:
>> >> >
>> >> > ENOENT: /proc filesystem not available.
>> >> >
>> >> > ref: http://lkml.org/lkml/2006/12/27/140
>> >>
>> >> surely the error is ENOSYS (see the
On Wed, 2009-02-04 at 09:17 +1300, Michael Kerrisk wrote:
> >> > And for ERRORS:
> >> >
> >> > ENOENT: /proc filesystem not available.
> >> >
> >> > ref: http://lkml.org/lkml/2006/12/27/140
> >>
> >> surely the error is ENOSYS (see the glibc source), which is already
> >> documented in the man page
On Wed, Feb 4, 2009 at 9:12 AM, Timo Sirainen wrote:
> On Wed, 2009-02-04 at 07:42 +1300, Michael Kerrisk wrote:
>> > To prevent other people from wasting their time with fexecve(), I suggest
>> > adding something like this to the description:
>> >
>> > Linux implements fexecve() by executing the
On Wed, 2009-02-04 at 07:42 +1300, Michael Kerrisk wrote:
> > To prevent other people from wasting their time with fexecve(), I suggest
> > adding something like this to the description:
> >
> > Linux implements fexecve() by executing the binary via proc filesystem,
> > so /proc needs to be mounted
Hi Timo,
On Wed, Feb 4, 2009 at 6:58 AM, Timo Sirainen wrote:
> Package: manpages-dev
> Version: 3.01-1
> Severity: wishlist
>
> To prevent other people from wasting their time with fexecve(), I suggest
> adding something like this to the description:
>
> Linux implements fexecve() by executing t
Package: manpages-dev
Version: 3.01-1
Severity: wishlist
To prevent other people from wasting their time with fexecve(), I suggest
adding something like this to the description:
Linux implements fexecve() by executing the binary via proc filesystem,
so /proc needs to be mounted and available duri
11 matches
Mail list logo
