Podcasts about gplv2

This is a recap of the top 10 posts on Hacker News on June 27th, 2023.This podcast was generated by Wondercraft: https://www.wondercraft.ai/?utm_source=hackernews_recap Please ping at team AT wondercraft.ai with feedback.(00:42): macOS command-line tools you might not know aboutOriginal post: https://news.ycombinator.com/item?id=36491704&utm_source=wondercraft_ai(02:36): Outlook now ignores Windows' Default Browser and opens links in Edge by defaultOriginal post: https://news.ycombinator.com/item?id=36492329&utm_source=wondercraft_ai(04:37): FedEx Accused of Largest Odometer Rollback Fraud in History with Used VansOriginal post: https://news.ycombinator.com/item?id=36492010&utm_source=wondercraft_ai(06:49): The Deep Sea (2019)Original post: https://news.ycombinator.com/item?id=36491514&utm_source=wondercraft_ai(09:10): The hidden cost of air quality monitoringOriginal post: https://news.ycombinator.com/item?id=36499905&utm_source=wondercraft_ai(11:23): Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022Original post: https://news.ycombinator.com/item?id=36495667&utm_source=wondercraft_ai(13:36): Tinc, a GPLv2 mesh routing VPNOriginal post: https://news.ycombinator.com/item?id=36491338&utm_source=wondercraft_ai(15:37): It's weird that people get mocked for changing their mindsOriginal post: https://news.ycombinator.com/item?id=36491735&utm_source=wondercraft_ai(17:29): I Built Linux from ScratchOriginal post: https://news.ycombinator.com/item?id=36493422&utm_source=wondercraft_ai(19:37): Half of US wetlands lost federal protection. Their fate is up to the statesOriginal post: https://news.ycombinator.com/item?id=36499102&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

ReiserFS – The file system of the future Intro: Welcome to HPR; What I do; How I got in to computing; How I got in to Slackware and discovered ReiserFS A history of ReiserFS: Previous episode; Brief recap; A brief history; Lessons learned and experiences gained; Some tools to use Outro: Thanks ReiserFS From Wikipedia, the free encyclopedia ReiserFS is a general-purpose, journaling file system initially designed and implemented by a team at Namesys led by Hans Reiser and licensed under GPLv2. Introduced in version 2.4.1 of the Linux kernel, it was the first journaling file system to be included in the standard kernel. ReiserFS was the default file system in Novell's SUSE Linux Enterprise until Novell decided to move to ext3 on October 12, 2006, for future releases. Namesys considered ReiserFS version 3.6 which introduced a new on-disk format allowing bigger filesizes, now occasionally referred to as Reiser3, as stable and feature-complete and, with the exception of security updates and critical bug fixes, ceased development on it to concentrate on its successor, Reiser4. Namesys went out of business in 2008 after Reiser's conviction for murder. The product is now maintained as open source by volunteers. The reiserfsprogs 3.6.27 were released on 25 July 2017. ReiserFS is currently supported on Linux without quota support. It has been discussed for removal from the Linux kernel since early 2022 due to a lack of maintenance upstream, and technical issues inherent to the filesystem, such as the fact it suffers from the year 2038 problem; it was deprecated in Linux 5.18, with removal planned for 2025.

Primer episodio de la serie en la que analizamos WordPress a fondo CMS nacido como herramienta de blog WordPress tiene un 60.8% de cuota de mercado WordPress respalda a un 14.7% de los mejores sitios web del mundo Más de 500 sitios son creados al día usando WordPress frente a 60-80 otros ecommerce Punto fuerte Comunidad : El Directorio de Plugin de WordPress contiene más 55,000 plugins WooCommerce respalda a un 22% de los mejores sitios de ecommerce en el top 1 millón en el mundo Desarrollado por Matt Mullenweg y Mike Little cuando su desarrollador original descontinuó el desarrollo creado usando PHP y MySQL Licencia bajo el GPLv2 puedes modificarlo Se estima que el esfuerzo colaborativo detrás del desarrollo de WordPress ha requerido por lo menos 151 años humanos para construir, con un costo estimado de más de $8 millones. WordPress.com vs WordPress.org WordPress 5.9 → 39,107,877 Automattic → Automattic tiene un valor de $1.16 mil millones. Actualmente tiene a 873 empleados trabajando de forma remota Principales usos: Blog, Página web, e-commerce Directorios Intranets uso como API BackEnd-FrontEnd WPEngine headless server ¡Que tengas un Ingenioso día!

In the previous episodes, we looked at the rise of patents and software and their impact on the nascent computer industry. But a copyright is a right. And that right can be given to others in whole or in part. We have all benefited from software where the right to copy was waved and it's shaped the computing industry as much, if not more, than proprietary software. The term Free and Open Source Software (FOSS for short) is a blanket term to describe software that's free and/or whose source code is distributed for varying degrees of tinkeration. It's a movement and a choice. Programmers can commercialize our software. But we can also distribute it free of copy protections. And there are about as many licenses as there are opinions about what is unique, types of software, underlying components, etc. But given that many choose to commercialize their work products, how did a movement arise that specifically didn't? The early computers were custom-built to perform various tasks. Then computers and software were bought as a bundle and organizations could edit the source code. But as operating systems and languages evolved and businesses wanted their own custom logic, a cottage industry for software started to emerge. We see this in every industry - as an innovation becomes more mainstream, the expectations and needs of customers progress at an accelerated rate. That evolution took about 20 years to happen following World War II and by 1969, the software industry had evolved to the point that IBM faced antitrust charges for bundling software with hardware. And after that, the world of software would never be the same. The knock-on effect was that in the 1970s, Bell Labs pushed away from MULTICS and developed Unix, which AT&T then gave away as compiled code to researchers. And so proprietary software was a growing industry, which AT&T began charging for commercial licenses as the bushy hair and sideburns of the 70s were traded for the yuppy culture of the 80s. In the meantime, software had become copyrightable due to the findings of CONTU and the codifying of the Copyright Act of 1976. Bill Gates sent his infamous “Open Letter to Hobbyists” in 1976 as well, defending the right to charge for software in an exploding hobbyist market. And then Apple v Franklin led to the ability to copyright compiled code in 1983. There was a growing divide between those who'd been accustomed to being able to copy software freely and edit source code and those who in an up-market sense just needed supported software that worked - and were willing to pay for it, seeing the benefits that automation was having on the capabilities to scale an organization. And yet there were plenty who considered copyright software immoral. One of the best remembered is Richard Stallman, or RMS for short. Steven Levy described Stallman as “The Last of the True Hackers” in his epic book “Hackers: Heroes of the Computer Revolution.” In the book, he describes the MIT Stallman joined where there weren't passwords and we didn't yet pay for software and then goes through the emergence of the LISP language and the divide that formed between Richard Greenblatt, who wanted to keep The Hacker Ethic alive and those who wanted to commercialize LISP. The Hacker Ethic was born from the young MIT students who freely shared information and ideas with one another and help push forward computing in an era they thought was purer in a way, as though it hadn't yet been commercialized. The schism saw the death of the hacker culture and two projects came out of Stallman's technical work: emacs, which is a text editor that is still included freely in most modern Unix variants and the GNU project. Here's the thing, MIT was sitting on patents for things like core memory and thrived in part due to the commercialization or weaponization of the technology they were producing. The industry was maturing and since the days when kings granted patents, maturing technology would be commercialized using that system. And so Stallman's nostalgia gave us the GNU project, born from an idea that the industry moved faster in the days when information was freely shared and that knowledge was meant to be set free. For example, he wanted the source code for a printer driver so he could fix it and was told it was protected by an NDAQ and so couldn't have it. A couple of years later he announced GNU, a recursive acronym for GNU's Not Unix. The next year he built a compiler called GCC and the next year released the GNU Manifesto, launching the Free Software Foundation, often considered the charter of the free and open source software movement. Over the next few years as he worked on GNU, he found emacs had a license, GCC had a license, and the rising tide of free software was all distributed with unique licenses. And so the GNU General Public License was born in 1989 - allowing organizations and individuals to copy, distribute, and modify software covered under the license but with a small change, that if someone modified the source, they had to release that with any binaries they distributed as well. The University of California, Berkley had benefited from a lot of research grants over the years and many of their works could be put into the public domain. They had brought Unix in from Bell Labs in the 70s and Sun cofounder and Java author Bill Joy worked under professor Fabry, who brought Unix in. After working on a Pascal compiler that Unix coauthor Ken Thompson left for Berkeley, Joy and others started working on what would become BSD, not exactly a clone of Unix but with interchangeable parts. They bolted on the OSI model to get networking and through the 80s as Joy left for Sun and DEC got ahold of that source code there were variants and derivatives like FreeBSD, NetBSD, Darwin, and others. The licensing was pretty permissive and simple to understand: Copyright (c) . All rights reserved. Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the . The name of the may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. By 1990 the Board of Regents at Berkley accepted a four clause BSD license that spawned a class of licenses. While it's matured into other formats like a 0 clause license it's one of my favorites as it is truest to the FOSS cause. And the 90s gave us the Apache License, from the Apache Group, loosely based on the BSD License and then in 2004 leaning away from that with the release of the Apache License 2 that was more compatible with the GPL license. Given the modding nature of Apache they didn't require derivative works to also be open sourced but did require leaving the license in place for unmodified parts of the original work. GNU never really caught on as an OS in the mainstream, although a collection of tools did. The main reason the OS didn't go far is probably because Linus Torvalds started releasing prototypes of his Linux operating system in 1991. Torvalds used The GNU General Public License v2, or GPLv2 to license his kernel, having been inspired by a talk given by Stallman. GPL 2 had been released in 1991 and something else was happening as we turned into the 1990s: the Internet. Suddenly the software projects being worked on weren't just distributed on paper tape or floppy disks; they could be downloaded. The rise of Linux and Apache coincided and so many a web server and site ran that LAMP stack with MySQL and PHP added in there. All open source in varying flavors of what open source was at the time. And collaboration in the industry was at an all-time high. We got the rise of teams of developers who would edit and contribute to projects. One of these was a tool for another aspect of the Internet, email. It was called popclient, Here Eric S Raymond, or ESR for short, picked it up and renamed it to fetchmail, releasing it as an open source project. Raymond presented on his work at the Linux Congress in 1997, expanded that work into an essay and then the essay into “The Cathedral and the Bazaar” where bazaar is meant to be like an open market. That inspired many to open source their own works, including the Netscape team, which resulted in Mozilla and so Firefox - and another book called “Freeing the Source: The Story of Mozilla” from O'Reilly. By then, Tim O'Reilly was a huge proponent of this free or source code available type of software as it was known. And companies like VA Linux were growing fast. And many wanted to congeal around some common themes. So in 1998, Christine Peterson came up with the term “open source” in a meeting with Raymond, Todd Anderson, Larry Augustin, Sam Ockman, and Jon “Maddog” Hall, author of the first book I read on Linux. Free software it may or may not be but open source as a term quickly proliferated throughout the lands. By 1998 there was this funny little company called Tivo that was doing a public beta of a little box with a Linux kernel running on it that bootstrapped a pretty GUI to record TV shows on a hard drive on the box and play them back. You remember when we had to wait for a TV show, right? Or back when some super-fancy VCRs could record a show at a specific time to VHS (but mostly failed for one reason or another)? Well, Tivo meant to fix that. We did an episode on them a couple of years ago but we skipped the term Tivoization and the impact they had on GPL. As the 90s came to a close, VA Linux and Red Hat went through great IPOs, bringing about an era where open source could mean big business. And true to the cause, they shared enough stock with Linus Torvalds to make him a millionaire as well. And IBM pumped a billion dollars into open source, with Sun moving to open source openoffice.org. Now, what really happened there might be that by then Microsoft had become too big for anyone to effectively compete with and so they all tried to pivot around to find a niche, but it still benefited the world and open source in general. By Y2K there was a rapidly growing number of vendors out there putting Linux kernels onto embedded devices. TiVo happened to be one of the most visible. Some in the Linux community felt like they were being taken advantage of because suddenly you had a vendor making changes to the kernel but their changes only worked on their hardware and they blocked users from modifying the software. So The Free Software Foundation updated GPL, bundling in some other minor changes and we got the GNU General Public License (Version 3) in 2006. There was a lot more in GPL 3, given that so many organizations were involved in open source software by then. Here, the full license text and original copyright notice had to be included along with a statement of significant changes and making source code available with binaries. And commercial Unix variants struggled with SGI going bankrupt in 2006 and use of AIX and HP-UX Many of these open source projects flourished because of version control systems and the web. SourceForge was created by VA Software in 1999 and is a free service that can be used to host open source projects. Concurrent Versions System, or CVS had been written by Dick Grune back in 1986 and quickly became a popular way to have multiple developers work on projects, merging diffs of code repositories. That gave way to git in the hearts of many a programmer after Linus Torvalds wrote a new versioning system called git in 2005. GitHub came along in 2008 and was bought by Microsoft in 2018 for 2018. Seeing a need for people to ask questions about coding, Stack Overflow was created by Jeff Atwood and Joel Spolsky in 2008. Now, we could trade projects on one of the versioning tools, get help with projects or find smaller snippets of sample code on Stack Overflow, or even Google random things (and often find answers on Stack Overflow). And so social coding became a large part of many a programmers day. As did dependency management, given how many tools are used to compile a modern web app or app. I often wonder how much of the code in many of our favorite tools is actually original. Another thought is that in an industry dominated by white males, it's no surprise that we often gloss over previous contributions. It was actually Grace Hopper's A-2 compiler that was the first software that was released freely with source for all the world to adapt. Sure, you needed a UNIVAC to run it, and so it might fall into the mainframe era and with the emergence of minicomputers we got Digital Equipment's DECUS for sharing software, leading in part to the PDP-inspired need for source that Stallman was so adamant about. General Motors developed SHARE Operating System for the IBM 701 and made it available through the IBM user group called SHARE. The ARPAnet was free if you could get to it. TeX from Donald Knuth was free. The BASIC distribution from Dartmouth was academic and yet Microsoft sold it for up to $100,000 a license (see Commodore ). So it's no surprise that people avoided paying upstarts like Microsoft for their software or that it took until the late 70s to get copyright legislation and common law. But Hopper's contributions were kinda' like open source v1, the work from RMS to Linux was kinda' like open source v2, and once the term was coined and we got the rise of a name and more social coding platforms from SourceForge to git, we moved into a third version of the FOSS movement. Today, some tools are free, some are open source, some are free as in beer (as you find in many a gist), some are proprietary. All are valid. Today there are also about as many licenses as there are programmers putting software out there. And here's the thing, they're all valid. You see, every creator has the right to restrict the ability to copy their software. After all, it's their intellectual property. Anyone who chooses to charge for their software is well within their rights. Anyone choosing to eschew commercialization also has that right. And every derivative in between. I wouldn't judge anyone based on any model those choose. Just as those who distribute proprietary software shouldn't be judged for retaining their rights to do so. Why not just post things we want to make free? Patents, copyrights, and trademarks are all a part of intellectual property - but as developers of tools we also need to limit our liability as we're probably not out there buying large errors and omissions insurance policies for every script or project we make freely available. Also, we might want to limit the abuse of our marks. For example, Linus Torvalds monitors the use of the Linux mark through the Linux Mark Institute. Apparently some William Dell Croce Jr tried to register the Linux trademark in 1995 and Torvalds had to sue to get it back. He provides use of the mark using a free and perpetual global sublicense. Given that his wife won the Finnish karate championship six times I wouldn't be messing with his trademarks. Thank you to all the creators out there. Thank you for your contributions. And thank you for tuning in to this episode of the History of Computing Podcast. Have a great day.

Несколько эпичных провалов в безопасности, случившихся недавно у крупных компаний.1) Ubiquity, известный разработчик “просьюмерских” раутеров ещё в начале января заявила о “небольшом инциденте с безопасностью, который уже решён”. На деле же оказалось что злоумышленники получили полный доступ к инфраструктуре компании в AWS и другим критическим ресурсам. Забавнее всего, что это было сделано через взлом аккаунта LastPass одного из ведущих разработчиков, содержавшего все необходимые ключи и секреты. По словам инсайдера, злоумышленники получили доступ ко всем бакетам S3, логам, базам данных, аккаунтам пользователей и даже секретам для доступа на пользовательские устройства. В сети компании были установлены несколько виртуальных машин и бэкдоров для доступа в сеть. Когда сотрудники компании обнаружили активность и вычислили один из бэкдоров, хакеры потребовали 50 биткойнов за информацию о втором бэкдоре. Платить им не стали и в итоге нашли его сами. Хотя кто знает, а было ли их всего два. Особое возмущение общественности вызвал тот факт что Ubiquity преуменьшили масштаб проблемы из опасения что это негативно повлияет на курс акций, и просто рекомендовали пользователям сменить пароли вместо того чтоб сбросить их принудительно.2) Вторая новость того же порядка: в интернете выложили данные о 533 миллионах пользователях Facebook из 106 стран — данные включают телефоны, имена, адреса, даты рождения и для некоторых email-адреса. Многие из этих данных продолжают оставаться актуальными, что явно сыграет на руку скамерам и другим мошенникам. Забавно то, что в утекших данных есть и частичная информация об аккаунте Цукерберга. В Facebook заявили что эти данные — результат утечки 2019 года, которая “давно была устранена” и, судя по всему, не собираются уведомлять пострадавших пользователей, несмотря на то, что законы Евросоюза и Калифорнии прямо и непосредственно требуют это сделать. 3) Третья новость звучит как сценарий какого-то киберпанка, но это — не чья-то фантазия, а факт. ФБР в США получили разрешение от суда и начали операцию по "активному противодействию" распространению malware на тысячах серверов с Microsoft Exchange пострадавших недавно от уязвимостей. Проще говоря, хакеры-разведчики из ФБР будут вламываться на пострадавшие сервера и удалять последствия работы хакеров-шпионов.Как невинное изменение сломало Ruby on Rails и ряд других библиотек.Одной из важных зависимостей RoR является gem mimemagic, выпущенный под лицензией MIT. Оказалось, что этот gem в свою очередь зависит от стороннего кода, выпущенного под лицензией GPLv2. Разработчик gem-а решил устранить нарушение GPL (как все мы помним, она относится к “вирусным” лицензиям) и перевыпустил его под GPLv2, удалив попутно старые версии библиотеки под MIT лицензией. Это ожидаемо привело к поломке многих популярных библиотек, в том числе и Ruby on Rails. Последовало предложение хотя бы временно вернуть старые версии библиотеки, чтоб восстановить работоспособность, но автор mimemagic отказался это сделать. После некоторых раздумий, команда RoR заменила зависимость в своей библиотеке на mini_mime, но последствия некоторым командам программистов по всему миру приходится расхлёбывать до сих пор.Bonus тема: Что делать с токсичным сотрудником?Что делать руководителю проекта (команды, компании), если один из ключевых разработчиков оказался очень плох по софт-скилам и своей токсичностью отправляет жизнь других членов своей команды?

Ruby has gone off the rails this week, and Wes is here to explain what’s happened. Plus emails into the show send Chris into a full Linux panic.

✏️ Deja tu comentario Bienvenidos a este especial sobre GPL. Dejaremos claro en qué consiste esta licencia bajo la que está todo el software de WordPress y hablaremos de las polémicas, interpretaciones y debates morales que surgen a raíz de ello. Novedades Comenzamos las novedades con un pequeño vídeo para los amantes de la tecnología y los videojuegos. Yannick ha recibido Stadia como regalo de Elías y nos ha hecho un pequeño vídeo con sus primeras impresiones en su canal RetroPanik. https://www.youtube.com/watch?v=wcEhs4g-15I Tras la actualización de Elementor PRO a su versión 3, se nos planetea una nueva forma de trabajo donde podemos definir estilos globales o estilos del tema. De esta forma el flujo de trabajo estará más optimizado (y la web también). Si queréis saber cómo se hace todo esto, lo mejor es echar un ojo al vídeo que ha subido Yannick a la Zona Premium de La Máquina del Branding. https://lamaquinadelbranding.com/definiendo-estilos-globales-con-elementor-pro/ Por cierto, Yannick nos avisa de un pequeño fallo en uno de sus vídeos donde no aparece un detalle muy importante. Y es que para crear un formulario de Jet Booking que genere un pedido no hay que poner el campo order_ID en el formulario. Tiene sentido, pues es un nuevo pedido que generará un nuevo ID. Elías nos trae noticias interesantes del mundo digital. Clickup, Hyundai y Boston Dynamics son los implicados. Aquí tenéis el enlace a las noticias de la semana de Elías Gómez. https://eliasgomez.pro/curacion/%f0%9f%a4%96-hyundai-compra-al-fabricante-de-robots-boston-dynamics-por-921-millones-de-dolares-para-incorporarlos-en-su-cadena-de-montaje/ https://eliasgomez.pro/curacion/%f0%9f%94%81-clickup-lanza-las-nuevas-relaciones-mejorando-muchas-las-tareas-y-avanzando-un-poco-mas-para-reemplazar-a-airtable/ https://eliasgomez.pro/curacion/%f0%9f%92%b6-clickup-obtiene-otros-100-millones-de-dolares-para-mejorar-su-plataforma-en-estabilidad-y-funcionalidades/ WordPress y la GPL Y nos vamos al tema de la semana. Muchísimas gracias a todos por el feedback en directo. Los temas que tratamos durante el episodio son los siguientes. Qué es una licencia de software (https://es.wikipedia.org/wiki/Licencia_de_software)Qué dice la licencia GPL https://www.gnu.org/licenses/gpl-faq.es.html#WhatDoesGPLStandFor)Los 4 Derechos (De uso, de análisis, de modificación, de distribución)El factor hereditarioPolémica, interpretaciones y debates moralesQuienes quieren que los usuarios compren el software al desarrollador y no lo puedan revender, compartir o adquirir en otros sitios.Quienes quieren que los usuarios aporten algo a la comunidad a cambio de las libertades que permite la GPL.Quienes desarrollan software para WordPress que no funciona si no introduces una licencia comprada al desarrollador.Nuestra postura Os dejamos también por aquí un par de cuestione sinteresantes explicadas en esa FAQ de GNU. Algunas cosas interesantes de esa FAQHe descubierto que una empresa tiene una copia de un programa bajo la GPL y que para conseguirla hay que pagar. ¿No están vulnerando la GPL al no ponerlo a disposición en Internet? (#CompanyGPLCostsMoney) No. La GPL no exige a nadie usar Internet para la distribución. Tampoco exige a nadie en particular que redistribuya el programa. Y (aparte de un caso especial), aun cuando alguien decida a veces redistribuir el programa, la GPL no dice que tenga que facilitarle una copia a usted o a cualquier otra persona en particular.Lo que exige la GPL es que ha de tener la libertad de facilitarle a usted una copia, si así lo desea. Una vez el titular del copyright distribuye una copia del programa a alguien, ese alguien puede luego redistribuir el programa a usted o a cualquier otra persona, como crea conveniente. ¿Me autoriza la GPL a exigir que cualquiera que reciba el software haya de abonarme alguna cantidad o notificármelo? (#DoesTheGPLAllowRequireFee)No. De hecho, una exigencia de ese tipo haría que el programa no sea libre. Si la gente tiene que pagar cuando obtiene una copia del programa, o si tiene que notificárselo a alguien en particular, entonces el programa no es libre. Véase la definición de software libre.La GPL es una licencia de software libre, y por tanto permite el uso e incluso la redistribución de los programas sin que para hacerlo haya que pagarle nada a nadie.Sí puede cobrar cuando es usted mismo quien entrega la copia. No puede exigir ningún pago cuando quien entrega la copia es alguna otra persona. Si distribuyo software con licencia GPL a cambio de dinero, ¿es necesario que lo ponga a disposición también gratuitamente? (#DoesTheGPLRequireAvailabilityToPublic)No. No obstante, si alguien abona esa cantidad y obtiene una copia, la GPL le concede la libertad de publicarla poniéndole un precio o no. Por ejemplo, alguien podría pagarle el precio y después colgar una copia en su sitio web para el público en general. Herramientas isapplesiliconready.comElías nos trae esta herramienta para comprobar si una aplicación es compatible con Apple Silicon. Enlaces STADIA - Primeras impresiones - ¿Hay input lag?Definiendo estilos globales con ELEMENTOR PRO

✏️ Deja tu comentarioCompletito episodio para todos los gustos. Trataremos temas de diseño gráfico, ciencia del color, hablaremos sobre salseo WordPress con la polémica surgida a raíz de lo acontecido con el plugin de Redsys de José Conti, os contaremos experiencias y trucos para WordPress y como siempre, os traeremos las novedades más destacadas de la semana. Novedades Comenzamos hablando sobre la WWDC 2020, la keynote de Apple que nos ha sorprendido con una puesta en escena virtual. Os dejamos con este resumen de 18 minutos. https://youtu.be/_Q8AKghK44M Comentamos también un par de novedades que Elías nos dejó por Twitter. Una de ellas, relacionada precisamente con Twitter y sus listas de usuarios. La otra acerca del nuevo límite de 32 usuarios en Google Duo desde Chrome. https://twitter.com/EliasNS/status/1276063842255192065 https://twitter.com/EliasNS/status/1275858230149820420 Comenzamos con los salseos y el drama. Y lo hacemos con la problemática que José Conti advierte en muchos profesionales que, aún haciendo uso legítimo de la GPL, no cumplen, a su parecer, con un mínimo moral que vaya acorde a la filosofía de esta licencia. Esperamos que nos digáis qué opináis sobre todo esto. Si queréis información de primera mano, os recomendamos la lectura de estos 2 artículos: Vivir GPL o explotar GPLA vueltas con la licencia GPLv2 y WordPress El segundo WPdrama lo tenemos con JetPack. Ahora ha decidido incluir un módulo, activo por defecto y sin previo aviso, que analiza los datos de tu tienda online y los envía directamente a Auttomatic. En AyudaWP te explican lo que puedes hacer al respecto: https://ayudawp.com/jetpack-woocommerce-analytics/#%C2%BFQue_hago Elías nos trae una herramienta, que cae en la sección de novedades semanales ya que la ha tenido que utilizar en un proyecto propio. Y es que esta web te permite previsualizar todo tipo de material de merchandising, como camisetas, con la imagen adherida al objeto y totalmente integrada aún disponiendo de múltiples ángulos de vista del producto. Se trata del generador de Printful. Pasamos a Yannick que nos trae un par de curiosidades sobre el color, cómo lo percibimos, cuáles son realmente los colores primarios y por qué, en cierto modo, el magenta no existe. Toma ya. Seguimos con el mundo del diseño y reflexionamos acerca de los logotipos con símbolos o isotipos abstractos. ¿Son mejores o simplemente es otra forma de representar una marca igualmente válida? Otra herramienta que se cuela en el bloque de Novedades ya que Yannick ha tenido que utilizarla para extraer un listado de las urls de un sitio web. El plugin en cuestión se llama Export All URLs. https://es.wordpress.org/plugins/export-all-urls/ Hablaremos también de la importancia de los artículos de marca que hablan de la competencia en comparativas y contenidos similares. Y de paso recomendaremos la herramienta CookieFirst que Yannick ha encontrado como alternativa a CookieBot. ¡Y pasamos a la Máquina del Branding, cuyo canal de YouTube ha alcanzado los 8.000 suscriptores! Como siempre, hablaremos sobre los nuevos contenidos de la Zona Premium y en particular sobre un tutorial que nos presenta a los Tokens, una especie de códigos dinámicos que gracias al plugin Dynamic Content nos permite extraer datos de cualquier tipo y jugar con ellos. https://lamaquinadelbranding.com/tokens-introduccion-opciones-textos-y-formularios-con-los-tokens-de-dynamic-content/ https://lamaquinadelbranding.com/importar-csv-con-posts-taxonomias-o-campos-a-wordpress-compatible-con-jet-engine-wp-all-import/ https://lamaquinadelbranding.com/crea-enlaces-internos-automaticos-con-internal-link-juicer-seo-auto-linker/ Y terminamos las novedades analizando las tareas de Elías que podemos resumir en la preparación de camisetas para su venta, realización de 2 directos de "A Quemar Zapatillas de Casa" y un tema complicado acerca de Quancast. Sobre esto último, Elías nos explicará de qué se trata y os pide feedback sobre si sabéis del tema. Feedback Esta semana agradecemos las palabras de ánimo de nuestros oyentes que nos agradecen el tipo de contenido que creamos tanto en Negocios y WordPress como en La Máquina del Branding. Muchas gracias chicos. Herramientas AWPCP – Classifieds PluginMonta un sistema de anuncios clasificados al estilo de Milanuncios utilizando este plugin para WordPress. SEO Data TransporterTransfiere datos entre los plugins de SEO más conocidos, e incluso entre temas o plantillas de WordPress. Enlaces Magenta Ain't A ColourPrintful - Generador de maquetas y archivos de impresiónVivir GPL o explotar GPLA vueltas con la licencia GPLv2 y WordPressApple WWDC 2020 keynote in 18 minutesTOKENS - Introducción, opciones, textos y formularios con los TOKENS de Dynamic ContentIMPORTAR CSV con Posts, Taxonomías o Campos a WordPress (Compatible con JET Engine) - WP All ImportCrea ENLACES INTERNOS automáticos con Internal Link Juicer: SEO Auto LinkerJetPack espía las ventas y productos de tu tienda online WooCommerce

