Podcasts about plan9

Lumière sur le festival Fenêtres sur courts, Festival international du court métrage à Dijon, proposé par l'association Plan9 depuis 2012. 29ème édition du 16 au 23 novembre dans sept lieux culturels de la ville. Pas moins de 4 000 spectateurs sont attendus ! On fait le point sur le programme avec Hélène Bernard, directrice du festival Fenêtres sur courts.

Lumière sur le festival Fenêtres sur courts, Festival international du court métrage à Dijon, proposé par l'association Plan9. 28ème édition du 11 au 18 novembre dans 8 lieux culturels de la ville, près de 4 000 spectateurs sont attendus ! 100 films seront présentés pour cette 28ème édition, 19 séances sont programmées, ainsi que 4 compétitions, un concours étudiant, un BD-Concert, des ateliers, des rencontres... On fait le point sur le programme avec Louise Fruitier, chargée de la communication et de la coordination du festival Fenêtres sur courts, au micro de Charlie Chevasson, notre reporter Fréquence Plus. Plus d'infos : fenetres-sur-courts.com

Lumière sur le festival Fenêtres sur courts, Festival international du court métrage à Dijon, proposé par l'association Plan9. 28ème édition du 11 au 18 novembre dans 8 lieux culturels de la ville, près de 4 000 spectateurs sont attendus ! 100 films seront présentés pour cette 28ème édition, 19 séances sont programmées, ainsi que 4 compétitions, un concours étudiant, un BD-Concert, des ateliers, des rencontres... On fait le point sur le programme avec Louise Fruitier, chargée de la communication et de la coordination du festival Fenêtres sur courts, au micro de Charlie Chevasson, notre reporter Fréquence Plus. Plus d'infos : fenetres-sur-courts.com

Halloween is soon approaching, Cultists!  No better time to Dissect the debut album from Horror Punk Legends, The Misfits! 1982's Walk Among Us clocks in at a scant 24.38 minutes so obviously your Horror Hosts took four times as long discussing it. Please join us for the dissection Dissection Topic  Misfits - Walk Among Us https://www.discogs.com/master/105458-Misfits-Walk-Among-Us Dark Tidings https://ditto.fm/lanoviadefrankenstein?fbclid=IwAR1ayxUdPR_dwMBJvsh8h53dIlOQidf8QS3VOK1SJn9jLPov_sARlhMQkbE https://www.rollingstone.com/music/music-news/social-distortion-mike-ness-cancer-update-1234835688/ https://www.amazon.com/Goth-History-Lol-Tolhurst/dp/0306828421 Vault Of Darkness https://crowblackdream.bandcamp.com/ https://www.calabreserock.com/ http://www.tigerarmy.com/ Unholy Sacrament https://untp.beer/mL8Xj Theme Music https://tridroid.bandcamp.com/album/crimson-shadows #themisfits #misfits #originalmisfits #walkamongus #glenndanzig #jerryonly #doylewolfgangvonfrankenstein #arthurgoogy #doyle #horrorpunk #deathrock #hardcorepunk #americanhardcore #nyhc #fiendclub #iwantyourskull #mommycanigooutandkilltonight #astrozombies #evilive #plan9

Dr. Umar Saif comes on the podcast for an extremely informative discussion on the state of Information Technology in Pakistan; from why Pakistani Universities are failing to produce high level graduates to how political instability is destroying Pakistan's progress, on this deep dive podcast we discuss I.T., India, I.I.Ts, Higher Education, LUMS, PITB, Punjab Government, ITU, and how I.T. was used in Government projects in Punjab. Dr. Umar Saif is the founder and CEO of aiSight.ai (formerly SurveyAuto.com). He is the CEO of Khudi Ventures, Pakistan's largest venture studio. He works as the Chief Digital Officer of the Jang/Geo group. He is also an advisor to the United Nations Development Programme (UNDP) in Pakistan. Previously, Dr. Saif was a cabinet member in Government of Punjab and served as the Chairman of the Punjab Information Technology Board (PITB). His work led to a radical digital transformation of the government in Punjab and several of his initiatives were replicated throughout the country. He was the founding Vice Chancellor of ITU and established it as one of premier technology universities in Pakistan. Dr. Saif founded Plan9, Pakistan's first government-backed startup incubator, as well as Punjab's e-rozgaar program. He is often cited as one of the main forces behind Pakistan's startup ecosystem. Dr. Saif received his PhD in Computer Science in 2001 at University of Cambridge and worked at MIT for several years before returning to Pakistan. He was the first Pakistani to be named as one of the top 35 young innovators in the world by the MIT Technology Review (TR35) and the first Pakistani to receive a Google faculty research award in 2011. He was selected as a Young Global Leader by the World Economic Forum in 2010. He has received the MIT Technovator Award, Mark Weiser Award, IDG Technology Pioneer Award and the British Council Outstanding Alumni Award. Dr. Saif was awarded Sitara-i-Imtiaz in 2014, one of the highest civil awards by government of Pakistan. He was named among the 500 most influential Muslims in the world consecutively between 2015-2020. In 2018, he was awarded the UNESCO Chair for using ICT for Development. Dr. Saif has founded several technology companies and serves on the board of various private, public and financial institutions. The Pakistan Experience is an independently produced podcast looking to tell stories about Pakistan through conversations. Please consider supporting us on Patreon: https://www.patreon.com/thepakistanexperience To support the channel: Jazzcash/Easypaisa - 0325 -2982912 Patreon.com/thepakistanexperience And Please stay in touch: https://twitter.com/ThePakistanExp1https://www.facebook.com/thepakistanexperiencehttps://instagram.com/thepakistanexpeperience The podcast is hosted by comedian and writer, Shehzad Ghias Shaikh. Shehzad is a Fulbright scholar with a Masters in Theatre from Brooklyn College. He is also one of the foremost Stand-up comedians in Pakistan and frequently writes for numerous publications. Instagram.com/shehzadghiasshaikh Facebook.com/Shehzadghias/ Twitter.com/shehzad89 Chapters: 0:00 Introduction 2:07 His PHD from Cambridge, being a professor at LUMS, teaching at MIT, and why Pakistan is left behind compared to Indian IITs 19:14 What our universities lack, his IT university, and how universities work abroad, the quality of our PHDs 29:46 Why he felt he could make a difference and how he joined the government 43:01 Government Issues & Punjab's digitization of land records 55:55 Shahbaz Sharif and sales tax crowdsourcing, black economies, UPI and digitization 1:09:28 How India has digitized, importance of cash in Pakistan and India's demonetization, and our lack of import substitution 1:17:59 Atoms and how they started, IT exports, remittances, tech industry in India vs Pakistan 1:33:31 What's stopping PayPal in Pak, unicorn culture in India, 1:38:55 Audience Questions

Hé mais coucou !Long time no see. Bon on dirait bien que notre émission prend un format annuel ces derniers temps mais on a jamais oublié notre podcast. La vérité c'est que le temps passe, on s'éloigne et on revient (comme une chanson populaire) et on a un peu moins de temps de créer du contenu (surtout Noé qui procrastine). Cependant si on te manque, va écouter notre seconde émission qui s'appelle "Good Morning Plan 9" qu'on fait avec le festival de films 2300 Plan9 ! D'ailleurs on est plus actifs là qu'ailleurs hehe. Bref, t'as loupé Avatar 2 cette année et Los Tallos Amargos en 1957 ? Bah nickel on t'en parle ici, anecdotes personnelles et autres digressions, on reste fidèles à nous-mêmes. La bise,Arthur et NoéN'hésitez pas à partager si ça vous plaît (ou *te* plaît)Aussi disponibles sur Apple podcast (et bientôt spotify. Hehe en fait toujours pas, c'est des crevures)Musiques utilisées:00:12 : Christmas is all around - Love Actually01:11 : Agitations Tropicales - L'impératrice35:34 : Enjoy the Silence - Depeche Mode41:21 : A beautiful mine - version jazz56:40 : Le Cabinet du Dr Cagliari Ost01:00:36 : Fumio Hayasaka - Rashômon01:19:24 : Wham! - Last Christmas (et ouais)

FreeBSD Foundation's Software Development review of 2022, what can we learn from Vintage Computing, OpenBSD KDE Status Report 2022, a Decade of HardenedBSD, In Praise of Plan9, and more NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) and the BSDNow Patreon (https://www.patreon.com/bsdnow) Headlines 2022 in Review: Software Development (https://freebsdfoundation.org/blog/2022-in-review-software-development/) What can we learn from Vintage Computing (https://github.com/readme/featured/vintage-computing) News Roundup OpenBSD KDE Status Report 2022 (https://www.sizeofvoid.org/posts/2022-26-12-openbsd-kde-status-report-2022/) A Decade of HardenedBSD (https://git.hardenedbsd.org/shawn.webb/articles/-/blob/master/hardenedbsd/2023-01_decade/article.md) In Praise of Plan9 (https://drewdevault.com/2022/11/12/In-praise-of-Plan-9.html) Beastie Bits LibreSSL 3.7.0 Released (https://undeadly.org/cgi?action=article;sid=20221212183516) OPNsense 22.7.10 released (https://opnsense.org/opnsense-22-7-10-released/) BSDCan 2023 call for papers (https://lists.bsdcan.org/pipermail/bsdcan-announce/2022-December/000194.html) How to lock OpenSSH authentication agent (https://sleeplessbeastie.eu/2022/12/28/how-to-lock-openssh-authentication-agent/) Once upon a time long ago, I was sitting alone in the UCLA ARPANET site... (https://mastodon.laurenweinstein.org/@lauren/109588605178700335) Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) ***

October is here! Halloween is approaching, and the walking dead are getting restless… Welcome to this very special Sixth Edition of DEAD MAN STILL WALKING, starring your intrepid host, Dr. Walking Dead Kyle Bishop, who dares to discuss “the quintessential bad movie,” the infamous Plan 9 From Outer Space (1957), with special guest Dave “Dr. Shock” Becker! Listen to these two Mad Doctors as they simultaneously laugh and ridicule Ed Wood's labor of love, while also revering it, taking time to recognize and celebrate its importance in zombie film and bad movie history! Join us! Note: To view ALL of Dr. Bishop's Dead Man Still Walking solocast episode can USE THIS LINK. Dead Man Still Walking is a biweekly, short-form solocast hosted by Dr. Walking Dead Kyle Bishop, author of American Zombie Gothic and How Zombies Conquered Popular Culture. Dr. Walking Dead also presents a popular segment called The Dead Zone on regular episodes of this podcast. For his Dead Man Still Walking solocast episodes, Dr. Bishop will focus exclusively on zombie films, with the occasional exploration of zombie-related themes, zombie television, and other zombie media (e.g., comics, literature, etc.). Dr. Bishop is an academic and professional scholar of zombie films and other zombie narratives. He has been teaching for 22 years. Dr. Bishop serves as an English professor, Film Studies professor, and he's currently the English Department Chair at Southern Utah University. You are welcome to reach out to Dr. Bishop with comments or questions via email:bishopk@suu.edu, Twitter: @DrWalkingDead, or by leaving him a voicemail: (801) 899-9798. You can also watch the documentary, Doc of the Dead (2014), which features Dr. Walking Dead. Find more links below for Dr. Bishop. Be sure to subscribe to Jay of the Dead's new Horror movie podcast on:   Apple Podcasts Spotify Google Podcasts Deezer Stitcher     You are welcome to email our show at HauntingYourHeadphones@gmail.com, or call and leave us a voicemail at (801) 899-9798. You can also follow Jay of the Dead's New Horror Movies on Twitter: @HorrorAvengers Dead Man Still Walking with Dr. Kyle Bishop is brought to you by Jay of the Dead's New Horror Movies, an audio Horror movie podcast. It features nine experienced Horror hosts review new Horror movies and deliver specialty Horror segments. Your hosts are Jay of the Dead, Dr. Shock, Gillman Joel, Mister Watson, Dr. Walking Dead, GregaMortis, Mackula, Ron Martin and Dave Zee! Due to the large number and busy schedule of its nine Horror hosts, Jay of the Dead's New Horror Movies will be recorded in segments, piecemeal, at various times and recording sessions. Therefore, as you listen to our episodes, you will notice a variety of revolving door hosts and segments, all sewn together and reanimated like the powerful Monster of Dr. Frankenstein!

Tim Burton's "Ed Wood" is beloved by critics but was a massive box office failure. The opening credits cost more than the original Ed Wood's "Plan 9."@DrScifi, @kesseljunkie, and @TheInsaneRobin take a look at this film about bad films.

Tim Burton's "Ed Wood" is beloved by critics but was a massive box office failure. The opening credits cost more than the original Ed Wood's "Plan 9." @DrScifi, @kesseljunkie, and @TheInsaneRobin take a look at this film about bad films.

When Andrew Pask pointed me toward Plan 9 (and made an initial introduction), I couldn't really tell what I was getting into. The soundtrack work was very interesting, and their recent releases mapped out a compelling set of skills. But then I checked out Modwheel – which is their sample library company – and started to connect the dots: Really unique sound design and instrument design led to quirky soundtrack work, which led to crazy sample libraries, which leads to even more sound design work. An organic circle of life! Speaking with Steve Roche and David Donaldson open the door to understanding how Plan 9 got started, how they developed their interesting and unique sound (can you believe that The Flying Nun makes an appearance?), and how they create a creative working atmosphere that puts them in a position to constantly make great work. Their ‘systemic' approach to building a work life is an inspiration, and has got me paying attention to these Wellington natives. Check out https://www.plan9.co.nz and https://www.modwheel.co.nz to see their work in action. Enjoy! Transcription available at http://www.darwingrosse.com/AMT/transcript-0369.html Exclusive extra content on the Patron page: https://www.patreon.com/darwingrosse

Matt and Tyler talk about Artix, Plan9, Gnome and GTK, Installing your own kernel, and why people are so loyal to their distros.  ===== Thanks to Our Patrons! ==== Devon C. -- Tier 4 Patron Chris - Tier 4 Patron EastCoastWeb - Tier 4 Patron Gentoo is Fun Too- Tier 4 Patron Marcus B.  - Tier 3 Patron Maeglin - Tier 3 Patron Sven C. - Tier 3 Patron. Jackson Knife and Tool - Tier 3 Patron Joshua Lee - Tier 3 Patron Steve A. - Tier 3 Patron Mitchel V - Tier 2 Patron ArchSinner - Tier 2 on YT Marek M. - Tier 1 Patron Camp514 - Tier 1 Patron Joris - Tier 1 Patron ===== Follow us

