From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: "richardvoigt@gmail.com" <richardvoigt@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Automatic module license checking
Date: Tue, 12 Apr 2011 07:48:46 +0200 [thread overview]
Message-ID: <4DA3E7BE.6080701@gmail.com> (raw)
In-Reply-To: <BANLkTik0MqNsgDmCAspG03S27x9ZOH4A2A@mail.gmail.com>
[-- 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 --]
prev parent reply other threads:[~2011-04-12 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=4DA3E7BE.6080701@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=richardvoigt@gmail.com \
/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 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.