Sinceramente esto de convertir formatos multimedia cada vez lo hago menos. Salvo el script que cree hace algún tiempo para crear un video a partir de un audio para tener el podcast en YouTube, lo cierto es que cada vez lo hago menos. Esto creo que es debido principalmente a dos razones. Por un lado, está el tema que cada vez consumo mas multimedia vía streaming. Por otro lado, antes utilizaba algún dispositivo para consumir el contenido multimedia que tenía problemas con determinados formatos. Sin embargo, actualmente, todo el contenido multimedia que consumo, lo hago a través de dispositivos Android. Ya sea en el móvil, que en este caso es principalmente podcast o en la TV, para lo que utilizo un TVBox. Sin embargo, esta es mi situación. Es probable que tu estés consumiendo el contenido multimedia, en algún dispositivo que no permite uno u otro formato. Si este es tu caso, en el episodio del podcast de hoy, precisamente quiero tratar la conversión entre formatos multimedia en Linux. Convertir formatos multimedia en Linux Como te he comentado en la introducción, el objetivo del podcast de hoy es ver diferentes herramientas y aplicaciones, que te permitan convertir entre diferentes formatos multimedia de forma sencilla, y sin excesivas complicaciones. En este sentido, como hago normalmente, te voy a mostrar algunas herramientas, para el entorno de escritorio, y otras que son para utilizar directamente en el terminal. ¿porque utilizar el terminal para la conversión de archivos? Que te voy a decir. Sin lugar a dudas, la conversión de formatos es carne de automatización. Así, puedes utilizar dos técnicas, Mediante un cron que cada cierto tiempo revise lo que contienes en un determinado directorio, y si tienes un formato determinado lo convierte a otroDetectando que se han producido cambios en el directorio. En el caso de que así sea, se lanza un script que realice la conversión, si se encuentra algún archivo con el formato a convertir. Sin embargo, esto te lo comentaré mas adelante para que tu seas el que decida… Antes, primero te quiero comentar las herramientas gráficas. Herramientas gráficas HandBrake Como dicen los propios desarrolladores de HandBrake, esta aplicación, es una herramienta para convertir vídeo de casi cualquier formato, a una selección codecs actuales y ampliamente soportados. Se trata de una herramienta multiplataforma, disponible para los tres grandes sistemas operativos de escritorio, Linux, MacOs y Windows, que es Open Source, liberado bajo licencia GPLv2, y gratuita. Encontrarás toda la información en las notas del podcast sobre convertir formatos multimedia en Linux

Sinceramente esto de convertir formatos multimedia cada vez lo hago menos. Salvo el script que cree hace algún tiempo para crear un video a partir de un audio para tener el podcast en YouTube, lo cierto es que cada vez lo hago menos. Esto creo que es debido principalmente a dos razones. Por un lado, está el tema que cada vez consumo mas multimedia vía streaming. Por otro lado, antes utilizaba algún dispositivo para consumir el contenido multimedia que tenía problemas con determinados formatos. Sin embargo, actualmente, todo el contenido multimedia que consumo, lo hago a través de dispositivos Android. Ya sea en el móvil, que en este caso es principalmente podcast o en la TV, para lo que utilizo un TVBox. Sin embargo, esta es mi situación. Es probable que tu estés consumiendo el contenido multimedia, en algún dispositivo que no permite uno u otro formato. Si este es tu caso, en el episodio del podcast de hoy, precisamente quiero tratar la conversión entre formatos multimedia en Linux. Convertir formatos multimedia en Linux Como te he comentado en la introducción, el objetivo del podcast de hoy es ver diferentes herramientas y aplicaciones, que te permitan convertir entre diferentes formatos multimedia de forma sencilla, y sin excesivas complicaciones. En este sentido, como hago normalmente, te voy a mostrar algunas herramientas, para el entorno de escritorio, y otras que son para utilizar directamente en el terminal. ¿porque utilizar el terminal para la conversión de archivos? Que te voy a decir. Sin lugar a dudas, la conversión de formatos es carne de automatización. Así, puedes utilizar dos técnicas, Mediante un cron que cada cierto tiempo revise lo que contienes en un determinado directorio, y si tienes un formato determinado lo convierte a otroDetectando que se han producido cambios en el directorio. En el caso de que así sea, se lanza un script que realice la conversión, si se encuentra algún archivo con el formato a convertir. Sin embargo, esto te lo comentaré mas adelante para que tu seas el que decida… Antes, primero te quiero comentar las herramientas gráficas. Herramientas gráficas HandBrake Como dicen los propios desarrolladores de HandBrake, esta aplicación, es una herramienta para convertir vídeo de casi cualquier formato, a una selección codecs actuales y ampliamente soportados. Se trata de una herramienta multiplataforma, disponible para los tres grandes sistemas operativos de escritorio, Linux, MacOs y Windows, que es Open Source, liberado bajo licencia GPLv2, y gratuita. Encontrarás toda la información en las notas del podcast sobre convertir formatos multimedia en Linux

Description iOS 13 will be able to automatically silence any calls coming in from an unknown number. The new "silence unknown callers" option can be toggled on or off based on your preference, but I'm thinking most people will enable it right after updating. So many of the spam calls we're bombarded with on a daily basis are spoofed to look like a local number. But Apple says that iOS 13 will "use Siri intelligence to allow calls to ring your phone from numbers in Contacts, Mail, and Messages." Any number that can't be found in one of those places will be routed to voicemail. More The Russian government has added dating service Tinder on a government database that legally forces the company to hand over user data and private communications to the country's law enforcement and intelligence agencies. According to Russian laws, companies added to this database must hand over data to Russian police or Russian intelligence agencies like in order to help with investigations into terrorist and national security cases. More All newly created user accounts in macOS Catalina will use zee shell by default. Bash shell will still be available, but Apple is signaling that developers should start moving to zee shell on macOS Mojave. Apple hasn't explained exactly why it's making this change, but bash isn't exactly a modern shell. Apple is stuck using version 3.2 of bash that has been licensed under GPLv2, as newer versions are licensed under GPLv3. Apple has kept clear of using GPLv3 packages in macOS as the license is generally more restrictive to companies like Apple that sign their own code and it includes explicit patent grants, too. More --- Send in a voice message: https://anchor.fm/iamrp/message

Bradley and Karen discuss two additional permissions that can be used to “backport” the GPLv3 Termination provisions to GPLv2 — the Kernel Enforcement Statement Additional Permission, and the Red Hat Cooperation Commitment. A blog post on Conservancy's site summarizes the discussion on this show. Show Notes: Segment 0 (00:35) Bradley mentioned irregardless is not actually a word, but it does appear to be slang, which dates back to 1795! (03:23) The additional permission system was codified as a formal part of GPLv3, but are generally more informal under GPLv2. (05:24) Karen explained what the Principles of Community-Oriented GPL Enforcement. (07:49) Karen mentioned that Daleks terminate! (08:51) Segment 1 (13:04) Bradley mentioned the inbound=outbound FOSS licensing contributor assent system (18:15) Segment 2 (26:10) Karen and Bradley discuss the term “non-defensive” and what it means. Bradley mentioned the Twin Peaks lawsuit as a non-hypothetical case where the RHCC would not apply where GPL enforcement was used by Red Hat itself as a retaliation tactic. (29:23) The Kernel Enforcement Statement and the RHCC are available online. Segment 3 (38:40) The next episode of will be an interview with Molly De Blanc and recording of her keynote at CopyleftConf 2019 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).

Bradley and Karen discuss two additional permissions that can be used to “backport” the GPLv3 Termination provisions to GPLv2 — the Kernel Enforcement Statement Additional Permission, and the Red Hat Cooperation Commitment. A blog post on Conservancy's site summarizes the discussion on this show. Show Notes: Segment 0 (00:35) Bradley mentioned irregardless is not actually a word, but it does appear to be slang, which dates back to 1795! (03:23) The additional permission system was codified as a formal part of GPLv3, but are generally more informal under GPLv2. (05:24) Karen explained what the Principles of Community-Oriented GPL Enforcement. (07:49) Karen mentioned that Daleks terminate! (08:51) Segment 1 (13:04) Bradley mentioned the inbound=outbound FOSS licensing contributor assent system (18:15) Segment 2 (26:10) Karen and Bradley discuss the term “non-defensive” and what it means. Bradley mentioned the Twin Peaks lawsuit as a non-hypothetical case where the RHCC would not apply where GPL enforcement was used by Red Hat itself as a retaliation tactic. (29:23) The Kernel Enforcement Statement and the RHCC are available online. Segment 3 (38:40) The next episode of will be an interview with Molly De Blanc and recording of her keynote at CopyleftConf 2019 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 on Twitter and and FaiF on 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).

Dans cet épisode Emmanuel est de retour et assure l’intérim de Guillaume sur les blagues tout en discutant Java 10, Kubernetes et son écosystème, départs, rachats et IPO mais aussi diversité et Facebook avec Arnaud, Audrey et Vincent. Merci à Morgan pour sa crowdquestion sur les logs ! Enregistré le 29 mars 2018 Téléchargement de l’épisode LesCastCodeurs-Episode–186.mp3 News Langages The baby and the bathwater The Oracle JDK (java.oracle.com) will not be freely available as of #JDK11. This is the one that has LTS. The #OpenJDK binary (GPLv2 with CPE license) will be free, but only have updates until the next release (6 months, 2 scheduled updates). Simon Ritter Style Guidelines for Local Variable Type Inference in Java Introducing Java SE 10 * JDK 10 General-Availability Release A Proposal for Package Versioning in Go Librairies Apache Spark 2.3.0 Vavr one log 01 Middleware SpringBoot 2 performance — servlet stack vs WebFlux reactive stack Salesforce achete Mulesoft pour 6 milliards$ Pivotal lance son offre publique d’achat Micronaut framework Infrastructure Retour utilisation Prometheus Cloud Solomon Hykes quitte Docker Java 10 will no longer sucks on Docker Kubernetes 1.10 Web Polymer 3.0 Capacitor 1.0.0 Data Facebook et les appels téléphoniques: Details techniques sur comment trouver Article du monde Outillage Introducing Skaffold: Easy and repeatable Kubernetes development Building Container Images Securely on Kubernetes IntelliJ IDEA 2018.1: Kubernetes support Jenkins X Jenkins Configuration as Code Plugin Gradle 4.6.0 Apache Maven 3.5.3 Open Source à la MAIF Architecture Que se passe-t-il quand vous appuyez sur lecture dans Netflix ? Méthodologies Greve perlee Sécurité GitHub survived the biggest DDOS attack ever recorded ACME v2 and Wildcard Certificate Support is Live TLS 1.3 ratifié : Qu’est-ce que TLS 1.3 Ratification Loi, société et organisation A counterintuitive way to increase diversity in tech Les nouveaux outils de Slack: un espion au service des patrons ? Revealed: 50 million Facebook profiles harvested for Cambridge Analytica in major data breach Inside the Two Years that shook Facebook - and the World EU wants to require platforms to filter uploaded content (including code) Oracle Wins Court Ruling Against Google in Multibillion-Dollar Copyright Case Crowdquestion Morgan Durand sur les logs Conférences Devoxx France du 18 au 20 avril 2018 - Le programme est publié dites nous ce qui vous plait ( mercredi, jeudi, vendredi ) MixIT le 19–20 avril 2018 à Lyon Riviera Dev les 2, 3 et 4 mai 2018 à Sophia Antipolis NCrafts les 18 et 19 mai 2018 Best Of Web les 7 et 8 juin 2018 EclipseCon les 13 et 14 juin 2018 JHipster Conf le 21 juin DevFest Lille le 21 juin 2018 Voxxed Luxembourg le 22 juin 2018 Sunny Tech les 28 et 29 juin 2018 Jenkins User Conference le 28 juin 2018 - Le CfP est ouvert jusqu’au 15 avril. Paris Web les 4, 5 et 6 octobre 2018 Jenkins World Europe du 22 au 25 octobre 2018 à Nice - Le CfP est ouvert jusqu’au 15 avril - Les inscriptions sont ouvertes (utilisez le code JWAHERITIER pour obtenir 20% de réduction). DevFest Toulouse le 8 novembre 2018 Nous contacter Faire un crowdcast ou une crowdquestion Contactez-nous via twitter https://twitter.com/lescastcodeurs sur le groupe Google https://groups.google.com/group/lescastcodeurs ou sur le site web https://lescastcodeurs.com/ Flattr-ez nous (dons) sur https://lescastcodeurs.com/ En savoir plus sur le sponsoring? sponsors@lescastcodeurs.com

