public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: ebiederm@xmission.com
Cc: riel@conectiva.com.br, akropel1@rochester.rr.com,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18pre3-ac1
Date: Mon, 14 Jan 2002 01:28:31 -0800 (PST)	[thread overview]
Message-ID: <20020114.012831.44983761.davem@redhat.com> (raw)
In-Reply-To: <m1y9j1pf6r.fsf@frodo.biederman.org>
In-Reply-To: <Pine.LNX.4.33L.0201140409260.32617-100000@imladris.surriel.com> <m1y9j1pf6r.fsf@frodo.biederman.org>

   From: ebiederm@xmission.com (Eric W. Biederman)
   Date: 14 Jan 2002 00:25:16 -0700
   
   But for make -j the forking is done by make and it is nearly a
   fork bomb

Someone has probably mentioned this, but it is important to recognize
that make uses vfork().

  reply	other threads:[~2002-01-14  9:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 21:44 Linux 2.4.18pre3-ac1 Alan Cox
2002-01-13 19:23 ` Thiago Rondon
2002-01-13 22:52 ` Ville Herva
2002-01-13 22:57   ` Alan Cox
2002-01-14  0:15 ` Adam Kropelin
2002-01-14  0:47   ` Alan Cox
2002-01-14  2:13     ` Benjamin LaHaise
2002-01-14  2:54   ` Rik van Riel
2002-01-14  5:47     ` Eric W. Biederman
2002-01-14  6:17       ` Rik van Riel
2002-01-14  7:25         ` Eric W. Biederman
2002-01-14  9:28           ` David S. Miller [this message]
2002-01-14 12:05             ` Rik van Riel
2002-01-21  3:46           ` Daniel Phillips
2002-01-21  5:30             ` Richard Gooch
2002-01-21  5:34               ` Rik van Riel
2002-01-21  7:01                 ` Eric W. Biederman
2002-01-21 12:02                   ` Rik van Riel
2002-01-21 14:02                   ` Daniel Phillips
2002-01-21 13:22               ` Daniel Phillips

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=20020114.012831.44983761.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=akropel1@rochester.rr.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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