Re: libc license

2023-02-10 Thread Michael Cheponis
I believe the font size of the printed documentation is not specified... I liked what Perry Metzger said about BSD vs 'other' licenses: "Instead of worrying that people are going to steal my code, with BSD, I *know* they will!" On Fri, Feb 10, 2023 at 10:55 AM r0ller wrote: > Hi All, > >

Re: libc license

2023-02-10 Thread r0ller
Hi All, Thanks for the clarification! Best regards, r0ller PS: If only the libc could be redistributed with 0BSD license, it would have a big impact on the embedded use cases. On 2023. 02. 10. 16:07, Greg Troxel wrote: Julian Coleman writes: If you want to redistribute libc, you need to

Re: libc license

2023-02-10 Thread Greg Troxel
Julian Coleman writes: > If you want to redistribute libc, you need to provide some way to display > the licences for every libc source file as part of the documentation for > the embedded device. I think it is acceptable to ship the device with a paper license. There is no requirement that

Re: libc license

2023-02-10 Thread Julian Coleman
Hi all, > The license is more or less per file/system and thus if you include a > file you have to follow the license. > > A straightforward reading is that when you distribute a binary that you > must include in accompanying documentation a copy of the license. It > follows that distributing

Re: libc license

2023-02-10 Thread Greg Troxel
r0ller writes: > Hi All, > > I read on netbsd.org that netbsd uses the 2 clause BSD license where > the 2nd clause says: > > Redistributions in binary form must reproduce the above copyright > notice, this list of conditions and the following disclaimer in the > documentation and/or other

libc license

2023-02-10 Thread r0ller
Hi All, I read on netbsd.org that netbsd uses the 2 clause BSD license where the 2nd clause says: Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the