RE: [Xen-devel] iscsi patch

[James Harper <JamesH@xxxxxxxxxxxxxxxx>]

actually, to make it for xenU from xen0 (no compiler tools in xenU on my setup), i have to also replace all occurances 'uname -r' with something that gives me '2.6.7-xenU' (eg echo 2.6.7-xenU) in both the makefile and install.sh files. it's a bit of a pain.

 

the initrd comment is true though, unless iscsi (built in to the kernel) could be convinced to connect via a kernel parameter... that seems a bit extreme though when an initrd would solve the problem nicely.

 

as for patches, would a patch.d directory be out of the question? something that the makefile could call via run-parts after extracting each source tree? It could pass the name of the source tree as a parameter. The patch.d directory would contain scripts that actually apply the patches.

 

James

 

 

---

From: Ian Pratt
Sent: Tue 24/08/2004 12:42 AM
To: James Harper
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx; Ian.Pratt@xxxxxxxxxxxx
Subject: Re: [Xen-devel] iscsi patch

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

I find it easy to build the iscsi initiator module outside the
kernel tree. [Even if you build it into the kernel you'll still
need an initrd anyhow]

Just edit TOPDIR and KDIR, then "make ARCH=xen".

If you want to apply it as a patch, you could follow the
ebtables example in the to-level Makefiles.

Ian