On Wed, May 2, 2012 at 3:49 AM, Mike Frysinger <vapier@xxxxxxxxxx> 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
