From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gleb Natapov <gleb@redhat.com>,
kvm developers <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
bochs developers <bochs-developers@lists.sourceforge.net>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] Add BIOS splash image support
Date: Wed, 17 Dec 2008 19:30:36 +0100 [thread overview]
Message-ID: <4949454C.5000501@siemens.com> (raw)
In-Reply-To: <49493372.3020205@codemonkey.ws>
Anthony Liguori wrote:
> Jan Kiszka wrote:
>> Paul Brook wrote:
>>
>>>> BTW, why does qemu not carry all bochs bios source? For reference, but
>>>> also to fully comply with the LGPL (pointing to the original source is
>>>> not sufficient when delivering binaries - like e.g. bios.bin...).
>>>>
>>> If this is really an issue, then I strongly suggest we fix it by
>>> moving the bios into its own project, and have everyone fetch it from
>>> there.
>>>
>>
>> Qemu distributes binaries that have been generated from LGPLed sources
>> (this is at least the case for bochs, one would have to check the
>> situation for the other firmware images), so it has to provide the
>> corresponding source code according to the license terms.
>
> You are not qualified to make the statement "has to". This is a legal
> issue and depends on how the GPL is interpreted. The FSF provides a set
> of guidelines and so does Debian. Debian's guidelines are more
> extreme. If you look at the FSF FAQ on this subject, the main issue is
> ensuring that the source code is always available.
>
> Since Bochs is on SF, as long as we ensure that the version we base on
> is always available, you could certainly conclude that's enough.
Well, I guess we are both not qualified to finally judge over this. But
this is not my point.
>
> But please, this is not an issue worth even discussing here. It is only
> relevant for people distributing QEMU and it's up to those people to
> consult with their legal teams to determine whether they need to do
> anything special.
And why complicating things downstream when it can be fixed upstream?
Because it is only a legal issue? As a redistributor of OSS who cares a
lot about such issues, you have a lot of "fun" getting things right when
upstream forgot it.
But as it looks like, there is a consensus on changing the situation
anyway. And up to now, no animal should have been harmed, too.
Jan
--
Siemens AG, Corporate Technology, CT SE 26
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2008-12-17 18:31 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 15:20 [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Laurent Vivier
2008-12-16 15:20 ` [Qemu-devel] [PATCH 1/3] Correct fw_cfg_add_callback() Laurent Vivier
2008-12-16 15:20 ` [Qemu-devel] [PATCH 2/3] [BIOS] Add splash image support Laurent Vivier
2008-12-16 15:20 ` [Qemu-devel] [PATCH 3/3] [QEMU] Add BIOS splash image Laurent Vivier
2008-12-16 15:33 ` Andreas Färber
2008-12-16 17:22 ` Laurent Vivier
2008-12-16 16:16 ` Blue Swirl
2008-12-16 17:32 ` Laurent Vivier
2008-12-16 17:41 ` Blue Swirl
2008-12-16 17:58 ` Laurent Vivier
2008-12-16 20:06 ` [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Blue Swirl
2008-12-16 20:28 ` Anthony Liguori
2008-12-16 20:46 ` Blue Swirl
2008-12-16 21:51 ` Laurent Vivier
2008-12-17 0:10 ` Carl-Daniel Hailfinger
2008-12-17 13:09 ` Laurent Vivier
2008-12-17 16:21 ` [Bochs-developers] " Carl-Daniel Hailfinger
2008-12-17 22:58 ` [Bochs-developers] [Qemu-devel] [PATCH 0/3] Add BIOS splashimage support Sebastian Herbszt
2008-12-17 11:03 ` [Qemu-devel] [PATCH 0/3] Add BIOS splash image support Daniel P. Berrange
2008-12-17 13:18 ` Paul Brook
2008-12-17 13:45 ` Jan Kiszka
2008-12-17 13:55 ` Gleb Natapov
2008-12-17 14:53 ` Jan Kiszka
2008-12-17 15:06 ` Jan Kiszka
2008-12-17 15:17 ` Paul Brook
2008-12-17 16:35 ` Jan Kiszka
2008-12-17 17:14 ` Anthony Liguori
2008-12-17 18:30 ` Jan Kiszka [this message]
2008-12-17 18:43 ` Anthony Liguori
2008-12-17 18:09 ` Andreas Färber
2008-12-17 17:15 ` Anthony Liguori
2008-12-17 22:28 ` Sebastian Herbszt
2008-12-18 8:59 ` Volker Ruppert
2008-12-18 21:46 ` H. Peter Anvin
2008-12-17 17:12 ` Carl-Daniel Hailfinger
2008-12-17 14:49 ` Gerd Hoffmann
2008-12-17 14:54 ` Jan Kiszka
2008-12-17 15:04 ` Kevin Wolf
2008-12-17 15:26 ` Daniel P. Berrange
2008-12-17 16:44 ` [Qemu-devel] " Jan Kiszka
2008-12-17 17:06 ` Gildas
2008-12-17 17:22 ` M. Warner Losh
2008-12-17 17:17 ` Gleb Natapov
2008-12-17 18:01 ` Anthony Liguori
2008-12-17 22:03 ` [Qemu-devel] " Sebastian Herbszt
2008-12-17 22:09 ` [Qemu-devel] " Anthony Liguori
2008-12-17 14:01 ` [Qemu-devel] " Daniel P. Berrange
2008-12-17 13:51 ` Kevin O'Connor
2008-12-17 21:58 ` [Qemu-devel] Re: [Bochs-developers] " Sebastian Herbszt
2008-12-17 23:24 ` Laurent Vivier
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=4949454C.5000501@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=bochs-developers@lists.sourceforge.net \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).