From: Simon Brenner <brennersimon-KvP5wT2u2U0@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: GPLv2 for cifs-utils existing?
Date: Sat, 03 Sep 2011 09:39:17 +0200 [thread overview]
Message-ID: <4E61D9A5.6010303@arcor.de> (raw)
In-Reply-To: <20110902124740.GB15846-Znhnm/lQSyjxW5zecs3cv0EOCMrvLtNR@public.gmane.org>
Thanks for all your answers so far!
> That's to say that if you are distributing a single installable
> firmware file for your router, and it contains GPL'd software, you would
> arguably need to provide source for the entire work generating the
> firmware file. And this isn't specific to v3 of the GPL either, AFAIK,
> it's kind of the point of the license to begin with.
So how is it when, say, a router manufacturer has its own (proprietary +
closed) file format for the firmware files. Within the firmware he uses
several GPL projects (v2 or v3) as well as some own closed projects
which he doesn't want to be seen by everyone.
Would the manufacturer then have to provide all source code, even its
own which he originally wanted to keep private?
How about the toolchain he used to compile all the stuff?
If every user has to be able to rebuild his own firmware files then the
manufacturer would be forced to open all code.
Can you clarify that for me?
Thanks!
-Simon.
next prev parent reply other threads:[~2011-09-03 7:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <240043230.241860.1314945935851.JavaMail.ngmail@webmail12.arcor-online.net>
[not found] ` <240043230.241860.1314945935851.JavaMail.ngmail-hrWuGRo80rQUOsVZMWqyoH/75uz/KqYjrE5yTffgRl4@public.gmane.org>
2011-09-02 10:40 ` GPLv2 for cifs-utils existing? Jeff Layton
[not found] ` <20110902064023.51a3c945-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-09-02 12:47 ` sean finney
[not found] ` <20110902124740.GB15846-Znhnm/lQSyjxW5zecs3cv0EOCMrvLtNR@public.gmane.org>
2011-09-03 7:39 ` Simon Brenner [this message]
[not found] ` <4E61D9A5.6010303-KvP5wT2u2U0@public.gmane.org>
2011-09-05 9:26 ` sean finney
[not found] ` <20110905092634.GA28829-Znhnm/lQSyjxW5zecs3cv0EOCMrvLtNR@public.gmane.org>
2011-09-05 12:39 ` simo
2011-09-02 13:10 ` simo
2011-09-05 13:50 brennersimon-KvP5wT2u2U0
[not found] ` <498443694.299882.1315230630011.JavaMail.ngmail-hrWuGRo80rQUOsVZMWqyoH/75uz/KqYjrE5yTffgRl4@public.gmane.org>
2011-09-05 16:20 ` sean finney
-- strict thread matches above, loose matches on Subject: below --
2011-09-05 10:27 brennersimon-KvP5wT2u2U0
[not found] ` <901868733.695320.1315218442622.JavaMail.ngmail-n1zztEYQUKrHtOu4I4oYOX/75uz/KqYjrE5yTffgRl4@public.gmane.org>
2011-09-05 12:42 ` simo
[not found] ` <1315226544.22877.174.camel-akOVU7JyYd8WIfilqQrPtNi2O/JbrIOy@public.gmane.org>
[not found] ` <1315226341.22877.170.camel-akOVU7JyYd8WIfilqQrPtNi2O/JbrIOy@public.gmane.org>
2011-09-05 16:10 ` sean finney
[not found] ` <20110905161012.GA30136-Znhnm/lQSyjxW5zecs3cv0EOCMrvLtNR@public.gmane.org>
2011-09-05 17:50 ` simo
2011-09-01 13:08 brennersimon-KvP5wT2u2U0
[not found] ` <1473841237.231172.1314882534664.JavaMail.ngmail-hrWuGRo80rTYJ3RwVI/HE3/75uz/KqYjrE5yTffgRl4@public.gmane.org>
2011-09-01 15:05 ` Jeff Layton
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=4E61D9A5.6010303@arcor.de \
--to=brennersimon-kvp5wt2u2u0@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.