RE: 2.3.34-pre1: chopped boot command line problem

Tigran Aivazian (tigran@sco.COM)
Fri, 17 Dec 1999 16:13:00 +0000 (GMT)


On Fri, 17 Dec 1999 nathan.zook@amd.com wrote:
> First, this is not our problem. The buffer we are working on holds 256
> bytes, so this looks like a SEP.

Nay, this is not Someone Else's Problem, this is OP (Our Problem). By
"our" I meant the Linux Community in general, not the E820 Group.

> Does the ramdisk work?

I don't care if ramdisk works or not (well, I do which is why I use
bde-ramdisk patch) - I just put ramdisk parameters there as example.
And no, ramdisk does not see the parameters, i.e. it uses the defaults
(which is why I changed the default 4096K to 8192K - I need big ramdisks).
The /proc/cmdline displays saved_command_line[] (up to '\0'
terminator, see fs/proc/proc_misc.c:cmdline_read_proc() calling sprintf())
which should be an exact copy made by parse_mem_cmdline() very early.

So, it is a problem and needs fixing. Btw, if you are not working on it -
that's good - I will take it as my weekend hacking project :)

Regards,
Tigran.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/