From owner-freebsd-scsi@FreeBSD.ORG  Mon Feb 21 09:22:01 2005
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
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 03F8216A4CE; Mon, 21 Feb 2005 09:22:01 +0000 (GMT)
Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A299C43D2D; Mon, 21 Feb 2005 09:22:00 +0000 (GMT)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by cs1.cs.huji.ac.il with esmtp
	id 1D39lO-000ES6-L4; Mon, 21 Feb 2005 11:21:58 +0200
X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4
To: Danny Braniss <danny@cs.huji.ac.il>
In-Reply-To: Message from Danny Braniss <danny@cs.huji.ac.il> 
	<E1D2Erx-000HSG-CK@cs1.cs.huji.ac.il> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 21 Feb 2005 11:21:58 +0200
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1D39lO-000ES6-L4@cs1.cs.huji.ac.il>
cc: Scott Long <scottl@freebsd.org>
cc: scsi@freebsd.org
Subject: and now it's walking! Re: iSCSI first steps! 
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2005 09:22:01 -0000

> 
> Looks wonderful!  What are your next steps for it?
> 
it's still alpha, but
 o- fdisk/newfs/dump/restore/fsck seem to be doing ok, tried it against
	- NetAPP: all ok
	- Intransa: all ok
	- Linux: it crashed when i tried newfs
		the linux panicked, my driver recoverd, but i need abort
		the cam commands, soon.

missing:
	- error recovery
		- when link goes down; i'll use  the Linux as a target.
		- screwed up connection, i guess this will wait
	- the user interface:
		- at the moment it does very basic things.
	- documentation, documentation, documentation.

help needed with:
	- how can i do the equivalent of 'camcontrol rescan n' from inside
	  the driver, after it 'hooked up' to a target?

comming real soon now:
	invitation to testers.

danny