WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] iscsi patch

I don't know if you use a Debian system. If so I'll be releasing the
XenLinux-Build utility and an iSCSI initator deb in the next couple of
days. The XenLinux-BUild is being setup to use the debian style
/usr/src/kernel-patches structure to apply various patches
auto-magically prior to building your kernel and creating the tarball.

The only glitch that I can't figure out is this: how best to keep the
minimal number of kernel source trees while still keeping track of what
patches were applied and removeing/applying the necessary ones as
apropriate for each config file... For now if you use it you will need
to either always use the source with the same patches, or run
debian/rules clean prior to creating a different kernel without patches
that you have applied before. Anyone have any ideas on this part?

First release is tonight btw.  Haven't written the deb creation part as
of yet, just tarball creation.

Brian


On Mon, 2004-08-23 at 07:53, James Harper wrote:
> what's the best way of setting up the source tree so that 'make
> linux26' will automagically apply a given patch to a particular source
> tree? eg iscsi initiator patch to 2.6.7-xenU.
>  
> thanks
>  
> James 



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>