We explain the physics behind ZFS, DTrace switching to the GPL, Emacs debugging, syncookies coming to PF & FreeBSD's history on EC2. This episode was brought to you by Headlines 128 bit storage: Are you high? (https://blogs.oracle.com/bonwick/128-bit-storage:-are-you-high) For people who have heard about ZFS boiling oceans and wonder where that is coming from, we dug out this old piece from 2004 on the blog of ZFS co-creator Jeff Bonwick, originally from the Sun website. 64 bits would have been plenty ... but then you can't talk out of your ass about boiling oceans then, can you? Well, it's a fair question. Why did we make ZFS a 128-bit storage system? What on earth made us think it's necessary? And how do we know it's sufficient? Let's start with the easy one: how do we know it's necessary? Some customers already have datasets on the order of a petabyte, or 2^50 bytes. Thus the 64-bit capacity limit of 2^64 bytes is only 14 doublings away. Moore's Law for storage predicts that capacity will continue to double every 9-12 months, which means we'll start to hit the 64-bit limit in about a decade. Storage systems tend to live for several decades, so it would be foolish to create a new one without anticipating the needs that will surely arise within its projected lifetime. If 64 bits isn't enough, the next logical step is 128 bits. That's enough to survive Moore's Law until I'm dead, and after that, it's not my problem. But it does raise the question: what are the theoretical limits to storage capacity? Although we'd all like Moore's Law to continue forever, quantum mechanics imposes some fundamental limits on the computation rate and information capacity of any physical device. In particular, it has been shown that 1 kilogram of matter confined to 1 liter of space can perform at most 10^51 operations per second on at most 10^31 bits of information [see Seth Lloyd, "Ultimate physical limits to computation." Nature 406, 1047-1054 (2000)]. A fully-populated 128-bit storage pool would contain 2^128 blocks = 2^137 bytes = 2^140 bits; therefore the minimum mass required to hold the bits would be (2^140 bits) / (10^31 bits/kg) = 136 billion kg. That's a lot of gear. To operate at the 1031 bits/kg limit, however, the entire mass of the computer must be in the form of pure energy. By E=mc^2, the rest energy of 136 billion kg is 1.2x1028 J. The mass of the oceans is about 1.4x1021 kg. It takes about 4,000 J to raise the temperature of 1 kg of water by 1 degree Celcius, and thus about 400,000 J to heat 1 kg of water from freezing to boiling. The latent heat of vaporization adds another 2 million J/kg. Thus the energy required to boil the oceans is about 2.4x106 J/kg * 1.4x1021 kg = 3.4x1027 J. Thus, fully populating a 128-bit storage pool would, literally, require more energy than boiling the oceans. Best part of all: you don't have to understand any of this to use ZFS. Rest assured that you won't hit any limits with that filesystem for a long time. You still have to buy bigger disks over time, though... *** dtrace for Linux, Oracle relicenses dtrace (https://gnu.wildebeest.org/blog/mjw/2018/02/14/dtrace-for-linux-oracle-does-the-right-thing/) At Fosdem we had a talk on dtrace for linux in the Debugging Tools devroom. Not explicitly mentioned in that talk, but certainly the most exciting thing, is that Oracle is doing a proper linux kernel port: ``` commit e1744f50ee9bc1978d41db7cc93bcf30687853e6 Author: Tomas Jedlicka tomas.jedlicka@oracle.com Date: Tue Aug 1 09:15:44 2017 -0400 dtrace: Integrate DTrace Modules into kernel proper This changeset integrates DTrace module sources into the main kernel source tree under the GPLv2 license. Sources have been moved to appropriate locations in the kernel tree. ``` That is right, dtrace dropped the CDDL and switched to the GPL! The user space code dtrace-utils and libdtrace-ctf (a combination of GPLv2 and UPL) can be found on the DTrace Project Source Control page. The NEWS file mentions the license switch (and that it is build upon elfutils, which I personally was pleased to find out). The kernel sources (GPLv2+ for the core kernel and UPL for the uapi) are slightly harder to find because they are inside the uek kernel source tree, but following the above commit you can easily get at the whole linux kernel dtrace directory. The UPL is the Universal Permissive License, which according to the FSF is a lax, non-copyleft license that is compatible with the GNU GPL. Thank you Oracle for making everyone's life easier by waving your magic relicensing wand! Now there is lots of hard work to do to actually properly integrate this. And I am sure there are a lot of technical hurdles when trying to get this upstreamed into the mainline kernel. But that is just hard work. Which we can now start collaborating on in earnest. Like systemtap and the Dynamic Probes (dprobes) before it, dtrace is a whole system observability tool combining tracing, profiling and probing/debugging techniques. Something the upstream linux kernel hackers don't always appreciate when presented as one large system. They prefer having separate small tweaks for tracing, profiling and probing which are mostly separate from each other. It took years for the various hooks, kprobes, uprobes, markers, etc. from systemtap (and other systems) to get upstream. But these days they are. And there is now even a byte code interpreter (eBPF) in the mainline kernel as originally envisioned by dprobes, which systemtap can now target through stapbpf. So with all those techniques now available in the linux kernel it will be exciting to see if dtrace for linux can unite them all. Debugging Emacs or: How I Learned to Stop Worrying and Love DTrace (http://nullprogram.com/blog/2018/01/17/) For some time Elfeed was experiencing a strange, spurious failure. Every so often users were seeing an error (spoiler warning) when updating feeds: “error in process sentinel: Search failed.” If you use Elfeed, you might have even seen this yourself. From the surface it appeared that curl, tasked with the responsibility for downloading feed data, was producing incomplete output despite reporting a successful run. Since the run was successful, Elfeed assumed certain data was in curl's output buffer, but, since it wasn't, it failed hard. Unfortunately this issue was not reproducible. Manually running curl outside of Emacs never revealed any issues. Asking Elfeed to retry fetching the feeds would work fine. The issue would only randomly rear its head when Elfeed was fetching many feeds in parallel, under stress. By the time the error was discovered, the curl process had exited and vital debugging information was lost. Considering that this was likely to be a bug in Emacs itself, there really wasn't a reliable way to capture the necessary debugging information from within Emacs Lisp. And, indeed, this later proved to be the case. A quick-and-dirty work around is to use condition-case to catch and swallow the error. When the bizarre issue shows up, rather than fail badly in front of the user, Elfeed could attempt to swallow the error — assuming it can be reliably detected — and treat the fetch as simply a failure. That didn't sit comfortably with me. Elfeed had done its due diligence checking for errors already. Someone was lying to Elfeed, and I intended to catch them with their pants on fire. Someday. I'd just need to witness the bug on one of my own machines. Elfeed is part of my daily routine, so surely I'd have to experience this issue myself someday. My plan was, should that day come, to run a modified Elfeed, instrumented to capture extra data. I would have also routinely run Emacs under GDB so that I could inspect the failure more deeply. For now I just had to wait to hunt that zebra. Bryan Cantrill, DTrace, and FreeBSD Over the holidays I re-discovered Bryan Cantrill, a systems software engineer who worked for Sun between 1996 and 2010, and is most well known for DTrace. My first exposure to him was in a BSD Now interview in 2015. I had re-watched that interview and decided there was a lot more I had to learn from him. He's become a personal hero to me. So I scoured the internet for more of his writing and talks. Some interesting operating system technology came out of Sun during its final 15 or so years — most notably DTrace and ZFS — and Bryan speaks about it passionately. Almost as a matter of luck, most of it survived the Oracle acquisition thanks to Sun releasing it as open source in just the nick of time. Otherwise it would have been lost forever. The scattered ex-Sun employees, still passionate about their prior work at Sun, along with some of their old customers have since picked up the pieces and kept going as a community under the name illumos. It's like an open source flotilla. Naturally I wanted to get my hands on this stuff to try it out for myself. Is it really as good as they say? Normally I stick to Linux, but it (generally) doesn't have these Sun technologies available. The main reason is license incompatibility. Sun released its code under the CDDL, which is incompatible with the GPL. Ubuntu does infamously include ZFS, but other distributions are unwilling to take that risk. Porting DTrace is a serious undertaking since it's got its fingers throughout the kernel, which also makes the licensing issues even more complicated. Linux has a reputation for Not Invented Here (NIH) syndrome, and these licensing issues certainly contribute to that. Rather than adopt ZFS and DTrace, they've been reinvented from scratch: btrfs instead of ZFS, and a slew of partial options instead of DTrace. Normally I'm most interested in system call tracing, and my go to is strace, though it certainly has its limitations — including this situation of debugging curl under Emacs. Another famous example of NIH is Linux's epoll(2), which is a broken version of BSD kqueue(2). So, if I want to try these for myself, I'll need to install a different operating system. I've dabbled with OmniOS, an OS built on illumos, in virtual machines, using it as an alien environment to test some of my software (e.g. enchive). OmniOS has a philosophy called Keep Your Software To Yourself (KYSTY), which is really just code for “we don't do packaging.” Honestly, you can't blame them since they're a tiny community. The best solution to this is probably pkgsrc, which is essentially a universal packaging system. Otherwise you're on your own. There's also openindiana, which is a more friendly desktop-oriented illumos distribution. Still, the short of it is that you're very much on your own when things don't work. The situation is like running Linux a couple decades ago, when it was still difficult to do. If you're interested in trying DTrace, the easiest option these days is probably FreeBSD. It's got a big, active community, thorough documentation, and a huge selection of packages. Its license (the BSD license, duh) is compatible with the CDDL, so both ZFS and DTrace have been ported to FreeBSD. What is DTrace? I've done all this talking but haven't yet described what DTrace really is. I won't pretend to write my own tutorial, but I'll provide enough information to follow along. DTrace is a tracing framework for debugging production systems in real time, both for the kernel and for applications. The “production systems” part means it's stable and safe — using DTrace won't put your system at risk of crashing or damaging data. The “real time” part means it has little impact on performance. You can use DTrace on live, active systems with little impact. Both of these core design principles are vital for troubleshooting those really tricky bugs that only show up in production. There are DTrace probes scattered all throughout the system: on system calls, scheduler events, networking events, process events, signals, virtual memory events, etc. Using a specialized language called D (unrelated to the general purpose programming language D), you can dynamically add behavior at these instrumentation points. Generally the behavior is to capture information, but it can also manipulate the event being traced. Each probe is fully identified by a 4-tuple delimited by colons: provider, module, function, and probe name. An empty element denotes a sort of wildcard. For example, syscall::open:entry is a probe at the beginning (i.e. “entry”) of open(2). syscall:::entry matches all system call entry probes. Unlike strace on Linux which monitors a specific process, DTrace applies to the entire system when active. To run curl under strace from Emacs, I'd have to modify Emacs' behavior to do so. With DTrace I can instrument every curl process without making a single change to Emacs, and with negligible impact to Emacs. That's a big deal. So, when it comes to this Elfeed issue, FreeBSD is much better poised for debugging the problem. All I have to do is catch it in the act. However, it's been months since that bug report and I'm not really making this connection yet. I'm just hoping I eventually find an interesting problem where I can apply DTrace. Bryan Cantrill: Talks I have given (http://dtrace.org/blogs/bmc/2018/02/03/talks/) *** News Roundup a2k18 Hackathon preview: Syncookies coming to PF (https://undeadly.org/cgi?action=article;sid=20180207090000) As you may have heard, the a2k18 hackathon is in progress. As can be seen from the commit messages, several items of goodness are being worked on. One eagerly anticipated item is the arrival of TCP syncookies (read: another important tool in your anti-DDoS toolset) in PF. Henning Brauer (henning@) added the code in a series of commits on February 6th, 2018, with this one containing the explanation: ``` syncookies for pf. when syncookies are on, pf will blindly answer each and every SYN with a syncookie-SYNACK. Upon reception of the ACK completing the 3WHS, pf will reconstruct the original SYN, shove it through pf_test, where state will be created if the ruleset permits it. Then massage the freshly created state (we won't see the SYNACK), set up the sequence number modulator, and call into the existing synproxy code to start the 3WHS with the backend host. Add an - somewhat basic for now - adaptive mode where syncookies get enabled if a certain percentage of the state table is filled up with half-open tcp connections. This makes pf firewalls resilient against large synflood attacks. syncookies are off by default until we gained more experience, considered experimental for now. see http://bulabula.org/papers/2017/bsdcan/ for more details. joint work with sashan@, widely discussed and with lots of input by many ``` The first release to have this feature available will probably be the upcoming OpenBSD 6.3 if a sufficient number of people test this in their setups (hint, hint). More info is likely to emerge soon in post-hackathon writeups, so watch this space! [Pale Moon] A Perfect example of how not to approach OS developers/packagers Removed from OpenBSD Ports due to Licensing Issues (https://github.com/jasperla/openbsd-wip/issues/86) FreeBSD Palemoon branding violation (https://lists.freebsd.org/pipermail/freebsd-ports/2018-February/112455.html) Mightnight BSD's response (https://twitter.com/midnightbsd/status/961232422091280386) *** FreeBSD EC2 History (http://www.daemonology.net/blog/2018-02-12-FreeBSD-EC2-history.html) A couple years ago Jeff Barr published a blog post with a timeline of EC2 instances. I thought at the time that I should write up a timeline of the FreeBSD/EC2 platform, but I didn't get around to it; but last week, as I prepared to ask for sponsorship for my work I decided that it was time to sit down and collect together the long history of how the platform has evolved and improved over the years. Normally I don't edit blog posts after publishing them (with the exception of occasional typographical corrections), but I do plan on keeping this post up to date with future developments. August 25, 2006: Amazon EC2 launches. It supports a single version of Ubuntu Linux; FreeBSD is not available. December 13, 2010: I manage to get FreeBSD running on EC2 t1.micro instances. March 22, 2011: I manage to get FreeBSD running on EC2 "cluster compute" instances. July 8, 2011: I get FreeBSD 8.2 running on all 64-bit EC2 instance types, by marking it as "Windows" in order to get access to Xen/HVM virtualization. (Unfortunately this meant that users had to pay the higher "Windows" hourly pricing.) January 16, 2012: I get FreeBSD 9.0 running on 32-bit EC2 instances via the same "defenestration" trick. (Again, paying the "Windows" prices.) August 16, 2012: I move the FreeBSD rc.d scripts which handle "EC2" functionality (e.g., logging SSH host keys to the console) into the FreeBSD ports tree. October 7, 2012: I rework the build process for FreeBSD 9.1-RC1 and later to use "world" bits extracted from the release ISOs; only the kernel is custom-built. Also, the default SSH user changes from "root" to "ec2-user". October 31, 2012: Amazon launches the "M3" family of instances, which support Xen/HVM without FreeBSD needing to pay the "Windows" tax. November 21, 2012: I get FreeBSD added to the AWS Marketplace. October 2, 2013: I finish merging kernel patches into the FreeBSD base system, and rework the AMI build (again) so that FreeBSD 10.0-ALPHA4 and later use bits extracted from the release ISOs for the entire system (world + kernel). FreeBSD Update can now be used for updating everything (because now FreeBSD/EC2 uses a GENERIC kernel). October 27, 2013: I add code to EC2 images so that FreeBSD 10.0-BETA2 and later AMIs will run FreeBSD Update when they first boot in order to download and install any critical updates. December 1, 2013: I add code to EC2 images so that FreeBSD 10.0-BETA4 and later AMIs bootstrap the pkg tool and install packages at boot time (by default, the "awscli" package). December 9, 2013: I add configinit to FreeBSD 10.0-RC1 and later to allow systems to be easily configured via EC2 user-data. July 1, 2014: Amazon launches the "T2" family of instances; now the most modern family for every type of EC2 instance (regular, high-memory, high-CPU, high-I/O, burstable) supports HVM and there should no longer be any need for FreeBSD users to pay the "Windows tax". November 24, 2014: I add code to FreeBSD 10.2 and later to automatically resize their root filesystems when they first boot; this means that a larger root disk can be specified at instance launch time and everything will work as expected. April 1, 2015: I integrate the FreeBSD/EC2 build process into the FreeBSD release building process; FreeBSD 10.2-BETA1 and later AMIs are built by the FreeBSD release engineering team. January 12, 2016: I enable Intel 82599-based "first generation EC2 Enhanced Networking" in FreeBSD 11.0 and later. June 9, 2016: I enable the new EC2 VGA console functionality in FreeBSD 11.0 and later. (The old serial console also continues to work.) June 24, 2016: Intel 82599-based Enhanced Networking works reliably in FreeBSD 11.0 and later thanks to discovering and working around a Xen bug. June 29, 2016: I improve throughput on Xen blkfront devices (/dev/xbd*) by enabling indirect segment I/Os in FreeBSD 10.4 and later. (I wrote this functionality in July 2015, but left it disabled by default a first because a bug in EC2 caused it to hurt performance on some instances.) July 7, 2016: I fix a bug in FreeBSD's virtual memory initialization in order to allow it to support boot with 128 CPUs; aka. FreeBSD 11.0 and later support the EC2 x1.32xlarge instance type. January 26, 2017: I change the default configuration in FreeBSD 11.1 and later to support EC2's IPv6 networking setup out of the box (once you flip all of the necessary switches to enable IPv6 in EC2 itself). May 20, 2017: In collaboration with Rick Macklem, I make FreeBSD 11.1 and later compatible with the Amazon "Elastic File System" (aka. NFSv4-as-a-service) via the newly added "oneopenown" mount option (and lots of bug fixes). May 25, 2017: I enable support for the Amazon "Elastic Network Adapter" in FreeBSD 11.1 and later. (The vast majority of the work — porting the driver code — was done by Semihalf with sponsorship from Amazon.) December 5, 2017: I change the default configuration in FreeBSD 11.2 and later to make use of the Amazon Time Sync Service (aka. NTP-as-a-service). The current status The upcoming FreeBSD release (11.2) supports: IPv6, Enhanced Networking (both generations), Amazon Elastic File System, Amazon Time Sync Service, both consoles (Serial VGA), and every EC2 instance type (although I'm not sure if FreeBSD has drivers to make use of the FPGA or GPU hardware on those instances). Colin's Patreon' page if you'd like to support him (https://www.patreon.com/cperciva) X network transparency X's network transparency has wound up mostly being a failure (https://utcc.utoronto.ca/~cks/space/blog/unix/XNetworkTransparencyFailure) I was recently reading Mark Dominus's entry about some X keyboard problems, in which he said in passing (quoting himself): I have been wondering for years if X's vaunted network transparency was as big a failure as it seemed: an interesting idea, worth trying out, but one that eventually turned out to be more trouble than it was worth. [...] My first reaction was to bristle, because I use X's network transparency all of the time at work. I have several programs to make it work very smoothly, and some core portions of my environment would be basically impossible without it. But there's a big qualification on my use of X's network transparency, namely that it's essentially all for text. When I occasionally go outside of this all-text environment of xterms and emacs and so on, it doesn't go as well. X's network transparency was not designed as 'it will run xterm well'; originally it was to be something that should let you run almost everything remotely, providing a full environment. Even apart from the practical issues covered in Daniel Stone's slide presentation, it's clear that it's been years since X could deliver a real first class environment over the network. You cannot operate with X over the network in the same way that you do locally. Trying to do so is painful and involves many things that either don't work at all or perform so badly that you don't want to use them. In my view, there are two things that did in general X network transparency. The first is that networks turned out to not be fast enough even for ordinary things that people wanted to do, at least not the way that X used them. The obvious case is web browsers; once the web moved to lots of images and worse, video, that was pretty much it, especially with 24-bit colour. (It's obviously not impossible to deliver video across the network with good performance, since YouTube and everyone else does it. But their video is highly encoded in specialized formats, not handled by any sort of general 'send successive images to the display' system.) The second is that the communication facilities that X provided were too narrow and limited. This forced people to go outside of them in order to do all sorts of things, starting with audio and moving on to things like DBus and other ways of coordinating environments, handling sophisticated configuration systems, modern fonts, and so on. When people designed these additional communication protocols, the result generally wasn't something that could be used over the network (especially not without a bunch of setup work that you had to do in addition to remote X). Basic X clients that use X properties for everything may be genuinely network transparent, but there are very few of those left these days. (Not even xterm is any more, at least if you use XFT fonts. XFT fonts are rendered in the client, and so different hosts may have different renderings of the same thing, cf.) < What remains of X's network transparency is still useful to some of us, but it's only a shadow of what the original design aimed for. I don't think it was a mistake for X to specifically design it in (to the extent that they did, which is less than you might think), and it did help X out pragmatically in the days of X terminals, but that's mostly it. (I continue to think that remote display protocols are useful in general, but I'm in an usual situation. Most people only ever interact with remote machines with either text mode SSH or a browser talking to a web server on the remote machine.) PS: The X protocol issues with synchronous requests that Daniel Stone talks about don't help the situation, but I think that even with those edges sanded off X's network transparency wouldn't be a success. Arguably X's protocol model committed a lesser version of part of the NeWS mistake. X's network transparency was basically free at the time (https://utcc.utoronto.ca/~cks/space/blog/unix/XFreeNetworkTransparency) I recently wrote an entry about how X's network transparency has wound up mostly being a failure for various reasons. However, there is an important flipside to the story of X's network transparency, and that is that X's network transparency was almost free at the time and in the context it was created. Unlike the situation today, in the beginning X did not have to give up lots of performance or other things in order to get network transparency. X originated in the mid 1980s and it was explicitly created to be portable across various Unixes, especially BSD-derived ones (because those were what universities were mostly using at that time). In the mid to late 1980s, Unix had very few IPC methods, especially portable ones. In particular, BSD systems did not have shared memory (it was called 'System V IPC' for the obvious reasons). BSD had TCP and Unix sockets, some System V machines had TCP (and you could likely assume that more would get it), and in general your safest bet was to assume some sort of abstract stream protocol and then allow for switchable concrete backends. Unsurprisingly, this is exactly what X did; the core protocol is defined as a bidirectional stream of bytes over an abstracted channel. (And the concrete implementation of $DISPLAY has always let you specify the transport mechanism, as well as allowing your local system to pick the best mechanism it has.) Once you've decided that your protocol has to run over abstracted streams, it's not that much more work to make it network transparent (TCP provides streams, after all). X could have refused to make the byte order of the stream clear or required the server and the client to have access to some shared files (eg for fonts), but I don't think either would have been a particularly big win. I'm sure that it took some extra effort and care to make X work across TCP from a different machine, but I don't think it took very much. (At the same time, my explanation here is probably a bit ahistorical. X's initial development seems relatively strongly tied to sometimes having clients on different machines than the display, which is not unreasonable for the era. But it doesn't hurt to get a feature that you want anyway for a low cost.) I believe it's important here that X was intended to be portable across different Unixes. If you don't care about portability and can get changes made to your Unix, you can do better (for example, you can add some sort of shared memory or process to process virtual memory transfer). I'm not sure how the 1980s versions of SunView worked, but I believe they were very SunOS dependent. Wikipedia says SunView was partly implemented in the kernel, which is certainly one way to both share memory and speed things up. PS: Sharing memory through mmap() and friends was years in the future at this point and required significant changes when it arrived. Beastie Bits Grace Hopper Celebration 2018 Call for Participation (https://www.freebsdfoundation.org/news-and-events/call-for-papers/grace-hopper-celebration-2018-call-for-participation/) Google Summer of Code: Call for Project Ideas (https://www.freebsdfoundation.org/blog/google-summer-of-code-call-for-project-ideas/) The OpenBSD Foundation 2018 Fundraising Campaign (https://undeadly.org/cgi?action=article;sid=20180129190641) SSH Mastery 2/e out (https://blather.michaelwlucas.com/archives/3115) AsiaBSDcon 2018 Registration is open (https://2018.asiabsdcon.org/) Tarsnap support for Bitcoin ending April 1st; and a Chrome bug (http://mail.tarsnap.com/tarsnap-announce/msg00042.html) Feedback/Questions Todd - Couple Questions (http://dpaste.com/195HGHY#wrap) Seth - Tar Snap (http://dpaste.com/1N7NQVQ#wrap) Alex - sudo question (http://dpaste.com/3D9P1DW#wrap) Thomas - FreeBSD on ARM? (http://dpaste.com/24NMG47#wrap) Albert - Austria BSD User Group (http://dpaste.com/373CRX7#wrap)

Bitcoin breaks $10k and we ponder its true value, big companies join the compliance-first approach to GPLv2, we spot some red flags in the latest Raspbian x86 release, and Mozilla has a new open source project. Plus Jolla gets in on the blockchain hype, and we clarify the Linux LTS situation.

Bitcoin breaks $10k and we ponder its true value, big companies join the compliance-first approach to GPLv2, we spot some red flags in the latest Raspbian x86 release, and Mozilla has a new open source project.

Bitcoin breaks $10k and we ponder its true value, big companies join the compliance-first approach to GPLv2, we spot some red flags in the latest Raspbian x86 release, and Mozilla has a new open source project.

Bitcoin breaks $10k and we ponder its true value, big companies join the compliance-first approach to GPLv2, we spot some red flags in the latest Raspbian x86 release, and Mozilla has a new open source project. Plus Jolla gets in on the blockchain hype, and we clarify the Linux LTS situation.

Bitcoin breaks $10k and we ponder its true value, big companies join the compliance-first approach to GPLv2, we spot some red flags in the latest Raspbian x86 release, and Mozilla has a new open source project. Plus Jolla gets in on the blockchain hype, and we clarify the Linux LTS situation.

This week on BSD Now, we clear up some ZFS FUD, show you how to write a NetBSD kernel module, and cover DragonflyBSD on the desktop. This episode was brought to you by Headlines ZFS is the best file system (for now) (http://blog.fosketts.net/2017/07/10/zfs-best-filesystem-now/) In my ongoing effort to fight misinformation and FUD about ZFS, I would like to go through this post in detail and share my thoughts on the current state and future of OpenZFS. The post starts with: ZFS should have been great, but I kind of hate it: ZFS seems to be trapped in the past, before it was sidelined it as the cool storage project of choice; it's inflexible; it lacks modern flash integration; and it's not directly supported by most operating systems. But I put all my valuable data on ZFS because it simply offers the best level of data protection in a small office/home office (SOHO) environment. Here's why. When ZFS first appeared in 2005, it was absolutely with the times, but it's remained stuck there ever since. The ZFS engineers did a lot right when they combined the best features of a volume manager with a “zettabyte-scale” filesystem in Solaris 10 The skies first darkened in 2007, as NetApp sued Sun, claiming that their WAFL patents were infringed by ZFS. Sun counter-sued later that year, and the legal issues dragged on. The lawsuit was resolved, and it didn't really impede ZFS. Some say it is the reason that Apple didn't go with ZFS, but there are other theories too. By then, Sun was hitting hard times and Oracle swooped in to purchase the company. This sowed further doubt about the future of ZFS, since Oracle did not enjoy wide support from open source advocates. Yes, Oracle taking over Sun and closing the source for ZFS definitely seemed like a setback at the time, but the OpenZFS project was started and active development has continued as an ever increasing pace. As of today, more than half of the code in OpenZFS has been written since the fork from the last open version of Oracle ZFS. the CDDL license Sun applied to the ZFS code was https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/ (judged incompatible) with the GPLv2 that covers Linux, making it a non-starter for inclusion in the world's server operating system. That hasn't stopped the ZFS-on-Linux project, or Ubuntu… Although OpenSolaris continued after the Oracle acquisition, and FreeBSD embraced ZFS, this was pretty much the extent of its impact outside the enterprise. Sure, NexentaStor and http://blog.fosketts.net/2008/09/15/greenbytes-embraces-extends-zfs/ (GreenBytes) helped push ZFS forward in the enterprise, but Oracle's lackluster commitment to Sun in the datacenter started having an impact. Lots of companies have adopted OpenZFS for their products. Before OpenZFS, there were very few non-Sun appliances that used ZFS, now there are plenty. OpenZFS Wiki: Companies with products based on OpenZFS (http://open-zfs.org/wiki/Companies) OpenZFS remains little-changed from what we had a decade ago. Other than the fact that half of the current code did not exist a decade ago… Many remain skeptical of deduplication, which hogs expensive RAM in the best-case scenario. This is one of the weaker points in ZFS. As it turns out, the demand for deduplication is actually not that strong. Most of the win can be had with transparent compression. However, there are a number of suggested designs to work around the dedup problems: Dedup Ceiling: Set a limit on the side of the DDT and just stop deduping new unique blocks when this limit is reached. Allocation Classes: A feature being developed by Intel for a supercomputer, will allow different types of data to be classified, and dedicated vdevs (or even metaslabs within a vdev), to be dedicated to that class of data. This could be extended to having the DDT live on a fast device like an PCIe NVMe, combined with the Dedup Ceiling when the device is full. DDT Pruning: Matt Ahrens described a design where items in the DDT with only a single reference, would be expired in an LRU type fashion, to allow newer blocks to live in the DDT in hopes that they would end up with more than a single reference. This doesn't cause bookkeeping problems since when a block is about to be freed, if it is NOT listed in the DDT, ZFS knows it was never deduplicated, so the current block must be the only reference, and it can safely be freed. This provides a best case scenario compared to Dedup Ceiling, since blocks that will deduplicate well, are likely to be written relatively close together, whereas the chance to a dedup match on a very old block is much lower. And I do mean expensive: Pretty much every ZFS FAQ flatly declares that ECC RAM is a must-have and 8 GB is the bare minimum. In my own experience with FreeNAS, 32 GB is a nice amount for an active small ZFS server, and this costs $200-$300 even at today's prices. As we talked about a few weeks ago, ECC is best, but it is not required. If you want your server to stay up for a long time, to be highly available, you'll put ECC in it. Don't let a lack of ECC stop you from using ZFS, you are just putting your data at more risk. The scrub of death is a myth. ZFS does not ‘require' lots of ram. Your NAS will work happily with 8 GB instead of 32 GB of RAM. Its cache hit ratio will be much lower, so performance will be worse. It won't be able to buffer as many writes, so performance will be worse. Copy-on-Write has some drawbacks, data tends to get scattered and fragmented across the drives when it is written gradually. The ARC (RAM Cache) lessens the pain of this, and allows ZFS to batch incoming writes up into nice contiguous writes. ZFS purposely alternates between reading and writing, since both are faster when the other is not happening. So writes are batched up until there is too much dirty data, or the timeout expires. Then reads are held off while the bulk linear write finishes as quickly as possible, and reads are resumed. Obviously all of this works better and more efficiently in larger batches, which you can do if you have more RAM. ZFS can be tuned to use less RAM, and if you do not have a lot of RAM, or you have a lot of other demand on your RAM, you should do that tuning. And ZFS never really adapted to today's world of widely-available flash storage: Although flash can be used to support the ZIL and L2ARC caches, these are of dubious value in a system with sufficient RAM, and ZFS has no true hybrid storage capability. It's laughable that the ZFS documentation obsesses over a few GB of SLC flash when multi-TB 3D NAND drives are on the market. And no one is talking about NVMe even though it's everywhere in performance PC's. Make up your mind, is 32GB of ram too expensive or not… the L2ARC exists specifically for the case where it is not possible to just install more RAM. Be it because there are no more slots, of limits of the processor, or limits of your budget. The SLOG is optional, but it never needs to be very big. A number of GBs of SLC flash is all you need, it is only holding writes that have not been flushed to the regular storage devices yet. The reason the documentation talks about SLC specifically is because your SLOG needs a very high write endurance, something never the newest NVMe devices cannot yet provide. Of course you can use NVMe devices with ZFS, lots of people do. All flash ZFS arrays are for sale right now. Other than maybe a little tuning of the device queue depths, ZFS just works and there is nothing to think about. However, to say there is nothing happening in this space is woefully inaccurate. The previously mentioned allocation classes code can be used to allocate metadata (4 KB blocks) on SSD or NVMe, while allocating bulk storage data (up to 16 MB blocks) on spinning disks. Extended a bit beyond what Intel is building for their super computer, this will basically create hybrid storage for ZFS. With the metaslab classes feature, it will even be possible to mix classes on the same device, grouping small allocations and large allocations in different areas, decreasing fragmentation. Then there's the question of flexibility, or lack thereof. Once you build a ZFS volume, it's pretty much fixed for life. There are only three ways to expand a storage pool: Replace each and every drive in the pool with a larger one (which is great but limiting and expensive) It depends on your pool layout. If you design with this in mind using ZFS Mirrors, it can be quite useful Add a stripe on another set of drives (which can lead to imbalanced performance and redundancy and a whole world of potential stupid stuff) The unbalanced LUNs performance issues were sorted out in 2013-2016. 2014: OpenZFS Allocation Performance (http://open-zfs.org/w/images/3/31/Performance-George_Wilson.pdf) 2016: OpenZFS space allocation: doubling performance on large and fragmented pools (http://www.bsdcan.org/2016/schedule/events/710.en.html) These also mostly solved the performance issues when a pool gets full, you can run a lot closer to the edge now Build a new pool and “zfs send” your datasets to it (which is what I do, even though it's kind of tricky) This is one way to do it, yes. There is another way coming, but I can't talk about it just yet. Look for big news later this year. Apart from option 3 above, you can't shrink a ZFS pool. Device removal is arriving now. It will not work for RAIDZ*, but for Mirrors and Stripes you will be able to remove a device. I've probably made ZFS sound pretty unappealing right about now. It was revolutionary but now it's startlingly limiting and out of touch with the present solid-state-dominated storage world. I don't feel like ZFS is out of touch with solid state. Lots of people are running SSD only pools. I will admit the tiered storage options in ZFS are a bit limited still, but there is a lot of work being done to overcome this. After all, reliably storing data is the only thing a storage system really has to do. All my important data goes on ZFS, from photos to music and movies to office files. It's going to be a long time before I trust anything other than ZFS! + I agree. + ZFS has a great track record of doing its most important job, keeping your data safe. + Work is ongoing to make ZFS more performance, and more flexible. The import thing is that this work is never allowed to compromise job #1, keeping your data safe. + Hybrid/tiered storage features, re-RAID-ing, are coming + There is a lot going on with OpenZFS, check out the notes from the last two OpenZFS Developer Summits just to get an idea of what some of those things are: 2015 (http://open-zfs.org/wiki/OpenZFS_Developer_Summit_2015) & 2016 (http://open-zfs.org/wiki/OpenZFS_Developer_Summit_2016) Some highlights: Compressed ARC Compressed send/recv ABD (arc buf scatter/gather) ZFS Native Encryption (scrub/resilver, send/recv, etc without encryption keys loaded) Channel Programs (do many administrative operations as one atomic transaction) Device Removal Redacted send/recv ZStandard Compression TRIM Support (FreeBSD has its own, but this will be more performant and universal) Faster Scrub/Resilver (https://youtu.be/SZFwv8BdBj4) Declustered RAID (https://youtu.be/MxKohtFSB4M) Allocation Classes (https://youtu.be/28fKiTWb2oM) Multi-mount protection (for Active/Passive failover) Zpool Checkpoint (undo almost anything) Even more Improved Allocator Performance vdev spacemap log ZIL performance improvements (w/ or w/o SLOG) Persistent L2ARC What I don't think the author of this article understands is how far behind every other filesystem is. 100s of Engineer years have gone into OpenZFS, and the pace is accelerating. I don't see how BtrFS can ever catch up, without a huge cash infusion. Writing a NetBSD kernel module (https://saurvs.github.io/post/writing-netbsd-kern-mod/) Kernel modules are object files used to extend an operating system's kernel functionality at run time. In this post, we'll look at implementing a simple character device driver as a kernel module in NetBSD. Once it is loaded, userspace processes will be able to write an arbitrary byte string to the device, and on every successive read expect a cryptographically-secure pseudorandom permutation of the original byte string. You will need the NetBSD Source Code. This doc (https://www.netbsd.org/docs/guide/en/chap-fetch.html) will explain how you can get it. The article gives an easy line by line walkthrough which is easy to follow and understand. The driver implements the bare minimum: open, close, read, and write, plus the module initialization function It explains the differences in how memory is allocated and freed in the kernel It also describes the process of using UIO to copy data back and forth between userspace and the kernel Create a Makefile, and compile the kernel module Then, create a simple userspace program to use the character device that the kernel module creates All the code is available here (https://github.com/saurvs/rperm-netbsd) *** DragonFlyBSD Desktop! (https://functionallyparanoid.com/2017/07/11/dragonflybsd-desktop/) If you read my last post (https://functionallyparanoid.com/2017/06/30/boot-all-the-things/), you know that I set up a machine (Thinkpad x230) with UEFI and four operating systems on it. One, I had no experience with – DragonFlyBSD (other than using Matthew Dillon's C compiler for the Amiga back in the day!) and so it was uncharted territory for me. After getting the install working, I started playing around inside of DragonFlyBSD and discovered to my delight that it was a great operating system with some really unique features – all with that BSD commitment to good documentation and a solid coupling of kernel and userland that doesn't exist (by design) in Linux. So my goal for my DragonFlyBSD desktop experience was to be as BSD as I possibly could. Given that (and since I'm the maintainer of the port on OpenBSD ), I went with Lumina as the desktop environment and XDM as the graphical login manager. I have to confess that I really like the xfce terminal application so I wanted to make sure I had that as well. Toss in Firefox, libreOffice and ownCloud sync client and I'm good to go! OK. So where to start. First, we need to get WiFi and wired networking happening for the console at login. To do that, I added the following to /etc/rc.conf: wlans_iwn0=”wlan0″ ifconfig_wlan0=”WPA DHCP” ifconfig_em0=”DHCP” I then edited /etc/wpa_supplicant.conf to put in the details of my WiFi network: network={ ssid=”MY-NETWORK-NAME” psk=”my-super-secret-password” } A quick reboot showed that both wired and wireless networking were functional and automatically were assigned IP addresses via DHCP. Next up is to try getting into X with whatever DragonFlyBSD uses for its default window manager. A straight up “startx” met with, shall we say, less than stellar results. Therefore, I used the following command to generate a simple /etc/X11/xorg.conf file: # Xorg -configure # cp /root/xorg.conf.new /etc/X11/xorg.conf With that file in place, I could get into the default window manager, but I had no mouse. After some searching and pinging folks on the mailing list, I was able to figure out what I needed to do. I added the following to my /etc/rc.conf file: moused_enable=”YES” moused_type=”auto” moused_port=”/dev/psm0″ I rebooted (I'm sure there is an easier way to get the changes but I don't know it… yet) and was able to get into a basic X session and have a functional mouse. Next up, installing and configuring Lumina! To do that, I went through the incredibly torturous process of installing Lumina: # pkg install lumina Wow! That was really, really hard. I might need to pause here to catch my breath.

Bradley and Karen give a basic introduction of copyright licensing of Open Source and Free Software. Show Notes: Segment 0 (00:35) Bradley mentioned the phrase “fixed in a tangible medium” which appears in the USA copyright law. (03:10) Bradley mentioned the Sherman Antitrust act. (04:05) Bradley mentioned the card game Pit (04:15) Bradley jokingly quoted Mit Romney's famous gaffe, “Corporations are people, my friend.” (04:44) Bradley read Title 17, the USA Copyright act many times. (06:50) Bradley mentioned the court case, UNIX System Laboratories, Inc. v. Berkeley Software Design, Inc., which resulted in releasing the parts of BSD that could be Free Software. (12:27) Bradley mentioned the FSF's Free Software Definition (13:11) Bradley mentioned OSI's Open Source Definition (13:16) Apparently, the problem of categorization is called Categorization in Philosophy. (14:30) The issue of Open Source not being trademarked is discussed in this essay by Richard Stallman. (15:44) The basic categorizations of types of FLOSS licenses are copyleft and non-copyleft. Karen suggests reading GPLv2 and GPLv3. (39:31) Bradley made a crude drawing of the spectrum of licenses. (40:20) Bradley mentioned the The Principles of Community-Oriented GPL Enforcement (55: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).

Bradley and Karen give a basic introduction of copyright licensing of Open Source and Free Software. Show Notes: Segment 0 (00:35) Bradley mentioned the phrase “fixed in a tangible medium” which appears in the USA copyright law. (03:10) Bradley mentioned the Sherman Antitrust act. (04:05) Bradley mentioned the card game Pit (04:15) Bradley jokingly quoted Mit Romney's famous gaffe, “Corporations are people, my friend.” (04:44) Bradley read Title 17, the USA Copyright act many times. (06:50) Bradley mentioned the court case, UNIX System Laboratories, Inc. v. Berkeley Software Design, Inc., which resulted in releasing the parts of BSD that could be Free Software. (12:27) Bradley mentioned the FSF's Free Software Definition (13:11) Bradley mentioned OSI's Open Source Definition (13:16) Apparently, the problem of categorization is called Categorization in Philosophy. (14:30) The issue of Open Source not being trademarked is discussed in this essay by Richard Stallman. (15:44) The basic categorizations of types of FLOSS licenses are copyleft and non-copyleft. Karen suggests reading GPLv2 and GPLv3. (39:31) Bradley made a crude drawing of the spectrum of licenses. (40:20) Bradley mentioned the The Principles of Community-Oriented GPL Enforcement (55: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 on Twitter and and FaiF on 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).

This week on the show, we have an interview with Jamie This episode was brought to you by Headlines BSDCan 2016 List of Talks (http://www.bsdcan.org/2016/list-of-talks.txt) We are all looking forward to BSDCan Make sure you arrive in time for the Goat BoF, the evening of Tuesday June 7th at the Royal Oak, just up the street from the university residence There will also be a ZFS BoF during lunch of one of the conference days, be sure to grab your lunch and bring it to the BoF room Also, don't forget to get signed up for the various DevSummits taking place at BSDCan. *** What does Load Average really mean (https://utcc.utoronto.ca/~cks/space/blog/unix/ManyLoadAveragesOfUnix) Chris Siebenmann, a sysadmin at the University of Toronto, does some comparison of what “Load Average” means on different unix systems, including Solaris/IllumOS, FreeBSD, NetBSD, OpenBSD, and Linux It seems that no two OSes use the same definition, so comparing load averages is impossible On FreeBSD, where I/O does not affect load average, you can divide the load average by the number of CPU cores to be able to compare across machines with different core counts *** GPL violations related to combining ZFS and Linux (http://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/) As we mentioned in last week's episode, Ubuntu was preparing to release their next version with native ZFS support. + As expected, the Software Freedom Conservancy has issued a statement detailing the legal argument why they believe this is a violation of the GPL license for the Linux kernel. It's a pretty long and complete article, but we wanted to bring you the summary of the whole, and encourage you to read the rest, since it's good to be knowledgeable about the various open-source projects and their license conditions. “We are sympathetic to Canonical's frustration in this desire to easily support more features for their users. However, as set out below, we have concluded that their distribution of zfs.ko violates the GPL. We have written this statement to answer, from the point of view of many key Linux copyright holders, the community questions that we've seen on this matter. Specifically, we provide our detailed analysis of the incompatibility between CDDLv1 and GPLv2 — and its potential impact on the trajectory of free software development — below. However, our conclusion is simple: Conservancy and the Linux copyright holders in the GPL Compliance Project for Linux Developers believe that distribution of ZFS binaries is a GPL violation and infringes Linux's copyright. We are also concerned that it may infringe Oracle's copyrights in ZFS. As such, we again ask Oracle to respect community norms against license proliferation and simply relicense its copyrights in ZFS under a GPLv2-compatible license.” The Software Freedom Law Center's take on the issue (https://softwarefreedom.org/resources/2016/linux-kernel-cddl.html) Linux SCSI subsystem Maintainer, James Bottomley, asks “where is the harm” (http://blog.hansenpartnership.com/are-gplv2-and-cddl-incompatible/) FreeBSD and ZFS (http://freebsdfoundation.blogspot.ca/2016/02/freebsd-and-zfs.html) *** DragonFly i915 reaches Linux 4.2 (https://www.phoronix.com/scan.php?page=news_item&px=DragonFlyBSD-i915-4.2) The port of the Intel i915 DRM/KMS Linux driver to DragonFlyBSD has been updated to match Linux kernel 4.2 Various improvements and better support for new hardware are included One big difference, is that DragonFlyBSD will not require the binary firmware blob that Linux does François Tigeot explains: "starting from Linux 4.2, a separate firmware blob is required to save and restore the state of display engines in some low-power modes. These low-power modes have been forcibly disabled in the DragonFly version of this driver in order to keep it blob-free." Obviously this will have some disadvantage, but as those modes were never available on DragonFlyBSD before, users are not likely to miss them *** Interview - Jamie McParland - mcparlandj@newberg.k12.or.us (mailto:mcparlandj@newberg.k12.or.us) / @nsdjamie (https://twitter.com/nsdjamie) FreeBSD behind the chalkboard *** iXsystems My New IXSystems Mail Server (https://www.reddit.com/r/LinuxActionShow/comments/48c9nt/my_new_ixsystems_mail_server/) News Roundup Installing ELK on FreeBSD, Tutorial Part 1 (https://blog.gufi.org/2016/02/15/elk-first-part/) Are you an ELK user, or interested in becoming one? If so, Gruppo Utenti has a nice blog post / tutorial on how to get started with it on FreeBSD. Maybe you haven't heard of ELK, but its not the ELK in ports, specifically in this case he is referring to “ElasticSearch/Logstash/Kibana” as a stack. Getting started is relatively simply, first we install a few ports/packages: textproc/elasticsearch sysutils/logstash textproc/kibana43 www/nginx After enabling the various services for those (hint: sysrc may be easier), he then takes us through the configuration of ElasticSearch and LogStash. For the most part they are fairly straightforward, but you can always copy and paste his example config files as a template. Follow up to Installing ELK on FreeBSD (https://blog.gufi.org/2016/02/23/elk-second-part/) Jumping directly into the next blog entry, he then takes us through the “K” part of ELK, specifically setting up Kibana, and exposing it via nginx publically. At this point most of the CLI work is finished, and we have a great walkthrough of doing the Kibana configuration via their UI. We are still awaiting the final entry to the series, where the setup of ElastAlert will be detailed, and we will bring that to your attention when it lands. *** From 1989: An Empirical Study of the Reliablity of Unix Utilities (http://ftp.cs.wisc.edu/paradyn/technical_papers/fuzz.pdf) A paper from 1989 on the results of fuzz testing various unix utilities across a range of available unix operating systems Very interesting results, it is interesting to look back at before the start of the modern BSD projects New problems are still being found in utilities using similar testing methodologies, like afl (American Fuzzy lop) *** Google Summer of Code Both FreeBSD (https://summerofcode.withgoogle.com/organizations/4892834293350400/) and NetBSD (https://summerofcode.withgoogle.com/organizations/6246531984261120/) Are running 2016 Google Summer of Code projects. Students can start submitting proposals on March 14th. In the meantime, if you have any ideas, please post them to the Summer Of Code Ideas Page (https://wiki.freebsd.org/SummerOfCodeIdeas) on the FreeBSD wiki Students can start looking at the list now and try to find mentors to get a jump start on their project. *** High Availablity Sync for ipfw3 in Dragonfly (http://lists.dragonflybsd.org/pipermail/commits/2016-February/459424.html) Similar to pfsync, this new protocol allows firewall dynamic rules (state) to be synchronized between two firewalls that are working together in HA with CARP Does not yet sync NAT state, it seems libalias will need some modernization first Apparently it will be relatively easy to port to FreeBSD This is one of the only features ipfw lacks when compared to pf *** Beastie Bits FreeBSD 10.3-BETA3 Now Available (https://lists.freebsd.org/pipermail/freebsd-stable/2016-February/084238.html) LibreSSL isnt affected by the OpenSSL DROWN attack (http://undeadly.org/cgi?action=article&sid=20160301141941&mode=expanded) NetBSD machines at the Open Source Conference 2016 in Toyko (http://mail-index.netbsd.org/netbsd-advocacy/2016/02/29/msg000703.html) OpenBSD removes Linux Emulation (https://marc.info/?l=openbsd-ports-cvs&m=145650279825695&w=2) Time is an illusion - George Neville-Neil (https://queue.acm.org/detail.cfm?id=2878574) OpenSSH 7.2 Released (http://www.openssh.com/txt/release-7.2) Feedback/Questions Shane - IPSEC (http://slexy.org/view/s2qCKWWKv0) Darrall - 14TB Zpool (http://slexy.org/view/s20CP3ty5P) Pedja - ZFS setup (http://slexy.org/view/s2qp7K9KBG) ***

Karen and Bradley announce Conservancy's DMCA filing and Conservancy and FSF's joint launch of the copyleft.org project, and then discuss Eileen Evans' FOSDEM 2014 talk, entitled Licensing Models and Building an Open Source Community. Show Notes: Segment 0 (00:36) Conservancy file a DMCA petition regarding so-called “Smart TVs”. (02:00) Bradley mentioned the magic marker that was as circumvention technique under DMCA. Here's an amusing joke press release about the issue. (03:10) There isn't much documentation online of Bruce Perens live DMCA violation, but this article appears to be the main one on the subject, and there is also this interview (06:46). Bradley and Karen talked about the joint FSF/Conservancy copyleft.org announcement. (09:10) Bradley first pulled together the materials for copyleft.org for FSF's CLE seminars, particularly the one in March 2014. (10:00) Karen noted that Conservancy donated the time to write up a pristine example of good complete, corresponding source code for a GPL'd product. (11:30) Bradley discussed the incorrect GPLv2§2(a) violation accusations that some made against Red Hat regarding its changes to its publication of RHEL's Linux fork. (12:00) Karen and Bradley encouraged listeners to submit talk proposals for the FOSDEM 2015 Legal and Policy Issues DevRoom (15:03) Segment 1 (19:38) This is a recording of Eileen Evans' FOSDEM 2014 talk, entitled Licensing Models and Building an Open Source Community. If you'd rather watch the video, which includes the slides from her talk, it's available on FOSDEM's site. Segment 2 (46:40) Bradley and Karen discuss Eileen's talk. Bradley mentioned the OpenStack CLA fight, which was covered in a panel discussion on FaiF 0x4B. (56:16) Karen mentioned the 501(c)(6) issues that OpenStack Foundation has faced, which were discussed already on FaiF 0x4E. (56:34) 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).

Karen and Bradley announce Conservancy's DMCA filing and Conservancy and FSF's joint launch of the copyleft.org project, and then discuss Eileen Evans' FOSDEM 2014 talk, entitled Licensing Models and Building an Open Source Community. Show Notes: Segment 0 (00:36) Conservancy file a DMCA petition regarding so-called “Smart TVs”. (02:00) Bradley mentioned the magic marker that was as circumvention technique under DMCA. Here's an amusing joke press release about the issue. (03:10) There isn't much documentation online of Bruce Perens live DMCA violation, but this article appears to be the main one on the subject, and there is also this interview (06:46). Bradley and Karen talked about the joint FSF/Conservancy copyleft.org announcement. (09:10) Bradley first pulled together the materials for copyleft.org for FSF's CLE seminars, particularly the one in March 2014. (10:00) Karen noted that Conservancy donated the time to write up a pristine example of good complete, corresponding source code for a GPL'd product. (11:30) Bradley discussed the incorrect GPLv2§2(a) violation accusations that some made against Red Hat regarding its changes to its publication of RHEL's Linux fork. (12:00) Karen and Bradley encouraged listeners to submit talk proposals for the FOSDEM 2015 Legal and Policy Issues DevRoom (15:03) Segment 1 (19:38) This is a recording of Eileen Evans' FOSDEM 2014 talk, entitled Licensing Models and Building an Open Source Community. If you'd rather watch the video, which includes the slides from her talk, it's available on FOSDEM's site. Segment 2 (46:40) Bradley and Karen discuss Eileen's talk. Bradley mentioned the OpenStack CLA fight, which was covered in a panel discussion on FaiF 0x4B. (56:16) Karen mentioned the 501(c)(6) issues that OpenStack Foundation has faced, which were discussed already on FaiF 0x4E. (56:34) 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 on Twitter and and FaiF on 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).

In this episode we talk to Johannes Schindelin from the msysgit project, a tool used for building Git for Windows. If you cannot see the audio controls, your browser does not support the audio element. Use the link below to download the mp3 manually. Link to mp3Johannes is a mathematician with a degree in genetics. In his day job, he supports biologists with image processing and analysis. He is involved in a number of Open Source projects and he co-maintains Git for Windows with Sebastian Schuberth, Pat Thoyts and Erik Faye-Lund. He is from Germany, but currently lives in the Mid-West of the US.Note: We briefly discussed libgit2 being licensed as BSD. This is not the case anymore: It has switched to GPLv2 with a linking exception,Links:Johannes on Google+, GitHubJohannes' first OSS project: LibVNCServer/LibVNCClient(Fancy redesigned) MsysGit homepage Git for Windows wikiMailing list/forumThe “garden shears”Explanation what the “garden shears” are all aboutThe git-svn ref issue The newly redesigned msysgit homepage sourcesInteractive rebase with Eclipse EGitInteractive rebase with SourceTree (this was released right after we recorded)Installing Git for Windows from within Visual Studio (video)Listen to the episode on YouTube

This week I promised an interview with Gary J Brooks in regards to his startup of CloudAccess.net but this week we see quite a debate spark up over the relicensing of the Joomla Framework from GPL to LGPL. I have to stress, thats the relicensing of the Joomla Framework and not of the Joomla CMS itself.This is where some of the original confusion came from. There were also some assumptions that the license version was something different which would mean the GPLv2 license of the Joomla CMS would have to change and this we don't want to happen.I spent a Sunday afternoon with Andrew Eddie, one of the Joomla Framework developers, asking him about what were the implications of the license change, how it would affect my business and many others around the world. Andrew explains all from the point of view for changing the license to LGPL, and I welcome someone else to join me on the podcast to speak for the other side of the argument to keep the Joomla Framework as GPL.

On this week's episode, we'll be talking with Ted Unangst of the OpenBSD team about their new signing infrastructure. After that, we've got a tutorial on how to run your own NTP server. News, your feedback and even... the winner of our tutorial contest will be announced! So stay tuned to BSD Now - the place to B.. SD. This episode was brought to you by Headlines FreeBSD foundation's 2013 fundraising results (http://freebsdfoundation.blogspot.com/2014/01/freebsd-foundation-announces-2013.html) The FreeBSD foundation finally counted all the money they made in 2013 $768,562 from 1659 donors Nice little blog post from the team with a giant beastie picture "We have already started our 2014 fundraising efforts. As of the end of January we are just under $40,000. Our goal is to raise $1,000,000. We are currently finalizing our 2014 budget. We plan to publish both our 2013 financial report and our 2014 budget soon." A special thanks to all the BSD Now listeners that contributed, the foundation was really glad that we sent some people their way (and they mentioned us on Facebook) *** OpenSSH 6.5 released (https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-January/032152.html) We mentioned the CFT last week, and it's finally here (https://news.ycombinator.com/item?id=7154925)! New key exchange using elliptic-curve Diffie Hellman in Daniel Bernstein's Curve25519 (now the default when both clients support it) Ed25519 public keys are now available for host keys and user keys, considered more secure than DSA and ECDSA Funny side effect: if you ONLY enable ed25519 host keys, all the compromised Linux boxes can't even attempt to login (http://slexy.org/view/s2rI13v8F4) lol~ New bcrypt private key type, 500,000,000 times harder to brute force Chacha20-poly1305 transport cipher that builds an encrypted and authenticated stream in one Portable version already in (https://svnweb.freebsd.org/base?view=revision&revision=261320) FreeBSD -CURRENT, and ports (https://svnweb.freebsd.org/ports?view=revision&sortby=date&revision=342618) Lots more bugfixes and features, see the full release note or our interview (http://www.bsdnow.tv/episodes/2013_12_18-cryptocrystalline) with Damien Work has already started on 6.6, which can be used without OpenSSL (https://twitter.com/msfriedl/status/427902493176377344)! *** Crazed Ferrets in a Berkeley Shower (http://blather.michaelwlucas.com/archives/1942) In 2000, MWL (http://www.bsdnow.tv/episodes/2013_11_06-year_of_the_bsd_desktop) wrote an essay for linux.com about why he uses the BSD license: "It's actually stood up fairly well to the test of time, but it's fourteen years old now." This is basically an updated version about why he uses the BSD license, in response to recent comments from Richard Stallman (http://gcc.gnu.org/ml/gcc/2014-01/msg00247.html) Very nice post that gives some history about Berkeley, the basics of the BSD-style licenses and their contrast to the GNU GPL Check out the full post if you're one of those people that gets into license arguments The takeaway is "BSD is about making the world a better place. For everyone." *** OpenBSD on BeagleBone Black (http://www.tedunangst.com/flak/post/OpenBSD-on-BeagleBone-Black) Beaglebone Blacks are cheap little ARM devices similar to a Raspberry Pi A blog post about installing OpenBSD on a BBB from.. our guest for today! He describes it as "everything I wish I knew before installing the newly renamed armv7 port on a BeagleBone Black" It goes through the whole process, details different storage options and some workarounds Could be a really fun weekend project if you're interested in small or embedded devices *** Interview - Ted Unangst - tedu@openbsd.org (mailto:tedu@openbsd.org) / @tedunangst (https://twitter.com/tedunangst) OpenBSD's signify (http://www.tedunangst.com/flak/post/signify) infrastructure, ZFS on OpenBSD Tutorial Running an NTP server (http://www.bsdnow.tv/tutorials/ntpd) News Roundup Getting started with FreeBSD (http://smyck.net/2014/02/01/getting-started-with-freebsd/) A new video and blog series about starting out with FreeBSD The author has been a fan since the 90s and has installed it on every server he's worked with He mentioned some of the advantages of BSD over Linux and how to approach explaining them to new users The first video is the installation, then he goes on to packages and other topics - 4 videos so far *** More OpenBSD hackathon reports (http://undeadly.org/cgi?action=article&sid=20140204080515) As a followup to last week, this time Kenneth Westerback writes about his NZ hackathon experience He arrived with two goals: disklabel fixes for drives with 4k sectors and some dhclient work This summary goes into detail about all the stuff he got done there *** X11 in a jail (https://svnweb.freebsd.org/base?view=revision&revision=261266) We've gotten at least one feedback email about running X in a jail Well.. with this commit, looks like now you can! A new tunable option will let jails access /dev/kmem and similar device nodes Along with a change to DRM, this allows full X11 in a jail Be sure to check out our jail tutorial and jailed VNC tutorial (http://www.bsdnow.tv/tutorials) for ideas *** PCBSD weekly digest (http://blog.pcbsd.org/2014/01/whoami-im-pc-bsd-10-0-weekly-feature-digest-15/) 10.0 "Joule Edition" finally released (http://blog.pcbsd.org/2014/01/pc-bsd-10-0-release-is-now-available/)! AMD graphics are now officially supported GNOME3, MATE and Cinnamon desktops are available Grub updates and fixes PCBSD also got a mention in eweek (http://www.eweek.com/enterprise-apps/slideshows/freebsd-open-source-os-comes-to-the-pc-bsd-desktop.html) *** Feedback/Questions Justin writes in (http://slexy.org/view/s21VnbKZsH) Daniel writes in (http://slexy.org/view/s2nD7RF6bo) Martin writes in (http://slexy.org/view/s2jwRrj7UV) Alex writes in (http://slexy.org/view/s201koMD2c) - unofficial FreeBSD RPI Images (http://people.freebsd.org/~gjb/RPI/) James writes in (http://slexy.org/view/s2AntZmtRU) John writes in (http://slexy.org/view/s20bGjMsIQ) ***

In this episode we discussed: MongoDB Standardization of NoSQL databases Portability between non-relational databases CouchDB PostgreSQL AGPL license PostgreSQL license (like the BSD license) MySQL is GPLv2 Drizzle has rewritten their MySQL driver so it’s not GPL Oracle’s behavior toward products they own that compete InnoDB MySQL engine Microsoft SQL – The price hike and bug report that drove Josh to PostgreSQL Customer expectations vs Intended functionality GreenPlum Alexa Implementing the minimum feature set and getting feedback. Transactional DDL – All operations are transactional except create database. Database Migrations – PostgreSQL can do migrations with no downtime. Memcached Redis Solr ElasticSearch Foreign Data Wrappers – a driver for external data sources that can then be managed through PostgreSQL Lucene Hadoop HBase Cassandra Project Voldemort HyperTable Riak Amazon Cap Theorem Papers VoltDB

Bradley and Karen discuss the inclusion of ZFS GPLv2-or-later code inclusion into GNU GRUB. Show Notes: Segment 0 (00:35) Bradley and Karen discussed the inclusion of ZFS code now included in GRUB, as the GRUB Project announced and was covered at LWN by Jonathan Corbet. It's not mandatory that GNU projects have assignment to the FSF. The GNU Maintainer's guide discuss the requirements when items are assigned to FSF. (14:40) FSF requires that the entire codebase be assigned once GNU project maintainers choose to assign copyrights. Conservancy's policy on copyright assignment differs here; Conservancy will accept partial copyright assignment. (16:07) Bradley mentioned the COBOL front end to GCC that is not in the main GCC codebase because it is not copyright assigned to FSF. (17:40) Bradley and Karen discussed the Squeak relicensing last call. (25:49) Bradley posted a comment to Corbet's article. (32:30) Final (45:45) The calendar Bradley was thinking of was the International Fixed Calendar, which Wikipedia confirms, with a sourced link, was used by the Eastman Kodak Company from 1928 to 1989. 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).

Bradley and Karen discuss the inclusion of ZFS GPLv2-or-later code inclusion into GNU GRUB. Show Notes: Segment 0 (00:35) Bradley and Karen discussed the inclusion of ZFS code now included in GRUB, as the GRUB Project announced and was covered at LWN by Jonathan Corbet. It's not mandatory that GNU projects have assignment to the FSF. The GNU Maintainer's guide discuss the requirements when items are assigned to FSF. (14:40) FSF requires that the entire codebase be assigned once GNU project maintainers choose to assign copyrights. Conservancy's policy on copyright assignment differs here; Conservancy will accept partial copyright assignment. (16:07) Bradley mentioned the COBOL front end to GCC that is not in the main GCC codebase because it is not copyright assigned to FSF. (17:40) Bradley and Karen discussed the Squeak relicensing last call. (25:49) Bradley posted a comment to Corbet's article. (32:30) Final (45:45) The calendar Bradley was thinking of was the International Fixed Calendar, which Wikipedia confirms, with a sourced link, was used by the Eastman Kodak Company from 1928 to 1989. 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 on Twitter and and FaiF on 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).

Karen and Bradley discuss the debates regarding Apple's online store restrictions that make it impossible to distribute GPL'd software via Apple's store. Then, they discuss question the usefulness of the term “Open Core” Note: Bradley's audio was too low compared to Karen's on this episode. We're still sorting out our recording issues, and apologize for this. This is completely Bradley's fault: don't blame Producer Dan. :) Show Notes: Segment 0 (00:34) Karen mentioned first Brett's statement on the VLC mailing list, although that is toward the end of the story that was covered last month. (05:30) Bradley mentioned that the story started with FSF's enforcement regarding Apple's distribution of GNU Go in Apple's application store. (05:54) Don't confused GNU Go (the game) with Google Go (the programming language). Bradley pointed out that Google did assign some of its copyright on the language Go, for the GCC frontend for the Go language. (06:51) Bradley mentioned that the game Go has been around thousands of years, although according the Go Wikipedia entry, it's been around for approximately 2,500 years. (08:21) Bradley pointed out that the primary goal of GPL enforcement is to get compliance, not to get companies to cease distribution, but sometimes the companies prefer to cease distribution rather than complying with the license. (09:57) There was disagreement in the VLC community about the enforcement action (11:50). There's an original thread on the VLC mailing list that discussed this (12:35), and then Brett's response on that list. (13:25) GPLv2 requires in § 6 that you cannot impose terms that restrict the downstream more than GPL otherwise does. (15:40) FSF made a statement that linked this issue to the DRM issue, which caused some confusion. It's our view that what Apple is doing against GPL software is part of their initiative to put DRM (both for software and more traditional content) onto devices. (17:20) Bradley mentioned that Apple lawyers have a pathological hatred of GPL, which he believes comes directly down from Steve Jobs, who began his dislike of GPL when he tried, while at NeXT, to distribute a proprietary front-end for GCC for Objective-C. (RMS discussed the story briefly in his essay Copyleft: Pragmatic Idealism.) (23:45) Segment 1 (27:40) Bradley has decided that the term “Open Core” is so confusing that it's now useless. The Gnus IMAP backend is being rewritten, and Joel Adamson mentioned that he's using Emacs development mainline and the new IMAP implementation is working well. (29:58) Alexandre Oliva started a project called Linux Libre, to remove proprietary software from Linux. (31:31) There is a file called WHENCE in Linux that is a long list of proprietary software included inside Linux. Fontana linked the WHENCE file on identi.ca (31:02) Alexandre made an announcement calling Linux an “Open Core” project. (32:56) Bradley mentioned that Alexandre appears to have been convinced that Open Core is a problematic term in this context (during this identica conversation). Alexandre seems to be favoring the term “Free Bait” now. (35:16) Karen mentioned Nina Paley's intellectual pooperty cartoon. (38:39) Bradley mentioned the softer side of Sears marketing campaign, which was used as a cruel joke by Cordelia in the pilot of Buffy the Vampire Slayer to make fun of Willow's clothes. Sears apparently dropped the campaign in 1999. (40:23) Join us on #faif on freenode and the !FaiFCast group on identi.ca (43:47) 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).

Karen and Bradley discuss the debates regarding Apple's online store restrictions that make it impossible to distribute GPL'd software via Apple's store. Then, they discuss question the usefulness of the term “Open Core” Note: Bradley's audio was too low compared to Karen's on this episode. We're still sorting out our recording issues, and apologize for this. This is completely Bradley's fault: don't blame Producer Dan. :) Show Notes: Segment 0 (00:34) Karen mentioned first Brett's statement on the VLC mailing list, although that is toward the end of the story that was covered last month. (05:30) Bradley mentioned that the story started with FSF's enforcement regarding Apple's distribution of GNU Go in Apple's application store. (05:54) Don't confused GNU Go (the game) with Google Go (the programming language). Bradley pointed out that Google did assign some of its copyright on the language Go, for the GCC frontend for the Go language. (06:51) Bradley mentioned that the game Go has been around thousands of years, although according the Go Wikipedia entry, it's been around for approximately 2,500 years. (08:21) Bradley pointed out that the primary goal of GPL enforcement is to get compliance, not to get companies to cease distribution, but sometimes the companies prefer to cease distribution rather than complying with the license. (09:57) There was disagreement in the VLC community about the enforcement action (11:50). There's an original thread on the VLC mailing list that discussed this (12:35), and then Brett's response on that list. (13:25) GPLv2 requires in § 6 that you cannot impose terms that restrict the downstream more than GPL otherwise does. (15:40) FSF made a statement that linked this issue to the DRM issue, which caused some confusion. It's our view that what Apple is doing against GPL software is part of their initiative to put DRM (both for software and more traditional content) onto devices. (17:20) Bradley mentioned that Apple lawyers have a pathological hatred of GPL, which he believes comes directly down from Steve Jobs, who began his dislike of GPL when he tried, while at NeXT, to distribute a proprietary front-end for GCC for Objective-C. (RMS discussed the story briefly in his essay Copyleft: Pragmatic Idealism.) (23:45) Segment 1 (27:40) Bradley has decided that the term “Open Core” is so confusing that it's now useless. The Gnus IMAP backend is being rewritten, and Joel Adamson mentioned that he's using Emacs development mainline and the new IMAP implementation is working well. (29:58) Alexandre Oliva started a project called Linux Libre, to remove proprietary software from Linux. (31:31) There is a file called WHENCE in Linux that is a long list of proprietary software included inside Linux. Fontana linked the WHENCE file on identi.ca (31:02) Alexandre made an announcement calling Linux an “Open Core” project. (32:56) Bradley mentioned that Alexandre appears to have been convinced that Open Core is a problematic term in this context (during this identica conversation). Alexandre seems to be favoring the term “Free Bait” now. (35:16) Karen mentioned Nina Paley's intellectual pooperty cartoon. (38:39) Bradley mentioned the softer side of Sears marketing campaign, which was used as a cruel joke by Cordelia in the pilot of Buffy the Vampire Slayer to make fun of Willow's clothes. Sears apparently dropped the campaign in 1999. (40:23) Join us on #faif on freenode and the !FaiFCast group on identi.ca (43:47) 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 on Twitter and and FaiF on 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).