From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"Marc Kleine-Budde" <mkl@pengutronix.de>
Subject: Re: [PATCH can-utils 3/3] slcand: remove program as it is undistributable
Date: Sun, 12 Jan 2014 19:22:51 +0100 [thread overview]
Message-ID: <52D2DD7B.2070003@hartkopp.net> (raw)
In-Reply-To: <CAGm1_kuooN2PUQGAEqhG=59qJWT-10F0yvAQWVgnS9jDXnB05Q@mail.gmail.com>
On 12.01.2014 17:09, Yegor Yefremov wrote:
> On Sun, Jan 12, 2014 at 11:57 AM, Oliver Hartkopp
> <socketcan@hartkopp.net> wrote:
>>
>>
>> On 12.01.2014 00:38, Yegor Yefremov wrote:
>>> On Sun, Jan 12, 2014 at 12:10 AM, Uwe Kleine-König
>>> <u.kleine-koenig@pengutronix.de> wrote:
>>>> The source file specifies slcand to be licensed under both GPL-2+ and GFDL.
>>>> These two licenses are incompatible which makes this file undistributable.
>>>> The clean way to fix this is to remove the file and reimplement its
>>>> functionality under a valid license when need arises.
>>>
>>> There is need for this daemon. I'm using it in production tests.
>>>
>>
>> Oh, yes. There was so much effort put into this slcand.
>> We should better look how we might fix the license issues.
>>
>> The original thread where slcand comes from was here:
>>
>> http://socket-can.996257.n3.nabble.com/slcan-attach-and-resetting-line-disciplines-td1396.html
>>
>> And here was the original commit to the SVN:
>> http://svn.berlios.de/wsvn/socketcan/trunk/can-utils/slcand.c?rev=973&peg=973
>>
>> The code has been removed from Wikipedia in October 2009
>> http://en.wikipedia.org/w/index.php?title=Daemon_%28computing%29&diff=321383226&oldid=320644717
>> (not a textbook. these examples are completely opaque to non-experts)
>>
>> And it has been added here (wihout any license information):
>> http://en.wikipedia.org/w/index.php?title=Daemon_%28computing%29&diff=273831207&oldid=273016660
>>
>> I assume we need to rewrite the daemon-specific code, e.g. use the
>> other reference in Wikipedia:
>>
>> http://www-theorie.physik.unizh.ch/~dpotter/howto/daemonize
>>
>> which is public domain - and I assume this to be the original source ...
>
> Would this call do the job: http://man7.org/linux/man-pages/man3/daemon.3.html?
Yes, I think so.
Here's a uClibc code for daemon()
https://github.com/hwoarang/uClibc/blob/master-metag/libc/unistd/daemon.c
As we do not need any 'specialties' for slcand (e.g. file i/o, logging, etc)
this could shorten the slcand a lot.
There are also some examples out there that could be adopted without getting
into a licensing issue again:
https://www.google.de/#q=linux+daemon+unistd
Regards,
Oliver
next prev parent reply other threads:[~2014-01-12 18:22 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 19:05 license issues of can-utils Uwe Kleine-König
2013-08-17 20:24 ` Marc Kleine-Budde
2013-08-18 10:26 ` Oliver Hartkopp
2014-01-11 23:10 ` [PATCH can-utils 0/3] License cleanup Uwe Kleine-König
2014-01-11 23:10 ` [PATCH can-utils 1/3] Update license information for some header files Uwe Kleine-König
2014-01-12 10:09 ` Oliver Hartkopp
2014-01-12 19:02 ` [PATCH] can: add explicit copyrights to can userspace header Uwe Kleine-König
2014-01-12 19:27 ` Oliver Hartkopp
2014-01-16 16:27 ` Marc Kleine-Budde
2014-01-12 19:53 ` [PATCH can-utils 1/3] Update license information for some header files Uwe Kleine-König
2014-01-11 23:10 ` [PATCH can-utils 2/3] ioctl.h: drop unused header Uwe Kleine-König
2014-01-12 10:18 ` Oliver Hartkopp
2014-01-11 23:10 ` [PATCH can-utils 3/3] slcand: remove program as it is undistributable Uwe Kleine-König
2014-01-11 23:38 ` Yegor Yefremov
2014-01-12 10:57 ` Oliver Hartkopp
2014-01-12 16:09 ` Yegor Yefremov
2014-01-12 18:22 ` Oliver Hartkopp [this message]
2014-01-12 19:54 ` Yegor Yefremov
2014-01-12 19:59 ` Oliver Hartkopp
2014-01-12 21:24 ` [PATCH can-utils v2 0/3] License cleanup Uwe Kleine-König
2014-01-12 21:24 ` [PATCH can-utils v2 1/3] headers: use include/linux only for Linux kernel headers Uwe Kleine-König
2014-01-13 6:23 ` Oliver Hartkopp
2014-01-13 7:20 ` Uwe Kleine-König
2014-01-13 18:25 ` Oliver Hartkopp
2014-01-13 20:45 ` Uwe Kleine-König
2014-01-13 21:18 ` Oliver Hartkopp
2014-01-13 21:26 ` Uwe Kleine-König
2014-01-13 21:31 ` Oliver Hartkopp
2014-01-13 21:37 ` Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 0/4] License cleanup Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 1/4] Remove two unused header files Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 2/4] Move includes copied from the Linux kernel into include/linux Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 3/4] ioctl.h: drop unused header Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 4/4] isotp.h: add explicit license information Uwe Kleine-König
2014-01-14 7:01 ` Oliver Hartkopp
2014-01-14 8:46 ` Uwe Kleine-König
2014-01-14 15:49 ` Oliver Hartkopp
2014-01-16 19:18 ` Uwe Kleine-König
2014-01-16 22:05 ` Marc Kleine-Budde
2014-01-12 21:24 ` [PATCH can-utils v2 2/3] ioctl.h: drop unused header Uwe Kleine-König
2014-01-12 21:24 ` [PATCH can-utils v2 3/3] isotp.h: add explicit license information Uwe Kleine-König
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=52D2DD7B.2070003@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yegorslists@googlemail.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 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).