From: Rusty Russell <rusty@rustcorp.com.au>
To: Burton Windle <bwindle@fint.org>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [2.5.51+] kernel not honoring init= bootparm? (fwd)
Date: Mon, 23 Dec 2002 13:08:57 +1100 [thread overview]
Message-ID: <20021223021009.8E1482C0A7@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 20 Dec 2002 15:41:52 CDT." <Pine.LNX.4.43.0212201540160.3821-100000@morpheus>
In message <Pine.LNX.4.43.0212201540160.3821-100000@morpheus> you write:
> I think this might be due to the changes you made.
Indeed it was. Looks like overzealous patch cropping on my part.
This works for me. Linus, please apply.
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
Name: init= boot command line fix
Author: Rusty Russell
Status: Tested on 2.5.52
D: Restores the accidentally dropped code to handle init=.
diff -urNp --exclude TAGS -X /home/rusty/current-dontdiff --minimal linux-2.5.52/init/main.c working-2.5.52-noexit/init/main.c
--- linux-2.5.52/init/main.c Tue Dec 17 08:11:00 2002
+++ working-2.5.52-noexit/init/main.c Mon Dec 23 12:49:41 2002
@@ -259,6 +259,22 @@ static int __init unknown_bootoption(cha
return 0;
}
+static int __init init_setup(char *str)
+{
+ unsigned int i;
+
+ execute_command = str;
+ /* In case LILO is going to boot us with default command line,
+ * it prepends "auto" before the whole cmdline which makes
+ * the shell think it should execute a script with such name.
+ * So we ignore all arguments entered _before_ init=... [MJ]
+ */
+ for (i = 1; i < MAX_INIT_ARGS; i++)
+ argv_init[i] = NULL;
+ return 1;
+}
+__setup("init=", init_setup);
+
extern void setup_arch(char **);
extern void cpu_idle(void);
parent reply other threads:[~2002-12-23 2:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.43.0212201540160.3821-100000@morpheus>]
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=20021223021009.8E1482C0A7@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=bwindle@fint.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®