From: Christoph Hellwig <hch@infradead.org>
To: devzero@web.de
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: Disable SCSI-Reservation at the driver level ?
Date: Mon, 27 Nov 2006 17:18:12 +0000 [thread overview]
Message-ID: <20061127171812.GA9185@infradead.org> (raw)
In-Reply-To: <1456266874@web.de>
On Mon, Nov 27, 2006 at 10:45:42AM +0100, devzero@web.de wrote:
> > And more. It's in fact one of the most blatant violations of the
> > Linux 2.4 kernel copyrights. Don't expect support if you use such
> > an illegal product.
>
> really?
> this is the first time i hear that ESX is an "illegal" product from the point of view of the kernel community.
> afaik, the esx kernel (vmnix) is a completely different product and for example, the source of the linux drivers they have modified to run under ESX are made available for download, as GPL tells them to do.
>
> what`s the problem here?
It's a modified linux kernel with hooks for a big binary module that takes
over part of the control. It's rather hard to argue that it's not a derived
work. Especially as they reuse various I/O subsystem of the kernel
that has been parasited.
> can you provide a link to some thread where this has been discussed?
I don't think so.
> something to be resolved with the help of gpl-violations.org ?
I haven't found any evidence that they are using enough code that
gpl-violations.org has the right to defend.
next prev parent reply other threads:[~2006-11-27 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 9:45 Disable SCSI-Reservation at the driver level ? devzero
2006-11-27 17:18 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-27 18:36 devzero
2006-11-26 16:31 roland
2006-11-26 17:46 ` James Bottomley
2006-11-26 19:22 ` roland
2006-11-28 19:23 ` Douglas Gilbert
2006-11-27 5:56 ` Christoph Hellwig
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=20061127171812.GA9185@infradead.org \
--to=hch@infradead.org \
--cc=devzero@web.de \
--cc=linux-scsi@vger.kernel.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