Re: Need help in compiling open-iscsi-2.0-870.2 for kernel 2.6.28

2009-02-02 Thread Boaz Harrosh
Mike Christie wrote: > Jeronimo de A. Barros wrote: >> Hello, >> >> Any help or hint to compile open-iscsi-2.0-870.2 for kernel 2.6.28 ? >> >> I'm trying on a Bluewhite64 12.2 running kernel 2.6.28.2: >> >> r...@test:/usr/local/src/open-iscsi-2.0-870.2# uname -a >> Linux test 2.6.28.2 #1 SMP Sun F

Re: Issues with intel firmware initiator, ibft and 2-way chap

2009-02-02 Thread Konrad Rzeszutek
On Mon, Feb 02, 2009 at 11:39:18AM +0100, Hans de Goede wrote: > > Hi, > > When using 2-way chap and booting from an intel network card with intel > firmware initiator, their is no way to specify the username in the firmware > initiator for the reverse chap, nor does it care what username the t

Re: Issues with intel firmware initiator, ibft and 2-way chap

2009-02-02 Thread Mike Christie
Konrad Rzeszutek wrote: > On Mon, Feb 02, 2009 at 11:39:18AM +0100, Hans de Goede wrote: >> Hi, >> >> When using 2-way chap and booting from an intel network card with intel >> firmware initiator, their is no way to specify the username in the firmware >> initiator for the reverse chap, nor does

Re: [PATCH 1/2] open-iscsi: Makefile: Don't build out-of-tree Kernel modules by default

2009-02-02 Thread Mike Christie
Boaz Harrosh wrote: > > Separate out the build of "kernel:" and "user:" targets. > Let "all:" depend on "user:" only, though making kernel builds > optional. > I like what the patches are doing by warning the user and fixing up the output, but could we just switch up the default? I think kerne

Re: Issues with intel firmware initiator, ibft and 2-way chap

2009-02-02 Thread Konrad Rzeszutek
On Mon, Feb 02, 2009 at 12:06:05PM -0600, Mike Christie wrote: > > Konrad Rzeszutek wrote: > > On Mon, Feb 02, 2009 at 11:39:18AM +0100, Hans de Goede wrote: > >> Hi, > >> > >> When using 2-way chap and booting from an intel network card with intel > >> firmware initiator, their is no way to spe

Re: Need help in compiling open-iscsi-2.0-870.2 for kernel 2.6.28

2009-02-02 Thread Jeronimo de A. Barros
Mike, 2009/2/1 Mike Christie > > Yeah, that is not going to work, because the 2.6.28 kernel changed some > kernel APIs. The kernel modules need to be updated for the new APIs. I > have done this to the code in git: > git clone git://git.kernel.org/pub/scm/linux/kernel/git/mnc/open-iscsi.git > >

[PATCH 1/2] open-iscsi: Makefile: Don't build out-of-tree Kernel modules by default

2009-02-02 Thread Boaz Harrosh
Separate out the build of "kernel:" and "user:" targets. Let "all:" depend on "user:" only, though making kernel builds optional. [Mike please revisit the @echo output if we need anything added?] Signed-off-by: Boaz Harrosh --- Makefile | 26 +++--- 1 files changed, 15 i

Re: PATCH: fix iBFT firmware reading with newer kernels

2009-02-02 Thread Mike Christie
Mike Christie wrote: > Mike Christie wrote: >> Hans de Goede wrote: >>> Yes it does the same thing, is this from the open-iscsi VCS ? and where do >>> I >>> find that ? >>> >> Ok, I will merge up your code instead with the fixes in the thread. Thanks! >> > > Here is the rediffed patch. I used s

Re: Need help in compiling open-iscsi-2.0-870.2 for kernel 2.6.28

2009-02-02 Thread Mike Christie
Boaz Harrosh wrote: > > Hi mike, if we are already at the subject. Something I wanted for a while. > > It is expected for out-of-tree Kernel modules to constantly break at the > development edge. What happens today is that I can't finish compiling and > installing user-mode tools, if Kernel does

[PATCH 2/2] open-iscsi: kernel/Makefile: Better Makefile output when compiling with new Kernels

2009-02-02 Thread Boaz Harrosh
In case we are compiling against a newer kernel then what the out-of-tree is expecting, Output to the user that use of in-tree modules are recommended. This will still fail the compilation. because we don't want to compile in that case. But the user can see that this is an acceptable situation a

Issues with intel firmware initiator, ibft and 2-way chap

2009-02-02 Thread Hans de Goede
Hi, When using 2-way chap and booting from an intel network card with intel firmware initiator, their is no way to specify the username in the firmware initiator for the reverse chap, nor does it care what username the target provides. However under sysfs (ibft) there is a reverse username at

Re: Issues with intel firmware initiator, ibft and 2-way chap

2009-02-02 Thread Michael Brown
On Monday 02 February 2009 19:12:25 Konrad Rzeszutek wrote: > A year ago that was the problem - you got something like this: > > konrad@/data/git/ibft$ hexdump intel_nic.bin > 000 4269 5446 029c 0001 4e49 4554 004c > 010 > * > 030

[PATCH 0/2] open-iscsi: Makefile enhancements

2009-02-02 Thread Boaz Harrosh
Mike Christie wrote: > Boaz Harrosh wrote: >> Separate out the build of "kernel:" and "user:" targets. >> Let "all:" depend on "user:" only, though making kernel builds >> optional. >> > > I like what the patches are doing by warning the user and fixing up the > output, but could we just switch

[PATCH 1/2] open-iscsi: Makefile: separate out user: and kernel: make targets

2009-02-02 Thread Boaz Harrosh
Separate out the build of "kernel:" and "user:" targets. [Mike please revisit the @echo output if we need anything added] Signed-off-by: Boaz Harrosh --- Makefile | 25 ++--- 1 files changed, 14 insertions(+), 11 deletions(-) diff --git a/Makefile b/Makefile index 95786

[PATCH 2/2] open-iscsi: kernel/Makefile: Better Makefile output when compiling with new Kernels

2009-02-02 Thread Boaz Harrosh
In case we are compiling against a newer kernel then what the out-of-tree is expecting, Output to the user that use of in-tree modules are recommended. This will still fail the compilation. because we don't want to compile in that case. But the user can see that this is an acceptable situation a