similar to: Samba clarification around GPL and VFS modules.

Release Announcements ===================== This is the first release candidate of Samba 4.14. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.14 will be the next version of the Samba suite. UPGRADING ========= New GPG key ----------- The GPG

Release Announcements ===================== This is the first release candidate of Samba 4.14. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.14 will be the next version of the Samba suite. UPGRADING ========= New GPG key ----------- The GPG

Release Announcements ===================== This is the fourth release candidate of Samba 4.14. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.14 will be the next version of the Samba suite. UPGRADING ========= New GPG key ----------- The GPG

Release Announcements ===================== This is the fourth release candidate of Samba 4.14. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.14 will be the next version of the Samba suite. UPGRADING ========= New GPG key ----------- The GPG

Release Announcements --------------------- This is the first stable release of the Samba 4.14 release series. Please read the release notes carefully before upgrading. New GPG key =========== The GPG release key for Samba releases changed from: pub dsa1024/6F33915B6568B7EA 2007-02-04 [SC] [expires: 2021-02-05] Key fingerprint = 52FB C0B8 6D95 4B08 4332 4CDC 6F33 915B 6568 B7EA uid

Release Announcements --------------------- This is the first stable release of the Samba 4.14 release series. Please read the release notes carefully before upgrading. New GPG key =========== The GPG release key for Samba releases changed from: pub dsa1024/6F33915B6568B7EA 2007-02-04 [SC] [expires: 2021-02-05] Key fingerprint = 52FB C0B8 6D95 4B08 4332 4CDC 6F33 915B 6568 B7EA uid

>From what I have been able to piece together from the archives of prior discussions on this topic, it appears that one cannot write a proprietary vfs module, correct? If that is true, how far does the non-proprietary nature need to extend? For instance, would it be allowed to write a vfs module which talks to Oracle to get the data which backs the filesystem rather than an actual filesystem?

For a project I am porting some of R's source code, and I want to get the license for my project correct, but the top level COPYING file for R's source states GPL v2, but when using: > license() (which also states GPL version 2) points me towards: > RShowDoc('COPYING') which states GPL v3. Which is correct? Thanks for clarification (and the amazing amount of

Thanks for your replies. This is indeed a helpful mailing list. I made some more researches about the licensing issue and this is what I discovered: - from FSF it seems that packaging together a GPL application and a commercial one it is a corner case of licensing. Here is what they say: http://www.fsf.org/licensing/licenses/gpl-faq.html#MereAggregation

The virtio modules do not advertise themselves as GPL but rely on exported GPL symbols. This makes them unloadable as modules. This patch adds the appropriate MODULE_LICENSE(). Signed-off: Anthony Liguori <aliguori@us.ibm.com> diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index 54a8017..8f6040d 100644 --- a/drivers/block/virtio_blk.c +++

The virtio modules do not advertise themselves as GPL but rely on exported GPL symbols. This makes them unloadable as modules. This patch adds the appropriate MODULE_LICENSE(). Signed-off: Anthony Liguori <aliguori@us.ibm.com> diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index 54a8017..8f6040d 100644 --- a/drivers/block/virtio_blk.c +++

after creating a git clone I executed "bootstrap" and then entered "libguestfs/.gnulib/modules" and executed "grep -rn GPL * | grep ":GPL" | grep -v "build tool" > ~/GPLed" On Thu, Aug 22, 2013 at 11:05 AM, Richard W.M. Jones <rjones@redhat.com>wrote: > How did you construct this list? It appears to list modules which are > not

well, correct me if I'm wrong, but there is at least one module that is used and is GPL: xvasprintf On Thu, Aug 22, 2013 at 11:38 AM, Richard W.M. Jones <rjones@redhat.com>wrote: > On Thu, Aug 22, 2013 at 11:18:09AM +0300, Or Goshen wrote: > > after creating a git clone I executed "bootstrap" and then entered > > "libguestfs/.gnulib/modules" and

How did you construct this list? It appears to list modules which are not used by libguestfs directly or indirectly, eg (picked at random): > avltreehash-list:31:GPL > avltree-list:24:GPL > avltree-oset:21:GPL Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many

Subject: Non-GPL packages for R Packages that are not licensed in a way that permits re-distribution on CRAN are frequently a source of comment and concern on R-help and other lists. A good example of this problem is the Rdonlp2 package that has caused a lot of annoyance for a number of optimization users in R. They are also an issue for efforts like Dirk Eddelbuettel's cran2deb. There

On Thu, Aug 22, 2013 at 11:18:09AM +0300, Or Goshen wrote: > after creating a git clone I executed "bootstrap" and then entered > "libguestfs/.gnulib/modules" and executed "grep -rn GPL * | grep ":GPL" | > grep -v "build tool" > ~/GPLed" The .gnulib subdirectory is the gnulib submodule, so it contains a complete copy of the gnulib

On 2019/06/19, Ilia Mirkin wrote: > The bulk SPDX addition made all these files into GPL-2.0 licensed files. > However the remainder of the project is MIT-licensed, these files > (primarily header files) were simply missing the boiler plate and got > caught up in the global update. > > Fixes: b24413180f5 (License cleanup: add SPDX GPL-2.0 license identifier to files with no

Then you are in violation of section 3 of the GPL as printed at http://oss.snapappliance.com/license.html Samba is licensed under the GPL, and the version in SNAP is modified. I'd like the modifications. The modifications available at oss.snapappliance.com are old. -Tom > Hi Tom, > > I am terribly sorry but this is Confidential information that cannot be > distributed outside

Hello Tom, The update has been posted to http://oss.snapappliance.com We apologize for the delay in updating the source code page. Have a nice day -Sean -----Original Message----- From: Tom Dickson [mailto:bombcar@bombcar.com] Sent: Friday, July 23, 2004 7:20 AM To: Support, Snap Subject: Re: Can I get the GPL source for the Samba version used in the Gu ardian OS? Thank you very much!

Hi all, I'm wondering if the GPL-2.0 licensed mbedTLS (that's the version in OpenWrt) is 'compatible' with NUT binaries (not including the Python or Perl binaries which aren't used in OpenWrt) which is GPL 2.1+ AIUI. Because mbedTLS is the default library for OpenWrt and NSS is not yet in OpenWrt, and because OpenSSL is considered incompatible (I seem to recall reading that