Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Feb 2019 17:19:41 -0500
From:      Shawn Webb <shawn.webb@hardenedbsd.org>
To:        rgrimes@freebsd.org
Cc:        "K. Macy" <kmacy@freebsd.org>, svn-src-head@freebsd.org, Matt Macy <mmacy@freebsd.org>, svn-src-all@freebsd.org, Brooks Davis <brooks@freebsd.org>, src-committers <src-committers@freebsd.org>
Subject:   Re: svn commit: r344487 - in head/sys: conf gnu/gcov
Message-ID:  <20190226221941.zt4y7t2455c5dwlb@mutt-hbsd>
In-Reply-To: <201902261627.x1QGRefq046574@pdx.rh.CN85.dnsmgr.net>
References:  <20190226154535.q32nwf6xyupexkta@mutt-hbsd> <201902261627.x1QGRefq046574@pdx.rh.CN85.dnsmgr.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--2e7hjzos5uhwlegf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 26, 2019 at 08:27:40AM -0800, Rodney W. Grimes wrote:
> > On Mon, Feb 25, 2019 at 06:18:42PM -0800, Rodney W. Grimes wrote:
> > > > > The modest increase in activation energy for that task seems wort=
h it
> > > > > for the short-term gains of reduced integration cost (this code w=
ill
> > > > > greatly improve our ZFS-on-Linux test coverage.)
> > > > >
> > > > > Rod rightly points out that we haven't accepted SPDX tags alone as
> > > > > license statements.  The standard GPL v2.0 boiler plate should be=
 added
> > > > > to this file along side the tag.
> > > >=20
> > > > I've copied the full copyright attribution that is in the
> > > > corresponding files on Linux. Is there some reason why FreeBSD
> > > > requires the files to be inflated with the full license text where =
the
> > > > original lacks it?
> > >=20
> > > I think for a few reasons, I doubt you copied the whole distribution
> > > that this file came from, as I am sure that distribution included
> > > a LICENSE file.  Second if you actually read the GPL v2 documentation
> > > and follow what it says it says you must do this, just because some
> > > one else does not follow the rules of what the GPL v2 says does not
> > > give us to knowingling not do it.  Third this is a particular dangeri=
ous
> > > area for BSD to be mixing a GPL code with its kernel, to my knowlege
> > > we have never had any gpl code in the kernel, no have we ever
> > > allowed it, but thats a seperate argument, that should be made.
> >=20
> > Would the arm64 DTS/DTB files count as "GPL code in the kernel?"
> >=20
> > I, too, would like less GPL in project, both in userland in kernel.
> > But, I can understand the desire for gcov. Note that I'm not
> > advocating either way that FreeBSD perform an action. ;)
>=20
> Didnt we just remove an inbase, compiling BSD licensed chunk of
> code called DRM and move it to ports.  So if that was possible
> this should be very rapidly applied here and this issue goes away.

DRM !=3D DTS/DTB

--=20
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

Tor-ified Signal:    +1 443-546-8752
Tor+XMPP+OTR:        lattera@is.a.hacker.sx
GPG Key ID:          0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE

--2e7hjzos5uhwlegf
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAlx1u3gACgkQaoRlj1JF
bu4V+g//SyK0wMt07RJ74BbZUqYJ918yTyPrMyslrErWWUJSKU4EdLKLL64JyWSZ
AplfxhJvi22oDguiGOg3aeEr+cpS2AugssfhATsxBD+6ub3Y6uFKm0btDz8M+20r
+YrvhKInaRsZDA64T3kGoxSAnaxGOrMFGYNwMPcONzBwvqbrmWbWtkLggDe72TmM
1t7mUQzspwgxFJUWzXpq3AbKnQ01oE2teoY8ziRREO49RC1Vn9cx5fIB5z2lO760
VaLbwdh+agUnqmHxUbImA8KwuQjXT1BK3O5Yr6fnCfI+RwGOyEKAJf/99a3WQkXp
F156sZ83ou8+jvgg6ibb0B+VC7i6y+E3Fkiu0nnJhu6iZloX1sC4ewx7YHNK52ft
zc7sctKsAmH8aRqqTUOUeLGXln2iaBOcSOD3AhxMouDkIkoOG+bHTVQ40XoRF4OU
Q97xmjpTygibMKdQQqnYJyGcxU8hXe7D0OXDmNRU0kJ3E4xte31V2e/5iE2PuMXm
H/O/jVo1ryeUaD8YLc0OgrxKva2Yz+e2vMX5WnUAY+2ES7VYYeOkXE0lE6SGAEAU
3IMOKUNmbunzHHQyVbEGmJka8y5kRayGoYwWI96UPKVTrnHWb42Q8h0HU7s3buPo
WtJ5+OoGYZ1AIVCY+GFQR17A840FETSfEI37Bp5lxC6ywo+fGcM=
=InE5
-----END PGP SIGNATURE-----

--2e7hjzos5uhwlegf--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190226221941.zt4y7t2455c5dwlb>