* Automatic module license checking
@ 2011-04-11 21:11 Vladimir 'φ-coder/phcoder' Serbinenko
2011-04-12 4:33 ` richardvoigt
0 siblings, 1 reply; 3+ messages in thread
From: Vladimir 'φ-coder/phcoder' Serbinenko @ 2011-04-11 21:11 UTC (permalink / raw)
To: The development of GRUB 2
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
Hello, all. Due to recent case of non-compliance with GPL in a project
using GRUB2 codebase and according to new GNU guidelines I've
implemented an automatic module license checking. This checks doesn't
change in nothing the distributor obligation: any GRUB2 module is
covered by GPLv3(+) (and optionally dual-licensed under another
license). However, this change makes this compliance requirement
explicit by requiring author to put a GRUB_MOD_LICENSE macro. Also note
that everybody is allowed to remove the said check but doing so doesn't
free from legal GPL obligation. When implementing this check I've added
a bunch of GRUB_MOD_LICENSE and GRUB_MOD_DUAL_LICENSE, I'll be grateful
if everyone who sees a problem (e.g. non-correspondance between license
header and macro) would report it to me and I'll fix it as soon as time
permits.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Automatic module license checking
2011-04-11 21:11 Automatic module license checking Vladimir 'φ-coder/phcoder' Serbinenko
@ 2011-04-12 4:33 ` richardvoigt
2011-04-12 5:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
0 siblings, 1 reply; 3+ messages in thread
From: richardvoigt @ 2011-04-12 4:33 UTC (permalink / raw)
To: The development of GNU GRUB
Cc: Vladimir 'φ-coder/phcoder' Serbinenko
When does this check run? Seems ridiculous to do this on every boot
cycle, a bootloader should execute as quickly as possible, not try to
solve the world's legal problems.
Just my $0.02
2011/4/11 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
> Hello, all. Due to recent case of non-compliance with GPL in a project
> using GRUB2 codebase and according to new GNU guidelines I've
> implemented an automatic module license checking. This checks doesn't
> change in nothing the distributor obligation: any GRUB2 module is
> covered by GPLv3(+) (and optionally dual-licensed under another
> license). However, this change makes this compliance requirement
> explicit by requiring author to put a GRUB_MOD_LICENSE macro. Also note
> that everybody is allowed to remove the said check but doing so doesn't
> free from legal GPL obligation. When implementing this check I've added
> a bunch of GRUB_MOD_LICENSE and GRUB_MOD_DUAL_LICENSE, I'll be grateful
> if everyone who sees a problem (e.g. non-correspondance between license
> header and macro) would report it to me and I'll fix it as soon as time
> permits.
>
> --
> Regards
> Vladimir 'φ-coder/phcoder' Serbinenko
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Automatic module license checking
2011-04-12 4:33 ` richardvoigt
@ 2011-04-12 5:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
0 siblings, 0 replies; 3+ messages in thread
From: Vladimir 'φ-coder/phcoder' Serbinenko @ 2011-04-12 5:48 UTC (permalink / raw)
To: richardvoigt@gmail.com; +Cc: The development of GNU GRUB
[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]
On 12.04.2011 06:33, richardvoigt@gmail.com wrote:
> When does this check run? Seems ridiculous to do this on every boot
> cycle, a bootloader should execute as quickly as possible, not try to
> solve the world's legal problems.
>
Check is done when loading module. Performance penalty is limited to
reading few additional bytes, additional section search and 3 strcmp's.
It's much simpler than resolving even a single symbol.
> Just my $0.02
>
> 2011/4/11 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>> Hello, all. Due to recent case of non-compliance with GPL in a project
>> using GRUB2 codebase and according to new GNU guidelines I've
>> implemented an automatic module license checking. This checks doesn't
>> change in nothing the distributor obligation: any GRUB2 module is
>> covered by GPLv3(+) (and optionally dual-licensed under another
>> license). However, this change makes this compliance requirement
>> explicit by requiring author to put a GRUB_MOD_LICENSE macro. Also note
>> that everybody is allowed to remove the said check but doing so doesn't
>> free from legal GPL obligation. When implementing this check I've added
>> a bunch of GRUB_MOD_LICENSE and GRUB_MOD_DUAL_LICENSE, I'll be grateful
>> if everyone who sees a problem (e.g. non-correspondance between license
>> header and macro) would report it to me and I'll fix it as soon as time
>> permits.
>>
>> --
>> Regards
>> Vladimir 'φ-coder/phcoder' Serbinenko
>>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>
>>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-04-12 5:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-11 21:11 Automatic module license checking Vladimir 'φ-coder/phcoder' Serbinenko
2011-04-12 4:33 ` richardvoigt
2011-04-12 5:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.