From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Christie Subject: Re: Request for review of Linux iSCSI driver version 4.0.0.1 Date: Wed, 29 Oct 2003 11:33:00 -0800 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <3FA015EC.6030102@us.ibm.com> References: <20031027153932.A16679@infradead.org> <018b01c39e1f$e013bab0$a0074d0a@apac.cisco.com> <20031029134557.A17523@infradead.org> <3F9FF8C7.70909@us.ibm.com> <3FA00E9E.7000704@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from e3.ny.us.ibm.com ([32.97.182.103]:38302 "EHLO e3.ny.us.ibm.com") by vger.kernel.org with ESMTP id S261464AbTJ2TeG (ORCPT ); Wed, 29 Oct 2003 14:34:06 -0500 In-Reply-To: List-Id: linux-scsi@vger.kernel.org To: Clay Haapala Cc: linux-scsi@vger.kernel.org Clay Haapala wrote: > On Wed, 29 Oct 2003, Mike Christie outgrape: > >>>This may turn out to be a discussion about where this code resides >>>and what code is best to (re)use, not if it is needed. "Early >>>boot" here is from PXE -- setting up the iSCSI initiator to reach a >>>target at some IP where the rest of the boot (initrd and friends) >>>is. >>> >> >>Oops. I forgot you guys use iNBP.com. I was thinking of pxelinux. >> >>Mike > > Oh, now I have to find out about pxelinux ... google ... OK. :-) > > Yeah, like that only different -- using iSCSI to a target to fetch > blocks rather than TFTP of files from a filestore. Once inbp.com reads in the kernel and initrd, it looks like your linuxrc just insmods the netwrok driver and iscsi mod. At this point (after you insmod the network driver but before you insmod iscsi.ko.) you can start the networking interface from userspace. Include a statically compiled dhcp program and run it from the linuxrc. Mike