Rik and Richard,
As you see, I in good faith prior to this holy war, had initiated a formal
request include a new protocol into the Linux kernel prior to the freeze.
The extention was requested to insure the product was of the highest
quality and not limited with excessive erratium as the ratification of the
IETF modified, postponed, and delayed ; regardless of reason.
Obviously, PyX had (has) on its schedule to product a high quality target
which is transport independent on each side of the protocol. We are not
sure of this position because of the uncertain nature of the basic usages
of headers and export_symbols.
Regards,
Andre Hedrick, CTO & Founder
iSCSI Software Solutions Provider
http://www.PyXTechnologies.com/
---------- Forwarded message ----------
Date: 23 Oct 2002 09:57:43 +0100
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andre Hedrick <andre@pyxtechnologies.com>
Cc: Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Linux iSCSI Initiator, OpenSource
On Wed, 2002-10-23 at 09:30, Andre Hedrick wrote:
>
> Greetings Linus and Alan,
>
> PyX Technologies is asking for a formal extention beyond the Oct 31st
> Feature Freeze. The exception to the rules is generally granted to no
> one, and is well understood by PyX. Only because PyX is under review for
> full funding on "Oct 31st" in the morning, would I even consider this
> motion. Our position is to formally open source a full feature with all
> corner cases resolved under "error recovery level zero".
I can't see an iscsi initiator needing to touch core code anyway. Its
just another (slightly demented) scsi adapter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jan 07 2003 - 22:00:27 EST