Podcasts about Copyleft

Play Episode Listen Later Jun 24, 2021 59:59

copyleft netlabels

[nws498] netwaves 15.04: slowly upwards and downwards

upwards copyleft netlabels

Play Episode Listen Later Jun 17, 2021 59:59

[nws497] netwaves 15.03: and the beat goes on

Play Episode Listen Later Jun 10, 2021 59:59

copyleft netlabels

[nws.bpm0102] Lockdown Edition #43 - the one before we go live

lockdown go live copyleft netlabels

Play Episode Listen Later Jun 3, 2021 66:27

[nws.bpm0101] Lockdown Edition #42 - Herk-Mombeek

lockdown herk copyleft netlabels

Play Episode Listen Later May 27, 2021 64:13

Episode 78: Stormy Peters: Sustaining FLOSS at Microsoft's Open Source Programs Office

Sustain

Play Episode Listen Later May 21, 2021 34:19

Guest Stormy Peters Panelists Eric Berry | Justin Dorfman | Richard Littauer Show Notes Hello and welcome to Sustain! Our amazing guest today is Stormy Peters, Director of the Open Source Programs Office at Microsoft and long-time advocate of free and open source software. Stormy tells us how she started her journey into open source and how she got involved with the OSPO at Microsoft. We find out about the impact of Duane O’Brien’s FOSS Fund, what Stormy is doing at Microsoft to help other nonfinancial ways of supporting communities and building great open source ecosystems of communities, and about how they support Outreachy. Also, Stormy fills us in on where she thinks open source is going in the future, her team’s goals, and their focus on cultural change. Download this episode now to find out much more! [00:01:16] We find out how Stormy got into open source. [00:02:40] Stormy tells us how she got involved with the Open Source Program Office at Microsoft, if she ever found herself defending open source more so than today, and if she ever thought Microsoft would be in a position they are now of how much they’ve given back to open source. [00:04:14] Richard is curious how Stormy feels about sustain, how the process has been like for her, how has it been to see the change from just being a licensing issue to being a culture, and if she thinks most people are paid for open source. [00:08:45] Eric wonders what the overall mentality was for Stormy when she got to Microsoft regarding supporting open source and if it’s changed since she’s been there. [00:12:17] Eric asks Stormy if in five years our whole development environment is on Microsoft platform if we’re going to get locked in and is that going to cause the same type of negative frustration as he is with Apple right now. [00:13:40] Richard wonders if tools are owned by Microsoft how will that affect his development and how will affect the open source ecosystem if very large corporations become the main stakeholders in open source and direct the projects in their own ways, and Stormy replies and also explains how the people get paid. [00:16:10] Justin wonders how much impact Duane O’Brien’s program FOSS Fund has made in the way they operate and the rest of the bigger OSPO’s out there. We also learn what she’s doing at Microsoft to help other nonfinancial ways of supporting communities and building great open source ecosystems of communities. [00:18:53] Stormy fills us in on who makes up their team of employees at OSPO Microsoft and where you can go to see what they are doing. [00:20:12] Richard is curious where Stormy sees the role for OSPO’s for universities, governments, cities, and anything that’s not a large corporation. She also tells us about how they support Outreachy. [00:23:08] We learn from Stormy where she thinks open source is going in the future and why she thinks a Copyleft is dropped out of the parlance. [00:25:49] Stormy tells us how she sees Ethical Source progressing and if she sees it being a major player with people or as being a movement that will cause the same tensions that GPL used to cause. [00:27:24] Richard wonders if Microsoft has a mapping of what resources they have used of what code is in their system, what open source packages they depend on, and how they are actively working towards giving back to them as a whole down the stack. [00:29:12] Eric asks Stormy what is on the forefront of her team’s mind right now, and she fills us in on her team’s goals. [00:29:56] Find out where you can follow Stormy on the internet. Quotes [00:01:53] “And this was just about the time that Linux was getting popular and they had not one, but two desktops that were popular, GNOME and KDE, and I thought surely we can collaborate on this like they do.” [00:03:42] “I’d like to joke now that I think Microsoft’s first contribution to open source was being the common enemy.” [00:04:54] “I think it’s still evolving, and I think it always will evolve and so I think it’s important that all of us continue to think about it and figure out what the new models look like.” [00:05:32] “I think a much larger majority than before get paid to work on open source.” [00:06:33] “So, I know when I was at Mozilla we consciously thought about this with Firefox OS, having people full-time on it and even more than full-time, as they worked extra hours to try to get out the door, could you still welcome people that only had two or three hours a week to work on it.” [00:08:56] “So to go back to the question about my career that it looked like it changed with this last move, I don’t think it did. To me, this was the next step in the path.” [00:09:27] “Microsoft, I think, is ideally positioned to make the next big change in open source software.” [00:12:33] “So it’s my job, extended team’s job, to make sure that Microsoft does open source well, and part of us being successful in open source is making sure we have active communities around our projects that are broader than us so that the projects are broader than us that we’re not creating that lock-in.” [00:14:51] “Microsoft uses a program called FOSS Fund that Duane O’Brien at INDEED started, where we let employees pick a project every month to give them $10,000, and the idea’s that’s not going to be enough money to support them forever but we just want to recognize some of the projects that we’re using that aren’t getting a lot of funding in other ways.” [00:15:54] “Those companies started doing contract work for an open source software project and now they work on open source software projects and other projects in general.” [00:16:34] “I think Duane’s a good thinker, like when COVID started, he started an effort to raise money for the events that were impacted, so I hope that’s empowering to a lot of people that one person can have a good idea that is a need and get people involved.” [00:17:44] “So, we’re unofficially giving Azure Credits to a number of open source software projects. I’m trying to launch an official program by which people can apply to get Azure Credits whether it’s just do their builds or whether it’s to make sure that stuff runs on Azure.” [00:18:05] “We have a lot of Microsoft employees who work on projects on GitHub. I think it’s definitely over 30,000 Microsoft employees have linked their Microsoft identity to their GitHub identity.” [00:23:13] “I think if you’d asked me that like twenty years ago, I would not have realized that Copyleft would drop out of importance as much as it has.” [00:23:36] “I don’t know if I would make an accurate prediction, but I hope it’s to continue to make, not only to make more software available to more people, but to make it more possible for people that aren’t in tech careers to write code and make computers do what they need them to do.” [00:24:20] “I think it’s cause the fear has dropped out. In the beginning it was fear that I was going to have to open source something I didn’t want to and fear that somebody was going to take my stuff and take advantage of my stuff.” [00:29:17] “Our goal is to make sure that Microsoft business units can use open source software in their strategy, that they can consume open source, that they can open source things, and that they have all the tools and knowledge they need to do that.” Spotlight [00:30:41] Eric’s spotlight is Kombucha (KeVita). [00:31:29] Justin’s spotlight is Jekyll Admin. [00:32:04] Richard’s spotlight is Carl Boettiger. [00:33:04] Stormy’s spotlight is Educational Software Projects like Khan Academy and Internet-in-a-Box. Links Stormy Peters Twitter (https://twitter.com/storming) Stormy Peters Linkedin (https://www.linkedin.com/in/stormy/) Microsoft Open Source (https://opensource.microsoft.com/) Microsoft Open Source Blog (https://cloudblogs.microsoft.com/opensource/) FOSS Contributor Fund- Duane O’Brien blog post (https://engineering.indeedblog.com/blog/2019/07/foss-fund-six-months-in/) What is copyleft? By Ben Cotton (https://opensource.com/resources/what-is-copyleft) Outreachy (https://www.outreachy.org/) KeVita Kombucha (https://www.kevita.com/) Open Collective (https://opencollective.com/) Carl Boettiger (https://ourenvironment.berkeley.edu/people/carl-boettiger) Internet-in-a-Box (http://internet-in-a-box.org/) Khan Academy (https://www.khanacademy.org/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Stormy Peters.

[nws.bpm0100] Lockdown Edition #41 - past year some DJ's saved my life

lockdown saved my life copyleft netlabels

Play Episode Listen Later May 20, 2021 63:37

C'mmons baby! #090 (grande finale)

C'mmons baby!

Play Episode Listen Later May 15, 2021

Benvidas e benvidos á última emisión de C'mmons baby! Antes de nada clarexar que isto é unha conclusión, non un regreso. Quero tamén desculparme por tardar cinco anos en gravar iso -a vida non deixa vivir ás veces- e desculpas tamén polo son estraño, por momentos, da miña voz, mais non sei que pasaba co micrófono que facía cousas raras. Debe ser que xa non lembraba traballar... Con todo, desta vez, os protagonistas sodes vós, os que estivestes aí do outro lado durante oito fabulosos anos. Grazas! (duración: 1h 18' 09'') baixar .mp3 / baixar .ogg Pararrayos. Inusual (EP Rombos o Diamantes 2019, CC-BY-NC-ND) The Dots. C'mon babe (EP Fashion For The Dressed And Naked 2007, CC-BY-NC-ND) Grampoder. A longa marcha (LP Golf Whiskey 2013, CC-BY-NC-SA) tdBt & the Garys. Feel like... (LP À la poursuite de René Fonck 2007, CC-BY-SA) Juana Chicharro. Dejad de chutaros (LP Juana Chicharro 2011, CC-BY-NC-SA) Dadalú. Brilla* (LP Periodo, Ponk Records 2011, CC-BY-NC-ND) El Diluvi. Als bons amics per peteneres (LP Motius 2014, CC-BY-NC-SA) Ataque Escampe. Vista Alegre Social Club (vol. 2) (LP Noites de agosto con Ataque Escampe 2012, CC-BY-NC-SA) Happy Elf. Come back (Mini LP Sexmachine, WM Recordings 2009, CC-BY-NC-SA) Megaloves. Perfil perfecto (Single Perfil perfecto 2009) The Easton Ellises. Liquorstore (EP ONE, Enough Records 2011, CC-BY-NC-ND) Winston. Tombeau du tréponème pâle (LP Passe-temps 2014, CC-BY-NC) Oláfachada. There Is Another Sky (Single ePop012, EardrumsPop 2010, CC-BY-NC-ND) The Wind Whistles. The Sun (LP Animal are people too, Aaahh! Records 2009, CC-BY-NC-ND) Bonus track Lizard Kisses. Close (Single Close 2012, CC-BY-SA) Até sempre! Abraços e beijinhos e carinhos sem ter fim...

music babies rock single pop sun als animal records antes indie punk folk electronic lp musica debe passe quero dots perfil cc by sa periodo brilla diamantes free music noites cc by nc garys cc by nc sa grande finale dejad sex machine inusual tombeau copyleft netlabels grazas easton ellises netaudio ataque escampe

[nws.bpm099] Lockdown Edition #40 - language is never innocent

language lockdown innocent copyleft netlabels

Play Episode Listen Later May 13, 2021 60:02

[nws.bpm098] Lockdown Edition #39 - hop met de beentjes!

Play Episode Listen Later May 6, 2021 72:06

lockdown copyleft netlabels mb3

[nws.bpm097] Lockdown Edition #38 - weitermachen

lockdown weitermachen copyleft netlabels

Play Episode Listen Later Apr 29, 2021 62:40

[nws.bpm096] Lockdown Edition #37 - Afterbosch

Chronic Table with the Portland Cannabis Tasting Society

Play Episode Listen Later Apr 22, 2021 68:26

lockdown copyleft netlabels mb3

HPR3317: Reading a manifesto: Towards A Cooperative Technology Movement

Hacker Public Radio

Play Episode Listen Later Apr 20, 2021

Three good decades ago, Richard Stallman founded the free software movement and gave it a name. Two good decades ago there was a fork and Eric S. Raymond, Bruce Perens and others founded the open source software movement, and neglected to tell us who gave it a name. (it was Christine Peterson[0]) Ever since then, the free software side of the two movements has been careful to guard the boundary between the two, see Richard Stallman's essay "Open Source Misses the Point".[1] But lately a lot of people have increasingly been feeling that free software misses the point. Ironically a lot of this has been coming from the open source side of things, as the official free software philosophy has been firmly anchored with Stallman, and he hasn't been interested in moving his philosophy in more inclusive directions. For sure, there are a lot of people in free software who have been wanting to go in this direction as well. I've been thinking of it as a "free software plus", as it builds on the free software philosophy, but adds aspects of social responsibility. The fact that Stallman was forced to resign from being Free Software Foundation president two years ago was a sign that people inside free software cared about more than just the code and what freedoms it gives the recipient. A month ago, if you are listening to this on April the 20th 2021, a manifesto was published called "Towards A Communal Software Movement", and I'll get to that in a minute. I mentioned the names of the drivers of the previous movements, but this author has said "I intentionally left authors' names out of it"[2], and I think that makes sense. Part of the problems with previous movements has been this Great Man of History fallacy, which may have kept them focused and on track, but it has also held them back. The movement is young and has already changed names once as I was writing about it. The manifesto is now "Towards A Cooperative Technology Movement", and I have updated the shownotes and my commentary to reflect that. https://misskey.de/notes/8k0igd5tcd I see the difference between free software and cooperative technology similarly as the difference between open source and free software. There are certainly people within open source and on the Open Source Initiative board that look further than just the license, and treat open source like just another brand name for free software. But at its core, the Open Source Definition is all about the licensing and that document is the shared common ground for all open source. People write code for different reasons and there's a license and contribution model that allow them to come together without those differences of purpose getting too much in the way. So if the software and the license is "what" we're building, the philosophical documents of free software provide the guidance on "why" we are building it: We want to get away from proprietary software, we want to control our own computing, we want the freedoms to use, learn, modify and share, etc. Free software is about our freedoms. So just like "free" is right there in the name, maybe the "community" in "communal software" or the "cooperative" in "cooperative technology" is all about the "who": Who gets the freedom, who has the influence, who is affected. And again, lots of people in free software do care about community principles beyond code, care about social responsibility, but the shared baseline is the care for formal, technical and individual user freedom: If you receive the code, you are allowed the technical rights to update the code, the code or license should not restrict your freedoms, you, the recipient of the software, the hacker, the code contributor. It says nothing about practical user freedom and it says nothing about the community beyond the immediate user. That was my commentary. Now let's read the manifesto. https://cooperativetechnology.codeberg.page/ Before I saw the manifesto, I had written a draft list of aspects beyond licensing and contribution that determine the social good of your project: https://libranet.de/display/0b6b25a8-3060-61f6-28df-cae554943983 The conversations that led directly to the creation of the manifesto: https://social.polymerwitch.com/@polymerwitch/105934078911643041 https://fosstodon.org/@be/105952735879246194 [0] https://opensource.com/article/18/2/coining-term-open-source-software [1] https://www.gnu.org/philosophy/open-source-misses-the-point.en.html [2] https://fosstodon.org/@be/105952960559032774 Towards A Cooperative Technology Movement In response to the surprise, undemocratic reinstatement of Richard Stallman to the board of directors of the Free Software Foundation after his resignation in September 2019, the Free and Open Source Software movement is in the midst of a reckoning. The authors of this document recognize and honor the contributions Richard Stallman has made to this movement while unequivocally condemning his harmful behavior which has pushed many capable, dedicated people away from the movement. Regardless of what happens in the Free Software Foundation, we believe it is time to reflect on the shortcomings of our advocacy so we can grow into a more effective and inclusive movement for justice. Towards this end, we believe the movement will benefit from new terminology to describe what we do and what we aim for. Richard Stallman authored the free software definition in 1986. This term has always created difficulties communicating the ideas behind it because of the different meanings of the word "free" in English. Moreover, it is not the freedom of machines we are concerned with, but the freedom of humans. In response to this and other issues, in 1998, the term open source was promoted using an adapted version of the Debian Free Software Guidelines. The history of computing in the past 23 years have validated critiques that the term "open source" is insufficient for communicating the values behind it. The term "open source" and the ecosystem of Free and Open Source Software (FOSS) is today used by powerful companies, governments, and other institutions to harm people on enormous scales through surveillance and violence. These institutions use FOSS to minimize economic costs by benefitting from decades of work done by others, much of which was done by unpaid volunteers motivated by curiosity, passion, and the ideals of the FOSS movement. We believe a significant reason for the failures of both "free software" and "open source" to prevent this cooptation is that the men who coined and initially promoted these terms did not and do not critique capitalism. Richard Stallman has generally dodged the question of whether free software is opposed to capitalism. In the historical context of the United States in the 1980s, that may have been a wise decision. But that was then, and now it is 2021. The promoters of "open source" emphasize its compatibility with capitalism and go out of their way to distance "open source" from critiques of capitalism. We believe we need to build on the FOSS movement with an explicitly anticapitalist political movement which proactively collaborates with other movements for justice. We propose the term "cooperative technology" for this movement. By "cooperative technology", we mean technology that is constructed by and for the people whose lives are affected by its use. While this builds on the Free and Open Source Software movement, we aim to apply the same principles to hardware as well, although the criteria by which we evaluate hardware and software will of course not be identical. It is not sufficient to narrowly focus on the people who directly interact with computers. Cooperative software which is run on a server should not be controlled solely by the administrator of the server, but also by the people who interact with the server over a network. Similarly, the data generated by the technology and the data which it requires to function should be in the control of the people who are affected by the technology. Cooperative software that uses cameras should not be controlled solely by the people who own the cameras, but also the people who are observed by the cameras. Cooperative electronic medical record systems should not be designed for the interests of insurance companies or hospital administrators, but for the interests of patients and the clinicians who directly use it. We aim for a world in which all technology is cooperative technology and recognize that any amount of proprietary technology is in conflict with this goal. As an anticapitalist movement, we recognize that any institution which motivates people to put money, power, or self-interest above the welfare of humans is in conflict with our goals. Corporations are beholden to their shareholders who can hold the corporation legally liable for spending money in a way that is not intended to further enrich the shareholders. Other capitalist forms of enterprise have similar problems, incentivizing the profit of an elite few over the impact their activities have on others. We are not opposed to exchanges of money being involved in the creation or distribution of software or hardware. However, we should carefully consider the motivational structures of the institutions which fund technology development. Who benefits from the technology and who determines the priorities of its development and design? These are questions we ask about technology whether money is involved or not. It is in our interest to use safeguards to ensure that technology always remains controlled by the community which develops and uses it. Copyleft is one such safeguard, but it is insufficient on its own to prevent cooptation of our movement. Any cooperative technology project that receives funding from a for-profit enterprise must institute governance structures which prioritize community interests over profit in case there is a conflict between the two. We oppose business models which are in conflict with community interests such as "open core"/proprietary relicensing. Similarly, we are opposed to authoritarian and hierarchical governance structures of technology projects such as "benevolent dictators for life". Cooperative technology is developed democratically; no single individual should have ultimate authority in cooperative projects. While we recognize the need for leadership and private communication, discussions regarding cooperative technology should take place in public unless there is a specific reason for communications to be private. Organizations which advocate for cooperative technology should likewise operate democratically and transparently. We recognize that creating high quality technology requires much more than engineering skills. Cooperative technology is not only for people who have the skills of writing code (unless the software is for writing code such as a compiler) nor the skills to design hardware. Cooperative technology strives to be easy to use, including for people with disabilities, and acknowledges that this is best accomplished by continual dialog between engineers and users. Providing such feedback is a valuable way to contribute to the construction of cooperative technology without needing engineering skills. Ideally, the engineers of the technology should also be using it themselves. Moreover, there are many ways to contribute to cooperative technology without programming skills such as imagining ideas for new features, reporting bugs, writing documentation, graphic design, translation, promotion, and financial support. The free software movement has failed to create a world in which humans in technological societies can live without using proprietary software unless one chooses to live the ascetic lifestyle of Richard Stallman. Expecting people to not use any proprietary technology and judging people for not meeting this standard pushes people away from our movement. People who are coerced into using proprietary technology deserve our empathy and invitation into our movement, not condescension. Let us criticize institutions which pressure people into using proprietary technology, not the people who choose to use it. To that end, we strive to use cooperative technology tools as much as possible in our efforts to build cooperative technology. The purpose of this document is not to proclaim a legalistic set of criteria for determining what technology is cooperative and what technology is not. History has demonstrated that this is not an effective political tactic for the reasons explained above. The free software definition and the open source definition are useful criteria for evaluating copyright licenses for code, but an effective political movement cannot be so narrowly focused on legalistic and binary judgements of copyright licenses to judge whether certain technology aligns with our goals. We believe the focus of the cooperative technology movement should be on the practical impacts that the use of technology has on humans and the universe we inhabit. The scope of this extends beyond humans and must consider the environment around us. Moreover, we believe it is counterproductive to have a small self-appointed group of privileged men determine what our movement's terminology, goals, and tactics are. We encourage anyone interested in building a better world through technology to engage in discussions with your own communities about what you want "cooperative technology" to mean. While we agree with the Ethical Software Movement that we must resist when our efforts are coopted for unjust purposes, we reject putting restrictions on the ways people may use software through copyright licenses as a wise tactic for achieving our goals. The history of the Free and Open Source Software movement has shown that the proliferation of incompatible copyright licenses which prohibit software from being legally combined creates more obstacles than opportunities for our movement. Any new copyright licenses for use with cooperative software must be written with this consideration in mind to intentionally avoid fracturing the software ecosystem. Adopting incompatible copyright licenses for different software would make it easy for our adversaries to divide and suppress the movement. Language is constructed collectively and is always evolving. It is counterproductive to our movement to refuse to collaborate with people because they use the words "open source" or "free software" to describe their work. They may even disagree with the entire premise of this document. That does not mean we should not work together towards shared goals, but we should be conscious that our goals may not perfectly align and this may cause tension in our communities from time to time. We invite anyone to collaborate with us who is interested in building a better world and treats us and others in our communities with dignity and respect. This document is licensed under the CC0 license. Contributions are welcome on Codeberg. If you disagree with parts of this, feel free to fork it and say what you want to say.

CopyLeft Cultivars First Grassroots Interest Meeting

Play Episode Listen Later Apr 20, 2021 165:01

We had our friend Solshine Growing stop by to give his first public presentation for CopyLeft Cultivars, many of our good friends stopped by like Clackamas Coot, Wesingine, Potent Ponics and many others. Have a listen my friends! Copyleft Cultivars First Grassroots Interest Meeting Copyleft Cultivars is a to-be-formed nonprofit which will preserve and protect plant (especially Cannabis) genetics, breeders, and cultivators, with Copyleft Creative Commons. @copyleftcannabis This is an opportunity to learn about the concept of Copyleft protecting Cannabis, share your perspective, provide feedback, and get involved before we form the organization! Hope to see you tonight and in the future!

cannabis grassroots cultivars copyleft

0x6A: Live Show from SeaGL 2019

Play Episode Listen Later Mar 31, 2020 81:02

The first live podcast of Free as in Freedom, hosted at SeaGL 2019 in November 2019. Hear questions from the studio audience and answers from Bradley and Karen. Show Notes: Segment 0 (00:38) Producer Dan speaks on mic to introduce that this is a live show. Segment 1 (01:17) This is a live show from SeaGL 2019, a community-organized FaiP (02:15) Carol Smith from Microsoft asked about being a charity in the USA under recent tax changes regarding tax deduction and, and asked about Conservancy's annual fundraiser which had completed by the time this show was released. (04:53) Deb took a photo during the show (07:30) A questioner asked about the so-called “ethical but-non-FOSS licenses”. Bradley gave an answer that is supplemented well by this blog post (10:15) and Karen mentioned at CopyleftConf 2020 there was a discussion about this. (15:15) The follow up question was also related to these topics (15:44). Eric Hopper asked about how Conservancy decides when a project joins, and what factors Conservancy considers in projects joining (18:14) A written questioner asked how to handle schools requiring proprietary software as part of their coursework. (22:00) Michael Dexter asked about Karen's teaching at Columbia Law School. (27:25) A written questioner asked about copyleft-next's sunset clause. (29:22) Karen mentioned “Copyleft, All wrongs reversed” as it appeared on n June 1976 on Tiny BASIC, which inspired the term copyleft to mean what it does today. (30:45) Karen spoke about the issues of copyright and trademark regarding Disney, that is supplemented by this blog post. (32:52) Carol Smith asked what Karen and Bradley thought were Conservancy's and/or FOSS' biggest achievements in the last decade. (35:20) Karen mentioned Outreachy was a major success. (37:08) A questioner asked about using the CASE Act to help in GPL enforcement. Bradley discussed how it might ultimately introduce problems similar to arbitration clauses. (41:42) Since the podcast was recorded, the CASE Act has also passed the Senate, but does not seem to have been signed by the President. (47:30) Bradley noted that Mako Hill has pointed out that FOSS has not been involved in lobbying enough. (48:10) A questioner in the audience asked about the Mozilla Corporation structure would allow Mozilla to do lobbying for FOSS. (50:57) Karen explained the Mozilla corporate legal structure (51:35). A questioner in the audience asked about Mako Hill's keynote and how individuals can help further the cause of software freedom. (54:53) Michael Dexter asked if software patents are still as much of a threat as they once were. (1:01:30) Carol asked about the supreme court hearing the Oracle v. Google case (1:09:04) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

united states president google disney freedom law sound microsoft price legal senate oracle live show open source linux drafts arbitration mozilla foss cc by sa irc columbia law school conservancy bsd gpl producer dan dan lynch copyleft ogg vorbis carol smith outreachy lgpl software freedom michael dexter mike tarantino

0x64: Our Producer Dan Lynch Interviewed at Copyleft Conf 2019

Play Episode Listen Later Mar 27, 2019 36:00

Bradley and Karen interview their own producer, Dan Lynch, on site at Copyleft Conf 2019. Show Notes: Segment 0 (00:46) Karen now teaches teaches a course at Columbia University. (03:40) In addition to being the producer of Free as in Freedom, Dan Lynch was the host of Rat Hole Radio, the co-host of Linux Outlaws, and currently co-hosts Hollywood Outlaws. (04:30) Segment 1 (5:19) Dan helps co-organize Oggcamp which is having its tenth-anniversary event on Saturday 19 October 2019. (08:00) Bradley mentioned the phrase from IT Crowd quote: Did you see that ludicrous display last night? (11:08) Dan talked about The Manchester Ship Canal. (13:16) Dan promoted Hollywood Outlaws where he and his co-host Fab talk about Bosch. (23:18) Dan promoted his own podcast about comics called Tales of the Unattested. (23:27) Dan Lynch has a personal website, which has his blog. (23:55) Bradley referenced the phrase You are no Jack Kennedy which was stated by Bentsen on Wednesday 5 October 1988 during the VP debate between Quayle and Bentsen for the 1988 USA Presidential campaign. Details and background of this are explained by NBC in this story. (26:30) Segment 2 (28:23) Bradley and Karen briefly dissect the interview with Dan. Segment 3 (32:22) Karen and Bradley mention that they'll discuss the Linux Foundation initiative, “Community Bridge” in the next episode. If you want a preview Bradley and Karen's thoughts, you can read their blog post about Linux Foundation's “Community Bridge” initiative. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

interview freedom law sound tales legal nbc columbia university senators conf open source linux bosch fab cc by sa irc conservancy it crowd linux foundation gpl bsd quayle jack kennedy producer dan dan lynch copyleft ogg vorbis bentsen usa presidential oggcamp software freedom lgpl manchester ship canal linux outlaws mike tarantino

232: FOSDEM 2018

Play Episode Listen Later Feb 7, 2018 95:06

We talk about our recent trip to FOSDEM, we discuss the pros and cons of permissive licensing, cover the installation of OpenBSD on a dedibox with full-disk encryption, the new Lumina guide repository, and we explain ZFS vs. OpenZFS. This episode was brought to you by Headlines [FOSDEM Trip report] Your BSDNow hosts were both at FOSDEM in Brussels, Belgium over the weekend. On the friday before FOSDEM, we held a FreeBSD devsummit (3rd consecutive year), sponsored by the FreeBSD Foundation and organized by Benedict (with the help from Kristof Provost, who did it in previous years but could not make it this year). We had 21 people attend, a good mixture of FreeBSD committers (mostly ports) and guests. After introductions, we collected topics and discussed various topics, including a new plan for a future FreeBSD release roadmap (more frequent releases, so that features from HEAD can be tried out earlier in RELEASES). The devsummit concluded with a nice dinner in a nearby restaurant. On Saturday, first day of FOSDEM, we set up the FreeBSD Foundation table with flyers, stickers, FreeBSD Journal print editions, and a small RPI 3 demo system that Deb Goodkin brought. Our table was located next to the Illumos table like last year. This allowed us to continue the good relationship that we have with the Illumos people and Allan helped a little bit getting bhyve to run on Illumos with UEFI. Meanwhile, our table was visited by a lot of people who would ask questions about FreeBSD, take info material, or talk about their use cases. We were busy refilling the table throughout the day and luckily, we had many helpers at the table. Some items we had ran out in the early afternoon, an indicator of how popular they were. Saturday also featured a BSD devroom (https://twitter.com/fosdembsd), organized by Rodrigo Osorio. You can find the list of talks and the recordings on the BSD Devroom schedule (https://fosdem.org/2018/schedule/track/bsd/). The room was very crowded and popular. Deb Goodkin gave the opening talk with an overview of what the Foundation is doing to change the world. Other speakers from various BSD projects presented their talks after that with a range of topics. Among them, Allan gave his talk about ZFS: Advanced Integration (https://fosdem.org/2018/schedule/event/zfs_advanced_integration/), while Benedict presented his Reflections on Teaching a Unix Class With FreeBSD (https://fosdem.org/2018/schedule/event/reflections_on_reaching_unix_class_with_freebsd/). Sunday was just as busy on the FreeBSD table as Saturday and we finally ran out of stickers and some other goodies. We were happy with the results of the two days. Some very interesting conversations at the table about FreeBSD took place, some of which we're going to follow up afterwards. Check out the FOSDEM schedule as many talk recordings are already available, and especially the ones from the BSD devroom if you could not attend the conference. We would like to thank everyone who attended the FreeBSD devsummit, who helped out at the FreeBSD table and organized the BSD devroom. Also, thanks to all the speakers, organizers, and helping hands making FOSDEM another success this year. *** NetBSD kernel wscons IOCTL vulnerable bug class (http://blog.infosectcbr.com.au/2018/01/netbsd-kernel-wscons-ioctl-vulnerable.html) I discovered this bug class during the InfoSect public code review session we ran looking specifically at the NetBSD kernel. I found a couple of these bugs and then after the session was complete, I went back and realised the same bug was scattered in other drivers. In total, 17 instances of this vulnerability and its variants were discovered. In all fairness, I came across this bug class during my kernel audits in 2002 and most instances were patched. It just seems there are more bugs now in NetBSD while OpenBSD and FreeBSD have practically eliminated them. See slide 41 in http://www.blackhat.com/presentations/bh-usa-03/bh-us-03-cesare.pdf (http://www.blackhat.com/presentations/bh-usa-03/bh-us-03-cesare.pdf) for exactly the same bug (class) 16 years ago. The format of the this blog post is as follows: Introduction Example of the Bug Class How to Fix How to Detect Automatically with Coccinelle More Bugs Conclusion These source files had bugs ./dev/tc/tfb.c ./dev/ic/bt485.c ./dev/pci/radeonfb.c ./dev/ic/sti.c ./dev/sbus/tcx.c ./dev/tc/mfb.c ./dev/tc/sfb.c ./dev/tc/stic.c ./dev/tc/cfb.c ./dev/tc/xcfb.c ./dev/tc/sfbplus.c ./arch/arm/allwinner/awin_debe.c ./arch/arm/iomd/vidcvideo.c ./arch/pmax/ibus/pm.c ./dev/ic/igfsb.c ./dev/ic/bt463.c ./arch/luna68k/dev/lunafb.c Reporting of the bugs was easy. In less than a week from reporting the specific instances of each bug, patches were committed into the mainline kernel. Thanks to Luke Mewburn from NetBSD for coming to the code review session at InfoSect and coordinating with the NetBSD security team. The patches to fix these issues are in NetBSD: https://mail-index.netbsd.org/source-changes/2018/01/24/msg091428.html (https://mail-index.netbsd.org/source-changes/2018/01/24/msg091428.html) "Permissive licensing is wrong!” – Is it? (https://eerielinux.wordpress.com/2017/11/25/permissive-licensing-is-wrong-is-it-1-2/) A few weeks ago I've been attacked by some GNU zealots on a German tech site after speaking in favor of permissive licenses. Unfortunately a discussion was not possible there because that would require the will to actually communicate instead of simply accusing the other side of vile motives. Since I actually do care about this topic and a reader asked for a post about it in comments a while ago, here we go. This first part tries to sum up the most important things around the topic. I deliberately aim for an objective overview that tries not to be one-sided. The second part will then contain my points in defence of permissive licensing. Why license software at all? Licenses exist for reasons of protection. If you're the author/inventor of some software, a story or whatever product, you get to decide what to do with it. You can keep it for yourself or you can give it away. If you decide for the latter, you have to decide who may use it and in which way(s). In case you intend to give it to a (potentially) large group of people, you may not want to be asked for permission to xyz by everybody. That's when you decide to write a license which states what you are allowing and explicitly disallowing. Most of the well-known commercial licenses focus on what you're not allowed to do (usually things like copying, disassembling, etc.). Open source licenses on the other hand are meant to grant the user rights (e.g. the right to distribute) while reserving some rights or only giving permission under certain conditions – and they usually make you claim responsibility for using the software. For these reasons licenses can actually be a good thing! If you got an unlicensed piece of code, you're not legally allowed to do anything with it without getting the author's permission first. And even if you got that permission, your project would be risky, since the author can withdraw it later. A proper license protects both parties. The author doesn't get his mail account full of email asking for permission, he's save from legal trouble if his code breaks anything for you and at the same time you have legal certainty when you decide to put the code to long-term use. Permissive vs. Copyleft (in a nutshell) In short terms, permissive licensing usually goes like this: “Here you are, have fun. Oh, and don't sue me if it does something else than what you expect!” Yes, it's that easy and there's little to dispute over. Copyleft on the other side sounds like this (if you ask somebody in favor of Copyleft): “Sure, you can use it, it's free. Just keep it free, ok?”. Also quite simple. And not too bad, eh? Other people however read the same thing like this: “Yes, you're free to use it. Just read these ten pages of legalese and be dead certain that you comply. If you got something wrong, we will absolutely make you regret it.” The GNU Public license (GPL) The most popular copyleft license in use is the GPL (in various versions) (https://www.gnu.org/licenses/gpl.html). It got more and more complex with each version – and to be fair, it had to, because it was necessary to react to new threats and loop holes that were found later. The GNU project states that they are committed to protect what they call the four freedoms of free software: the freedom to use the software for any purpose the freedom to change the software to suit your needs the freedom to share the software with your friends and neighbors the freedom to share the changes you make These are freedoms that every supporter of open source software should be able to agree with. So what's the deal with all the hostility and fighting between the two camps? Let's take a look at a permissive license, too. The BSD license Unlike the GPL, the BSD family of licenses begun with a rather simple license that span four rules (“original BSD license”). It was later revised and reduced to three (“modified BSD license”). And the modern BSD license that e.g. FreeBSD uses is even just two (“simplified BSD license”). Did you read the GPLv3 that I linked to above? If you are using GPL'd code you really should. In case you don't feel like reading all of it, at least take a look and grasp how long that text is. Now compare it to the complete modern BSD license (https://opensource.org/licenses/bsd-license.php). What's the problem? There are essentially two problems that cause all the trouble. The first one is the question of what should be subject to the freedom that we're talking about. And closely related, the second one is where that freedom needs to end. Ironically both camps claim that freedom is the one important thing and it must not be restricted. The GPL is meant to protect the freedom of the software and enforces the availability of the source code, hence limiting the freedom of actual persons. BSD on the other hand is meant to protect the freedom of human beings who should be able to use the software as they see fit – even if that means closing down former open source code! The GNU camp taunts permissive licenses as being “lax” for not providing the protection that they want. The other camp points out that the GPL is a complex monster and that it is virulent in nature: Since it's very strict in a lot of areas, it's incompatible with many other licenses. This makes it complicated to mix GPL and non-GPL code and in the cases where it's legally possible, the GPL's terms will take precedence and necessarily be in effect for the whole combined work. Who's right? That totally depends on what you want to achieve. There are pros and cons to both – and in fact we're only looking at the big picture here. There's also e.g. the Apache license which is often deemed as kind of middle ground. Then you may want to consider the difference between weak (e.g. LGPL) as well as strong copyleft (GPL). Licensing is a potentially huge topic. But let's keep it simple here because the exact details are actually not necessary to understand the essence of our topic. In the next post I'll present my stance on why permissive licensing is a good thing and copyleft is more problematic than many people may think. “Permissive licensing is wrong?” – No it's not! (https://eerielinux.wordpress.com/2018/01/25/permissive-licensing-is-wrong-no-its-not-2-2/) The previous post gave a short introduction into the topic of software licenses, focusing on the GPL vs. BSD discussion. This one is basically my response to some typical arguments I've seen from people who seem to loathe permissive licensing. I'll write this in dialog style, hoping that this makes it a little lighter to read. Roundup Install OpenBSD on dedibox with full-disk encryption (https://poolp.org/posts/2018-01-29/install-openbsd-on-dedibox-with-full-disk-encryption/) TL;DR: I run several "dedibox" servers at online.net, all powered by OpenBSD. OpenBSD is not officially supported so you have to work-around. Running full-disk encrypted OpenBSD there is a piece of cake. As a bonus, my first steps within a brand new booted machine ;-) Step #0: choosing your server OpenBSD is not officially supported, I can't guarantee that this will work for you on any kind of server online.net provides, however I've been running https://poolp.org on OpenBSD there since 2008, only switching machines as they were getting a bit old and new offers came up. Currently, I'm running two SC 2016 (SATA) and one XC 2016 (SSD) boxes, all three running OpenBSD reliably ever since I installed them. Recently I've been willing to reinstall the XC one after I did some experiments that turned it into a FrankenBSD, so this was the right occasion to document how I do it for future references. I wrote an article similar to this a few years ago relying on qemu to install to the disk, since then online.net provided access to a virtual serial console accessed within the browser, making it much more convenient to install without the qemu indirection which hid the NIC devices and disks duid and required tricks. The method I currently use is a mix and adaptation from the techniques described in https://www.2f30.org/guides/openbsd-dedibox.html to boot the installer, and the technique described in https://geekyschmidt.com/2011/01/19/configuring-openbsd-softraid-fo-encryption.html to setup the crypto slice. Step #1: boot to rescue mode Step #2: boot to the installer Step #3: prepare softraid Step #4: reboot to encrypted OpenBSD system Bonus: further tightening your system enable doas disable the root account update system with syspatch add my ssh public key to my ~/.ssh/authorized_keys disable password authentication within ssh reboot so you boot on a brand new up-to-date system with latest stable kernel VOILA ! January 2018 Development Projects Update (https://www.freebsdfoundation.org/blog/january-2018-development-projects-update/) Spectre and Meltdown in FreeBSD Issues affecting most CPUs used in servers, desktops, laptops, and mobile devices are in the news. These hardware vulnerabilities, known by the code-names “Meltdown” and “Spectre”, allow malicious programs to read data to which they should not have access. This potentially includes credentials, cryptographic material, or other secrets. They were originally identified by a researcher from Google's Project Zero, and were also independently discovered by researchers and academics from Cyberus Technology, Graz University of Technology, the University of Pennsylvania, the University of Maryland, Rambus, the University of Adelaide and Data61. These vulnerabilities affect many CPU architectures supported by FreeBSD, but the 64-bit x86 family of processors from Intel and AMD are the most widely used, and are a high priority for software changes to mitigate the effects of Meltdown and Spectre. In particular, the Meltdown issue affects Intel CPUs and may be used to extract secret data from the running kernel, and therefore, is the most important issue to address. The FreeBSD Foundation collaborates with Intel, and under this relationship participated in a briefing to understand the details of these issues and plan the mitigations to be applied to the x86 architectures supported by FreeBSD. We also made arrangements to have FreeBSD's security officer join me in the briefing. It is through the generous support of the Foundation's donors that we are able to dedicate resources to focus on these issues on demand as they arise. Foundation staff member Konstantin (Kostik) Belousov is an expert on FreeBSD's Virtual Memory (VM) system as well as low-level x86 details, and is developing the x86 kernel mitigations for FreeBSD. The mitigation for Meltdown is known as Page Table Isolation (PTI). Kostik created a PTI implementation which was initially committed in mid-January and is available in the FreeBSD-CURRENT development repository. This is the same approach used by the Linux kernel to mitigate Meltdown. One of the drawbacks of the PTI mitigation is that it incurs a performance regression. Kostik recently reworked FreeBSD's use of Process-Context Identifiers (PCID) in order to regain some of the performance loss incurred by PTI. This change is also now available in FreeBSD-CURRENT. The issue known as Spectre comes in two variants, and variant 2 is the more troubling and pressing one. It may be mitigated in one of two ways: by using a technique called “retpoline” in the compiler, or by making use of a CPU feature introduced in a processor microcode update. Both options are under active development. Kostik's change to implement the CPU-based mitigation is currently in review. Unfortunately, it introduces a significant performance penalty and alternatives are preferred, if available. For most cases, the compiler-based retpoline mitigation is likely to be the chosen mitigation. Having switched to the Clang compiler for the base system and most of the ports collection some years ago, FreeBSD is well-positioned to deploy Clang-based mitigations. FreeBSD developer Dimitry Andric is spearheading the update of Clang/LLVM in FreeBSD to version 6.0 in anticipation of its official release; FreeBSD-CURRENT now includes an interim snapshot. I have been assisting with the import, particularly with respect to LLVM's lld linker, and will support the integration of retpoline. This support is expected to be merged into FreeBSD in the coming weeks. The Foundation's co-op students have also participated in the response to these vulnerabilities. Mitchell Horne developed the patch to control the PTI mitigation default setting, while Arshan Khanifar benchmarked the performance impact of the in-progress mitigation patches. In addition, Arshan and Mitchell each developed changes to FreeBSD's tool chain to support the full set of mitigations that will be applied. These mitigations will continue be tested, benchmarked, and refined in FreeBSD-CURRENT before being merged into stable branches and then being made available as updates to FreeBSD releases. Details on the timing of these merges and releases will be shared as they become available. I would like to acknowledge all of those in the FreeBSD community who have participated in FreeBSD's response to Meltdown and Spectre, for testing, reviewing, and coordinating x86 mitigations, for developing mitigations for other processor architectures and for the Bhyve hypervisor, and for working on the toolchain-based mitigations. Guides: Getting Started & Lumina Theme Submissions (https://lumina-desktop.org/guides-getting-started-lumina-themes/) I am pleased to announce the beginning of a new sub-series of blog posts for the Lumina project: Guides! The TrueOS/Lumina projects want to support our users as they use Lumina or experiment with TrueOS. To that end, we've recently set up a central repository for our users to share instructions or other “how-to” guides with each other! Project developers and contributors will also submit guides to the repository on occasion, but the overall goal is to provide a simple hub for instructions written by any Lumina or TrueOS user. This will make it easier for users to not only find a “how-to” for some procedure, but also a very easy way to “give back” to the community by writing simple instructions or more detailed guides. Guides Repository Our first guide to get the whole thing started was created by the TrueOS Linebacker (https://discourse.trueos.org/t/introducing-the-trueos-linebacker/991) (with technical assistance from our own q5sys). In this guide, Terry Tate will walk you through the steps necessary to submit new wallpaper images to the Lumina Themes collection. This procedure is fully documented with screenshots every step of the way, walking you through a simple procedure that only requires a web browser and a Github account! Guide: Lumina Themes Submissions (https://github.com/trueos/guides/blob/master/lumina-themes-submissions/readme.md) The end result of this guide was that Terry Tate was able to submit this cool new “Lunar-4K” wallpaper to the “lumina-nature” collection. TrueOS Community Guides (https://github.com/trueos/guides/tree/master) ZFS vs. OpenZFS (by Michael Dexter) (https://www.ixsystems.com/blog/zfs-vs-openzfs/) You've probably heard us say a mix of “ZFS” and “OpenZFS” and an explanation is long-overdue. Our Senior Analyst clears up what ZFS and OpenZFS refer to and how they differ. I admit that we geeks tend to get caught up in the nuts and bolts of enterprise storage and overlook the more obvious questions that users might have. You've probably noticed that this blog and the FreeNAS blog refer to “ZFS” and “OpenZFS” seemingly at random when talking about the amazing file system at the heart of FreeNAS and every storage product that iXsystems sells. I will do my best to clarify what exactly these two terms refer to. From its inception, “ZFS” has referred to the “Zettabyte File System” developed at Sun Microsystems and published under the CDDL Open Source license in 2005 as part of the OpenSolaris operating system. ZFS was revolutionary for completely decoupling the file system from specialized storage hardware and even a specific computer platform. The portable nature and advanced features of ZFS led FreeBSD, Linux, and even Apple developers to start porting ZFS to their operating systems and by 2008, FreeBSD shipped with ZFS in the 7.0 release. For the first time, ZFS empowered users of any budget with enterprise-class scalability and data integrity and management features like checksumming, compression and snapshotting, and those features remain unrivaled at any price to this day. On any ZFS platform, administrators use the zpool and zfs utilities to configure and manage their storage devices and file systems respectively. Both commands employ a user-friendly syntax such as‘zfs create mypool/mydataset' and I welcome you to watch the appropriately-titled webinar “Why we love ZFS & you should too” or try a completely-graphical ZFS experience with FreeNAS. Yes, ZFS is really as good as people say it is. After enjoying nearly a decade of refinement by a growing group of developers around the world, ZFS became the property of database vendor Oracle, which ceased public development of both ZFS and OpenSolaris in 2010. Disappointed but undeterred, a group of OpenSolaris users and developers forked the last public release of OpenSolaris as the Illumos project. To this day, Illumos represents the official upstream home of the Open Source OpenSolaris technologies, including ZFS. The Illumos project enjoys healthy vendor and user participation but the portable nature and compelling features of ZFS soon produced far more ZFS users than Illumos users around the world. While most if not all users of Illumos and its derivatives are ZFS users, the majority of ZFS users are not Illumos users, thanks significantly in part to FreeNAS which uses the FreeBSD operating system. This imbalance plus several successful ZFS Day events led ZFS co-founder Matt Ahrens and a group of ZFS developers to announce the OpenZFS project, which would remain a part of the Illumos code base but would be free to coordinate development efforts and events around their favorite file system. ZFS Day has grown into the two-day OpenZFS Developer Summit and is stronger than ever, a testament to the passion and dedication of the OpenZFS community. Oracle has steadily continued to develop its own proprietary branch of ZFS and Matt Ahrens points out that over 50% of the original OpenSolaris ZFS code has been replaced in OpenZFS with community contributions. This means that there are, sadly, two politically and technologically-incompatible branches of “ZFS” but fortunately, OpenZFS is orders of magnitude more popular thanks to its open nature. The two projects should be referred to as “Oracle ZFS” and “OpenZFS” to distinguish them as development efforts, but the user still types the ‘zfs' command, which on FreeBSD relies on the ‘zfs.ko' kernel module. My impression is that the terms of the CDDL license under which the OpenZFS branch of ZFS is published protects its users from any patent and trademark risks. Hopefully, this all helps you distinguish the OpenZFS project from the ZFS technology. Beastie Bits Explaining Shell (https://explainshell.com/) OPNsense® 18.1 Released (https://opnsense.org/opnsense-18-1-released/) “SSH Mastery 2/e” copyedits back (https://blather.michaelwlucas.com/archives/3104) Sponsoring a Scam (https://blather.michaelwlucas.com/archives/3106) Thursday, February 8, 2018 - Come to Netflix to talk about FreeBSD (https://www.meetup.com/BAFUG-Bay-Area-FreeBSD-User-Group/events/246623825/) BSD User Group meeting in Stockholm: March 22, 17:30 - 21:00 (https://www.meetup.com/BSD-Users-Stockholm/events/247552279/) FreeBSD Flavoured talks from Linux.conf.au: You can't unit test C, right? (https://www.youtube.com/watch?v=z-uWt5wVVkU) and A Brief History of I/O (https://www.youtube.com/watch?v=qAhZEI_6lbc) EuroBSDcon 2018 website is up (https://2018.eurobsdcon.org/) Full day bhyvecon Tokyo, Japan, March 9, 2018 (http://bhyvecon.org/) *** Feedback/Questions Thomas - freebsd installer improvements (http://dpaste.com/3G2F7RC#wrap) Mohammad - FreeBSD 11 installation from a read only rescue disk (http://dpaste.com/0HGK3FQ#wrap) Stan - Follow up on guide you covered (http://dpaste.com/2S169SH#wrap) Jalal - couple questions (http://dpaste.com/35N8QXP#wrap)

university netflix head google apple interview technology guide japan running project teaching foundation german pennsylvania open reflections maryland built tokyo scams released belgium oracle developers intel releases meltdown guides brussels storage nic how to ironically io open source tutorials brief history disappointed linux github spectre licensing amd apache tl cpu ssd licenses cpus xc sun microsystems rpi digital ocean pti lumina jalal project zero permissive sata bsd gpl gnu freebsd clang uefi intel cpus llvm fosdem zfs openbsd copyleft data61 rambus openzfs freenas netbsd graz university lgpl allan jude opensolaris ixsystems freebsd foundation arshan trueos tarsnap matt ahrens eurobsdcon dragonflybsd clang llvm michael dexter cddl freebsd journal

130: Store all the Things | BSD Now 130

Play Episode Listen Later Feb 24, 2016 130:04

This week on BSDNow, Allan is back from the Storage Summit in Silicon Valley! We are going to get his thoughts on how the conference went, plus bring you the latest ZFS info discussed. That plus the usual BSD news is This episode was brought to you by Headlines OpenBSD website operators urged to fix mind-alteringly bad bug (http://www.theregister.co.uk/2016/02/21/openbsd_website_operator_patch_now_for_the_sake_of_your_sanity/?mt=1456206806399) We start off a bit light-hearted this week, with the important, breaking news that finally a long-standing OpenBSD bug has been addressed for the HTTP daemon. Specifically? It changes the default 404 page fonts away from Comic Sans, to a bit more crowd-pleasing alternative: “For some reason the httpd status pages (e.g. 404) use the Comic Sans typeface. This patch removes comic sans and sets the typeface to the default sans-serif typeface of the client. “This lowers the number of people contacting website maintainers with typeface complaints bordering on harassment”. Operators running HTTPD are highly encouraged to update their systems to the latest code, right now……... No seriously, we are waiting for you. Get it done now and then we'll continue with the show. Registration for AsiaBSDCon 2016 is now open + Talk Schedule (https://2016.asiabsdcon.org/registration/?lang=en) After a few delays, the registration for AsiaBSDCon has now opened! The conference starts in less than two weeks! now, so be sure to get signed up ASAP. In addition the schedule has been posted, and here's some of the highlights of this year's conference. In addition to FreeBSD and NetBSD dev summits on the first two days, we have some excellent tutorials being given this year by Kirk, Gnn, Dru and more! (https://2016.asiabsdcon.org/program.html.en) The regular paper talks also have lots of good ones this year, including this crazy encrypted boot loader one given by our very own Allan Jude! *** OPENBSD ON AWS : AN UNEXPECTED JOURNEY (http://blog.d2-si.fr/2016/02/15/openbsd-on-aws/?hn) We have a blog post from Antoine Jacoutot, talking about the process of getting OpenBSD up and running in AWS It starts with his process of creating an AMI from scratch, which ended up not being that bad: create and loopback-mount a raw image containing a UFS filesystem extract the OpenBSD base sets (which are just regular tarballs) and kernel enable console output (so that one could “aws ec2 get-console-output”) install the boot loader on the image then use the ec2 tools to import the RAW image to S3, convert it into a volume (ec2-import-volume) which we can snapshot (ec2-create-snapshot) and create an AMI from (ec2-register) The blog post also has a link to a script which automates this process, so don't be daunted if you didn't quite follow all of that. Thanks to the recently landed DomU support, the final pieces of the puzzle fell into place, allowing OpenBSD to function as a proper guest (with networking!) Next it details the process of injecting a public SSH key into the instances for instant remote access. An ec2-init.sh script was created (also on github) which does the following: setting the hostname installing the provided SSH public key to /root/.ssh/authorized_keys executing user-data (if it starts with a shebang) displaying the host SSH fingerprints on the console (to match cloud-init) With that done, OpenBSD is pretty much AWS ready! He then gives a brief walkthrough of setting up nginx for new users, but if you've already done this before then the instance is ready for you to hacking on. Start thinking of ideas for things with FreeBSD for Google's 2016 Summer of Code (https://wiki.freebsd.org/SummerOfCodeIdeas) Students and Developers, listen up! It's time to start thinking about GSoC again, and FreeBSD is looking to update its project ideas page. There's some good ones on the list, plus ones that should be pruned (such as GELI boot), but now is the time to start adding new ones before we get too deep into the process. This goes for the other BSD's as well, start thinking about your proposals, or if you are developer, which projects would be a good fit for mentoring. (Improving the Linux Compat layer is one I think should be done!) Guide to getting started with kernel hacking (https://wiki.freebsd.org/Graphics/Getting%20started%20with%20kernel%20projects) One of the things that's been asked frequently is how to contribute towards the efforts to bring updated DRM / X drivers to the FreeBSD kernel. Jean-Sébastien Pédron has started a great guide on the Wiki which details how to get started with the porting effort, and that developers need not be afraid of helping. *** Storage Summit Roundup Earlier this week a number of developers from FreeBSD, as well as various vendors that use FreeBSD, or provide products used with FreeBSD met for a Storage Summit (https://wiki.freebsd.org/201602StorageSummit), to discuss the future of these technologies The summit was co-located with the USENIX FAST (Filesystems And Storage Technologies) conference The summit was sponsored by the FreeBSD Foundation and FlightAware After a short introduction, the event opened with a Networking Synergy panel The focus of this panel was to see if there were techniques and lessons learned in improving the networking stack over the last 10 years that could be applied to improving the storage stack A lot of time was spent discussing issues like multi-queue support, CPU scheduling, and ways to modernize the stack CAM Scheduling & Locking Revamp (https://wiki.freebsd.org/201602StorageSummit/CAM) No notes posted User Space Storage Stack (https://wiki.freebsd.org/201602StorageSummit/UserSpace) One of the user space storage stacks discussed was Diskmap Like netmap, but for disks (diskmap) Kernel bypass for accessing disks Ilias Marinos, who is working on diskmap at Cambridge University, described diskmap to the group A design discussion then followed in which the memory management was covered as that's an issue for any sort of "IO" map system Action Items: Discuss with Luigi the idea of code merges Need a reset path API Kernel buffer mapping for reliability Support for other interfaces (SATA/SCSI) GEOM layer adaptation Adapting to New Storage Technologies (https://wiki.freebsd.org/201602StorageSummit/NewStorageTechnologies) This working group was led by Adrian Palmer, from Seagate SMR Persistent Memory Session 1: Device Identification and the structural requirements Agenda: We'll look over the Identification nuances and what needs to change to support the structure. Support for IO order guarantees, forward-write only requirements, new commands and topology. Dig into CAM and GEOM layers. Solutions should be fast and have as few code paths as possible Results: Small audience. We talked about zoned characteristics, and how it can be used in various workloads, projected to be implemented in years Session 2: Information dissemination and consumption Agenda: Where and how will information from the report_zones command be gathered, stored, combined and used. This will include userspace storage and multi-volume management. Will CAM store this data, or will GEOM? How frequently will this need to be queried/updated/verified from the drive? Results: Merged with ZFS working group to discuss SMR. Came up with idea that could be implemented as circular buffer zone type. Began to discuss solutions among developers ZFS (https://wiki.freebsd.org/201602StorageSummit/ZFS) During the first session we discussed how to improve dedup support + A dedup throttle or cap was discussed. When the size of the DDT grows beyond this size, new entries would not be deduped. An alternative to this was also discussed, where when the DDT reached the cap size, it would remove a random entry with only a single reference from the DDT to make room for the new entry. When a block is going to be freed, if it is not found in the DDT, it is assumed to have only 1 reference, and removed. There was also discussion of replacing the DDT with an in-memory hash table and a “log” of increment/decrement operations, that is periodically compacted. The hash table is recreated from the log at pool import time. This would reduce the in-memory footprint of the DDT, as well as speed up all write operations as adding an entry to the dedup log will be less expensive than updating the DDT. There was also discussion of using dedicated device(s) for the DDT, either using the DDT on SSD work by Nexenta, or the Metadata Classes work by Intel The first session also discussed Secure Delete and related things The desire for an implementation of TRIM that uses the “secure erase” functionality provided by some disks was expressed Overwriting sectors with patterns of garbage may be insufficient because SSDs may internally remap where a specific LBA physically resides The possibility of using something like the “eager zero” feature to periodically write zeros over all free blocks in the pool to erase any lingering data fragments Problems with the FreeBSD TRIM implementation were discussed, as well as looking at ways to implement the new ZFS TRIM implementation on FreeBSD ABD (ARC Buf Data) was discussed, a new design that lessens the requirement for contiguous memory. Only a small area of contiguous blocks is reserved at boot, and compressed ARC blocks are constructed of scatter-gather lists of individual pages The second session combined with the SMR group and talked about SMR support in ZFS Later in the second session ZFS Encryption was also discussed, mostly with a focus on what the use cases are The third session combined all of the groups for an overview of upcoming ZFS features including device removal and channel programs There was also a request for code review, for mostly finished projects like Persistent L2ARC, Writeback cache, and Large dnode support Hallway Track ZFS / VFS Interaction Adrian Palmer has been a FreeBSD hobbyist since FreeBSD 7, and I think I managed to convince him to start contributing *** News Roundup One Week with NetBSD 7.0: Back to Unix basics (http://jamesdeagle.blogspot.com/2016/02/one-week-with-netbsd-70-back-to-unix.html) The author of this blog series is sending a week using NetBSD 7.0, following a previous series on Solaris 10 “This is actually familiar territory, as I've been using BSD variants almost exclusively since 2006. My recent SunOS explorations were triggered last summer by OpenBSD having choked on my current laptop's NVIDIA card, and from what I could see at the time, FreeBSD had the same problem, although I now know NVIDIA drivers exist for that system. The thing that keeps me from going all-in with FreeBSD 10.x, however, is the fact that Firefox crashes and leaves "core dump" messages in its wake, and I'm just not a Chrome kinda guy.” “For those with a catholic taste in Unix, NetBSD is a keg party at the Vatican. If you're an absolute Unix beginner, or have been living on Ubuntu-based Linux distros for too long, then you may feel stranded at first by NetBSD's sparseness. You'll find yourself staring into the abyss and seeing only a blinking cursor staring back. If you have the presence of mind to type startx, you'll be greeted by twm, a window manager offering little more than an xterm window with the same blinking cursor until you learn how to configure the .twmrc file to include whatever applications you want or need in the right-click menu.” “As for NetBSD itself, I can't think of any major productivity applications that can't be installed, and most multimedia stuff works fine.” Issues the author hopes to sort out in later posts: Audio playback (youtube videos in Firefox) Wireless Flash Digital Camera SD Card readability, video playback Audacity A “fancy” desktop like Gnome 2, KDE, or xfce In a follow-up post (http://jamesdeagle.blogspot.com/2016/02/one-week-with-netbsd-70-libreoffice.html), the author got LibreOffice installed and sorted out the audio issues they were having In a later follow-up (http://jamesdeagle.blogspot.com/2016/02/one-week-with-netbsd-70-mixed-review-of.html) XFCE is up and running as well *** ZFS is for Containers in Ubuntu 16.04 (http://blog.dustinkirkland.com/2016/02/zfs-is-fs-for-containers-in-ubuntu-1604.html) As you may have heard, Ubuntu 16.04 will include ZFS -- baked directly into Ubuntu -- supported by Canonical “ZFS one of the most beloved features of Solaris, universally coveted by every Linux sysadmin with a Solaris background. To our delight, we're happy to make to OpenZFS available on every Ubuntu system.” What does “supported by Canonical” mean? “You'll find zfs.ko automatically built and installed on your Ubuntu systems. No more DKMS-built modules” “The user space zfsutils-linux package will be included in Ubuntu Main, with security updates provided by Canonical” The article then provides a quick tutorial for setting up Linux Containers (LXC) backed by ZFS In the example, ZFS is backed by a file on the existing disk, not by a real disk, and with no redundancy However, the setup script seems to support using real block devices The Software Freedom Conservancy (https://sfconservancy.org/) is expected to issue a statement detailing their opinion on the legalities and licensing issues of bundling ZFS with Linux. *** Polling is a Hack: Server Sent Events (EventSource) with gevent, Flask, nginx, and FreeBSD (http://hypatia.software/2016/01/29/polling-is-a-hack-server-sent-events-eventsource-with-gevent-flask-nginx-and-freebsd/) A tutorial on setting up ‘Server-Sent Events', also know as EventSource in javascript, to notify website clients of new data, rather than having the javascript constantly poll for new data. The setup uses FreeBSD, nginx, gevent, Python, and the Flask framework The tutorial walks through setting a basic Python application using the Flask framework Then setting up the client side in Javascript Then for the server side setup, it covers installing and configuring nginx, and py-supervisor on FreeBSD The tutorial also includes links to additional resources and examples, including how to rate limit the Flash application *** Why FreeBSD? (http://www.aikchar.me/blog/why-freebsd.html) An excellent article written by Hamza Sheikh, discussing why FreeBSD is now his clear choice for learning UNIX. The article is pretty well written and lengthy, but has some great parts which we wanted to share with you: There were many rough edges in the Linux world and some of them exist even today. Choosing the right distribution (distro) for the task at hand is always the first and most difficult decision to make. While this is a strength of the Linux community it is also its weakness. This is exacerbated with the toxic infighting within the community in the last few years. A herd of voices believes it is their right to bring down a distro community because it is not like their distro of choice. Forking upstream projects has somehow become taboo. Hurling abuse in mailing lists is acceptable. Helping new users is limited to lambasting their distro of choice. Creating conspiracy theories over software decisions is the way to go. Copyleft zealots roam social media declaring non-copyleft free software heretic abominations. It all boils down to an ecosystem soured by the presence of maniacs who have the loudest voices and they seem to be everywhere you turn. Where is the engineering among all this noise? Btrfs - baking for a long time - is still nowhere near ZFS in stability or feature parity. systemd is an insatiable entity that feeds on every idea in sight and just devours indiscriminately. Wayland was promised years ago and its time has yet to arrive. Containers are represented by Docker that neither securely contains applications nor makes them easy to manage in production. Firewalling is dithering between firewalld, nftables, etc. SystemTap cannot match DTrace. In the same time span what do various BSDs offer? pf, CARP, ZFS, Hammer, OpenSSH, jails, pkgsrc, (software) ports, DTrace, hardware portability; just to name a few. Few would deny that BSDs have delivered great engineering with free software licenses to the entire world. To me they appear to be better flag bearers of free software with engineering to back it. He then goes through some of the various BSD's and the specifics on why FreeBSD was the logical choice for his situation. But at the end has a great summary on the community as a whole: Finally - and maybe repeating myself here - I have nothing but praise for the community. Be it BSD Now, mailing lists, Reddit, Twitter, LFNW, or SeaGL, people have encouraged me, answered my questions, and filed bugs for me. I have been welcomed and made a part of the community with open arms. These reasons are (good) enough for me to use FreeBSD and contribute to it. BeastieBits OPNsense 16.1.3 released (https://opnsense.org/opnsense-16-1-3-released/) Copies of "FreeBSD Mastery: Specialty Filesystems" seen in the wild (https://twitter.com/Savagedlight/status/700001944547491842) pfsense training available in Europe (http://www.netgate.com/training/) LiteBSD now has 50 ports in its ports tree (https://github.com/ibara/LiteBSD-Ports) Ports tree locked for OpenBSD 5.9 (http://marc.info/?l=openbsd-ports&m=145615281431064&w=2) “FreeBSD Filesystem Fun” at March semibug (http://blather.michaelwlucas.com/archives/2556) Event #46 — Embedded Platforms (BSD, OpenWRT, Plan 9 & Inferno) (http://oshug.org/event/46) Feedback/Questions Frank - ZFS RAM? (http://slexy.org/view/s21lcCKrSB) David - ARM Porting (http://slexy.org/view/s204lxjvlq) Johnny - Lumina Default? (http://slexy.org/view/s2xMiSNLYn) Adam - PC-BSD Install and Q's (http://slexy.org/view/s214gJbLwD) Jeremy - Video Card Q (http://slexy.org/view/s20UNyzEeh) ***

europe google interview guide news event plan code built silicon valley improving reddit flash summit large raw hammer developers arc nvidia vatican storage luigi how to inferno began io chrome jeans open source python tutorials aws linux cambridge university identification polling wiki ubuntu cpu firefox operators ssd containers trim gnome s3 docker copies solaris kde domu ddt carp kernel unix geli canonical for king wayland smr ssh digital ocean hurling flask comic sans bsd libreoffice freebsd dkms lba ufs openssh geom zfs openbsd xfce openwrt copyleft gnn gsoc will cam btrfs openzfs dtrace netbsd allan jude bsds ixsystems kris moore freebsd foundation lfnw tarsnap sunos bsd now dragonflybsd asiabsdcon

98: Our Code is Your Code

Play Episode Listen Later Jul 15, 2015 73:49

Coming up this time on the show, we'll be talking with the CTO of Xinuos, David Meyer, about their adoption of FreeBSD. We also discuss the BSD license model for businesses and the benefits of contributing changes back. This episode was brought to you by Headlines Enabling FreeBSD on AArch64 (https://community.arm.com/groups/processors/blog/2015/07/07/enabling-freebsd-on-aarch64) One of the things the FreeBSD foundation has been dumping money into lately is ARM64 support, but we haven't heard too much about it - this article should change that Since it's on a mainstream ARM site, the article begins with a bit of FreeBSD history, leading up to the current work on ARM64 There's also a summary of some of the ARM work done at this year's BSDCan, including details about running it on the Cavium ThunderX platform (which has 48 cores) As of just a couple months ago, dtrace is even working on this new architecture Come 11.0-RELEASE, the plan is for ARM64 to get the same "tier 1" treatment as X86, which would imply binary updates for base and ports - something Raspberry Pi users often complain about not having *** OpenBSD's tcpdump detailed (https://www.youtube.com/watch?v=8kR-tW1kyDc#t=8) Most people are probably familiar with tcpdump (https://en.wikipedia.org/wiki/Tcpdump), a very useful packet sniffing and capturing utility that's included in all the main BSD base systems This video guide is specifically about the version in OpenBSD, which has gone through some major changes (it's pretty much a fork with no version number anymore) Unlike on the other platforms, OpenBSD's tcpdump will always run in a chroot as an unprivileged user - this has saved it from a number of high-profile exploits It also has support for the "pf.os" system, allowing you to filter out operating system fingerprints in the packet captures There's also PF (and pflog) integration, letting you see which line in your ruleset triggered a specific match Being able to run tcpdump directly on your router (http://www.bsdnow.tv/tutorials/openbsd-router) is pretty awesome for troubleshooting *** More FreeBSD foundation at BSDCan (http://freebsdfoundation.blogspot.com/2015/07/bsdcan-2015-trip-report-kamil-czekirda.html) The FreeBSD foundation has another round of trip reports from this year's BSDCan First up is Kamil Czekirda, who gives a good summary of some of the devsummit, FreeBSD-related presentations, some tutorials, getting freebsd-update bugs fixed and of course eating cake A second post (http://freebsdfoundation.blogspot.com/2015/07/bsdcan-2015-trip-report-christian.html) from Christian Brueffer, who cleverly planned ahead to avoid jetlag, details how he got some things done during the FreeBSD devsummit Their third report (http://freebsdfoundation.blogspot.com/2015/07/bsdcan-2015-trip-report-warren-block.html) is from our buddy Warren Block, who (unsurprisingly) worked on a lot of documentation-related things, including getting more people involved with writing them In true doc team style, his report is the most well-written of the bunch, including lots of links and a clear separation of topics (doc lounge, contributing to the wiki, presentations...) Finally, the fourth one (http://freebsdfoundation.blogspot.com/2015/07/bsdcan-2015-trip-report-shonali.html) comes to us from Shonali Balakrishna, who also gives an outline of some of the talks "Not only does a BSD conference have way too many very smart people in one room, but also some of the nicest." *** DragonFly on the Chromebook C720 (https://www.dragonflydigest.com/2015/07/08/16391.html) If you've got one of the Chromebook laptops and weren't happy with the included OS, DragonFlyBSD might be worth a go This article is a "mini-report" on how DragonFly functions on the device as a desktop, and While the 2GB of RAM proved to be a bit limiting, most of the hardware is well-supported DragonFly's wiki has a full guide (http://www.dragonflybsd.org/docs/newhandbook/ConfigChromebook/) on getting set up on one of these devices as well *** Interview - David Meyer - info@xinuos.com (mailto:info@xinuos.com) / @xinuos (https://twitter.com/xinuos) Xinuos, BSD license model vs. others, community interaction News Roundup Introducing LiteBSD (https://github.com/sergev/LiteBSD) We definitely don't talk about 4.4BSD a lot on the show LiteBSD is "a variant of [the] 4.4BSD operating system adapted for microcontrollers" If you've got really, really old hardware (or are working in the embedded space) then this might be an interesting hobby project to look info *** HardenedBSD announces ASLR completion (http://hardenedbsd.org/article/shawn-webb/2015-07-06/announcing-aslr-completion) HardenedBSD, now officially a full-on fork of FreeBSD (http://hardenedbsd.org/content/about), has declared their ASLR patchset to be complete The latest and last addition to the work was VDSO (Virtual Dynamic Shared Object) randomization, which is now configurable with a sysctl This post gives a summary of the six main features they've added since the beginning (http://www.bsdnow.tv/episodes/2014_08_27-reverse_takeover) Only a few small things are left to do - man page cleanups, possibly shared object load order improvements *** Unlock the reaper (https://www.marc.info/?l=openbsd-tech&m=143636371501474&w=2) In the ongoing quest to make more of OpenBSD SMP-friendly, a new patch was posted that unlocks the reaper in the kernel When there's a zombie process (https://en.wikipedia.org/wiki/Zombie_process) causing a resource leak, it's the reaper's job (https://en.wikipedia.org/wiki/Wait_%28system_call%29) to deallocate their resources (and yes we're still talking about computers, not horror movies) Initial testing has yielded positive (https://www.marc.info/?l=openbsd-tech&m=143642748717836&w=2) results (https://www.marc.info/?l=openbsd-tech&m=143639356810690&w=2) and no regressions (https://www.marc.info/?l=openbsd-tech&m=143638955809675&w=2) They're looking for testers, so you can install a -current snapshot and get it automatically An updated version of the patch is coming soon (https://www.marc.info/?l=openbsd-tech&m=143643025118637&w=2) too A hackathon (http://www.openbsd.org/images/hackathons/c2k15-s.gif) is going on right now, so you can expect more SMP improvements in the near future *** The importance of mentoring (http://adrianchadd.blogspot.com/2015/07/the-importance-of-mentoring-or-how-i.html) Adrian Chadd has a blog post up about mentoring new users, and it tells the story of how he originally got into FreeBSD He tells the story of, at age 11, meeting someone else who knew about making crystal sets that became his role model Eventually we get to his first FreeBSD 1.1 installation (which he temporarily abandoned for Linux, since it didn't have a color "ls" command) and how he started using the OS Nowadays, there's a formal mentoring system in FreeBSD While he talks about FreeBSD in the post, a lot of the concepts apply to all the BSDs (or even just life in general) *** Feedback/Questions Sean writes in (http://slexy.org/view/s29LpvIxDD) Herminio writes in (http://slexy.org/view/s21I1MZsDl) Stuart writes in (http://slexy.org/view/s20kk3ilM6) Richard writes in (http://slexy.org/view/s2pL5xA80B) ***

business interview guide mit zombies code built os unlock developers cto ram arm copyright initial storage how to open source tutorials linux pf raspberry pi dragonfly chromebooks smp digital ocean gpl bsd 2gb freebsd david meyer x86 openbsd arm64 copyleft netbsd allan jude aslr bsds ixsystems kris moore tarsnap bsdcan aarch64 dragonflybsd

0x56: … & We're Back!

Play Episode Listen Later Jun 4, 2015 33:52

Bradley and Karen discuss the VMware lawsuit that Software Freedom Conservancy is funding. Show Notes: Bradley and Karen discuss the lawsuit that Christoph Hellwig filed. (07:37) Karen mentioned her LibrePlanet keynote about the VMware lawsuit. (21:30) Bradley's talk at LinuxConf Australia 2015, Considering The Future of Copyleft, is available online. (22:04) Bradley mentioned the discussion on pump.io about NPR fundraisers. (24:23) Bradley mentioned a Debian 8 release party at LinuxFest Northwest, which Microsoft didn't invite him to, since he wasn't willing to give Microsoft his contact info for marketing purposes. (29:16) Karen and Bradley promoted the Conservancy supporter program (31:40) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

freedom law sound microsoft legal npr open source linux vmware cc by sa irc conservancy gpl bsd debian dan lynch copyleft ogg vorbis software freedom conservancy lgpl software freedom linuxfest northwest mike tarantino

0x53: Can Plagiarism Happen Under Copyleft?

Play Episode Listen Later Dec 30, 2014 76:43

Bradley and Karen discuss what plagiarism is (or isn't) and how it interacts with copyleft licenses. Show Notes: Segment 0 (00:00:37) Please donate to to send Dan to a conference. There's a progress bar on faif.us now. You can also donate to support Software Freedom Conservancy, where Bradley and Karen work, by becoming a supporter. Karen mentioned her blog post about the supporter program. (00:08:30) Bradley mentioned his blog post about the supporter program as well. (00:09:30) Segment 1 (00:16:16) Bradley and Karen pick up on a topic original discussed in Segment 1 of FaiF 0x02. (00:16:50) Bradley discussed the Laurie Stearns' article from the California Law Review, entitled Copy Wrong: Plagiarism, Process, Property, and the Law (00:23:50) Bradley mentioned The GNOME Foundation Copyright Assignment Guidelines that he co-authored. (00:28:05) Bradley mentioned the Doris Kearns Goodwin Plagiarism controversy, and how it would have been simply redressed if the material she reused had been copylefted. (00:29:26) Karen mentioned that Flickr made different policies for CC-BY-SA'd works when selling printed versions. (32:30) Bradley mentioned that even software freedom advocates just comply with the copyleft licenses and don't work collaboratively, particularly during hostile forks, using Conservancy's Kallithea project as an example. (00:35:25) Bradley reiterated a point he made in FaiF 0x08, where he discussed that Linus Torvalds switched to GPL for Linux because he realized non-commercial restrictions weren't appropriate. (00:37:50) Bradley mentioned the hostile fork of GCC called egcs. The H-Online years later wrote a long article that discussed the egcs fork egcs fork. (00:39:46) Bradley mentioned that plagiarism is ultimately about attribution, and modern DVCS systems makes attribution easy and renders plagiarism impossible (if DVCS logs are accurate). (00:44:15) Bradley mentioned that he continually has learned the lesson that if you let your employer keep copyright, you lose everything you had when you switch employers (if the work isn't copylefted). (00:47:00) Bradley discussed the methods of attribution required in GPLv3. (00:50:05) Bradley mentioned that copyright notices are the primary method of attribution in copyleft licenses, and even non-copyleft ones too. (00:53:19) Karen discussed the attribution requirements in text of CC-BY-SA 4.0. (00:53:49) Bradley wants to do a whole FaiF show about how CC-BY-SA may not be a true copyleft since it has no source code requirement (00:54:40) Bradley mentioned the “fake name” that film directors use when they wish to disavow a work they aren't happy with. The name is, in fact, Alan Smithee, and indeed the 1984 film Dune lists Smithee as a director even though David Lynch is known publicly to be the director. (00:58:40) Bradley mentioned the unfair accusations against Red Hat when they stopped publishing their internal Linux Git repository and instead released a more standard ChangeLog. (01:05:30) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

freedom law sound legal dune property david lynch open source linux flickr red hat plagiarism cc by sa irc gcc conservancy gpl bsd linus torvalds changelog alan smithee dan lynch copyleft ogg vorbis smithee software freedom conservancy software freedom lgpl mike tarantino

0x4C: Copyleft vs permissive vs CLAs

Play Episode Listen Later Aug 26, 2014 74:47

Bradley and Karen discuss the talk, Copyleft vs. Permissive vs. Contributor License Agreements: A Veteran's Perspective by Simo Sorce given at FOSDEM 2013 on Sunday 3 February 2013. Show Notes: Segment 0 (00:00:38) Bradley and Karen introduce Simo's talk. Segment 1 (00:03:02) The slides from Simo's talk are available, if you want to follow along Segment 2 (00:59:50) Bradley menitoned his blog post about CLA's on Conservancy's website. (01:00:10) Segment 3 (01:10:22) Bradley and Karen are still trying to decide what to do about the FOSDEM 2014 talks. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

freedom law sound legal perspective open source linux simo cc by sa irc cla conservancy permissive gpl bsd clas fosdem dan lynch copyleft ogg vorbis lgpl software freedom mike tarantino

0x48: copyleft-next

Play Episode Listen Later Jul 1, 2014 95:07

Bradley and Karen discuss the talk, copyleft-next: an Introduction by Richard Fontana given at FOSDEM 2013 on Sunday 3 February 2013. Show Notes: Segment 0 (00:37) Bradley and Karen introduce the talk. Segment 1 (05:37) The slides Fontana's talk on copyleft-next are available. Segment 2 (01:06:51) Bradley mentioned the issue of Noam Chomsky's points on concision (01:13:23). Bradley mentioned the anti-GPL keynote by Tom Preseton-Werner of Github at OSCON 2013. (01:14:53) Bradley and Karen discussed the Harvey Birdman Rule. (1:27:45) Bradey mentioned a comment he posted about CHR-governed policy meetings. (01:29:00) Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

freedom law sound legal open source linux github contributing chr fontana noam chomsky cc by sa irc conservancy gpl bsd fosdem oscon dan lynch copyleft ogg vorbis lgpl software freedom mike tarantino

31: Edgy BSD Users

Play Episode Listen Later Apr 1, 2014 69:07

This week we'll be talking to Richard Stallman about the upcoming GPLv4 and how it will protect our software from being stolen. After that, we'll show you how to recover from those pesky ZFS on Linux corruption issues, as well as some tips on how to explain to your boss that all the production boxes were compromised. Your questions and all the latest GNUs, on Linux Now - the place to Lin.. ux. This episode was brought to you by Headlines Preorders for cool BSD stuff (http://www.amazon.com/gp/aw/d/0321968972/) The 2nd edition of The Design and Implementation of the FreeBSD Operating System is up for preorder We talked to GNN (http://www.bsdnow.tv/episodes/2014_01_29-journaled_news_updates) briefly about it, but he and Kirk (http://www.bsdnow.tv/episodes/2013-10-02_stacks_of_cache) have apparently finally finished the book "For many years, The Design and Implementation of the FreeBSD Operating System has been recognized as the most complete, up-to-date, and authoritative technical guide to FreeBSD's internal structure. Now, this definitive guide has been extensively updated to reflect all major FreeBSD improvements between Versions 5 and Versions 11" OpenBSD 5.5 preorders (https://https.openbsd.org/cgi-bin/order) are also up, so you can buy a CD set now You can help support the project, and even get the -release of the OS before it's available publicly 5.5 is a huge release with lots of big changes, so now is the right time to purchase one of these - tell Austin we sent you! *** pkgsrcCon 2014 CFP (http://mail-index.netbsd.org/pkgsrc-users/2014/03/18/msg019424.html) This year's pkgsrcCon is in London, on June 21st and 22nd There's a Call For Papers out now, so you can submit your talks Anything related to pkgsrc is fine, it's pretty informal Does anyone in the audience know if the talks will be recorded? This con is relatively unknown *** BSDMag issue for March 2014 (http://bsdmag.org/magazine/1860-deploying-netbsd-on-the-cloud-using-aws-ec2-march-bsd-issue) The monthly BSD magazine releases its newest issue Topics this time include: deploying NetBSD using AWS EC2, creating a multi-purpose file server with NetBSD, DragonflyBSD as a backup server, more GIMP lessons, network analysis with wireshark and a general security article The Linux article trend seems to continue... hmm *** Non-ECC RAM in FreeNAS (http://blog.brianmoses.net/2014/03/why-i-chose-non-ecc-ram-for-my-freenas.html) We've gotten a few questions about ECC RAM with ZFS Here we've got a surprising blog post about why someone did not go with ECC RAM for his NAS build The article mentions the benefits of ECC and admits it is a better choice in nearly all instances, but unfortunately it's not very widespread in consumer hardware motherboards and it's more expensive Regular RAM also has "special" issues with ZFS and pool corruption Long post, so check out the whole thing if you've been considering your memory options and weighing the benefits *** Interview - Pierre Pronchery - khorben@edgebsd.org (mailto:khorben@edgebsd.org) / @khorben (https://twitter.com/khorben) EdgeBSD (https://www.youtube.com/watch?v=_D_iaad5rPo) (slides (http://ftp.netbsd.org/pub/NetBSD/misc/khorben/asiabsdcon2014/)) Tutorial Building an OpenBSD desktop (http://www.bsdnow.tv/tutorials/the-desktop-obsd) News Roundup Getting to know your portmgr-lurkers (http://blogs.freebsdish.org/portmgr/2014/03/25/getting-to-know-your-portmgr-lurker-frederic-culot) This week we get to hear from Frederic Culot, colut@ Originally an OpenBSD user from France, Frederic joined as a ports committer in 2010 and recently joined the portmgr lurkers team "FreeBSD is also one of my sources of inspiration when it comes to how organizations behave and innovate, and I find it very interesting to compare FreeBSD with the for-profit companies I work for" We get to find out a little bit about him, why he loves FreeBSD and what he does for the project *** NetBSD on the Playstation 2 (https://blog.netbsd.org/tnf/entry/the_playstation2_port_is_back) Who doesn't want to run NetBSD on their old PS2? The PS2 port of NetBSD was sadly removed in 2009, but it has been revived It's using a slightly unusual MIPS CPU that didn't have much GCC support Hopefully a bootable kernel will be available soon *** The FreeBSD Challenge update (http://www.thelinuxcauldron.com/2014/03/24/freebsd-challenge-day-22-30/) Our friend from the Linux Foundation continues his FreeBSD switching journey This time he starts off by discovering virtual machines suck at keeping accurate time, and some ports weren't working because of his clock being way off After polling the IRC for help, he finally learns the difference between ntpdate and ntpd and both of their use cases Maybe he should've just read our NTP tutorial (http://www.bsdnow.tv/tutorials/ntpd)! *** PCBSD weekly digest (http://blog.pcbsd.org/2014/03/pc-bsd-weekly-feature-digest-23/) The mount tray icon got lots of updates and fixes The faulty distribution server has finally been tracked down and... destroyed New language localization project is in progress Many many updates to ports and PBIs, new -STABLE builds *** Feedback/Questions Antonio writes in (http://slexy.org/view/s27d69qHJW) Patrick writes in (http://slexy.org/view/s21FhLCHbB) Chris writes in (http://slexy.org/view/s20Hisk3Yw) Ron writes in (http://slexy.org/view/s20rBZyTLC) Tyler writes in (http://slexy.org/view/s2s4CxE4gd) ***

interview guide france talk design security sony os cd playstation presentation april fools copyright users cfp how to implementation stable tutorials arch linux ubuntu cpu desktops versions ps2 gnome frederic irc ecc edgy gimp rms playstation 2 ntp linux foundation bsd gpl mips gnu debian freebsd pbis richard stallman centos fosdem gentoo zfs openbsd xfce copyleft gnn gnus zol freenas netbsd allan jude ixsystems kris moore dragonflybsd

23: Time Signatures