From: Jeff Dike <jdike@karaya.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UML - part 2 of 3
Date: Tue, 13 Aug 2002 15:08:56 -0500 [thread overview]
Message-ID: <200208132008.PAA03902@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Tue, 13 Aug 2002 09:13:58 MST." <Pine.LNX.4.44.0208130912390.7291-100000@home.transmeta.com>
torvalds@transmeta.com said:
> Please use "root=0xXXYY" instead, or consider figuring out the name
> _automatically_ from the list of genhd's in the system (ie the reverse
> of blkdev_name() or whatever it is called).
OK, consider that patch withdrawn. In its place is the one below. It's in
UML arch code, so it needs to be applied after UML itself. It disables
'root=/dev/ubdxx' in UML for the time being.
The root_dev_names array looks like it can be eliminated entirely, as long
as the gendisk list is populated before checksetup. This means either there
needs to be a before_setup_initcall or the calculation of the rootdev kdev_t
needs to be split out from the argument parsing and put in a late initcall.
I don't know if that breaks anything.
If that is reasonable, I can start laying the groundwork.
Jeff
--- linus/arch/um/kernel/um_arch.c~ Fri Aug 2 22:06:03 2002
+++ linus/arch/um/kernel/um_arch.c Tue Aug 13 14:32:39 2002
@@ -38,7 +38,7 @@
int fg_console;
struct kbd_struct kbd_table[MAX_NR_CONSOLES];
-#define DEFAULT_COMMAND_LINE "root=/dev/ubd0"
+#define DEFAULT_COMMAND_LINE "root=6200"
unsigned long thread_saved_pc(struct task_struct *task)
{
next prev parent reply other threads:[~2002-08-13 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 17:05 [PATCH] UML - part 2 of 3 Jeff Dike
2002-08-13 16:13 ` Linus Torvalds
2002-08-13 20:08 ` Jeff Dike [this message]
2002-08-13 19:26 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2002-08-03 3:40 Jeff Dike
2002-07-28 16:34 Jeff Dike
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=200208132008.PAA03902@ccure.karaya.com \
--to=jdike@karaya.com \
--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