From: George G. Davis (gdavis@mvista.com)
Date: Wed Mar 27 2002 - 19:05:11 EST
Greetings,
I realise that the bootldr is a fast moving work in progress. But I've
been having a minor problem with the wrong kernel args getting passed
into the kernel lately via the `boot vfat` command, e.g. using
boot vfat
results in passing "vfat" into the kernel command line. This does the
same:
boot vfat foobar
This doesn't modify the current kernel command line at all as set via
the params file:
boot vfat foobar snafu
And if you actually "want" to pass an arg into the kernel via the boot
vfat command, you need to do:
boot vfat foobar snafu init=/bin/sh
Anyway, I've attached a patch below which fixes the problem for me.
The patch assumes that comments in the source and the help for "boot vfat"
are accurate, i.e.
boot vfat <filename> [kernel-optargs ...]
So, although the "kernel-filename" currently isn't used with
command_boot_vfat, it's a required place holder for a feature which
will be supported in the future, i.e. ability to specify the
kernel to boot on the command line.
Er, then again, maybe my build of the bootldr is just plain old broken
in some way?
Thanks!
-- Regards, George
This archive was generated by hypermail 2.1.5 : Fri Jan 17 2003 - 17:47:03 EST