Re: [Xen-merge] [PATCH] broken install

[Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>]

On Fri, Jan 06, 2006 at 01:38:54PM +0100, Jan Beulich wrote:
> >> Even beyond that, for consistency the architecture's install.sh
> should
> >> be used for installing the kernel, primarily to automate
> >> initrd/initramfs generation. I have such a patch in place all the
> time
> >> locally, and I had posted that long ago to xen-devel. I would be
> more
> >> than happy if that could also get integrated...
> >
> >I think this would also be preferable.  Please send the patch again.
> 
> Attached (applies cleanly only with the other patches applied before).
> I don't have an up-to-date path for the unstable tree at hand.

This is not quite what I had in mind -- I was hoping we could move all
of the install code into the script and have a xen one.

So, with the patch below, won't we then be using the regular i386
install.sh if we try installing to /boot (or /)?  That seems rather
optimistic...

> >The only open-issue is how and where to build vmlinuz.  My preference
> >would be to not do it in the boot-xen sub-directory at all but build
> it
> >directly from the arch/{i386,x86_64}/Makefiles.  It seems insane to
> me
> >to type "make vmlinuz" at the top of the tree resulting in the file
> >being created 3 levels further down in a non-obvious location.
> 
> Again, while I agree that this seems more logical, there are two
> arguments against it:
> - it is inconsistent with how native i386/x86-64 work

Neither of them build a vmlinuz target/file in the first place, how
can it be inconsistent?

    christian


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