[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



>I agree, I think we shouldn't install the header files from the linux
>kernel build.  It would be great if you had a patch which got the
headers
>installed from the xen-unstable build system...

I don't; at present I simply don't care about them and (in my private
trees) suppress their installation.

>> 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.

>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
- it pointlessly clutters the tree root with additional files

Jan

Attachment: xenlinux-install-sh.patch
Description: Text document

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.