From: Harry Butterworth Subject: Re: [RFC][PATCH] create an initrd for dom0 in install.sh script Date: Thu, 30 Mar 2006 17:47:57 +0100 Message-ID: <1143737277.17441.12.camel@localhost.localdomain> References: <1143731284.7695.9.camel@localhost.localdomain> <3d8eece20603300833x3264b5eet35395491d1469428@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3d8eece20603300833x3264b5eet35395491d1469428@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christian.Limpach@cl.cam.ac.uk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I put it there because that file is the one that creates the other symbolic links in /boot for the kernel images. Maybe they don't belong there either. I did think it was a bit weird that i386/boot-xen was creating symbolic links for the X86_64 build. I could create the link in the install.sh script instead. What do you think? On Thu, 2006-03-30 at 17:33 +0100, Christian Limpach wrote: > On 3/30/06, Harry Butterworth wrote: > > diff -r 9239f190736d -r 7d648c1099b2 > > linux-2.6-xen-sparse/arch/i386/boot-xen/Makefile > > --- a/linux-2.6-xen-sparse/arch/i386/boot-xen/Makefile Wed Mar 29 > > 23:11:53 2006 > > +++ b/linux-2.6-xen-sparse/arch/i386/boot-xen/Makefile Thu Mar 30 > > 14:57:57 2006 > > @@ -19,3 +19,4 @@ > > + ln -f -s initrd-$(XINSTALL_NAME)$(INSTALL_SUFFIX).img > > $(INSTALL_ROOT)/boot/initrd-$(VERSION).$(PATCHLEVEL)$(XENGUEST)$(INSTALL_SUFFIX).img > > This certainly doesn't belong in this file. > > christian > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >