From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] fork(2): add ENOSYS
Date: Tue, 1 May 2012 11:49:33 -0400 [thread overview]
Message-ID: <201205011149.34086.vapier@gentoo.org> (raw)
In-Reply-To: <CAKgNAkjx1a002xLYEYtgJr8Luy8mKSiWo8J8ZT+aYbzhVrRz5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- 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 --]
next prev parent reply other threads:[~2012-05-01 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 4:50 [PATCH] fork(2): add ENOSYS Mike Frysinger
[not found] ` <1335847802-15646-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2012-05-01 5:38 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjx1a002xLYEYtgJr8Luy8mKSiWo8J8ZT+aYbzhVrRz5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-01 15:49 ` Mike Frysinger [this message]
[not found] ` <201205011149.34086.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2012-05-01 18:21 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkiHQX4o0EiVW53W=PQbgp+RW6-LMqY7NpOb+4bGPdHFQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-01 18:33 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201205011149.34086.vapier@gentoo.org \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox