From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Muhammad Ali <M.ALI023@hotmail.com>
Cc: "Kernelnewbies@kernelnewbies.org" <Kernelnewbies@kernelnewbies.org>
Subject: Re: UAPI syscall exception interpretation
Date: Fri, 13 May 2022 22:00:36 -0400 [thread overview]
Message-ID: <618473.1652493636@turing-police> (raw)
In-Reply-To: <DM6PR07MB60744EB138CC00DDE2E83C22D9C89@DM6PR07MB6074.namprd07.prod.outlook.com>
On Wed, 11 May 2022 21:19:42 -0000, Muhammad Ali said:
> Does the Linux-syscall-note say that a.out can ALL be under any license of
> your choice?
> Or do you have to note that your binary is under License X and also includes
> code which is under license GPL-2.0-WITH-Linux-syscall-note?
Not a lawyer, but... :)
For any program that's big and complex enough that you aren't embarrassed to
distribute it, the kernel isn't going to be your problem, because down in the
details, your code is probably not issuing syscall() itself, but is letting
glibc or musl or whatever the cool kids are using this week do the syscall.
So what you need to worry about is the license on glibc or whatever... and also
the license on any *other* libraries that you use (you're not going to write
your own JSON parser or other stuff like that, are you?).
In particular, understand the difference between GPL and LGPL licenses. There's
also a lot of other userspace licenses in play - as an example on my laptop, I have:
[~] for i in `rpm -qa`; do rpm -qi $i | grep ^License; done | sort | uniq -c > /tmp/licenses
[~] wc /tmp/licenses
304 2397 14912 /tmp/licenses
[~] more /tmp/licenses
3 License : (ASL 2.0 or MIT) and (BSD and MIT)
1 License : (Artistic 2.0 or ASL 2.0) and MIT
1 License : (Copyright only) and (Artistic or GPL+)
1 License : (Copyright only) and (GPL+ or Artistic)
2 License : (FTL or GPLv2+) and BSD and MIT and Public Domain and zlib with acknowledgement
1 License : (GPL+ or Artistic) and (GPLv2+ or Artistic) and MIT
1 License : (GPL+ or Artistic) and Artistic 2.0 and UCD
3 License : (GPL+ or Artistic) and BSD
1 License : (GPL+ or Artistic) and BSD and HSRL and MIT and UCD and Public domain
1 License : (GPL+ or Artistic) and CC0
1 License : (GPL+ or Artistic) and CC0 and Public Domain
1 License : (GPL+ or Artistic) and FSFAP
(and so on for another 300-ish lines..
And as Greg noted, if the answer actually matters, hire a lawyer who is experienced
in intellectual property law.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2022-05-14 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 21:19 UAPI syscall exception interpretation Muhammad Ali
2022-05-12 4:03 ` Greg KH
2022-05-12 23:21 ` Muhammad Ali
2022-05-13 5:36 ` Greg KH
2022-05-13 20:43 ` Muhammad Ali
2022-05-14 2:00 ` Valdis Klētnieks [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=618473.1652493636@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=M.ALI023@hotmail.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).