Oxide and Friends Twitter Space: September 13th, 2021Docker, Inc., an Early EpitaphWe've been holding a Twitter Space weekly on Mondays at 5p for about an hour. Even though it's not (yet?) a feature of Twitter Spaces, we have been recording them all; here is the recording for our Twitter Space for September 13th, 2021.In addition to Bryan Cantrill and Adam Leventhal, speakers on September 13th included Steve Tuck, Tom Lyon, Dan Cross, Josh Clulow, Ian, Nick Gerace, Aaron Goldman, Drew Vogel, and vint serp. (Did we miss your name and/or get it wrong? Drop a PR!)Some of the topics we hit on, in the order that we hit them: Topic: Scott Carey's article How Docker broke in halfMore by Carey on Docker:  Docker Desktop is no longer free for enterprise users What is Docker? The spark for the container revolution Andrej Karpathy's tweet showing InfoWorld.com spamming ads Carey talked to: Solomon Hykes (Docker cofounder with Sebastien Pahl) Ben Golub (Docker CEO 2013-2017) Craig McLuckie (Kubernetes cofounder) Nick Stinemates (early employee and former VP of Business Development) [@5:21](https://youtu.be/l9LTJdT0sZ8?t=321) Akira Kurosawa's 1950 Rashomon ~90mins. Watch a 2min trailer Box office bomb “The Hottie and the Nottie” movie. Other stinkers: Gigli, Gotti [@9:31](https://youtu.be/l9LTJdT0sZ8?t=571) Jerry Kaplan's 1996 book Startup: A Silicon Valley Adventure Steve's take on commercialization > Bryan: There's no question that they hit on something very big. > We saw a container as an operational vessel, but we failed to see > a container as a development vessel. [@14:36](https://youtu.be/l9LTJdT0sZ8?t=876) dotCloud (PaaS) struggles to find a buyer; ultimately open sources as last resort > All of a sudden a company that nobody had heard of, > was a company that everybody had heard of. They took too much money. [@17:40](https://youtu.be/l9LTJdT0sZ8?t=1060) Pitfalls in raising money and scaling sales by imitating big companiesHBO's Silicon Valley Clip ~1min with Jan the Man, Keith, and Doug (I'm shadowing Keith) > Everybody should be spending time arm in arm with customers understanding > how is this technology going to solve a problem > which they'll want to pay to have a solution. Tom: Was there actually a business anyways? Or was it just technology? What if developers are attracted to those things they know cannot be monetized? There was this belief that if a technology is this ubiquitous, it will be readily monetizable. [@27:26](https://youtu.be/l9LTJdT0sZ8?t=1646) Docker Swarm and Kubernetes > Hykes: We didn't work at Google, we didn't go to Stanford, > we didn't have a PhD in computer science. Stinemates: (The Kubernetes team) had strong opinions about the need for a service level API and Docker technically had its own opinion about a single API from a simplicity standpoint. We couldn't agree. DockerCon 2015: No mentioning Kubernetes! Brendan Burns' talk “The distributed system toolkit: Container patterns for modular distributed system design” was unfortunately made private by Docker sometime in the last two years. The internet archive only has this. Burns wrote a blog post about the topics from his talk. rkt (“Rocket”), CoreOS [@36:11](https://youtu.be/l9LTJdT0sZ8?t=2171) Docker coming to market Enterprise teams wanted support Initial support offerings were expensive and limited (no after hours, no weekends) > Bryan: I floated to Solomon in 2014: run container management as a service. Rancher Labs, K3s (lightweight kubernetes) People care about GitHub stars (for better or worse) [@48:02](https://youtu.be/l9LTJdT0sZ8?t=2882) Monetizing open source technologies Triton implementing the Docker API The support relationships are the foothold to figure out the product. [@54:36](https://youtu.be/l9LTJdT0sZ8?t=3276) Venture capital going into DockerDocker acquires Tutum Product market fitAcquisitions [@1:04:42](https://youtu.be/l9LTJdT0sZ8?t=3882) Could the outcome have been materially different? Who made money on Docker? Cloud companies? Developers? VMware acquires Heptio Who invented containers? BSD Jails, Plan9 namespaces? Tyler Tringas' post about how small teams can create value with little outside investment, as a result of the Peace Dividend of the SaaS Wars. If we got something wrong or missed something, please file a PR! Our next Twitter space will likely be on Monday at 5p Pacific Time; stay tuned to our Twitter feeds for details. We'd love to have you join us, as we always love to hear from new speakers!

Before Cassandra Peterson's Elvira before Carolyn Jones or Angelica Houston immortalised Morticia Addams, long before Nico, The Cramps, Siouxsie and the Banshees before them all there was Vampira who paved the way for her Goth sisters to come. In this special episode of Deadly Doses, we are incredibly lucky to be joined by author Sandra Niemi who has just published a rather touching yet thoroughly bombastic biography of her incomparable aunt Maila Nurmi aka- Vampira - TV's first Horror Host. From tinning fish to “Life” magazine, Vampira's rise to fame in the 1950's is a riveting tale marked by her loves, losses and dogged determination to remain true to herself. "Glamour Ghoul: The Passions and Pain of the Real Vampira, Maila Nurmi” published by Feral House is out now!

another episode counting down to @keltuckian'a deportation.... viva la mexico! lol Otherwise, we're just pumping out a fresh episode on Memorial Day! Come celebrate with us! --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/under-the-tree-420/message Support this podcast: https://anchor.fm/under-the-tree-420/support

I will talk about the acme text editor, the impact of Plan9 and the Inferno operating system and other systems which were influenced by Plan9. More info: https://tsr-podcast.com https://blog.tsr-podcast.com viktor@tsr-podcast.com

Plan 9 from Bell Labs is a distributed operating system, originating in the Computing Science Research Center (CSRC) at Bell Labs in the mid-1980s, and building on UNIX concepts first developed there in the late 1960s. The final official release was in early 2015. Under Plan 9, UNIX's everything is a file metaphor is extended via a pervasive network-centric filesystem, and the cursor-addressed, terminal-based I/O at the heart of UNIX-like operating systems is replaced by a windowing system and graphical user interface without cursor addressing, although rc, the Plan 9 shell, is text-based. More info: https://tsr-podcast.com https://blog.tsr-podcast.com viktor@tsr-podcast.com

Sigrid Solveig Haflínudóttir discusses Plan 9

Ori Bernstein discusses Plan 9

Could an independent British black comedy film really be the surprise hit of the COVID-19-stricken year that is 2020? "Get Duked!" wants to prove that it could indeed. But, lest it get too much attention after it drops on Amazon Prime on August 28, Fanboy and Know-It-All give ample attention to one of the worst movies of all time: "Plan 9 from Outer Space." Oh, yeah, and they argue over their rankings of the best spy movies ever made. ("April Showers" by ProleteR is licensed under a Attribution-NonCommercial-NoDerivatives [aka Music Sharing] 3.0 International License.)

Could an independent British black comedy film really be the surprise hit of the COVID-19-stricken year that is 2020? "Get Duked!" wants to prove that it could indeed. But, lest it get too much attention after it drops on Amazon Prime on August 28, Fanboy and Know-It-All give ample attention to one of the worst movies of all time: "Plan 9 from Outer Space." Oh, yeah, and they argue over their rankings of the best spy movies ever made. ("April Showers" by ProleteR is licensed under a Attribution-NonCommercial-NoDerivatives [aka Music Sharing] 3.0 International License.)

Rethinking OpenBSD security, FreeBSD 2020 Q1 status report, the notion of progress and user interfaces, Comments about Thomas E. Dickey on NetBSD curses, making Unix a little more Plan9-like, Not-actually Linux distro review: FreeBSD, and more. Headlines Rethinking OpenBSD Security (https://flak.tedunangst.com/post/rethinking-openbsd-security) OpenBSD aims to be a secure operating system. In the past few months there were quite a few security errata, however. That’s not too unusual, but some of the recent ones were a bit special. One might even say bad. The OpenBSD approach to security has a few aspects, two of which might be avoiding errors and minimizing the risk of mistakes. Other people have other ideas about how to build secure systems. I think it’s worth examining whether the OpenBSD approach works, or if this is evidence that it’s doomed to failure. I picked a few errata, not all of them, that were interesting and happened to suit my narrative. FreeBSD 2020 Q1 Quarterly report (https://www.freebsd.org/news/status/report-2020-01-2020-03.html) Welcome, to the quarterly reports, of the future! Well, at least the first quarterly report from 2020. The new timeline, mentioned in the last few reports, still holds, which brings us to this report, which covers the period of January 2020 - March 2020. News Roundup The Notion of Progress and User Interfaces (https://herebeseaswines.net/essays/2020-04-13-the-notion-of-progress-and-user-interfaces) One trait of modern Western culture is the notion of progress. A view claiming, at large, everything is getting better and better. How should we think about progress? Both in general and regarding technology? Thomas E. Dickey on NetBSD curses (https://implementality.blogspot.com/2020/04/thomas-e-dickey-on-netbsd-curses.html) I was recently pointed at a web page on Thomas E. Dickeys site talking about NetBSD curses. It seems initially that the page was intended to be a pointer to some differences between ncurses and NetBSD curses and does appear to start off in this vein but it seems that the author has lost the plot as the document evolved and the tail end of it seems to be devolving into some sort of slanging match. I don't want to go through Mr. Dickey's document point by point, that would be tedious but I would like to pick out some of the things that I believe to be the most egregious. Please note that even though I am a NetBSD developer, the opinions below are my own and not the NetBSD projects. Making Unix a little more Plan9-like (https://woozle.org/papers/plan9.html) I’m not really interested in defending anything. I tried out plan9port and liked it, but I have to live in Unix land. Here’s how I set that up. A Warning The suckless community, and some of the plan9 communities, are dominated by jackasses. I hope that’s strong enough wording to impress the severity. Don’t go into IRC for help. Stay off the suckless email list. The software is great, the people who write it are well-spoken and well-reasoned, but for some reason the fandom is horrible to everyone. Not-actually Linux distro review: FreeBSD 12.1-RELEASE (https://arstechnica.com/gadgets/2020/04/not-actually-linux-distro-review-freebsd-12-1-release/) This month's Linux distro review isn't of a Linux distribution at all—instead, we're taking a look at FreeBSD, the original gangster of free Unix-like operating systems. The first FreeBSD release was in 1993, but the operating system's roots go further back—considerably further back. FreeBSD started out in 1992 as a patch-release of Bill and Lynne Jolitz's 386BSD—but 386BSD itself came from the original Berkeley Software Distribution (BSD). BSD itself goes back to 1977—for reference, Linus Torvalds was only seven years old then. Before we get started, I'd like to acknowledge something up front—our distro reviews include the desktop experience, and that is very much not FreeBSD's strength. FreeBSD is far, far better suited to running as a headless server than as a desktop! We're going to get a full desktop running on it anyway, because according to Lee Hutchinson, I hate myself—and also because we can't imagine readers wouldn't care about it. FreeBSD does not provide a good desktop experience, to say the least. But if you're hankering for a BSD-based desktop, don't worry—we're already planning a followup review of GhostBSD, a desktop-focused BSD distribution. Beastie Bits Wifi renewal restarted (https://blog.netbsd.org/tnf/entry/wifi_renewal_restarted) HAMMER2 and a quick start for DragonFly (https://www.dragonflydigest.com/2020/04/21/24421.html) Engineering NetBSD 9.0 (http://netbsd.org/~kamil/AsiaBSDCon/Kamil_Rytarowski_Engineering_NetBSD_9.0.pdf) Antivirus Protection using OPNsense Plugins (https://www.youtube.com/watch?v=94vz_-5lAkE) BSDCan Home Lab Panel recording session: May 5th at 18:00 UTC (https://twitter.com/allanjude/status/1251895348836143104) BSDNow is going Independent After being part of Jupiter Broadcasting since we started back in 2013, BSDNow is moving to become independent. We extend a very large thank you to Jupiter Broadcasting and Linux Academy for hosting us for so many years, and allowing us to bring you over 100 episodes without advertisements. LinuxAcademy is now under new leadership, and we understand that cutbacks needed to be made, and that BSD is not their core product. That does not mean your favourite BSD podcast is going away, we will continue and we expect things will not look much different. What does this mean for you, the listener? Not much will change, just make sure your subscription is via the RSS feed at BSDNow.tv rather than one of the Jupiter Broadcasting feeds. We will update you with more news as things settle out. Feedback/Questions Jordyn - ZFS Pool Problem (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/347/feedback/Jordyn%20zfs%20pool%20problem.md) debug - https://github.com/BSDNow/bsdnow.tv/raw/master/episodes/347/feedback/dbg.txt Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Your browser does not support the HTML5 video tag.

Rethinking OpenBSD security, FreeBSD 2020 Q1 status report, the notion of progress and user interfaces, Comments about Thomas E. Dickey on NetBSD curses, making Unix a little more Plan9-like, Not-actually Linux distro review: FreeBSD, and more.

Rethinking OpenBSD security, FreeBSD 2020 Q1 status report, the notion of progress and user interfaces, Comments about Thomas E. Dickey on NetBSD curses, making Unix a little more Plan9-like, Not-actually Linux distro review: FreeBSD, and more.

On this episode of On the Metal, we interview Ron Minnich. Ron has had a fascinating career working on the interface between software and hardware. Join us to hear a mesmerizing conversation about Unix, Plan9, LinuxBIOS, Chromebooks, RISC-V, of course some Gentoo jokes, flip flop programming toys, and more!

A PI-powered Plan 9 cluster, an SSH tarpit, rdist for when Ansible is too much, falling in love with OpenBSD again, how I created my first FreeBSD port, the Tilde Institute of OpenBSD education and more. Headlines A Pi-Powered Plan 9 Cluster Plan 9 from Bell Labs comes from the same stable as the UNIX operating system, which of course Linux was designed after, and Apple’s OS X runs on top of a certified UNIX operating system. Just like UNIX, Plan 9 was developed as a research O/S — a vehicle for trying out new concepts — with it building on key UNIX principles and taking the idea of devices are just files even further. In this post, we take a quick look at the Plan 9 O/S and some of the notable features, before moving on to the construction of a self-contained 4-node Raspberry Pi cluster that will provide a compact platform for experimentation. Endlessh: an SSH Tarpit I’m a big fan of tarpits: a network service that intentionally inserts delays in its protocol, slowing down clients by forcing them to wait. This arrests the speed at which a bad actor can attack or probe the host system, and it ties up some of the attacker’s resources that might otherwise be spent attacking another host. When done well, a tarpit imposes more cost on the attacker than the defender. The Internet is a very hostile place, and anyone who’s ever stood up an Internet-facing IPv4 host has witnessed the immediate and continuous attacks against their server. I’ve maintained such a server for nearly six years now, and more than 99% of my incoming traffic has ill intent. One part of my defenses has been tarpits in various forms. News Roundup rdist(1) – when Ansible is too much The post written about rdist(1) on johan.huldtgren.com sparked us to write one as well. It's a great, underappreciated, tool. And we wanted to show how we wrapped doas(1) around it. There are two services in our infrastructure for which we were looking to keep the configuration in sync and to reload the process when the configuration had indeed changed. There is a pair of nsd(8)/unbound(8) hosts and a pair of hosts running relayd(8)/httpd(8) with carp(4) between them. We didn't have a requirement to go full configuration management with tools like Ansible or Salt Stack. And there wasn't any interest in building additional logic on top of rsync or repositories. > Enter rdist(1), rdist is a program to maintain identical copies of files over multiple hosts. It preserves the owner, group, mode, and mtime of files if possible and can update programs that are executing. Falling in love with OpenBSD again I was checking the other day and was appalled at how long it has been since I posted here. I had been working a job during 2018 that had me traveling 3,600 miles by air every week so that is at least a viable excuse. So what is my latest project? I wanted to get something better than the clunky old T500 “freedom laptop” that I could use as my daily driver. Some background here. My first paid gig as a programmer was on SunOS 4 (predecessor to Solaris) and Ultrix (on a DEC MicroVAX). I went from there to a Commodore Amiga (preemptive multitasking in 1985!). I went from there to OS/2 (I know, patron saint of lost causes) and then finally decided to “sell out” and move to Windows as the path of least resistance in the mid 90’s. My wife bought me an iPod literally just as they started working with computers other than Macs and I watched with fascination as Apple made the big gamble and moved away from PowerPC chips to Intel. That was the beginning of the Apple Fan Boi years for me. My gateway drug was a G4 MacMini and I managed somehow to get in on the pre-production, developer build of an Intel-based Mac. I was quite happy on the platform until about three years ago. How I Created My First FreeBSD Port I created my first FreeBSD port recently. I found that FreeBSD didn't have a port for GoCD, which is a continuous integration and continuous deployment (CI/CD) system. This was a great opportunity to learn how to build a FreeBSD port while also contributing back to the community The Tilde Institute of OpenBSD Education Welcome to tilde.institute! This is an OpenBSD machine whose purpose is to provide a space in the tildeverse for experimentation with and education of the OpenBSD operating system. A variety of editors, shells, and compilers are installed to allow for development in a native OpenBSD environment. OpenBSD's httpd(8) is configured with slowcgi(8) as the fastcgi provider and sqlite3 available. This allows users to experiment with web development using compiled CGI in C, aka the BCHS Stack. In addition to php7.0 and mysql (mariadb) by request, this provides an environment where the development of complex web apps is possible. Beastie Bits SoloBSD 19.03-STABLE WireGuard for NetBSD [NetBSD - Removing PF](https://mail-index.netbsd.org/tech-kern/2019/03/29/msg024883.html ) What does the N in nmake stand for? A Map of the Internet from May 1973 NSA-B-Gone : A sketchy hardware security device for your x220 Feedback/Questions Jake - A single jail as a VPN client Matt - Surprising BSD Features cia - Routing and ZFS Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv Your browser does not support the HTML5 video tag.

Notre invité ce matin est : Aurélien Moulinet, Chargé de communication de l'association PLAN9 qui participe à la Fête du court-métrage à Dijon, au cinéma Eldorado du 15 au 17 mars ! Au programme: 4 projections publiques: Talents d'aujourd'hui, Drôle de bête, Abracadabra et Lumière. Des séances pour le jeune public seront aussi proposées à la MJC des Grésilles dès mercredi et un atelier pour les professionneles de la filière cinéma est prévu le 15 mars à La Minoterie, création jeune p

Notre invité ce matin est : Aurélien Moulinet, Chargé de communication de l'association PLAN9 qui participe à la Fête du court-métrage à Dijon, au cinéma Eldorado du 15 au 17 mars ! Au programme: 4 projections publiques: Talents d'aujourd'hui, Drôle de bête, Abracadabra et Lumière. Des séances pour le jeune public seront aussi proposées à la MJC des Grésilles dès mercredi et un atelier pour les professionneles de la filière cinéma est prévu le 15 mars à La Minoterie, création jeune p

Notre invité ce matin est : Aurélien Moulinet, Chargé de communication de l’association PLAN9 qui participe à la Fête du court-métrage à Dijon, au cinéma Eldorado du 15 au 17 mars ! Au programme: 4 projections publiques: Talents d'aujourd'hui, Drôle de bête, Abracadabra et Lumière. Des séances pour le jeune public seront aussi proposées à la MJC des Grésilles dès mercredi et un atelier pour les professionneles de la filière cinéma est prévu le 15 mars à La Minoterie, création jeune p

Notre invité ce matin est : Aurélien Moulinet, Chargé de communication de l’association PLAN9 qui participe à la Fête du court-métrage à Dijon, au cinéma Eldorado du 15 au 17 mars ! Au programme: 4 projections publiques: Talents d'aujourd'hui, Drôle de bête, Abracadabra et Lumière. Des séances pour le jeune public seront aussi proposées à la MJC des Grésilles dès mercredi et un atelier pour les professionneles de la filière cinéma est prévu le 15 mars à La Minoterie, création jeune p

Fanless server setup with FreeBSD, NetBSD on pinebooks, another BSDCan trip report, transparent network audio, MirBSD's Korn Shell on Plan9, static site generators on OpenBSD, and more.

Fanless server setup with FreeBSD, NetBSD on pinebooks, another BSDCan trip report, transparent network audio, MirBSD's Korn Shell on Plan9, static site generators on OpenBSD, and more.

Fanless server setup with FreeBSD, NetBSD on pinebooks, another BSDCan trip report, transparent network audio, MirBSD's Korn Shell on Plan9, static site generators on OpenBSD, and more. ##Headlines Silent Fanless FreeBSD Desktop/Server Today I will write about silent fanless FreeBSD desktop or server computer … or NAS … or you name it, it can have multiple purposes. It also very low power solution, which also means that it will not overheat. Silent means no fans at all, even for the PSU. The format of the system should also be brought to minimum, so Mini-ITX seems best solution here. I have chosen Intel based solutions as they are very low power (6-10W), if you prefer AMD (as I often do) the closest solution in comparable price and power is Biostar A68N-2100 motherboard with AMD E1-2100 CPU and 9W power. Of course AMD has even more low power SoC solutions but finding the Mini-ITX motherboard with decent price is not an easy task. For comparison Intel has lots of such solutions below 6W whose can be nicely filtered on the ark.intel.com page. Pity that AMD does not provide such filtration for their products. I also chosen AES instructions as storage encryption (GELI on FreeBSD) today seems as obvious as HTTPS for the web pages. Here is how the system look powered up and working This motherboard uses Intel J3355 SoC which uses 10W and has AES instructions. It has two cores at your disposal but it also supports VT-x and EPT extensions so you can even run Bhyve on it. Components Now, an example system would look like that one below, here are the components with their prices. $49 CPU/Motherboard ASRock J3355B-ITX Mini-ITX $14 RAM Crucial 4 GB DDR3L 1.35V (low power) $17 PSU 12V 160W Pico (internal) $11 PSU 12V 96W FSP (external) $5 USB 2.0 Drive 16 GB ADATA $4 USB Wireless 802.11n $100 TOTAL The PSU 12V 160W Pico (internal) and PSU 12V 96W FSP can be purchased on aliexpress.com or ebay.com for example, at least I got them there. Here is the 12V 160W Pico (internal) PSU and its optional additional cables to power the optional HDDs. If course its one SATA power and one MOLEX power so additional MOLEX-SATA power adapter for about 1$ would be needed. Here is the 12V 96W FSP (external) PSU without the power cord. This gives as total silent fanless system price of about $120. Its about ONE TENTH OF THE COST of the cheapest FreeNAS hardware solution available – the FreeNAS Mini (Diskless) costs $1156 also without disks. You can put plain FreeBSD on top of it or Solaris/Illumos distribution OmniOSce which is server oriented. You can use prebuilt NAS solution based on FreeBSD like FreeNAS, NAS4Free, ZFSguru or even Solaris/Illumos based storage with napp-it appliance. ###An annotated look at a NetBSD Pinebook’s startup Pinebook is an affordable 64-bit ARM notebook. Today we’re going to take a look at the kernel output at startup and talk about what hardware support is available on NetBSD. Photo Pinebook comes with 2GB RAM standard. A small amount of this is reserved by the kernel and framebuffer. NetBSD uses flattened device-tree (FDT) to enumerate devices on all Allwinner based SoCs. On a running system, you can inspect the device tree using the ofctl(8) utility: Pinebook’s Allwinner A64 processor is based on the ARM Cortex-A53. It is designed to run at frequencies up to 1.2GHz. The A64 is a quad core design. NetBSD’s aarch64 pmap does not yet support SMP, so three cores are disabled for now. The interrupt controller is a standard ARM GIC-400 design. Clock drivers for managing PLLs, module clock dividers, clock gating, software resets, etc. Information about the clock tree is exported in the hw.clk sysctl namespace (root access required to read these values). # sysctl hw.clk.sun50ia64ccu0.mmc2 hw.clk.sun50ia64ccu0.mmc2.rate = 200000000 hw.clk.sun50ia64ccu0.mmc2.parent = pllperiph02x hw.clk.sun50ia64ccu0.mmc2.parent_domain = sun50ia64ccu0 Digital Ocean http://do.co/bsdnow ###BSDCan 2018 Trip Report: Mark Johnston BSDCan is a highlight of my summers: the ability to have face-to-face conversations with fellow developers and contributors is invaluable and always helps refresh my enthusiasm for FreeBSD. While in a perfect world we would all be able to communicate effectively over the Internet, it’s often noted that locking a group of developers together in a room can be a very efficient way to make progress on projects that otherwise get strung out over time, and to me this is one of the principal functions of BSD conferences. In my case I was able to fix some kgdb bugs that had been hindering me for months; get some opinions on the design of a feature I’ve been working on for FreeBSD 12.0; hear about some ongoing usage of code that I’ve worked on; and do some pair-debugging of an issue that has been affecting another developer. As is tradition, on Tuesday night I dropped off my things at the university residence where I was staying, and headed straight to the Royal Oak. This year it didn’t seem quite as packed with BSD developers, but I did meet several long-time colleagues and get a chance to catch up. In particular, I chatted with Justin Hibbits and got to hear about the bring-up of FreeBSD on POWER9, a new CPU family released by IBM. Justin was able to acquire a workstation based upon this CPU, which is a great motivator for getting FreeBSD into shape on that platform. POWER9 also has some promise in the server market, so it’s important for FreeBSD to be a viable OS choice there. Wednesday morning saw the beginning of the two-day FreeBSD developer summit, which precedes the conference proper. Gordon Tetlow led the summit and did an excellent job organizing things and keeping to the schedule. The first presentation was by Deb Goodkin of the FreeBSD Foundation, who gave an overview of the Foundation’s role and activities. After Deb’s presentation, present members of the FreeBSD core team discussed the work they had done over the past two years, as well as open tasks that would be handed over to the new core team upon completion of the ongoing election. Finally, Marius Strobl rounded off the day’s presentations by discussing the state and responsibilities of FreeBSD’s release engineering team. One side discussion of interest to me was around the notion of tightening integration with our Bugzilla instance; at moment we do not have any good means to mark a given bug as blocking a release, making it easy for bugs to slip into releases and thus lowering our overall quality. With FreeBSD 12.0 upon us, I plan to help with the triage and fixes for known regressions before the release process begins. After a break, the rest of the morning was devoted to plans for features in upcoming FreeBSD releases. This is one of my favorite discussion topics and typically takes the form of have/need/want, where developers collectively list features that they’ve developed and intend to upstream (have), features that they are missing (need), and nice-to-have features (want). This year, instead of the usual format, we listed features that are intended to ship in FreeBSD 12.0. The compiled list ended up being quite ambitious given how close we are to the beginning of the release cycle, but many individual developers (including myself) have signed up to deliver work. I’m hopeful that most, if not all of it, will make it into the release. After lunch, I attended a discussion led by Matt Ahrens and Alexander Motin on OpenZFS. Of particular interest to me were some observations made regarding the relative quantity and quality of contributions made by different “camps” of OpenZFS users (illumos, FreeBSD and ZoL), and their respective track records of upstreaming enhancements to the OpenZFS project. In part due to the high pace of changes in ZoL, the definition of “upstream” for ZFS has become murky, and of late ZFS changes have been ported directly from ZoL. Alexander discussed some known problems with ZFS on FreeBSD that have been discovered through performance testing. While I’m not familiar with ZFS internals, Alexander noted that ZFS’ write path has poor SMP scalability on FreeBSD owing to some limitations in a certain kernel API called taskqueue(9). I would like to explore this problem further and perhaps integrate a relatively new alternative interface which should perform better. Friday and Saturday were, of course, taken up by BSDCan talks. Friday’s keynote was by Benno Rice, who provided some history of UNIX boot systems as a precursor to some discussion of systemd and the difficulties presented by a user and developer community that actively resist change. The rest of the morning was consumed by talks and passed by quickly. First was Colin Percival’s detailed examination of where the FreeBSD kernel spends time during boot, together with an overview of some infrastructure he added to track boot times. He also provided a list of improvements that have been made since he started taking measurements, and some areas we can further improve. Colin’s existing work in this area has already brought about substantial reductions in boot time; amusingly, one of the remaining large delays comes from the keyboard driver, which contains a workaround for old PS/2 keyboards. While there seems to be general agreement that the workaround is probably no longer needed on most systems, the lingering uncertainty around this prevents us from removing the workaround. This is, sadly, a fairly typical example of an OS maintenance burden, and underscores the need to carefully document hardware bug workarounds. After this talk, I got to see some rather novel demonstrations of system tracing using dwatch, a new utility by Devin Teske, which aims to provide a user-friendly interface to DTrace. After lunch, I attended talks on netdump, a protocol for transmitting kernel dumps over a network after the system has panicked, and on a VPC implementation for FreeBSD. After the talks ended, I headed yet again to the hacker lounge and had some fruitful discussions on early microcode loading (one of my features for FreeBSD 12.0). These led me to reconsider some aspects of my approach and saved me a lot of time. Finally, I continued my debugging session from Wednesday with help from a couple of other developers. Saturday’s talks included a very thorough account by Li-Wen Hsu of his work in organizing a BSD conference in Taipei last year. As one of the attendees, I had felt that the conference had gone quite smoothly and was taken aback by the number of details and pitfalls that Li-Wen enumerated during his talk. This was followed by an excellent talk by Baptiste Daroussin on the difficulties one encounters when deploying FreeBSD in new environments. Baptiste offered criticisms of a number of aspects of FreeBSD, some of which hit close to home as they involved portions of the system that I’ve worked on. At the conclusion of the talks, we all gathered in the main lecture hall, where Dan led a traditional and quite lively auction for charity. I managed to snag a Pine64 board and will be getting FreeBSD installed on it the first chance I get. At the end of the auction, we all headed to ByWard for dinner, concluding yet another BSDCan. Thanks to Mark for sharing his experiences at this years BSDCan ##News Roundup Transparent network audio with mpd & sndiod Landry Breuil (landry@ when wearing his developer hat) wrote in… I've been a huge fan of MPD over the years to centralize my audio collection, and i've been using it with the http output to stream the music as a radio on the computer i'm currently using… audio_output { type "sndio" name "Local speakers" mixer_type "software" } audio_output { type "httpd" name "HTTP stream" mixer_type "software" encoder "vorbis" port "8000" format "44100:16:2" } this setup worked for years, allows me to stream my home radio to $work by tunnelling the port 8000 over ssh via LocalForward, but that still has some issues: a distinct timing gap between the 'local output' (ie the speakers connected to the machine where MPD is running) and the 'http output' caused by the time it takes to reencode the stream, which is ugly when you walk through the house and have a 15s delay sometimes mplayer as a client doesn't detect the pauses in the stream and needs to be restarted i need to configure/start a client on each computer and point it at the sound server url (can do via gmpc shoutcast client plugin…) it's not that elegant to reencode the stream, and it wastes cpu cycles So the current scheme is: mpd -> http output -> network -> mplayer -> sndiod on remote machine | -> sndio output -> sndiod on soundserver Fiddling a little bit with mpd outputs and reading the sndio output driver, i remembered sndiod has native network support… and the mpd sndio output allows you to specify a device (it uses SIO_DEVANY by default). So in the end, it's super easy to: enable network support in sndio on the remote machine i want the audio to play by adding -L to sndiod_flags (i have two audio devices, with an input coming from the webcam): sndiod_flags="-L10.246.200.10 -f rsnd/0 -f rsnd/1" open pf on port 11025 from the sound server ip: pass in proto tcp from 10.246.200.1 to any port 11025 configure a new output in mpd: audio_output { type "sndio" name "sndio on renton" device "snd@10.246.200.10/0" mixer_type "software" } and enable the new output in mpd: $mpc enable 2 Output 1 (Local speakers) is disabled Output 2 (sndio on renton) is enabled Output 3 (HTTP stream) is disabled Results in a big win: no gap anymore with the local speakers, no reencoding, no need to configure a client to play the stream, and i can still probably reproduce the same scheme over ssh from $work using a RemoteForward. mpd -> sndio output 2 -> network -> sndiod on remote machine | -> sndio output 1 -> sndiod on soundserver Thanks ratchov@ for sndiod :) ###MirBSD’s Korn Shell on Plan9 Jehanne Let start by saying that I’m not really a C programmer. My last public contribution to a POSIX C program was a little improvement to the Snort’s react module back in 2008. So while I know the C language well enough, I do not know anything about the subtleness of the standard library and I have little experience with POSIX semantics. This is not a big issue with Plan 9, since the C library and compiler are not standard anyway, but with Jehanne (a Plan 9 derivative of my own) I want to build a simple, loosely coupled, system that can actually run useful free software ported from UNIX. So I ported RedHat’s newlib to Jehanne on top of a new system library I wrote, LibPOSIX, that provides the necessary emulations. I wrote several test, checking they run the same on Linux and Jehanne, and then I begun looking for a real-world, battle tested, application to port first. I approached MirBSD’s Korn Shell for several reason: it is simple, powerful and well written it has been ported to several different operating systems it has few dependencies it’s the default shell in Android, so it’s really battle tested I was very confident. I had read the POSIX standard after all! And I had a test suite! I remember, I thought “Given newlib, how hard can it be?” The porting begun on September 1, 2017. It was completed by tg on January 5, 2018. 125 nights later. Turn out, my POSIX emulation was badly broken. Not just because of the usual bugs that any piece of C can have: I didn’t understood most POSIX semantics at all! iXsystems ###Static site generator with rsync and lowdown on OpenBSD ssg is a tiny POSIX-compliant shell script with few dependencies: lowdown(1) to parse markdown, rsync(1) to copy temporary files, and entr(1) to watch file changes. It generates Markdown articles to a static website. It copies the current directory to a temporary on in /tmp skipping .* and _*, renders all Markdown articles to HTML, generates RSS feed based on links from index.html, extracts the first tag from every article to generate a sitemap and use it as a page title, then wraps articles with a single HTML template, copies everything from the temporary directory to $DOCS/ Why not Jekyll or “$X”? ssg is one hundred times smaller than Jekyll. ssg and its dependencies are about 800KB combined. Compare that to 78MB of ruby with Jekyll and all the gems. So ssg can be installed in just few seconds on almost any Unix-like operating system. Obviously, ssg is tailored for my needs, it has all features I need and only those I use. Keeping ssg helps you to master your Unix-shell skills: awk, grep, sed, sh, cut, tr. As a web developer you work with lots of text: code and data. So you better master these wonderful tools. Performance 100 pps. On modern computers ssg generates a hundred pages per second. Half of a time for markdown rendering and another half for wrapping articles into the template. I heard good static site generators work—twice as fast—at 200 pps, so there’s lots of performance that can be gained. ;) ###Why does FreeBSD have virtually no (0%) desktop market share? Because someone made a horrible design decision back in 1984. In absolute fairness to those involved, it was an understandable decision, both from a research perspective, and from an economic perspective, although likely not, from a technology perspective. Why and what. The decision was taken because the X Window System was intended to run on cheap hardware, and, at the time, that meant reduced functionality in the end-point device with the physical display attached to it. At the same time, another force was acting to also limit X displays to display services only, rather than rolling in both window management and specific widget instances for common operational paradigms. Mostly, common operational paradigms didn’t really exist for windowing systems because they also simply didn’t exist at the time, and no one really knew how people were going to use the things, and so researchers didn’t want to commit future research to a set of hard constraints. So a decision was made: separate the display services from the application at the lowest level of graphics primitives currently in use at the time. The ramifications of this were pretty staggering. First, it guaranteed that all higher level graphics would live on the host side of the X protocol, instead of on the display device side of the protocol. Despite a good understanding of Moore’s law, and the fact that, since no X Terminals existed at the time as hardware, but were instead running as emulations on workstations that had sufficient capability, this put the higher level GUI object libraries — referred to as “widgets” — in host libraries linked into the applications. Second, it guaranteed that display organization and management paradigms would also live on the host side of the protocol — assumed, in contradiction to the previous decision, to be running on the workstation. But, presumably, at some point, as lightweight X Terminals became available, to migrate to a particular host computer managing compute resource login/access services. Between these early decisions reigned chaos. Specifically, the consequences of these decisions have been with us ever since: Look-and-feel are a consequence of the toolkit chosen by the application programmer, rather than a user decision which applies universally to all applications. You could call this “lack of a theme”, and — although I personally despise the idea of customizing or “theming” desktops — this meant that one paradigm chosen by the user would not apply universally across all applications, no matter who had written them. Window management style is a preference. You could call this a more radical version of “theming” — which you will remember, I despise — but a consequence to this is that training is not universal across personnel using such systems, nor is it transferrable. In other words, I can’t send someone to a class, and have them come back and use the computers in the office as a tool, with the computer itself — and the elements not specific to the application itself — disappearing into the background. Both of these ultimately render an X-based system unsuitable for desktops. I can’t pay once for training. Training that I do pay for does not easily and naturally translate between applications. Each new version may radically alter the desktop management paradigm into unrecognizability. Is there hope for the future? Well, the Linux community has been working on something called Wayland, and it is very promising… …In the same way X was “very promising” in 1984, because, unfortunately, they are making exactly the same mistakes X made in 1984, rather than correcting them, now that we have 20/20 hindsight, and know what a mature widget library should look like. So Wayland is screwing up again. But hey, it only took us, what, 25 years to get from X in 1987 to Wayland in in 2012. Maybe if we try again in 2037, we can get to where Windows was in 1995. ##Beastie Bits New washing machine comes with 7 pages of open source licenses! BSD Jobs Site FreeBSD Foundation Update, May 2018 FreeBSD Journal looking for book reviewers zedenv ZFS Boot Environment Manager Tarsnap ##Feedback/Questions Wouter - Feedback Efraim - OS Suggestion kevr - Raspberry Pi2/FreeBSD/Router on a Stick Vanja - Interview Suggestion Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

My roots allow me to connect with two entrepreneurial ecosystems, US and Pakistan. It has allowed me to connect with both successful and aspiring entrepreneurs in Pakistan, do workshops when I visit, and also interview the ones that are helping accelerate the growth of startups over there. Today, I'm bringing you one of those facilitators, Nabeel Qadeer. Well, calling him a facilitator would be an understatement. Nabeel is:Director of Entrepreneurship at PITB, which is the equivalent of a state ministry. The chairman of that board, Umar Saif, is also a remarkable technologist and visionary, and I've had the pleasure of interviewing him on my previous podcast.Head of Plan9, an incubator in Lahore, my hometown. Plan9 sends startups to the US twice a year as part of a partnership with the US State Department and the City of Austin. In fact, this episode was recorded a few days after a cohort of those startups visited their business.Anchor / Content producer of Pakistan's first business-reality show, Idea Croron Ka “A Million Dollar Idea”, a show watched by 5-7M people. The focus of our episode is the creation and execution of this show.This episode was recorded in Capital Factory, to which I just won a 6-month membership in a pitch competition at the University of Texas In the middle of the show, we move rooms to avoid the heat pouring down and the creaking of the chairs... so, yeah just letting you know ha. As always, let me know you're listening in by tweeting @fireshowpodcast or @notthatmoby. You can continue this conversation with Nabeel by tweeting him @nabeelaq Ladies, gents, lizard people running the world, enjoy!

FreeBSD 11.1-Beta1 is out, we discuss Kernel address randomized link (KARL), and explore the benefits of daily OpenBSD source code reading This episode was brought to you by Headlines FreeBSD 11.1-Beta1 now available (https://lists.freebsd.org/pipermail/freebsd-stable/2017-June/087242.html) Glen Barber, of the FreeBSD release engineering team has announced that FreeBSD 11.1-Beta1 is now available for the following architectures: 11.1-BETA1 amd64 GENERIC 11.1-BETA1 i386 GENERIC 11.1-BETA1 powerpc GENERIC 11.1-BETA1 powerpc64 GENERIC64 11.1-BETA1 sparc64 GENERIC 11.1-BETA1 armv6 BANANAPI 11.1-BETA1 armv6 BEAGLEBONE 11.1-BETA1 armv6 CUBIEBOARD 11.1-BETA1 armv6 CUBIEBOARD2 11.1-BETA1 armv6 CUBOX-HUMMINGBOARD 11.1-BETA1 armv6 GUMSTIX 11.1-BETA1 armv6 RPI-B 11.1-BETA1 armv6 RPI2 11.1-BETA1 armv6 PANDABOARD 11.1-BETA1 armv6 WANDBOARD 11.1-BETA1 aarch64 GENERIC Note regarding arm/armv6 images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. The full schedule (https://www.freebsd.org/releases/11.1R/schedule.html) for 11.1-RELEASE is here, the final release is expected at the end of July It was also announced there will be a 10.4-RELEASE scheduled for October (https://www.freebsd.org/releases/10.4R/schedule.html) *** KARL – kernel address randomized link (https://marc.info/?l=openbsd-tech&m=149732026405941&w=2) Over the last three weeks I've been working on a new randomization feature which will protect the kernel. The situation today is that many people install a kernel binary from OpenBSD, and then run that same kernel binary for 6 months or more. We have substantial randomization for the memory allocations made by the kernel, and for userland also of course. Previously, the kernel assembly language bootstrap/runtime locore.S was compiled and linked with all the other .c files of the kernel in a deterministic fashion. locore.o was always first, then the .c files order specified by our config(8) utility and some helper files. In the new world order, locore is split into two files: One chunk is bootstrap, that is left at the beginning. The assembly language runtime and all other files are linked in random fashion. There are some other pieces to try to improve the randomness of the layout. As a result, every new kernel is unique. The relative offsets between functions and data are unique. It still loads at the same location in KVA. This is not kernel ASLR! ASLR is a concept where the base address of a module is biased to a random location, for position-independent execution. In this case, the module itself is perturbed but it lands at the same location, and does not need to use position-independent execution modes. LLDB: Sanitizing the debugger's runtime (https://blog.netbsd.org/tnf/entry/lldb_sanitizing_the_debugger_s) The good Besides the greater enhancements this month I performed a cleanup in the ATF ptrace(2) tests again. Additionally I have managed to unbreak the LLDB Debug build and to eliminate compiler warnings in the NetBSD Native Process Plugin. It is worth noting that LLVM can run tests on NetBSD again, the patch in gtest/LLVM has been installed by Joerg Sonnenberg and a more generic one has been submitted to the upstream googletest repository. There was also an improvement in ftruncate(2) on the LLVM side (authored by Joerg). Since LLD (the LLVM linker) is advancing rapidly, it improved support for NetBSD and it can link a functional executable on NetBSD. I submitted a patch to stop crashing it on startup anymore. It was nearly used for linking LLDB/NetBSD and it spotted a real linking error... however there are further issues that need to be addressed in the future. Currently LLD is not part of the mainline LLDB tasks - it's part of improving the work environment. This linker should reduce the linking time - compared to GNU linkers - of LLDB by a factor of 3x-10x and save precious developer time. As of now LLDB linking can take minutes on a modern amd64 machine designed for performance. Kernel correctness I have researched (in pkgsrc-wip) initial support for multiple threads in the NetBSD Native Process Plugin. This code revealed - when running the LLDB regression test-suite - new kernel bugs. This unfortunately affects the usability of a debugger in a multithread environment in general and explains why GDB was never doing its job properly in such circumstances. One of the first errors was asserting kernel panic with PT*STEP, when a debuggee has more than a single thread. I have narrowed it down to lock primitives misuse in the doptrace() kernel code. The fix has been committed. The bad Unfortunately this is not the full story and there is further mandatory work. LLDB acceleration The EV_SET() bug broke upstream LLDB over a month ago, and during this period the debugger was significantly accelerated and parallelized. It is difficult to declare it definitely, but it might be the reason why the tracer's runtime broke due to threading desynchronization. LLDB behaves differently when run standalone, under ktruss(1) and under gdb(1) - the shared bug is that it always fails in one way or another, which isn't trivial to debug. The ugly There are also unpleasant issues at the core of the Operating System. Kernel troubles Another bug with single-step functions that affects another aspect of correctness - this time with reliable execution of a program - is that processes die in non-deterministic ways when single-stepped. My current impression is that there is no appropriate translation between process and thread (LWP) states under a debugger. These issues are sibling problems to unreliable PTRESUME and PTSUSPEND. In order to be able to appropriately address this, I have diligently studied this month the Solaris Internals book to get a better image of the design of the NetBSD kernel multiprocessing, which was modeled after this commercial UNIX. Plan for the next milestone The current troubles can be summarized as data races in the kernel and at the same time in LLDB. I have decided to port the LLVM sanitizers, as I require the Thread Sanitizer (tsan). Temporarily I have removed the code for tracing processes with multiple threads to hide the known kernel bugs and focus on the LLDB races. Unfortunately LLDB is not easily bisectable (build time of the LLVM+Clang+LLDB stack, number of revisions), therefore the debugging has to be performed on the most recent code from upstream trunk. d2K17 Hackathon Reports d2k17 Hackathon Report: Ken Westerback on XSNOCCB removal and dhclient link detection (http://undeadly.org/cgi?action=article&sid=20170605225415) d2k17 Hackathon Report: Antoine Jacoutot on rc.d, syspatch, and more (http://undeadly.org/cgi?action=article&sid=20170608074033) d2k17 Hackathon Report: Florian Obser on slaacd(8) (http://undeadly.org/cgi?action=article&sid=20170609013548) d2k17 Hackathon Report: Stefan Sperling on USB audio, WiFi Progress (http://undeadly.org/cgi?action=article&sid=20170602014048) News Roundup Multi-tenant router or firewall with FreeBSD (https://bsdrp.net/documentation/examples/multi-tenant_router_and_firewall) Setting-up a virtual lab Downloading BSD Router Project images Download BSDRP serial image (prevent to have to use an X display) on Sourceforge. Download Lab scripts More information on these BSDRP lab scripts available on How to build a BSDRP router lab (https://bsdrp.net/documentation/examples/how_to_build_a_bsdrp_router_lab). Start the lab with full-meshed 5 routers and one shared LAN, on this example using bhyve lab script on FreeBSD: [root@FreeBSD]~# tools/BSDRP-lab-bhyve.sh -i BSDRP-1.71-full-amd64-serial.img.xz -n 5 -l 1 Configuration Router 4 (R4) hosts the 3 routers/firewalls for each 3 customers. Router 1 (R1) belongs to customer 1, router 2 (R2) to customer 2 and router 3 (R3) to customer 3. Router 5 (R5) simulates a simple Internet host Using pf firewall in place of ipfw pf need a little more configuration because by default /dev/pf is hidden from jail. Then, on the host we need to: In place of loading the ipfw/ipfw-nat modules we need to load the pf module (but still disabling pf on our host for this example) Modify default devd rules for allowing jails to see /dev/pf (if you want to use tcpdump inside your jail, you should use bpf device too) Replacing nojail tag by nojailvnet tag into /etc/rc.d/pf (already done into BSDRP (https://github.com/ocochard/BSDRP/blob/master/BSDRP/patches/freebsd.pf.rc.jail.patch)) Under the hood: jails-on-nanobsd BSDRP's tenant shell script (https://github.com/ocochard/BSDRP/blob/master/BSDRP/Files/usr/local/sbin/tenant) creates jail configuration compliant with a host running nanobsd. Then these jails need to be configured for a nanobsd: Being nullfs based for being hosted on a read-only root filesystem Have their /etc and /var into tmpfs disks (then we need to populate these directory before each start) Configuration changes need to be saved with nanobsd configuration tools, like “config save” on BSDRP And on the host: autosave daemon (https://github.com/ocochard/BSDRP/blob/master/BSDRP/Files/usr/local/sbin/autosave) need to be enabled: Each time a customer will issue a “config save” inside a jail, his configuration diffs will be save into host's /etc/jails/. And this directory is a RAM disk too, then we need to automatically save hosts configuration on changes. *** OpenBSD Daily Source Reading (https://blog.tintagel.pl/2017/06/09/openbsd-daily.html) Adam Wołk writes: I made a new year's resolution to read at least one C source file from OpenBSD daily. The goal was to both get better at C and to contribute more to the base system and userland development. I have to admit that initially I wasn't consistent with it at all. In the first quarter of the year I read the code of a few small base utilities and nothing else. Still, every bit counts and it's never too late to get better. Around the end of May, I really started reading code daily - no days skipped. It usually takes anywhere between ten minutes (for small base utils) and one and a half hour (for targeted reads). I'm pretty happy with the results so far. Exploring the system on a daily basis, looking up things in the code that I don't understand and digging as deep as possible made me learn a lot more both about C and the system than I initially expected. There's also one more side effect of reading code daily - diffs. It's easy to spot inconsistencies, outdated code or an incorrect man page. This results in opportunities for contributing to the project. With time it also becomes less opportunitstic and more goal oriented. You might start with a https://marc.info/?l=openbsd-tech&m=149591302814638&w=2 (drive by diff to kill) optional compilation of an old compatibility option in chown that has been compiled in by default since 1995. Soon the contributions become more targeted, for example using a new API for encrypting passwords in the htpasswd utility after reading the code of the utility and the code for htpasswd handling in httpd. Similarly it can take you from discussing a doas feature idea with a friend to implementing it after reading the code. I was having a lot of fun reading code daily and started to recommend it to people in general discussions. There was one particular twitter thread that ended up starting something new. This is still a new thing and the format is not yet solidified. Generally I make a lot of notes reading code, instead of slapping them inside a local file I drop the notes on the IRC channel as I go. Everyone on the channel is encouraged to do the same or share his notes in any way he/she seems feasable. Check out the logs from the IRC discussions. Start reading code from other BSD projects and see whether you can replicate their results! *** Become FreeBSD User: Find Useful Tools (https://bsdmag.org/become-freebsd-user-find-useful-tools/) BSD Mag has the following article by David Carlier: If you're usually programming on Linux and you consider a potential switch to FreeBSD, this article will give you an overview of the possibilities. How to Install the Dependencies FreeBSD comes with either applications from binary packages or compiled from sources (ports). They are arranged according to software types (programming languages mainly in lang (or java specifically for Java), libraries in devel, web servers in www …) and the main tool for modern FreeBSD versions is pkg, similar to Debian apt tools suite. Hence, most of the time if you are looking for a specific application/library, simply pkg search without necessarily knowing the fully qualified name of the package. It is somehow sufficient. For example pkg search php7 will display php7 itself and the modules. Furthermore, php70 specific version and so on. Web Development Basically, this is the easiest area to migrate to. Most Web languages do not use specific platform features. Thus, most of the time, your existing projects might just be “drop-in” use cases. If your language of choice is PHP, you are lucky as this scripting language is workable on various operating systems, on most Unixes and Windows. In the case of FreeBSD, you have even many different ports or binary package versions (5.6 to 7.1). In this case, you may need some specific PHP modules enabled, luckily they are available atomically, or if the port is the way you chose, it is via the www/php70-extensions's one. Of course developing with Apache (both 2.2 and 2.4 series are available, respectively www/apache22 and www/apache24 packages), or even better with Nginx (the last stable or the latest development versions could be used, respectively www/nginx and www/nginx-devel packages) via php-fpm is possible. In terms of databases, we have the regular RDMBS like MySQL and PostgreSQL (client and server are distinct packages … databases/(mysql/portgresql)-client, and databases/(mysql/postgresql)-server). Additionally, a more modern concept of NoSQL with CouchDB, for example (databases/couchdb), MongoDB (databases/mongodb), and Cassandra (databases/cassandra), to name but a few. Low-level Development The BSDs are shipped with C and C++ compilers in the base. In the case of FreeBSD 11.0, it is clang 3.8.0 (in x86 architectures) otherwise, modern versions of gcc exist for developing with C++11. Examples are of course available too (lang/gcc … until gcc 7.0 devel). Numerous libraries for various topics are also present, web services SOAP with gsoap through User Interfaces with GTK (x11-toolkits/gtk), QT4 or QT 5 (devel/qt), malware libraries with Yara (security/yara), etc. Android / Mobile Development To be able to do Android development, to a certain degree, the Linux's compatibility layer (aka linuxulator) needs to be enabled. Also, x11-toolkits/swt and linux-f10-gtk2 port/package need to be installed (note that libswt-gtk-3550.so and libswt-pi-gtk-3550.so are necessary. The current package is versioned as 3557 and can be solved using symlinks). In the worst case scenario, remember that bhyve (or Virtualbox) is available, and can run any Linux distribution efficiently. Source Control Management FreeBSD comes in base with a version of subversion. As FreeBSD source is in a subversion repository, a prefixed svnlite command prevents conflicts with the package/port. Additionally, Git is present but via the package/port system with various options (with or without a user interface, subversion support). Conclusion FreeBSD has made tremendous improvements over the years to fill the gap created by Linux. FreeBSD still maintains its interesting specificities; hence there will not be too much blockers if your projects are reasonably sized to allow a migration to FreeBSD. Notes from project Aeronix, part 10 (https://martin.kopta.eu/blog/#2017-06-11-16-07-26) Prologue It is almost two years since I finished building Aeronix and it has served me well during that time. Only thing that ever broke was Noctua CPU fan, which I have replaced with the same model. However, for long time, I wanted to run Aeronix on OpenBSD instead of GNU/Linux Debian. Preparation I first experimented with RAID1 OpenBSD setup in VirtualBox, plugging and unplugging drives and learned that OpenBSD RAID1 is really smooth. When I finally got the courage, I copied all the data on two drives outside of Aeronix. One external HDD I regulary use to backup Aeronix and second internal drive in my desktop computer. Copying the data took about two afternoons. Aeronix usually has higher temperatures (somewhere around 55°C or 65°C depending on time of the year), and when stressed, it can go really high (around 75°C). During full speed copy over NFS and to external drive it went as high as 85°C, which made me a bit nervous. After the data were copied, I temporarily un-configured computers on local network to not touch Aeronix, plugged keyboard, display and OpenBSD 6.1 thumb drive. Installing OpenBSD 6.1 on full disk RAID1 was super easy. Configuring NFS Aeronix serves primarily as NAS, which means NFS and SMB. NFS is used by computers in local network with persistent connection (via Ethernet). SMB is used by other devices in local network with volatile connection (via WiFi). When configuring NFS, I expected similar configuration to what I had in Debian, but on OpenBSD, it is very different. However, after reading through exports(5), it was really easy to put it together. Putting the data back Copying from the external drive took few days, since the transfer speed was something around 5MB/s. I didn't really mind. It was sort of a good thing, because Aeronix wasn't overheating that way. I guess I need to figure new backup strategy though. One interesting thing happened with one of my local desktops. It was connecting Aeronix with default NFS mount options (on Archlinux) and had really big troubles with reading anything. Basically it behaved as if the network drive had horrible access times. After changing the default mount options, it started working perfectly. Conclusion Migrating to OpenBSD was way easier than I anticipated. There are various benefits like more security, realiable RAID1 setup (which I know how will work when drive dies), better documentation and much more. However, the true benefit for me is just the fact I like OpenBSD and makes me happy to have one more OpenBSD machine. On to the next two years of service! Beastie Bits Running OpenBSD on Azure (http://undeadly.org/cgi?action=article&sid=20170609121413&mode=expanded&count=0) Mondieu - portable alternative for freebsd-update (https://github.com/skoef/mondieu) Plan9-9k: 64-bit Plan 9 (https://bitbucket.org/forsyth/plan9-9k) Installing OpenBSD 6.1 on your laptop is really hard (not) (http://sohcahtoa.org.uk/openbsd.html) UbuntuBSD is dead (http://www.ubuntubsd.org/) OPNsense 17.1.8 released (https://opnsense.org/opnsense-17-1-8-released/) *** Feedback/Questions Patrick - Operating System Textbooks (http://dpaste.com/2DKXA0T#wrap) Brian - snapshot retention (http://dpaste.com/3CJGW22#wrap) Randy - FreeNAS to FreeBSD (http://dpaste.com/2X3X6NR#wrap) Florian - Bootloader Resolution (http://dpaste.com/1AE2SPS#wrap) ***

上一期我们说到，林纳斯硕士毕业以后，去美国硅谷一家神秘的公司工作，这家公司叫全美达，并且引起了关心Linux以及开源软件的一些人士的担忧，林纳斯本人的一些澄清，并没有消除他和公众之间的一些误会。但是，生活总是要继续的，即使有人误会，生活也是要继续下去的。来到硅谷以后，以林纳斯的名气和实力，势必会引发硅谷各大公司的一阵骚动。就像把咱们这个太阳系里，扔进一颗土星或者木星进去，那么，太阳系里所有行星的轨道肯定会受到影响，要重新的运行于另外一个轨道。林纳斯的实力，在当时已经足可以影响硅谷的公司。如果是我们这种人99.999999%的普通人，去硅谷或者不去硅谷，来到这个世界或者离开这个世界，其实没什么影响的。虽然这说起来有点残酷，但是，现实就是这么残酷。林纳斯这种人，天生就是改变世界的，这个改变世界并不是口头上改变世界，他是真的改变了世界。我们这里有很多人只是口头上改变世界，实际上只是喊喊口号，忽悠一下不明真相的人民群众。这种人，其实挺缺德的，我的意思并不是说他对不起崇拜他的粉丝，因为粉丝都是心甘情愿的，一个愿打，一个愿挨，这都没什么问题，虐待狂和受虐狂，我们外人可能看着很血腥，但是讲台上的他和讲台下的他们，感觉那是天生的一对，以受虐狂的角度来看，你不虐待他才是真正的虐待他。我的意思是讲台上天天说改变世界的人，是对不起牛，因为他天天在台上吹牛B，人家牛很悲惨的，人家好好的过日子，吃个草，挤个奶，结果你天天吹人家，所以，请把B还给牛，牛也需要性生活！当然了，本文的主角林纳斯是真正改变了世界的人，虽然他没说过他的目标是改变世界。硅谷有另一个人也改变了世界，虽然他天天说他改变了世界，但是他真的改变了世界，那个人就是乔布斯。这两个人都是巨大的行星，丢到哪里都能引起其它行星轨道的变化。首先发起邀请的是乔布斯。乔布斯的秘书发了一封邮件，说能不能抽出1-2个小时来，和乔布斯见个面，乔布斯很希望和他谈谈。林纳斯虽然不知道到底怎么回事儿，但是还是爽快的答应了。因为这种事情，不答应是不行的。为什么说不答应是不行的呢？就像太阳系里，突然挤进来了一颗大行星，别的行星怎么会视而不见，都发生万有引力了，你这不见个面也说不过去。就像苏联和美国，两家都拥有巨量的核弹，即使在冷战的时候，他们还是有各种渠道说说话的，因为两个国家真的搞起冷战来，让双方互相猜忌，那更危险。林纳斯那时候，也已经是个大家伙了，硅谷的这些巨头，不说是拉关系吧，起码让人家知道你没有敌意，家里的客厅里突然坐进来一头大象，7，8吨，一万四五斤重，让人家主人假装看不见是不行的。林纳斯不是我们普通人，去旅游，人家都不搭理咱。爱来来，爱走走，随便，想当自由了。但是到了林纳斯那个层次，怀揣核武器，硅谷的公司当然会非常重视了。所以，除了乔布斯，还有SUN公司等等，都分别请林纳斯坐下聊聊天。按照常理，不见得是请林纳斯来做朋友，起码这些硅谷的公司要确认一下，这个家伙不会是敌人吧，毕竟，他有核武器呢。所以，林纳斯和硅谷巨头的一系列会面，是不得不去的。林纳斯就单枪匹马的去赴约了，乔布斯带来了一个人，就是苹果公司当时的首席工程师埃维•特凡尼安。埃维•特凡尼安这个人，我曾经有一期故事里提到过他，这个人不是个菜鸟，他是卡耐基梅隆大学的博士，是Mach项目的开发者之一，Mach项目卡耐基梅隆大学开发的一个操作系统的微内核，这个内核是最早实现的微内核之一，这个项目是后来FreeBSD的内核，以及苹果操作系统的内核Darwin的基础。所以，这个人非常的厉害。参与这个Mach项目的另一个人叫理查德•拉希德，这个人是微软的副总裁，也是个超级牛人。我觉得非常有必要说一下背景，为什么要详细的说背景呢，因为林纳斯和乔布斯的这次会面，吵架了，当然了，并不是我们这里网络上，比如网易这种网友的吵架，互相问候对方的祖先，而是，林纳斯和埃维•特凡尼安同学发生了激烈的争吵。是关于技术的。在讲这次吵架之前，我先讲吵架的缘由，或者说是可能的一些缘由，因为林纳斯的自传里，只说了微内核的垃圾，可能会让大家觉得微内核真的是垃圾，其实，都是一家之言，微内核没我们操作系统课上讲的那么好，但是也没有林纳斯嘴里那么糟糕。现在我开始讲我主观上认为的，比较客观的一个历史。在这里强调一点，是我本人主观上觉得比较客观的历史。我们都知道，Unix是最成功的操作系统之一，我在以前的几期节目里，把Unix吹成了一朵花，Unix是Bell实验室的两个家伙搞出来的，他主要的设计思想是，一切都是文件。我们教科书上也是这么说的，一切都是文件。但是实际上呢，并不是！为什么不是呢？因为Unix一旦流行起来，Unix上的扩展就越来越多了，而且，这些扩展很多根本就不是Bell实验室的汤姆逊和里奇这两个好基友写的。比如Unix上使用的图形支持最初有MIT写的，MIT写的图形界面中的对象就不是文件。Unix支持网络，这些网络大部分是UC Berkerly写的，我在前面关于BSD的节目里讲过，这些网络设备以及服务，也不是文件。所以，Unix所宣传的一切都是文件这个口号，很大程度上和共产主义按需分配一样，不是那么的准确。准确的来说，贝尔实验室写的Unix一切都是文件是没错的，但是别人扩展的部分，并不一定都是文件。和共产主义一样，按需分配的前提是必须要是县委书记以上，县委书记以上的是共产主义按需分配，县委书记到村长这一块是按劳分配，像我这种程序员是原始社会，按血汗分配。不管怎么说了，很多人对Unix是不满意的，最不满意的是Bell实验室的人，他们认为，好好的一个Unix，被你们这群傻X给搞坏了。然后，他们另起炉灶，详细设计了一番，来玩个真的，让“一切都是文件”这个宏伟的目标得以实现。然后，以Rob Pike，Ken Thompson和Dennies Ritchie为首的几个人，还包括C++的作者，提出管道概念的作者，写了awk这个语言的作者，组成了一个银河战舰，具体来说，以后这个团队，基本上都获得了图灵奖，美国总统奖这种级别的奖，再多说一句，现在Rob Pike现在在Google设计Go语言，另外，他在Google的邮箱是一个字母，r@google.com，谷歌整个公司只有他自己有权力使用单个字符作为邮箱，连公司的两个创始人都没资格。大家可以给他发垃圾邮件 :)就这样一个银河战舰，声势浩大的制造了Unix的升级版，名字叫Plan9，为啥叫plan9这个名字呢，因为在1959年，上映了一部美国科幻电影，B级片，导演叫艾德•伍德，这个电影的名字叫Plan9 from Outer Space, 翻译为中文叫外太空9号计划。这部片子相当的烂，因为这个操作系统，我曾经从海盗湾下载过，另外，这部电影曾经在1980年被评为最差电影，而突然名声大噪。实事求是的来说，这部电影之所以能被评为最差电影，是因为1980年么，郭敬明还没有当导演，如果再晚30年，这部电影即使走后门送礼也评不上最差电影。如果有人是程序员并且在Unix上编过程序的话，可以体会一下，任何Unix编程的书，都会提到Unix中一切都是文件，但是后来，发现实现上实在是有问题，因此引入了ioctl这个函数，这个函数争议极大，简直就是对Unix系统的一次恐怖袭击，而且还成功了，这个函数呆在Unix里不走了。Unix的作者也觉得，这样搞下去，Unix怕是要挂了，因此搞一个真的一切都是文件。在Plan9中，试图让一切都是文件，比如内存，显卡，CPU，都是文件，如果大家仔细想想的话，就会发现，Plan9其实就是个分布式操作系统。也就是说，现在我们用的云计算，在30年前，贝尔实验室的Plan9已经在试图实现了。当然了，这个步子有点大，扯到蛋了。这个Plan9最终没有代替掉Unix，但是，Plan9的副产品，比如UTF8可能是影响最大的副产品之一了，已经深深的影响了我们这个世界。然后，Linux实际上是模仿的Unix，而且模仿的惟妙惟肖，即使设计的一些缺陷，Linux也照单全收了。但是Linux也有所创新，这些创新，比如说所有的进程也是文件，就是抄袭的Plan9这个系统的，但是抄袭的又不够彻底，比如在Linux系统进程文件夹/proc这个文件夹里，进程虽然是文件，但是，这个文件我们是不可以使用文件的一些命令，比如rm，cp这些命令的，所以，只是看起来像文件，但是实际上不能使用文件操作命令的假文件。不止贝尔实验室的人觉得Unix并不太好，其它好多人觉得Unix并不好，他们打算连Unix的内核也不够好，这就是乔布斯同学会面时候带来的那个埃维•特凡尼安同学搞的Mach微内核。Linux的内核是宏内核，大体意思是讲内存管理以及文件系统这些模块都放在内核态，现在的操作系统，包括微软和苹果的，都没有真正的教科书上的微内核，而是混合内核。还是前文我所提到的Plan9的一个遗产，叫FUSE（Filesystem in Userspace）这个技术，虽然Plan9这个系统没成功，但是这个技术被广泛的用在了linux中，比如linux可以动态加载模块以及fuse，这属于Linux吸收的微内核的东西。也就是说，直到今天，主流的操作系统，已经不是泾渭分明的状态，基本上已经是你中有我，我中有你了。但是，在林纳斯和乔布斯会面的时候，大家都没有料到，在很多年后，微内核和宏内核会如漆似胶。如果我没有记错的话，linux内核2.6.14以后的版本，都可以激活fuse这个模块，只要激活了这个模块，可以不借助任何软件，直接ssh加载远程的目录，这个功能就是微内核的思想，当然，也是借鉴的plan9这个没有成功的操作系统。但是，在林纳斯会面的时候，林纳斯还没有意识到N年以后，他会添加微内核，以及动态模块这种东西到linux中，因此，在他的自传里，他将微内核贬的一文不值，原话是：说实话，我觉得那东西简直就是垃圾。至于吵架的细节，在林纳斯的自传里有另外详细的描述，首先是技术之争，其次，我认为是乔布斯，林纳斯，比尔盖茨这种人物，是不会在其它人手下打工的。你能想想项羽在刘邦手底下当大将的情景么？不会的，按照中国迷信的说法，这些人生下来是有王者之气的，他们出生的时候，可能天上打雷下雨，或者半夜里出太阳，反正有奇异的景象。不可能在别人手下打工赚钱的。好了，这期就到这里，我去打工赚钱去了！

Gregor PRIDUN, Stefan HASLINGER, Horst JENS und Denis KNAUF plaudern über freie Software und andere Nerd-Themen. Shownotes auf http://goo.gl/fnoGUg oder http://biertaucher.at

This week on the show, we have all the latest news and stories! Plus an interview with BSD developer Alfred Perlstein, that you This episode was brought to you by Headlines The May issus of BSDMag is now out (https://bsdmag.org/download/reusing_openbsd/) GhostBSD Reusing OpenBSD's arc4random in multi-threaded user space programs Securing VPN's with GRE / Strongswan Installing XFCE 4.12 on NetBSD 7 Interview with Fernando Rodriguez, the co-founder of KeepCoding *** A rundown of the FPTW^XEXT.1 security reqiurement for General Purpose Operating Systems by the NSA (http://blog.acumensecurity.net/fpt_wx_ext-1-a-rundown/) NIST/NSA Validation Scheme Report (https://www.commoncriteriaportal.org/files/ppfiles/pp_os_v4.1-vr.pdf) The SFR or Security Functional Requirement requires that; "The OS shall prevent allocation of any memory region with both write and execute permissions except for [assignment: list of exceptions]." While nearly all operating systems currently support the use of the NX bit, or the equivalent on processors such as SPARC and ARM, and will correctly mark the stack as non-executable, the fact remains that this in and of itself is deemed insufficient by NIST and NSA. OpenBSD 5.8, FreeBSD, Solaris, RHEL, and most other Linux distro have failed. HardenedBSD passes all three tests out of the box. NetBSD will do so with a single sysctl tweak. Since they are using the PaX model, anything else using PaX, such as a grsecurity-enabled Linux distribution pass these assurance activities as well. OpenBSD 5.9 does not allow memory mapping due to W^X being enforced by the kernel, however the kernel will panic if there are any attempts to create such mappings. *** DistroWatch reviews new features in FreeBSD 10.3 (https://distrowatch.com/weekly.php?issue=20160516#freebsd) DistroWatch did a review of FreeBSD 10.3 They ran into a few problems, but hopefully those can be fixed An issue with beadm setting the canmount property incorrectly causing the ZFS BE menu to not work as expected should be resolved in the next version, thanks to a patch from kmoore The limitations of the Linux 64 support are what they are, CentOS 6 is still fairly popular with enterprise software, but hopefully some folks are interested in working on bringing the syscall emulation forward In a third issue, the reviewer seemed to have issues SSHing from inside the jail. This likely has to do with how they got a console in the jail. I remember having problems with this in the past, something about a secure console. *** BSD Unix: Power to the people, from the code (https://www.salon.com/2000/05/16/chapter_2_part_one/) Salon.com has a very long article, chronicling much of the history behind BSD UNIX. It starts with detailing the humble origins of BSD, starting with Bill Joy in the mid-70's, and then goes through details on how it rapidly grew, and the influence that the University of Berkeley had on open-source. “But too much focus on Joy, a favorite target for business magazine hagiography, obscures the larger picture. Berkeley's most important contribution was not software; it was the way Berkeley created software. At Berkeley, a small core group — never more than four people at any one time — coordinated the contributions of an ever-growing network of far-flung, mostly volunteer programmers into progressive releases of steadily improving software. In so doing, they codified a template for what is now referred to as the “open-source software development methodology.” Put more simply, the Berkeley hackers set up a system for creating free software.” The article goes on to talk about some of the back and forth between Linux and BSD, and why Linux has captured more of the market in recent years, but BSD is far from throwing in the towel. “BSD patriots argue that the battle is far from over, that BSD is technically superior and will therefore win in the end. That's for the future to determine. What's indisputable is BSD's contribution in the past. Even if, by 1975, Berkeley's Free Speech Movement was a relic belonging to a fast-fading generation, on the fourth floor of Evans Hall, where Joy shared an office, the free-software movement was just beginning.” An excellent article (If a bit long), but well worth your time to understand the origins of what we consider modern day BSD, and how the University of Berkley helped shape it. *** iXsystems (http://ixsystems.com) #ServerEnvy: It's over 10,000 Terabytes! (https://www.ixsystems.com/blog/serverenvy-10000-terabytes/) *** Interview - Alfred Perlstein - alfred@freebsd.org (mailto:alfred@freebsd.org) / @splbio (https://twitter.com/splbio) Using BSD for projects *** News Roundup .NET framework ported to NetBSD (https://github.com/dotnet/coreclr/pull/4504/files) This pull request adds basic support for the .NET framework on NetBSD 7.x amd64 It includes documentation on how to get the .NET framework installed It uses pkgsrc to bootstrap the required tools pkgsrc-wip is used to get the actual .NET framework, as porting is still in progress The .NET Core-CLR is now available for: FreeBSD, Linux, NetBSD, and OS X *** OpenBSD SROP mitigation – call for testing (https://marc.info/?l=openbsd-tech&m=146281531025185&w=2) A new technique for exploiting flaws in applications and operating systems has been developed, called SROP “we describe Sigreturn Oriented Programming (SROP), a novel technique for exploits and backdoors in UNIX-like systems. Like return-oriented programming (ROP), sigreturn oriented programming constructs what is known as a ‘weird machine' that can be programmed by attackers to change the behavior of a process. To program the machine, attackers set up fake signal frames and initiate returns from signals that the kernel never really delivered. This is possible, because UNIX stores signal frames on the process' stack.” “Sigreturn oriented programming is interesting for attackers, OS developers and academics. For attackers, the technique is very versatile, with pre-conditions that are different from those of existing exploitation techniques like ROP. Moreover, unlike ROP, sigreturn oriented programming programs are portable. For OS developers, the technique presents a problem that has been present in one of the two main operating system families from its inception, while the fixes (which we also present) are non-trivial. From a more academic viewpoint, it is also interesting because we show that sigreturn oriented programming is Turing complete.” Paper describing SROP (http://www.cs.vu.nl/~herbertb/papers/srop_sp14.pdf) OpenBSD has developed a mitigation against SROP “Utilizing a trick from kbind(2), the kernel now only accepts signal returns from the PC address of the sigreturn(2) syscall in the signal trampoline. Since the signal trampoline page is randomized placed per process, it is only known by directly returning from a signal handler.” “As well, the sigcontext provided to sigreturn(2) now contains a magic cookie constructed from a per-process cookie XOR'd against the address of the signal context.” This is just a draft of the patch, not yet considered production quality *** Running Tor in a NetBSD rump unikernel (https://github.com/supradix/rumprun-packages/tree/33d9cc3a65a39e32b4bc8034c151a5d7e0b89f66/tor) We've talked about “rump” kernels before, and also Tor pretty frequently, but this new github project combines the two! Specifically, this set of Makefile and scripts will prep a system to run Tor via the Unikernel through Qemu. The script mainly describes how to do the initial setup on Linux, using iptables, but could easily be adapted to a BSD if somebody wants to do so. (Send them a pull request with the instructions!) All in all, this is a fascinating way to run a Tor node or relay, in the most minimal operating environment possible. *** An update on SSH protocol 1 ("we're most of the way towards fully deprecating SSH protocol 1" (http://lists.mindrot.org/pipermail/openssh-unix-dev/2016-May/035069.html) Damien Miller has given us an update on the status of the “SSH protocol 1”, and the current plans to deprecate it in an upcoming version of openssh. “We've had this old protocol in various stages of deprecation for almost 10 years and it has been compile-time disabled for about a year. Downstream vendors, to their credit, have included this change in recent OS releases by shipping OpenSSH packages that disable protocol 1 by default and/or offering separate, non-default packages to enable it. This seems to have proceeded far more smoothly than even my most optimistic hopes, so this gives us greater confidence that we can complete the removal of protocol 1 soon. We want to do this partly to hasten the demise of this cryptographic trainwreck, but also because doing so removes a lot of legacy code from OpenSSH that inflates our attack surface. Having it gone will make our jobs quite a bit easier as we maintain and refactor.” The current time-line looks like removing server-size protocol 1 support this August after OpenSSH 7.4 is released, leaving client-side disabled. Then a year from now (June 2017) all protocol 1 code will be removed. Beastie Bits Last day to get your BSDNow Shirts! Order now, wear at BSDCan! (https://teespring.com/bsdnow) Move local government (Austin TX) from Microsoft Windows (incl. Office) to Linux and/or PC-BSD (https://github.com/atxhack4change/2016-project-proposals/issues/15) Plan9 boot camp is back... and already at capacity. Another opportunity may come in September (http://lists.nycbug.org/pipermail/talk/2016-May/016642.html) Smaller is better - building an openbsd based router (https://functionallyparanoid.com/2016/04/22/smaller-is-better/) Baby Unix (https://i.redditmedia.com/KAjSscL9XOUdpIEWBQF1qi3QMr7zWgeETzQM6m3B4mY.jpg?w=1024&s=e8c08a7d4c4cea0256adb69b1e7c1887) Security Update for FreeBSD (https://security.freebsd.org/advisories/FreeBSD-SA-16:19.sendmsg.asc) & Another security update for FreeBSD (https://security.freebsd.org/advisories/FreeBSD-SA-16:18.atkbd.asc) Feedback/Questions Eric - The iX experience (http://pastebin.com/ZknTuKGv) Mike - Building Ports (http://pastebin.com/M760ZmHQ) David - ZFS Backups (http://pastebin.com/Pi0AFghV) James - BSD VPS (http://pastebin.com/EQ7envez) Rich - ZFS Followup (http://pastebin.com/p0HPDisH) ***

Umar Saif is a Pakistani computer scientist and entrepreneur, who is known for his work on using ICT solutions for developing-world problems. He is also the founder of Plan9, Pakistan's largest startup incubator and is often credited as one of the main forces behind the IT ecosystem in Pakistan.In his role as the Chairman of the Punjab Information Technology Board, his work to introduce technology in government using low-cost smart-phones has had a transformative impact in Pakistan. The World Bank President highlighted this work as one of three global examples of good governance innovations in his landmark speech on governance reforms in Philippines.

In dieser Sendung geht es um den Nachfolger von Unix, das Betriebssystem Plan 9. Was es auszeichnet und wie man ein Linux um Plan 9 Funktionalität erweitern kann erfahrt ihr hier. Als Gäste dürfen wir einerseits Carsten Strotmann begrüssen und dem Ruf des Fondue Caquelons folgend ist auch Raffzahn mit dabei, neben den Residents XTaran und Venty. Trackliste Jeroen Tel – Cybernoid 2 Rams – Magnificent Spacetrap Pippo Noviello – Commando Hi-Score Piano-Version Nächste Sendung am Samstag, 04. Februar 2012, 19:00 Uhr Plan 9 From Outer Space :: Der ganze Film von Ed Wood in voller Länge herunterladbar Plan 9 :: Plan 9 Website bei den Bell Labs Plan 9 From User Space :: Plan 9 Tools unter Linux, FreeBSD oder NetBSD benutzen 9vx :: Plan 9 API Emulator fuer Linux, FreeBSD und MacOS X 9vx Bitbucket :: Aktuellerer API Emulator, unterstützt auch 9Front 9vx Tutorial :: 9vx tutorial: running a cpu server from kfs Inferno OS :: Webseite des Inferno Betriebssystems 9atom :: Plan 9 Distribution 9atom 9front :: Plan 9 Fork 9front 9front Quellcode :: Der Quellcode zu 9front Plan 9 Intro :: Introduction to Plan 9 man 9mount :: Manpage for 9mount ACME :: ACME: A User Interface for Programmers ACME Video :: Videotutorial for ACME Blue Gene :: Plan9 auf IBMs Blue Gene NineTimes :: Newsblog NineTimes rund um Plan 9 9P :: 9P Filesystem 9P for Linux :: 9P for Linux NIX OS :: New multicore OS based on Plan9 WMII :: WindowManager Improved 2 (Unterstützt das 9P Protokoll) File Download (60:03 min / 74 MB)

In dieser Sendung geht es um den Nachfolger von Unix, das Betriebssystem Plan 9. Was es auszeichnet und wie man ein Linux um Plan 9 Funktionalität erweitern kann erfahrt ihr hier. Als Gäste dürfen wir einerseits Carsten Strotmann begrüssen und dem Ruf des Fondue Caquelons folgend ist auch Raffzahn mit dabei, neben den Residents XTaran und Venty. Trackliste Jeroen Tel – Cybernoid 2 Rams – Magnificent Spacetrap Pippo Noviello – Commando Hi-Score Piano-Version Nächste Sendung am Samstag, 04. Februar 2012, 19:00 Uhr Plan 9 From Outer Space :: Der ganze Film von Ed Wood in voller Länge herunterladbar Plan 9 :: Plan 9 Website bei den Bell Labs Plan 9 From User Space :: Plan 9 Tools unter Linux, FreeBSD oder NetBSD benutzen 9vx :: Plan 9 API Emulator fuer Linux, FreeBSD und MacOS X 9vx Bitbucket :: Aktuellerer API Emulator, unterstützt auch 9Front 9vx Tutorial :: 9vx tutorial: running a cpu server from kfs Inferno OS :: Webseite des Inferno Betriebssystems 9atom :: Plan 9 Distribution 9atom 9front :: Plan 9 Fork 9front 9front Quellcode :: Der Quellcode zu 9front Plan 9 Intro :: Introduction to Plan 9 man 9mount :: Manpage for 9mount ACME :: ACME: A User Interface for Programmers ACME Video :: Videotutorial for ACME Blue Gene :: Plan9 auf IBMs Blue Gene NineTimes :: Newsblog NineTimes rund um Plan 9 9P :: 9P Filesystem 9P for Linux :: 9P for Linux NIX OS :: New multicore OS based on Plan9 WMII :: WindowManager Improved 2 (Unterstützt das 9P Protokoll) File Download (60:03 min / 74 MB)