From: "Nicholas A. Bellinger" <nick@pyxtechnologies.com>
To: iscsi-initiator-core-announce@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>
Cc: iscsi-initiator-core-devel
<iscsi-initiator-core-devel@iscsi-initiator-core.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Christoph Hellwig <hch@lst.de>, Mike Christie <mikenc@us.ibm.com>
Subject: [ANNOUNCE] iscsi-initiator-core 1.6.2.0-rc1 for 2.6.12-rc1
Date: Fri, 01 Apr 2005 12:01:41 -0800 [thread overview]
Message-ID: <1112385701.3008.18.camel@haakon> (raw)
Greetings all,
http://www.kernel.org/pub/linux/kernel/people/nab/iscsi-initiator-core/iscsi-initiator-core-1.6.2.0-rc1-2.6.12-rc1.patch.bz2
A few minor fixes in this release, with the main feature addition being
support for persistent connection/session parameters as defined within
/etc/sysconfig/initiator. For example, it is now possible to define
specific connection/session parameters and have those values remain
throughout connection/session failures. Also, the first run of tests
with dm-multipath have been compelted successful. I am working on a
section within the documentation to describe how these two pieces work
together within linux 2.6.
Also an important milestone has been reached with v1.0 of the
iscsi-initiator-core.org howto located at:
http://iscsi-initiator-core.org/mediawiki/index.php/Howto
This is a work in progress as data is imported from the ASCII version
from iscsi-initiator-core-tools v2.3.
This release is now considered stable and no new features will be added
until 1.6.2.0-final is released.
Thanks!
--
Nicholas A. Bellinger <nick@pyxtechnologies.com>
Chief Architect, PyX Technologies, Inc.
http://www.iscsi-initiator-core.org
next reply other threads:[~2005-04-01 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 20:01 Nicholas A. Bellinger [this message]
2005-04-24 2:49 ` [ANNOUNCE] iscsi-initiator-core 1.6.2.0-rc1 for 2.6.12-rc1 James Bottomley
2005-04-26 0:00 ` Nicholas A. Bellinger
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=1112385701.3008.18.camel@haakon \
--to=nick@pyxtechnologies.com \
--cc=James.Bottomley@SteelEye.com \
--cc=hch@lst.de \
--cc=iscsi-initiator-core-announce@vger.kernel.org \
--cc=iscsi-initiator-core-devel@iscsi-initiator-core.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikenc@us.ibm.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