linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@kernel.org>
To: Core-iSCSI <Core-iSCSI@googlegroups.com>,
	Open iSCSI <open-iscsi@googlegroups.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Core-iSCSI v1.6.2.2 (STABLE) + Tools v3.1
Date: Fri, 09 Dec 2005 15:50:11 -0800	[thread overview]
Message-ID: <1134172211.5350.29.camel@haakon> (raw)

Greetings all,

Core-iSCSI v1.6.2.2 and Core-iSCSI-tools v3.1 will be available shortly
from:

http://www.kernel.org/pub/linux/kernel/people/nab/iscsi-initiator-core/core-iscsi-v1.6.2.2.tar.bz2
http://www.kernel.org/pub/linux/utils/storage/iscsi/core-iscsi-tools-v3.1.tar.bz2

This release would not have been possible without the help of:

http://www.sbei.com
Dominik and Dustin @ VBI
Daniel @ JHAPL
Bill and Chris @ Wasabi
Albert Pauw
Mike Mazarick
Micky Mazarick
Mark Tyler
jonas@wehey.com

This release includes a solution for single portal + multiple IQN names
that some iSCSI target nodes use as their primary naming scheme.  This
done via an optional parameter inside of the /etc/sysconfig/initiator
which does not break backwards comptability with existing installations.
Additionally a fix has been included for HP iSCSI Target Nodes that
involves the removal of a 'return on error' condition related to
Underflow + S_BIT checking.  For the former, manual pages and howto have
been updated to reflect the change to the /etc/sysconfig/initiator
configuration file.

Additionally, it was recently brought to my attention that a check
related to DataSequeceInOrder=Yes located in iscsi_initiator_erl0.c is
causing a problem with certain vendors iSCSI Target nodes.  I will be
getting more information on this issue in the next few days,  and will
release a fix as soon as possible.  I will keep everyone posted.

Also, the Core-iSCSI list has been created.  Everyone is invited to join
at:  http://groups.google.com/group/Core-iSCSI

And finally, the project's website should be going online sometime in
the next week.  I will keep everyone posted.  We have definately made an
amazing amount of progress in the last 8 days, and the Core-iSCSI team
will keep moving full steam ahead with the project as long as a need
exists.

Thanks for your support.

-- 
Nicholas A. Bellinger <nab@kernel.org>


                 reply	other threads:[~2005-12-09 23:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1134172211.5350.29.camel@haakon \
    --to=nab@kernel.org \
    --cc=Core-iSCSI@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=open-iscsi@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).