[Xen-ia64-devel] RE: [PATCH] Patch for loading module[2of2]

["Xu, Anthony" <anthony.xu@xxxxxxxxx>]

>> Using initrd to load Linux kernel image is only a temporally
>> workround and should be corrected.  There is no backward
>> compability issue on Xen/ia64 on loading kernel image per se.
>>  Rather, "initrd" should be maintained to load "initrd"
>> maintains the backward compability with current elilo.efi.
>> The "module" add-on is to continue to maintain elilo compability
>> Imaging a single elilo.conf to have multi-initrd with two
>> different meanings, this is definitely to confuse users.
>
>I suppose that's a reasonable argument, though I don't agree
>that your changed parameter names are any less confusing than
>the original way: "module" is hardly a parameter name for
>the domain0 image.
>
>Maybe the right answer is for elilo to allow a "domain0="
>parameter name, which could be an alias for "module=".
>I'm not sure the elilo maintainers would like that,
>but it would certainly be the least confusing alternative.
>
>This might be a good topic for a poll... we now have over
>70 people on this list.  Let's ask (see next message).
>
Elilo is a gerernal OS loader,it doesn't and doesn't need to know
presence of domain0,
For elilo, xen.gz is a OS kernel, initrd= it's Os's initial ramdisk,
module= is Os's parameter, we should keep all this meaning, we shouldn't
make elilo special just for xen.

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel