public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darryl L. Miles" <darryl@netbauds.net>
To: Christian Trefzer <ctrefzer@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 initrd module loading seems parallel on bootup
Date: Thu, 30 Jun 2005 09:45:15 +0100	[thread overview]
Message-ID: <42C3B11B.80909@netbauds.net> (raw)
In-Reply-To: <42C33149.3090305@web.de>


The exact patch for kernel/module.c that was marked for 2.6.11-rcX hit 
general release in patch-2.6.12.

What $PID is bash running as ?  Martin's comments on this are seem most 
relevant.

Can you build your own (2 pages of code) init process, that does 
something along the lines of
 * gracefully handles SIGCHLD
 * forks
 * executes bash
 * waits for bash to exit much like the patch does

So bash is not running a pid 1.  While nash is expected to run as init, 
bash is not, so fixing bash might also break it (its a complex beast).

-- 
Darryl L. Miles



  reply	other threads:[~2005-06-30  8:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-26  1:02 2.6.12 initrd module loading seems parallel on bootup Darryl L. Miles
2005-06-26  3:53 ` Christian Trefzer
2005-06-26  6:46 ` Andrew Morton
2005-06-26  9:26   ` Pozsár Balázs
2005-06-26 11:53     ` Christian Trefzer
2005-06-26 10:06   ` Darryl L. Miles
2005-06-26 12:00     ` Christian Trefzer
2005-06-26 14:11       ` Toon van der Pas
2005-06-27  5:47         ` Darryl L. Miles
2005-06-29 23:39           ` Christian Trefzer
2005-06-30  8:45             ` Darryl L. Miles [this message]
2005-06-30 14:12               ` Christian Trefzer
2005-06-26 13:19   ` Parag Warudkar
     [not found] <4jtOU-508-21@gated-at.bofh.it>
     [not found] ` <4jz7U-9S-7@gated-at.bofh.it>
     [not found]   ` <4jBCN-20Q-9@gated-at.bofh.it>
2005-06-27  6:24     ` Martin Wilck
  -- strict thread matches above, loose matches on Subject: below --
2005-06-25 22:09 Darryl L. Miles

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=42C3B11B.80909@netbauds.net \
    --to=darryl@netbauds.net \
    --cc=ctrefzer@web.de \
    --cc=linux-kernel@vger.kernel.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