From: Oliver Xymoron <oxymoron@waste.org>
To: Andrew Morton <akpm@digeo.com>
Cc: Andre Hedrick <andre@pyxtechnologies.com>,
Rik van Riel <riel@conectiva.com.br>,
Richard Stallman <rms@gnu.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux iSCSI Initiator, OpenSource (fwd) (Re: Gauntlet Set NOW!)
Date: Sun, 5 Jan 2003 21:06:22 -0600 [thread overview]
Message-ID: <20030106030622.GC28100@waste.org> (raw)
In-Reply-To: <3E179CCF.F4CAE1E5@digeo.com>
On Sat, Jan 04, 2003 at 06:47:43PM -0800, Andrew Morton wrote:
> Andre Hedrick wrote:
> >
> > 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.
> >
>
> I suggest that if a function happens to be implemented as an inline
> in a header then it should be treated (for licensing purposes) as
> an exported-to-all-modules symbol. So in Linux, that would be LGPL-ish.
>
> The fact that a piece of kernel functionality happens to be inlined
> is a pure technical detail of linkage.
>
> If there really is inlined functionality which we do not wish made
> available to non-GPL modules then it should be either uninlined and
> not exported or it should be wrapped in #ifdef GPL.
More pragmatically, who cares? There's already at least one vendor
(Cisco) who ships a perfectly good fully GPLed iSCSI initiator module
that doesn't need to touch any core code. It's already the benchmark
for compatibility at interoperability tests. And it's following the
IETF drafts closely too. Once we actually have an iSCSI RFC, it might
be worth pulling it into the kernel tree. I believe Red Hat is
shipping it some form already.
That leaves the question of using Linux as an iSCSI target, and I've
yet to see any reason why this couldn't be done in userspace. In fact,
in a lot of ways that's the right thing to do as it lets you take
proper advantage of MD/LVM/EVMS/crypto, etc..
There are a few other free implementations out there too.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
next prev parent reply other threads:[~2003-01-06 2:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 1:54 Linux iSCSI Initiator, OpenSource (fwd) (Re: Gauntlet Set NOW!) Andre Hedrick
2003-01-05 2:47 ` Andrew Morton
2003-01-05 3:26 ` NEURONET
2003-01-05 4:11 ` NEURONET
2003-01-05 4:41 ` Andre Hedrick
2003-01-05 6:16 ` Andrew Morton
2003-01-06 3:06 ` Oliver Xymoron [this message]
2003-01-06 3:38 ` Andre Hedrick
2003-01-06 5:24 ` Oliver Xymoron
2003-01-06 10:24 ` Andrew McGregor
2003-01-06 16:51 ` Roman Zippel
2003-01-07 0:28 ` Andre Hedrick
2003-01-07 20:36 ` Roman Zippel
2003-01-07 22:45 ` Andre Hedrick
2003-01-08 0:04 ` Roman Zippel
2003-01-08 1:43 ` Alan Cox
2003-01-08 1:08 ` Larry McVoy
2003-01-08 16:48 ` Vojtech Pavlik
2003-01-08 19:37 ` Andre Hedrick
2003-01-07 0:39 ` Andrew McGregor
2003-01-07 4:20 ` Oliver Xymoron
2003-01-07 5:38 ` Valdis.Kletnieks
2003-01-07 6:16 ` Werner Almesberger
2003-01-07 6:43 ` Valdis.Kletnieks
2003-01-07 7:08 ` Werner Almesberger
2003-01-07 8:00 ` Valdis.Kletnieks
2003-01-07 8:14 ` Werner Almesberger
2003-01-07 8:41 ` Valdis.Kletnieks
2003-01-07 17:07 ` Werner Almesberger
2003-01-07 12:12 ` Andrew McGregor
2003-01-07 6:45 ` Lincoln Dale
2003-01-07 7:02 ` Valdis.Kletnieks
2003-01-07 11:24 ` Andrew McGregor
2003-01-07 10:31 ` Olivier Galibert
2003-01-08 19:10 ` H. Peter Anvin
2003-01-08 20:09 ` Andrew McGregor
2003-01-08 20:40 ` Richard B. Johnson
2003-01-07 12:31 ` Alan Cox
2003-01-07 12:31 ` Andrew McGregor
2003-01-07 13:58 ` Alan Cox
2003-01-07 23:09 ` Andrew McGregor
2003-01-07 16:21 ` Oliver Xymoron
2003-01-07 13:04 ` Lionel Bouton
[not found] ` <Pine.LNX.4.10.10301051924140.421-100000@master.linux-ide.o rg>
2003-01-06 7:14 ` Lincoln Dale
2003-01-06 7:53 ` Linux iSCSI Initiator Andre Hedrick
[not found] ` <Pine.LNX.4.10.10301052337150.421-100000@master.linux-ide.o rg>
2003-01-06 9:10 ` Lincoln Dale
2003-01-06 9:28 ` Andre Hedrick
2003-01-06 3:25 ` Linux iSCSI Initiator, OpenSource (fwd) (Re: Gauntlet Set NOW!) Richard Stallman
2003-01-06 4:08 ` Andre Hedrick
2003-01-06 20:49 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-01-05 22:51 Adam J. Richter
[not found] <fa.kccjmvv.13go3jp@ifi.uio.no>
[not found] ` <fa.hjtum4v.fki8p1@ifi.uio.no>
2003-01-08 1:07 ` walt
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=20030106030622.GC28100@waste.org \
--to=oxymoron@waste.org \
--cc=akpm@digeo.com \
--cc=andre@pyxtechnologies.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rms@gnu.org \
/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