[PATCH] fork(2): add ENOSYS

[PATCH] fork(2): add ENOSYS

[Mike Frysinger]

Signed-off-by: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
---
 man2/fork.2 |    4 ++++
 1 file changed, 4 insertions(+)

diff --git a/man2/fork.2 b/man2/fork.2
index 4089fb9..fb604ac 100644
--- a/man2/fork.2
+++ b/man2/fork.2
@@ -184,6 +184,10 @@ capability.
 .B ENOMEM
 .BR fork ()
 failed to allocate the necessary kernel structures because memory is tight.
+.TP
+.B ENOSYS
+.BR fork ()
+is not supported on this platform (e.g. a no-mmu setup).
 .SH "CONFORMING TO"
 SVr4, 4.3BSD, POSIX.1-2001.
 .SH NOTES
-- 
1.7.9.7

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] fork(2): add ENOSYS

[Michael Kerrisk (man-pages)]

Hi Mike,

On Tue, May 1, 2012 at 4:50 PM, Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org> wrote:
> Signed-off-by: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
> ---
>  man2/fork.2 |    4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/man2/fork.2 b/man2/fork.2
> index 4089fb9..fb604ac 100644
> --- a/man2/fork.2
> +++ b/man2/fork.2
> @@ -184,6 +184,10 @@ capability.
>  .B ENOMEM
>  .BR fork ()
>  failed to allocate the necessary kernel structures because memory is tight.
> +.TP
> +.B ENOSYS
> +.BR fork ()
> +is not supported on this platform (e.g. a no-mmu setup).
>  .SH "CONFORMING TO"
>  SVr4, 4.3BSD, POSIX.1-2001.
>  .SH NOTES

I'm curious. Which architectures currently do this, do you know?

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] fork(2): add ENOSYS

[Mike Frysinger]

[-- Attachment #1: Type: Text/Plain, Size: 733 bytes --]

On Tuesday 01 May 2012 01:38:35 Michael Kerrisk (man-pages) wrote:
> On Tue, May 1, 2012 at 4:50 PM, Mike Frysinger wrote:
> > --- a/man2/fork.2
> > +++ b/man2/fork.2
> > @@ -184,6 +184,10 @@ capability.
> >  .B ENOMEM
> >  .BR fork ()
> >  failed to allocate the necessary kernel structures because memory is
> > tight. +.TP
> > +.B ENOSYS
> > +.BR fork ()
> > +is not supported on this platform (e.g. a no-mmu setup).
> >  .SH "CONFORMING TO"
> >  SVr4, 4.3BSD, POSIX.1-2001.
> >  .SH NOTES
> 
> I'm curious. Which architectures currently do this, do you know?

ones w/out an mmu ;)

looking at 'config MMU', arch/*/Kconfig, i see it could happen to:
	arm blackfin c6x frv h8300 microblaze mips xtensa
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [PATCH] fork(2): add ENOSYS

[Michael Kerrisk (man-pages)]

On Wed, May 2, 2012 at 3:49 AM, Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org> wrote:
> On Tuesday 01 May 2012 01:38:35 Michael Kerrisk (man-pages) wrote:
>> On Tue, May 1, 2012 at 4:50 PM, Mike Frysinger wrote:
>> > --- a/man2/fork.2
>> > +++ b/man2/fork.2
>> > @@ -184,6 +184,10 @@ capability.
>> >  .B ENOMEM
>> >  .BR fork ()
>> >  failed to allocate the necessary kernel structures because memory is
>> > tight. +.TP
>> > +.B ENOSYS
>> > +.BR fork ()
>> > +is not supported on this platform (e.g. a no-mmu setup).
>> >  .SH "CONFORMING TO"
>> >  SVr4, 4.3BSD, POSIX.1-2001.
>> >  .SH NOTES
>>
>> I'm curious. Which architectures currently do this, do you know?
>
> ones w/out an mmu ;)
>
> looking at 'config MMU', arch/*/Kconfig, i see it could happen to:
>        arm blackfin c6x frv h8300 microblaze mips xtensa

Thanks Mike. Patch applied. (But I couldn't see how one deduces that
mips is on that list.)

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] fork(2): add ENOSYS

[Mike Frysinger]

[-- Attachment #1: Type: Text/Plain, Size: 1145 bytes --]

On Tuesday 01 May 2012 14:21:36 Michael Kerrisk (man-pages) wrote:
> On Wed, May 2, 2012 at 3:49 AM, Mike Frysinger wrote:
> > On Tuesday 01 May 2012 01:38:35 Michael Kerrisk (man-pages) wrote:
> >> On Tue, May 1, 2012 at 4:50 PM, Mike Frysinger wrote:
> >> > --- a/man2/fork.2
> >> > +++ b/man2/fork.2
> >> > @@ -184,6 +184,10 @@ capability.
> >> >  .B ENOMEM
> >> >  .BR fork ()
> >> >  failed to allocate the necessary kernel structures because memory is
> >> > tight. +.TP
> >> > +.B ENOSYS
> >> > +.BR fork ()
> >> > +is not supported on this platform (e.g. a no-mmu setup).
> >> >  .SH "CONFORMING TO"
> >> >  SVr4, 4.3BSD, POSIX.1-2001.
> >> >  .SH NOTES
> >> 
> >> I'm curious. Which architectures currently do this, do you know?
> > 
> > ones w/out an mmu ;)
> > 
> > looking at 'config MMU', arch/*/Kconfig, i see it could happen to:
> >        arm blackfin c6x frv h8300 microblaze mips xtensa
> 
> Thanks Mike. Patch applied. (But I couldn't see how one deduces that
> mips is on that list.)

ah, i guess no-mmu mips hasn't been merged yet.  i thought it had (much like 
arm no-mmu finally was).
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]