public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Lingard <chris@ukpost.com>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: initramfs howto?
Date: Mon, 19 Apr 2004 20:48:29 +0100	[thread overview]
Message-ID: <200404192048.29666.chris@ukpost.com> (raw)
In-Reply-To: <1081531299.19918.13.camel@serpentine.pathscale.com>

On Friday 09 April 2004 6:21 pm, Bryan O'Sullivan wrote:
> On Thu, 2004-04-08 at 23:48, Miles Bader wrote:

> I'm agnostic.  It's a two-line patch.  I don't care if it's called
> /spam/fandango/wubble, so long as the brave souls who are trying out
> initramfs don't keep stumbling over the same problem again and again :-)

May I suggest

diff -Naur linux-2.6.5.old/init/main.c linux-2.6.5/init/main.c
--- linux-2.6.5.old/init/main.c 2004-04-05 18:19:04.000000000 +0100
+++ linux-2.6.5/init/main.c     2004-04-18 15:37:56.000000000 +0100
@@ -604,7 +604,12 @@
        smp_init();
        do_basic_setup();

-       prepare_namespace();
+       /*
+       * check if there is an early userspace init, if yes
+       * let it do all the work
+       */
+       if ( ! sys_access("/linuxrc", 0) == 0)
+               prepare_namespace();

        /*
         * Ok, we have completed the initial bootup, and

linuxrc already exists for initrd systems, and is coded in anyway.

I have tested this with both with both linuxrc -> bin/ash
and with a script that brings up a full system.  (I have made
a boot CD that installs Linux-2.6.5 with udev)

Chris Lingard

  parent reply	other threads:[~2004-04-19 19:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 19:17 initramfs howto? Chris Meadors
2004-04-09  5:56 ` Bryan O'Sullivan
2004-04-09  6:48   ` Miles Bader
2004-04-09 17:21     ` Bryan O'Sullivan
2004-04-10  0:50       ` Miles Bader
2004-04-19 19:48       ` Chris Lingard [this message]
2004-04-19 21:39         ` H. Peter Anvin

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=200404192048.29666.chris@ukpost.com \
    --to=chris@ukpost.com \
    --cc=bos@serpentine.com \
    --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