From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 26 20:30:19 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4676916A500 for ; Sun, 26 Sep 2004 20:30:19 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E1E243D53 for ; Sun, 26 Sep 2004 20:30:18 +0000 (GMT) (envelope-from scottl@FreeBSD.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i8QKUbpp055227; Sun, 26 Sep 2004 14:30:37 -0600 (MDT) (envelope-from scottl@FreeBSD.org) Message-ID: <4157267D.4090009@FreeBSD.org> Date: Sun, 26 Sep 2004 14:28:45 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040831 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Forrest Aldrich References: <415722AA.9080500@forrie.com> In-Reply-To: <415722AA.9080500@forrie.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-scsi@FreeBSD.org Subject: Re: Status of iSCSI X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Sep 2004 20:30:19 -0000 Forrest Aldrich wrote: > I read the April 2004 report (on freebsd.org); presuming that's > up-to-date, it may be a while before we have iSCSI support in FreeBSD. > I wanted to verify here, etc. > > I'm involved in a project that will require something of that nature. > > > Thanks, > Forrest > [Note that email to you is bouncing, so I'm responding publically] There was an implementation done by Lucent last year for 4.x, but it has a sticky license and is probably out of date. I and several others see iSCSI as something that really needs to get done, but the 3-4 months of development time is more than can be done on evenings and weekends. I would also want to do it 'right' and implement new infrastructure in CAM to accompany it rather than making it monolithic like the Lucent implementation. What kind of project do you need it for, and what kind of resources do you have right now? Scott