Podcasts about Red Hat Linux

In this episode of 'Cybersecurity Today,' host Jim Love discusses several urgent cybersecurity topics. Microsoft has released an emergency patch after a recent Windows update caused BitLocker recovery mode on certain systems, locking users out without warning. The issue stems from the May security update affecting systems using Intel, vPro chips, and TXT. Tech enthusiasts may manually download the patch through the Microsoft Update catalog, while Microsoft urges users to secure their BitLocker recovery keys. The episode also highlights day one of Pwn2Own Berlin 2025, where hackers successfully breached Windows 11, Red Hat Linux, and Oracle Virtual Box, earning a combined $260,000 in prize money. Additionally, US experts discovered hidden communication hardware in Chinese-made solar equipment, raising concerns about remote access risks to the power grid. The FBI warns of a new wave of AI-generated phishing attacks that bypass traditional security measures. Finally, the Consumer Financial Protection Bureau has quietly backed down from regulating data brokers, sparking controversy among privacy advocates. Jim Love offers insights and reminds listeners of the importance of cybersecurity. 00:00 Introduction and Headlines 00:27 Microsoft's Urgent Patch for BitLocker Issue 02:26 Pwn2Own Berlin 2025: Major Security Breaches 04:11 Hidden Devices in Chinese Solar Equipment 06:05 FBI Warns of New Linkless Phishing Attacks 07:58 CFPB Withdraws Rule on Data Brokers 09:33 Conclusion and Contact Information

Coinbase says hackers bribed staff to steal customer data and are demanding $20 million ransom Windows 11 and Red Hat Linux hacked on first day of Pwn2Own The Internet's biggest-ever black market just shut down amid a Telegram purge  Huge thanks to our sponsor, Vanta Do you know the status of your compliance controls right now? Like...right now? We know that real-time visibility is critical for security, but when it comes to our GRC programs…we rely on point-in-time checks. But more than 9,000 companies have continuous visibility into their controls with Vanta. Vanta brings automation to evidence collection across over 35 frameworks, like SOC 2 and ISO 27001. They also centralize key workflows like policies, access reviews, and reporting, and helps you get security questionnaires done 5 times faster with AI. Now that's…a new way to GRC. Get started at Vanta.com/headlines.

1994 erschienen nicht nur Netscape 0.9 und MS-DOS 6.22 - auch Red Hat Linux wurde in der ersten Version 0.9 veröffentlicht. Zeit, einen Blick auf die Historie zu werfen.

More from The Lunduke Journal:https://lunduke.com/ This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit lunduke.substack.com/subscribe

This may be controversial, however, we've been privately discussing how organizations benefit from penetration testing and vulnerability scanning. Do you still need these services as a critical part of your security program? Can't you just patch stuff that is missing patches? Tune in for a lively debate! Zyxl NAS devices are under attack and the exploit is pretty simple, A new UEFI vulnerability with a name that some people don't like, that time you setup a load balancer and forgot about it, I love it when there is a vulnerability in a Wifi driver, Polyfill is filling the Internet with supply chain vulnerabilities, open source doesn't mean more secure, what happens when there is a vulnerability in your bootload, The Red Hat Linux kernel model is broken, when disclosure goes wrong, and more IoT router vulnerabilities. Visit https://www.securityweekly.com/psw for all the latest episodes! Show Notes: https://securityweekly.com/psw-833

Zyxl NAS devices are under attack and the exploit is pretty simple, A new UEFI vulnerability with a name that some people don't like, that time you setup a load balancer and forgot about it, I love it when there is a vulnerability in a Wifi driver, Polyfill is filling the Internet with supply chain vulnerabilities, open source doesn't mean more secure, what happens when there is a vulnerability in your bootload, The Red Hat Linux kernel model is broken, when disclosure goes wrong, and more IoT router vulnerabilities. Show Notes: https://securityweekly.com/psw-833

This may be controversial, however, we've been privately discussing how organizations benefit from penetration testing and vulnerability scanning. Do you still need these services as a critical part of your security program? Can't you just patch stuff that is missing patches? Tune in for a lively debate! Zyxl NAS devices are under attack and the exploit is pretty simple, A new UEFI vulnerability with a name that some people don't like, that time you setup a load balancer and forgot about it, I love it when there is a vulnerability in a Wifi driver, Polyfill is filling the Internet with supply chain vulnerabilities, open source doesn't mean more secure, what happens when there is a vulnerability in your bootload, The Red Hat Linux kernel model is broken, when disclosure goes wrong, and more IoT router vulnerabilities. Visit https://www.securityweekly.com/psw for all the latest episodes! Show Notes: https://securityweekly.com/psw-833

Zyxl NAS devices are under attack and the exploit is pretty simple, A new UEFI vulnerability with a name that some people don't like, that time you setup a load balancer and forgot about it, I love it when there is a vulnerability in a Wifi driver, Polyfill is filling the Internet with supply chain vulnerabilities, open source doesn't mean more secure, what happens when there is a vulnerability in your bootload, The Red Hat Linux kernel model is broken, when disclosure goes wrong, and more IoT router vulnerabilities. Show Notes: https://securityweekly.com/psw-833

Welcome to episode 260 of the Cloud Pod podcast – where the forecast is always cloudy! This week your hosts Justin, Matthew, and Jonathan and Ryan are talking about changes in leadership over at Amazon, GPT-4.o and its image generating capabilities, and the new voice of Skynet, Amazon Polly! It's an action packed episode – and make sure to stay tuned for this week's after show.  Titles we almost went with this week: Who eats pumpkin pie in May Bytes and Goodbyes: AWS CEO Logs Off AWS lets you know that you are burning money sooner than before High-Ho, High-Ho, It's GPT-4-Ohhh The CloudPod pans for nuggets in the AI Gold rush A big thanks to this week's sponsor: Big thanks to Sonrai Security for sponsoring today's podcast! Check out Sonrai Securities’ new Cloud Permission Firewall. Just for our listeners, enjoy a 14 day trial at https://sonrai.co/cloudpod  General News  00:40 Terraform Enterprise adds Podman support and workflow enhancements The latest version of Terraform Enterprise now supports Podman with RHEL 8 and above.  Originally, it only supported Docker Engine and Cloud Managed K8 services.   With the upcoming EOL of RHEL 7 in June 2024, customers faced a lack of an end-to-end supported option for running a terraform enterprise on RHEL.   Now, with support from Podman, this is rectified.   01:18 Ryan – “This is for the small amount of customers running the enterprise either on -prem or in their cloud environment. It’s a pretty good option. Makes sense.” 01:42 Justin – “You know, the thing I was most interested in at this actually is that Red Hat Linux 7 is now end of life, which this is my first time in my entire 20 some odd career that I’ve never had to support Red Hat Linux in production because we use Ubuntu for some weird reason, which I actually appreciate because I always like Ubuntu best for my home projects, but I didn’t actually know Red Hat 7 was going away.” AI Is Going Great (Or, How ML Makes All It's Money)  03:58 Hello GPT-4o Open AI has launched their GPT-4o (o for Omni) model which can reason across audio, vision and text in real time.  The new model can accept input combinations of text, audio and image and generates any combination as output. It can respond to audio inputs in as little as 232 milliseconds, with an average of 320 milliseconds, similar to human response time in conversation.   It matches GPT-4 Turbo performance on text in English and OCDE, with significant improvements on text in non-english languages, while also being much f

An airhacks.fm conversation with Jonathan Ellis (@spyced) about: Jonathan's first computer experiences with IBM PC 8086 and Thinkpad laptop with Red Hat Linux, becoming a key contributor to Apache Cassandra and founding datastax, starting DataStax to provide commercial support for Cassandra, early experiences with Java, C++, and python, discussion about the evolution of Java and its ecosystem, the importance of vector databases for semantic search and retrieval augmented generation, the development of JVector for high-performance vector search in Java, the potential of integrating JVector with LangChain for Java / langchain4j and quarkus for serverless deployment, the advantages of Java's productivity and performance for building concurrent data structures, the shift from locally installed software to cloud-based services, the challenges of being a manager and the benefits of taking a sabbatical to focus on creative pursuits, the importance of separating storage and compute in cloud databases, Cassandra's write-optimized architecture and improvements in read performance, DataStax's investment in Apache Pulsar for stream processing, the llama2java project for high-performance language models in Java Jonathan Ellis on twitter: @spyced

Red Hat warns of backdoor in XZ tools used by most Linux distros

Doc Searls and Dan Lynch explore long-standing ethical and technical imperatives of the free software and open source movements, and the wild new challenges they face in an age of AI that is still just beginning. Hosts: Doc Searls and Dan Lynch Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss bitwarden.com/twit fastmail.com/twit

Doc Searls and Dan Lynch explore long-standing ethical and technical imperatives of the free software and open source movements, and the wild new challenges they face in an age of AI that is still just beginning. Hosts: Doc Searls and Dan Lynch Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss bitwarden.com/twit fastmail.com/twit

Doc Searls and Dan Lynch explore long-standing ethical and technical imperatives of the free software and open source movements, and the wild new challenges they face in an age of AI that is still just beginning. Hosts: Doc Searls and Dan Lynch Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss bitwarden.com/twit fastmail.com/twit

Doc Searls and Dan Lynch explore long-standing ethical and technical imperatives of the free software and open source movements, and the wild new challenges they face in an age of AI that is still just beginning. Hosts: Doc Searls and Dan Lynch Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: kolide.com/floss bitwarden.com/twit fastmail.com/twit

Episodio 72 del Podcast NHL y Pride, Red NABU Canada, Red Hat Linux, Caso creepy en Calgary, la demanda en la corte suprema de justicia de USA que no existe, la exclusión al acceso al agua mata niños en los Estados Unidos, Antropoceno, Ley 18 en Canada y el acceso a noticias, el abismal estado de Twitter, Frustraciones con el sistema bancario Colombiano, obituarios. --- Send in a voice message: https://podcasters.spotify.com/pod/show/edgarmtoro/message

Coming up in this episode 1. CentOS 2. ... 3. ... 4. Just CentOS 316 Audio Timestamps 0:00 Cold Open 1:48 With a Little Help From Our Friends 9:42 CentOS History, 90's - 1996 11:46 96 - 2000 14:01 2000 - 2003 20:29 The Clone Wars 24:47 2004 - 2014 30:25 2014 - 2022 36:41 Our CentOS Experience 1:11:00 Next Time: Topics! 1:14:31 Stinger Watch this episode on Youtube (https://www.youtube.com/watch?v=52MnZVvVumc) https://www.youtube.com/watch?v=52MnZVvVumc Banter Leo's font issue (https://mastodon.social/@leochavez/109809074194178438) The bug (https://bugzilla.redhat.com/show_bug.cgi?id=2144433#c6) HUGE Thanks to Carl George for technical help with this episode. Announcements Give us a sub on YouTube (https://linuxuserspace.show/youtube) You can watch us live on Twitch (https://linuxuserspace.show/twitch) the day after an episode drops. If you like what we're doing here, make sure to send us a buck over at https://patreon.com/linuxuserspace CentOS Linux the History July 1994 The "preview" release for Red Hat Linux is released internally (https://fedoraproject.org/wiki/History_of_Red_Hat_Linux) October 31 codenamed "Halloween" 0.9 is released. May 1995 "Mother's Day" 1.0 is released and introduces some iconic branding. March 1996 "Picasso" 3.0.3 is released. Version numbers might really matter, check out our Slackware episode (https://www.linuxuserspace.show/219) to find out how Patrick Volkerding felt about them. TL;DW (http://www.slackware.com/faq/do_faq.php?faq=general#0) September 2000 Red Hat Linux 7.0 has releases with their renamed gcc version (features.slashdot.org/article.pl?sid=00/10/12/163218&mode=thread) May 2002 Enter Red Hat Enterprise Linux (https://access.redhat.com/articles/3078) with version 2.1. Sometime within 2002, Warren Togami starts the Fedora Linux Project (https://fedoraproject.org/wiki/User:Wtogami?rd=WarrenTogami). It aimed to bring together (https://web.archive.org/web/20031008123733/http://www.fedora.us/index-main.html) additional packages for Red Hat Linux. It wasn't a distribution on its own (https://web.archive.org/web/20030219051938/http://www.fedora.us/fedora.html). It was Extras for the existing Red Hat Linuxes. March 2003 Red Hat Linux 9.0, named Shrike, is released. July 2003 Severn, the beta for what would be Red Hat Linux 10, changes to a more open and community focused development process (https://lwn.net/Articles/40201/). September 2003, Red Hat Linux and the Fedora Linux Project, [merge into The Fedora Project].(https://web.archive.org/web/20031001204515/http://www.fedora.us/). Mailing list announcement (https://listman.redhat.com/archives/fedora-devel-list/2003-September/msg00137.html) Transition info (https://www.linuxjournal.com/article/7169) Also in September, enter cAos (https://web.archive.org/web/20120507000526/http://www.caoslinux.org/about.html). cAos1-base and cAos1-enhanced couldn't really exist without each other (https://web.archive.org/web/20050207043816/https://www.linuxtimes.net/modules.php?name=News&file=article&sid=406). November 2003 Red Hat signals that it's getting out of the Boxed Linux business (https://lwn.net/Articles/56947/). What was to be Red Hat Linux 10 instead released as Fedora Core 1 with (https://web.archive.org/web/20031107044428/http://download.fedora.redhat.com/pub/fedora/linux/core/1/i386/os/RELEASE-NOTES.html) Extras. December 2003 the first alpha (https://web.archive.org/web/20040128013252/http://caosity.org:80/) of cAos. Three weeks later, CentOS 3 (https://web.archive.org/web/20040202083913/http://caosity.org/index.php?option=news&task=viewarticle&sid=10). Another week later, CentOS 2 beta (https://web.archive.org/web/20040202084601/http://caosity.org/index.php?option=news&task=viewarticle&sid=11). Whitebox Linux first release candidate (http://www.whiteboxlinux.org/news.html). David Parsley registered taolinux.org, and in December, started getting the site together (https://web.archive.org/web/20040111131901/http://taolinux.org:80/). Why Tao Linux? (https://web.archive.org/web/20040704030839/http://taolinux.org/?q=node/view/5) June 2006, David had to switch jobs (https://web.archive.org/web/20061013083339/http://taolinux.org/?q=node/view/8). Scientific Linux (https://scientificlinux.org) Feburary 2004 the final release cAos-1, the proof of concept,made it to mirrors (https://web.archive.org/web/20040402100908/http://caosity.org/index.php?option=news&task=viewarticle&sid=22). March 2004 CentOS 3.1 is released (https://web.archive.org/web/20040325064219/http://caosity.org:80/). Karanbir Singh, or KB, noted that 3.3 was the first proper release (https://www.youtube.com/watch?v=PTX5yguTxA4&t=352s). February 2005 CentOS receieved a Cease and Desist letter from the lawyers over at Red Hat in regards to using the Red Hat Logos and name on the centos.org website. CentOS's response (https://web.archive.org/web/20050222184509/http://www.centos.org/modules/news/article.php?storyid=66). March 2005 CentOS 4 was released two weeks after its upstream RHEL 4. Coverage was picking up (https://web.archive.org/web/20050507081709/www.linuxplanet.com/linuxplanet/reviews/5823/1/). Lance Davis announces (https://lists.centos.org/pipermail/centos/2005-March/537696.html) that CentOS is separating itself from the cAos project. May 2005 cAos 2 is announced (https://web.archive.org/web/20040522050643/http://caosity.org:80/), also based on RHEL 3. 2008 A new distribution, also called Caos (https://web.archive.org/web/20081203074352/http://lists.caosity.org/pipermail/caos/2008-November/002537.html). July 2009 Lance Davis, one of the Founders and lead of the CentOS 2 release, had been missing for many months (https://www.zdnet.com/article/centos-getting-their-st-together-is-a-top-priority/). From the mailing list (https://lists.centos.org/pipermail/centos/2009-July/079767.html) From the Register (https://www.theregister.com/2009/07/30/centos_open_letter/) October 14 2009 Caos Linux 1.0.25 is released and is the last release of Caos, ever. January of 2014, Red Hat acquires (https://www.redhat.com/en/about/press-releases/red-hat-and-centos-join-forces). July 2014 CentOS 7.0 is released (https://lists.centos.org/pipermail/centos-announce/2014-July/020393.html). 2019 Red Hat leaves Shadowman behind (https://www.redhat.com/en/about/brand/new-brand#). September 2019 Red Hat announces (https://www.redhat.com/en/blog/transforming-development-experience-within-centos) CentOS Stream. Also in in September 2019, CentOS Linux 8 and CentOS Stream are released (https://lists.centos.org/pipermail/centos-announce/2019-September/023449.html). January 2021; Red Hat changes the way their dev subscriptions work (https://www.theregister.com/2021/01/20/red_hat_amends_developer_license/). December 2021 CentOS 9 Stream is released (https://blog.centos.org/2021/12/introducing-centos-stream-9/). CentOS links Main Web Page (https://centos.org) About (https://www.centos.org/about/) Blog (https://blog.centos.org/) Wiki (https://wiki.centos.org/) Forums (https://www.centos.org/forums/) Mailing Lists (https://wiki.centos.org/GettingHelp/ListInfo) Git Repositories (https://git.centos.org) Bug reporting (https://wiki.centos.org/ReportBugs) IRC (https://wiki.centos.org/irc) Planet (http://planet.centos.org/) List of CentOS releases (http://mirror.centos.org/centos/) Other Links AlmaLinux (https://almalinux.org) Rocky Linux (https://rockylinux.org) Red Hat Linux family tree (https://upload.wikimedia.org/wikipedia/commons/a/a3/Redhat_family_tree_11-06.png) More Announcements Want to have a topic covered or have some feedback? - send us an email, contact@linuxuserspace.show Housekeeping Catch all the great topics as they unfold on our Subreddit or our News channel on Discord. * Linux User Space subreddit (https://linuxuserspace.show/reddit) * Linux User Space Discord Server (https://linuxuserspace.show/discord) * Linux User Space Telegram (https://linuxuserspace.show/telegram) * Linux User Space Matrix (https://linuxuserspace.show/matrix) * Linux User Space Twitch (https://linuxuserspace.show/twitch) * Linux User Space Mastodon (https://linuxuserspace.show/mastodon) * Linux User Space Twitter (https://linuxuserspace.show/twitter) * Linux User Space TILVids (https://linuxuserspace.show/tilvids) Next Time We will discuss a couple of topics and some feedback. Our next distro is Endless OS (https://endlessos.com/home/) Come back in two weeks for more Linux User Space Stay tuned and interact with us on Twitter, Mastodon, Telegram, Matrix, Discord whatever. Give us your suggestions on our subreddit r/LinuxUserSpace Join the conversation. Talk to us, and give us more ideas. All the links in the show notes and on linuxuserspace.show. We would like to acknowledge our top patrons. Thank you for your support! Producer Bruno John Dave Johnny Co-Producer Tim Super User Advait Bjørnar CubicleNate Eduardo S. Jill and Steve Larry LiNuXsys666 Livet Musical Coder Nicholas Paul sleepyeyesvince

This episode reports the value of multifactor authentication, news about new security patches for Red Hat Linux and Windows, an update on the BlackCat ransomware gang and more

Bonjour à tous et bienvenue dans le ZD Tech, le podcast quotidien de la rédaction de ZDNet.fr. Je m'appelle Guillaume Serries et aujourd'hui je vous explique qui est Jack Dongarra, prix Turing 2021, l'homme qui a imposé les super ordinateurs. Dans le monde de l'innovation, vous connaissez Elon Musk et Bill Gates. Mais pas Jack Dongarra. Et c'est inexcusable. Donc je vais réparer ça. Une bonne partie de la vie de Jack Dongarra a été consacrée à faire la navette entre deux mondes. Dans l'un, Jack s'assoit avec un groupe de mathématiciens, un stylo et du papier en main, et imagine des problèmes qui pourraient être résolues par des ordinateurs. Enfin, par des très très gros ordinateurs, de la taille d'une armoire, voire de plusieurs. Et dans un autre monde, il est face à ces colosses de circuits intégrés, installés dans des salles blanches, et dotés d'une puissance de calcul incroyable. Et il tente de les configurer en prenant en compte des contraintes incroyables, telles que la vitesse, la mémoire, l'énergie, et bien sûr le coût de ces machines gigantesques. Oui, Jack Dongarra a passé 50 années à réunir ces mondes. Et c'est pourquoi la semaine dernière, cette carrière a été célébrée par l'Association for Computing Machinery, qui a décerné à Jack Dongarra sa plus prestigieuse distinction, le prix Turing. Oui, c'est l'équivalent du prix Nobel pour l'industrie informatique. Google, qui sponsorise ce prix, va lui remettre un million de dollars de récompense. Et non, Jack Dongarra n'est pas déjà millionnaire. Il est professeur d'informatique à l'université du Tennessee, aux Etats-Unis. Il est titulaire d'un doctorat en mathématiques appliquées. Mais qu'est ce qu'a bien pu faire Jack Dongarra pour mériter ce prix, et un million de dollars ? Et bien il a créé des outils tels que LINPACK, largement utilisé pour évaluer les performances des systèmes. Il a aussi créé BLAS, un outil indispensable pour effectuer les opérations vectorielles et matricielles nécessaires au calcul scientifique. Ou encore il a mis sur pieds MAGMA, une bibliothèque d'algèbre linéaire qui fait tourner les cartes graphiques embarquées dans les super ordinateurs. Pour résumer, les outils de ce professeur permettent de concevoir des logiciels performants fonctionnant sur des machines à haute performance. Il a aussi travaillé sur les mécanismes de traitement parallèle, et enfin, et c'est peut être le plus connu de ces travaux, il a mis au point des techniques d'évaluation des performances pour mesurer la vitesse d'exécution de ces supers ordinateurs. De quoi élaborer la fameuse liste TOP500 des superordinateurs. A date, c'est le super calculateur japonais Fugaku, développé par Fujitsu, qui est depuis juin 2020 le plus puissant du monde, et donc en tête du TOP500. Et il utilise un système d'exploitation Red Hat Linux 8 pour fonctionner. "La science est guidée par la simulation" assure Jack Dongarra. "C'est dans cette adéquation entre les capacités du matériel et la nécessité des simulations pour utiliser ce matériel que mes logiciels trouvent leur place."

Jack Aboutboul joins us this hour to talk about Alma Linux, a Red Hat Linux clone that is now doing what the former CentOS did prior to it becoming CentOS Stream. -- During The Show -- 00:54 Caller Mommy 01:15 Write in about Ticking/Asset Managment 01:50 Convert Docker file to Podman file? - Charlie Docker Files are OCI Compliant 03:08 Caller James Feedback: Use thermal wire strippers for small gauge wires Q: Monitor for older people in the country A: Apple Watch "Series 3 or later with Cellular" 06:40 Podcast Aggregator - Mike Pod Get (http://podget.sourceforge.net/) FTP JellyFin (https://jellyfin.org/) Plex (Plex.tv) 09:25 Purchasing CDs from Amazon - Hank CD's bought as gifts on Amazon don't allow MP3 downloads 10:44 Open Source Engineering? - Ateriath Interview in the works 13:24 Interview Jack Aboutboul Community Manager for Alma Linux Cloud Linux Reaction to CentOS changes How did Alma Linux come into existence? Alma Linux OS Foundation How does Alma Linux serve the community differently? Who is the target audience for Alma Linux Alma Linux Build System What has been the response to Alma Linux? Tell me about Open Office Hours? How do you get involved in Open Office Hours Office Hours Date/Time (https://almalinux.org/blog/almalinux-open-office-hours/) Mattermost (https://chat.almalinux.org) Matrix (#almalinux:matrix.org) Libera.Chat (ircs://irc.libera.chat:6697/#almalinux) What is next for Alma Linux 53:20 Gadget of the Week Lenovo Gen 2 Thunderbolt Dock ((http://www.amazon.com/dp/B07M6S81CM/?tag=minddripmedia-20)) 3 Displays!! 54:30 Open Source Voices Interview with Gregory Kurtzur of Rocky Linux on OSV Ep 21 (https://www.opensourcevoices.org/21) -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard (http://podcast.asknoahshow.com/258) Phone Systems for Ask Noah provided by Voxtelesys (http://www.voxtelesys.com/asknoah) Join us in our dedicated chatroom #GeekLab:linuxdelta.com on Matrix (https://element.linuxdelta.com/#/room/#geeklab:linuxdelta.com) -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they're excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux (https://twitter.com/kernellinux) Ask Noah Show (https://twitter.com/asknoahshow) Altispeed Technologies (https://twitter.com/altispeed) Special Guest: Steve Ovens.

Jack Aboutboul joins us this hour to talk about Alma Linux, a Red Hat Linux clone that is now doing what the former CentOS did prior to it becoming CentOS Stream.

Kristoffer chats with Harald Achitz about Harald’s path as a developer, test-driven development, seeing the big picture, and more. The first part of the discussion is Harald’s background: Growing up on the far side of Europe, focusing on music, and how he eventually landed in computing. Freelancing as a developer in 1995 - what was that like? How did one find customers? The story then goes into Harald’s way into C and C++. Developing for medical devices and hospitals. Moving toward Linux, making a living as an open source developer, and eventually ending up in Sweden. Then, the conversation moves to Harald’s increasing interest in what happens after you finish writing the code; builds, releases, integrations, package managers, build systems, and so much more. We talk quite a bit about seeing the big picture, and how our code is, at best, a temporary and unimportant part of the greater whole. Are we too focused on the next task, at the expense of thinking about and seeing the whole? Harald explains why he likes to have 100% code coverage, how he goes about setting up his tests, and the challenges of setting up tests when responsibilities strech across teams. Many of the hardest problems are organizational, the code we write is, on the whole, often not very important. Code is temporary. All of which is more motivation for testing more. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Harald Stockholmcpp - C++ meetup which Harald arranges Tron Wargames The Iron curtain Conservatorium Visual basic for applications Novell netware Windows 95 Windows NT 3.51 Office 95 Lotus notes Microsoft press Access AS/400 Stored procedures DCOM MSDN KDE GNOME Red hat Slackware “Linux is cancer” Tobii Conan C and C++ package manager Jenkins Unit testing Test-driven development Boost unit test Github actions Scrum Devops Spock - testing and specification framework for Java, Nimoy - for Python Schrödinger’s cat Titles Austria in the 80s On the side of Europe I started and stopped a lot of things Just jamming around Where you play the songs you hate There were computers in offices I was the young person The internet became a thing Freelancing back in 95 I really loved databases I came back to medical devices Would you like to go to Switzerland? A different spirit in the Linux world I have no problem if things work It’s not just the code I write I love to have everything automated Holistic thinking All the tests are passing, but the thing is not useful Yes, it gives me no guarantee You need to fake it The place where people give up Software is their bread and butter The code I write is most likely not very important Software systems tend to change Code is temporary Throw it away as soon as possible Never enough, but always too much

TranscriptCorey: This episode is sponsored in part by LaunchDarkly. Take a look at what it takes to get your code into production. I'm going to just guess that it's awful because it's always awful. No one loves their deployment process. What if launching new features didn't require you to do a full-on code and possibly infrastructure deploy? What if you could test on a small subset of users and then roll it back immediately if results aren't what you expect? LaunchDarkly does exactly this. To learn more, visit launchdarkly.com and tell them Corey sent you, and watch for the wince.Jesse: Hello, and welcome to AWS Morning Brief: Fridays From the Field. I'm Jesse DeRose.Amy: I'm Amy Negrette.Tim: And I'm Tim Banks.Jesse: This is the podcast within a podcast where we talk about all the ways we've seen AWS used and abused in the wild. Today, we're going to be talking about AWS, an open-source software. Now, that's kind of a broad topic, but there have been some specific, recent events I'll say, over the last year maybe or maybe even less, related to AWS and open-source software that really got us talking, and I wanted to have a deeper conversation with both of you on this topic.Tim: Well, you should probably start by going over some of the things that you're mentioning, when you say ‘some of these things,' what are those things, Jesse?Jesse: Yeah. So, I think the best place to start is what constitutes open-source software. And specifically, I think, not just what constitutes open-source software, but how does that differ from an open-source company?Tim: So, open-source software can be anything: Linux kernel, bash, anything like that, any Python functioning module. If you make a piece of software, whatever it is, and you license it with one of the various open-source licenses, or your own open-source license or whatever, it's something that the community kind of owns. So, when they get big, they have maintainers, everything like that, but at its essence, it's a piece of software that you can freely download and use, and then you're free to modify it as you need, and then it's up to the specifics of the license to whether you're required to send those modifications back, to include them, or to whatever. But the essence is that it's a piece of software that's free for me to use and free for me to modify under it's license.Jesse: And one of the other things I want to add to that is, correct me if I'm wrong here, but isn't a lot of open-source software is very community-owned, so there's a lot of focus on folks from the community that is using this software giving back not because they need to under the licensing, necessarily, but because they want to continue using this and making it better over time.Amy: I think one of the issues is that becomes a very opinionated kind of statement where there are a lot of people in the open-source community who feel that if you're going to use something and make changes to better suit what your needs are, that you should be able to submit those changes back to the community, or back to whoever owns the base of the software. But that said, it's like the community edition of MySQL before Microsoft bought it, where the assumption was that there's essentially a candidate of it that anyone can use without the expectation of submitting it back.Jesse: So, that's a broad definition of open-source software, but how does open-source software, broadly speaking, differ from an open-source company? I'm thinking specifically there is the open-source software of Elasticsearch, for example, or I should say, previously the open-source software of Elasticsearch that was owned by the open-source company, Elastic. So, what does that relationship look like? How does an open-source company like that differ from the open-source software itself?Tim: So, there are typically a couple of ways. Usually, a company that is the owner of an open-source product still has some kind of retention of the IP in their various licenses that they can do that with, but essentially—and this is in the words of one of the founders of Elastic—that they're benevolent dictators over the software. And so they allow folks to contribute, but they don't have to. And most of those open-source software companies will have a commercial version of that software that has other features that are not available, packages with support or some of the things like that, some kind of value-added thing that you're going to wind up paying for. The best way to describe—like you said—there's the company Elastic and then the product Elasticsearch.I relate back to before: there was Red Hat Linux, which was open-source, and then the company Red Hat. And I remember when they went public and everyone was shocked that a company can make profit off of something they gave away for free. But while the core of the software itself was free, the support was not free, nor was the add-on features that enterprises wanted. And so that tends to be kind of what the business model is, is that you create the software, it's open-source for a while to get a big user base, and then when it gets adopted by enterprises or people that really would pay for support or for other features, that's when the license tends to change, or there's a fork between the open-source version and then the commercial version.Jesse: And it definitely sounds like there can be benefits to an open-source company essentially charging for not just the open-source software, but these extra benefits like supports and additional features because I know I've traced multiple code bugs back to a piece of open-source software that there's a PR or an issue that has been sitting open for months, if not longer because the community just doesn't have the time to look into the issue, doesn't have the time to work on the issue, they are managing it on their own, separate as a side job, separate from their day-to-day work. Whereas if that is a bug that I'm tracing back to a feature in an open-source piece of software, or I should say software that I am paying for through an open-source company, I have a much clearer support path to a resolution to resolving that issue.Tim: And I think what the end up doing is then you see it more like a traditional core software model, like, you know, a la Oracle, or something like that where you pay for the software essentially, but it comes packaged with these things that you get because of it, and then there's a support contract on top of it, and then there's hosting or cloud, whatever it is, on top of that, now, but you would still end up paying for the software and then support as part of the same deal. But as you know, these are for-profit companies. People get paid for them; they are publicly traded; they sell this software; they sell this product, whether it's the services or the hosting, for profit. That is not open-source software. So, if company X that makes software X, goes under, they are acting like the software would then go under as if the software doesn't belong to the community.So, a business that goes after a business is always going to be fair play; I believe they call it capitalism. But when you talk about going after open-source software, you're looking at what Microsoft was doing in the '90s and early 2000s, with Linux and other open-source challenges to the Windows and the other paid commercial enterprise software market. When folks started using Linux and servers because it was free, customizable, and they could do pretty much everything they wanted to or version of it that they were using commercial Unices for, or even replacing Windows for, you didn't really see the commercial Unices going after it because that very specialized use cases; the user had specialized hardware. What folks were doing, they're buying Wintel machines and putting Linux on them, they were getting them without Windows licenses, or trial licenses, throwing Linux on it. And Microsoft really went after open-source; they really went after open-source.They were calling it insecure, they were calling it flash in the pan, saying it would never happen. They ran a good marketing campaign for a long time against open-source software so that people would not use it and would instead use their closed-source software. That is going after open-source, not going after quote-unquote, “Open-source companies.”Jesse: Yeah, I think that's ultimately what I want to dive into next, which is, there's been a lot of buzz about AWS going after open-source, being a risk to open-source software, specifically, with the release of AWS Managed Services for software like Elasticsearch, for example, Kubernetes, Prometheus vs. Other open-source packages that you can now run as a managed service in AWS. There's a lot of concern that AWS is basically a risk to all of these pieces of open-source software, but that doesn't necessarily seem to be the case, based on what we're talking about. One of the things that I want to dive into really specifically here is this licensing idea. Is it important to end-users? How would they know about what license they're using, or if the license changes?Tim: I'll let Amy dig in on it because she's probably the expert of three of them, but I will say one case in point, I remember where licensing did become very important was Java. JDK licenses, when Oracle started cornering the market on enclosing all the licenses, you had to use different types of Javas. So, you had to get, like, open JDK; you couldn't use Sun, Oracle Java, or whatever it was. And so that became a heavy lift of replacing packages and making sure all that stuff was in compliance, and while tracking packages, replacing them, doing all the necessary things because if you're running Java, you're probably running it in production. Why you would, I don't know, but there are those things that you would have to do in order to be able to just replace a package. The impact of the license, even if it doesn't cost a dime for usage, it still matters, and in real dollars and real engineering time.Amy: Even free licensing will cost you money if you do it wrong. The reason why I love talking about licensing is because I used to work for the government—Jesse: [laugh].Amy: —and if you think a large company like Amazon or Microsoft loves doing anything to rattle the cage of smaller businesses, it's not nearly as much as they love doing it to the government. So, any company that has a government-specific license, and the government is not using it, they will get sued and fined for a bunch of money, which sounds like a conflict between a super-large company and the government and who the hell cares about that, but this also translates the way they handle licensing for end-users and for smaller companies. So, for the most part for the end-user, you're going to look at what is generally sent to you to use any piece of licensing, the EULA, the End-User License Agreement, and you're just going to say, “Yeah, fine, this thing is 20 pages long; I'm not going to read this, it's fine.” And for most end-users, that is actually, you're good to go because they're not going to be coming after small, single-person users. What these licenses do is restrict the way larger organizations—be it the government or mid to larger companies—actually use their software, so that—this is a little dating—someone does not buy a single disk that does not report home, and then install that one disk on 20 computers, which is a thing that everyone has seen done if they've been in the industry long enough.Jesse: Yeah.Amy: Yeah. And it means things like licensing inventory is important, to the single you're using this license at home and you install Adobe on three computers, you would think it's not… would not hurt their value very much, but they also make it so that you can't even do that anymore. So, in purchased software, it makes a big deal for end-users; if it's just something free like being able to use some community SQL workbench just to mess around with stuff at home or on personal projects, you're usually going to be okay.Corey: This episode is sponsored in part by our friends at ChaosSearch. You could run Elasticsearch or Elastic Cloud—or OpenSearch as they're calling it now—or a self-hosted ELK stack. But why? ChaosSearch gives you the same API you've come to know and tolerate, along with unlimited data retention and no data movement. Just throw your data into S3 and proceed from there as you would expect. This is great for IT operations folks, for app performance monitoring, cybersecurity. If you're using Elasticsearch, consider not running Elasticsearch. They're also available now in the AWS marketplace if you'd prefer not to go direct and have half of whatever you pay them count towards your EDB commitment. Discover what companies like HubSpot, Klarna, Equifax, Armor Security, and Blackboard already have. To learn more, visit chaossearch.io and tell them I sent you just so you can see them facepalm, yet again.Jesse: Yeah, this is a really big issue. There's so much complexity in this space because Tim, like you said, there's some amount of capitalism here of AWS competing with open-source companies; there's business opportunities to change licensing, which can be a good thing for a company or it could be a terrible thing for a company's user base. There's lots of complexity to this issue. And I mean, in the amount of time that we've been talking, we've only really scratched the surface. I think there's so much more to this space to talk about.Tim: There really is, and there's a lot of history that we really need to cover to really paint an accurate picture. I think back when web hosting first became a thing, and everyone was running LAMP stacks and nobody was saying, “Oh, no, using cPanel is going to kill Apache.” That wasn't a thing because, yeah, it was a for-profit company that was using open-source software to make money and yet Apache still lived, and [unintelligible 00:15:00] still lived; MySQL still made it; PHP was still around. So, to say that utilizing open-source software to provide a service, to provide a paid service, is going to kill the open-source softwares, at best it's misrepresentation and omits a lot of things. So, yeah, there's a lot of stuff we can dig into, a lot of things we can cover.And the topic is broad, and so this is why it's important for us to talk about it, I think, in the context of AWS and the AWS, kind of, ecosystem is that when you see companies with big crocodile tears, saying, “Oh, yeah, AWS is trying to kill open-source,” it's like, “No, they're not trying to kill open-source.” They may be trying to go after your company, but they aren't the same.Jesse: And it feels to me like that is part of the way that the business world works. And I'm not saying that it's a great part of the way the business world works, but how can you differentiate your company in such a way that you still retain your user base if AWS releases a competing product? I'm not thrilled with the fact that AWS is releasing all these products that are competing with open-source companies, but I'm also not going to say that it's not beneficial, in some ways, for AWS customers. So, I see both sides of the coin here and I don't have a clear idea of what the best path forward is.Amy: As much as I hate the market demands it type of argument, a lot of the libraries, and open-source software, and all of these other things that AWS has successfully gone after, they've gone after ones that weren't entirely easy to use in the first place. Things like Kubernetes, and Prometheus, and MongoDB, and Elastic. These are not simple solutions to begin with, so if they didn't do it, there are a lot of other management companies that will help you deal with these very specific products. The only difference is, one of them is AWS.Jesse: [laugh]. One of them is a multibillion-dollar company.Amy: Oh, they've all got money, man.Jesse: [laugh].Amy: I mean, let's be real. At our pay grade, the difference between a multimillion-dollar and a billion-dollar company, I don't think affects you at your level at all.Jesse: No.Amy: I'm not seeing any of that difference. I am not. [laugh].Tim: Yeah, I definitely think if you all want us to dig into more of this—and we could do a lot more—let us know. If there are things you think we're wrong on, or things that you think we need to dig deeper on, yeah, we'd love to do that. Because this is a complex and nuanced topic that does have a lot of information that should be discussed so that folks can have a clear view of what the picture looks like.Jesse: Well, that'll do it for us this week, folks. If you've got questions you'd like us to answer please go to lastweekinaws.com/QA, fill out the form and we'll answer those questions on a future episode of the show.If you've enjoyed this podcast, please go to lastweekinaws.com/review and give it a five-star review on your podcast platform of choice, whereas if you hated this podcast, please go to lastweekinaws.com/review, give it a five-star rating on your podcast platform of choice and tell us your thoughts on this conversation, on AWS versus open-source software versus open-source companies.Announcer: This has been a HumblePod production. Stay humble.

Welcome to Episode 103 Main Topic Getting into IT series: Nate What is Nate's story, How did he get into computers? How did that lead into IT?  What path has his career taken? Links https://en.wikipedia.org/wiki/Texas_Instruments_TI-99/4A https://en.wikipedia.org/wiki/Hunt_the_Wumpus https://en.wikipedia.org/wiki/TRS-80_Color_Computer https://en.wikipedia.org/wiki/Bulletin_board_system https://en.wikipedia.org/wiki/The_Major_BBS https://www.themajorbbs.com/phoenix/ https://en.wikipedia.org/wiki/Doom_(1993_video_game) https://en.wikipedia.org/wiki/Windows_NT_3.51 https://en.wikipedia.org/wiki/OS/2 https://en.wikipedia.org/wiki/Red_Hat_Linux https://www.icq.com/  It's kinda russian now... https://en.wikipedia.org/wiki/ICQ https://www.enlightenment.org/ https://en.wikipedia.org/wiki/AfterStep http://www.afterstep.org/ https://en.wikipedia.org/wiki/NetWare Announcements Patreon Update 21 Patrons, $108/mo Arinomi Andrew Tatro rootisgod Bruce Robert Matt David S0l3mn Trooper_Ish LinuXsys666 gimpyb Mark DeMentor  Jon Marc Julius Andi J Charles 22532 Get your Iron Sysadmin Merch at Teespring! https://teespring.com/stores/ironsysadmin  Reviews   Chat Nate and Marc diverge into Everquest, and a few other games.    [unclemarc] With the summer, nerd stuff is weak Although I smoked a mean pork butt last weekend for a Baby-B-Q I have not killed my 3D printer yet. Yay! Considering doing a No Man's Sky VR Permadeath Playthrough - stream the whole thing https://www.nomanssky.com/ Dan Vasc - https://www.youtube.com/c/DanVasc   [Nate] Currently tearing apart the suspension on my Jeep. Replacing these stupid C by GE bulbs.  Trying to build a cool hex-lamp for the office. News https://www.theverge.com/2021/6/9/22526266/facebook-smartwatch-two-cameras-heart-rate-monitor  https://www.theregister.com/2021/05/26/freenode_irc_takeover/ https://in.pcmag.com/security/143104/meat-supplier-jbs-pays-ransomware-hackers-11-million-despite-having-backups  https://www.nytimes.com/live/2021/06/07/us/biden-news-today Crypto rap battle: https://www.youtube.com/watch?v=JaMJi1_1tkA   Watch us live on the 2nd and 4th Thursday of every month! Subscribe and hit the bell! https://www.youtube.com/IronSysadminPodcast  OR https://twitch.tv/IronSysadminPodcast   Discord Community: https://discord.gg/wmxvQ4c2H6  Find us on Twitter, and Facebook! https://www.facebook.com/ironsysadmin https://www.twitter.com/ironsysadmin Subscribe wherever you find podcasts! And don't forget about our patreon! https://patreon.com/ironsysadmin   Intro and Outro music credit: Tri Tachyon, Digital MK 2http://freemusicarchive.org/music/Tri-Tachyon/ 

When Bart first started the Taming the Terminal series in October of 2015, he purposely declared every installment to be "of n" where n was not defined. It's been 3 years since there was an episode of Taming the Terminal, but today we've got a new one for you. In Taming the Terminal 36, recorded in 2016, Bart introduced us to a nifty command-line tool called screen. Screen allowed you to ssh into a server, and start a session but disconnect and come back to it without stopping the processes you were running. But in the last year, screen was deprecated by Red Hat Linux (which means it's gone from the free CentOS version as well). The good news is that it was replaced with an even more powerful tool called tmux. In this installment, Bart walks us through just how tmux solves the same problem as screen, but teases us with the knowledge that this tool has much more to offer. It was a super fun episode with lots of surprises (for me at least) and whether you followed along with the first 37 installments or not, I'm sure you'll find it useful as well. You can find Bart's fabulous shownotes at bartbusschots.ie/....

When Bart first started the Taming the Terminal series in October of 2015, he purposely declared every installment to be "of n" where n was not defined. It's been 3 years since there was an episode of Taming the Terminal, but today we've got a new one for you. In Taming the Terminal 36, recorded in 2016, Bart introduced us to a nifty command-line tool called screen. Screen allowed you to ssh into a server, and start a session but disconnect and come back to it without stopping the processes you were running. But in the last year, screen was deprecated by Red Hat Linux (which means it's gone from the free CentOS version as well). The good news is that it was replaced with an even more powerful tool called tmux. In this installment, Bart walks us through just how tmux solves the same problem as screen, but teases us with the knowledge that this tool has much more to offer. It was a super fun episode with lots of surprises (for me at least) and whether you followed along with the first 37 installments or not, I'm sure you'll find it useful as well. You can find Bart's fabulous shownotes at bartbusschots.ie/....

When Bart first started the Taming the Terminal series in October of 2015, he purposely declared every installment to be "of n" where n was not defined. It's been 3 years since there was an episode of Taming the Terminal, but today we've got a new one for you. In Taming the Terminal 36, recorded in 2016, Bart introduced us to a nifty command-line tool called screen. Screen allowed you to ssh into a server, and start a session but disconnect and come back to it without stopping the processes you were running. But in the last year, screen was deprecated by Red Hat Linux (which means it's gone from the free CentOS version as well). The good news is that it was replaced with an even more powerful tool called tmux. In this installment, Bart walks us through just how tmux solves the same problem as screen, but teases us with the knowledge that this tool has much more to offer. It was a super fun episode with lots of surprises (for me at least) and whether you followed along with the first 37 installments or not, I'm sure you'll find it useful as well. You can find Bart's fabulous shownotes at bartbusschots.ie/....

Hyperbola Developer interview, why you should migrate from Linux to BSD, FreeBSD is an amazing OS, improving the ptrace(2) API in LLVM 10, First FreeBSD conference in Australia, and a guide to containers on FreeNAS. Headlines FreeBSD is an amazing operating System (https://www.unixsheikh.com/articles/freebsd-is-an-amazing-operating-system.html) Update 2020-01-21: Since I wrote this article it got posted on Hacker News, Reddit and Lobster, and a few people have emailed me with comments. I have updated the article with comments where I have found it needed. As an important side note I would like to point out that I am not a FreeBSD developer, there may be things going on in the FreeBSD world that I know absolutely nothing about. I am also not glued to the FreeBSD developer mailing lists. I am not a FreeBSD "fanboy". I have been using GNU/Linux a ton more for the past two decades than FreeBSD, mainly due to hardware incompatibility (lacking or buggy drivers), and I love both Debian GNU/Linux and Arch Linux just as much as FreeBSD. However, I am concerned about the development of GNU/Linux as of late. Also this article is not about me trying to make anyone switch from something else to FreeBSD. It's about why I like FreeBSD and that I recommend you try it out if you're into messing with operating systems. I think the year was late 1999 or mid 2000 when I one day was browsing computer books at my favorite bookshop and I discovered the book The Complete FreeBSD third edition from 1999 by Greg Lehey. With the book came 4 CD Roms with FreeBSD 3.3. I had already familiarized myself with GNU/Linux in 1998, and I was in the process of migrating every server and desktop operating system away from Microsoft Windows, both at home and at my company, to GNU/Linux, initially Red Hat Linux and then later Debian GNU/Linux, which eventually became my favorite GNU/Linux distribution for many years. When I first saw The Complete FreeBSD book by Greg Lehey I remember noticing the text on the front page that said, "The Free Version of Berkeley UNIX" and "Rock Solid Stability", and I was immediately intrigued! What was that all about? A free UNIX operating system! And rock solid stability? That sounded amazing. Hyperbola Dev Interview (https://itsfoss.com/hyperbola-linux-bsd/) In late December 2019, Hyperbola announced that they would be making major changes to their project. They have decided to drop the Linux kernel in favor of forking the OpenBSD kernel. This announcement only came months after Project Trident announced that they were going in the opposite direction (from BSD to Linux). Hyperbola also plans to replace all software that is not GPL v3 compliant with new versions that are. To get more insight into the future of their new project, I interviewed Andre, co-founder of Hyperbola. News Roundup Improving the ptrace(2) API and preparing for LLVM-10.0 (https://blog.netbsd.org/tnf/entry/improving_the_ptrace_2_api) This month I have improved the NetBSD ptrace(2) API, removing one legacy interface with a few flaws and replacing it with two new calls with new features, and removing technical debt. As LLVM 10.0 is branching now soon (Jan 15th 2020), I worked on proper support of the LLVM features for NetBSD 9.0 (today RC1) and NetBSD HEAD (future 10.0). The first FreeBSD conference in Australia (https://rubenerd.com/the-first-freebsd-conference-in-australia/) FreeBSD has existed as an operating system, project, and foundation for more than twenty years, and its earlier incantations have exited for far longer. The old guard have been developing code, porting software, and writing documentation for longer than I’ve existed. I’ve been using it for more than a decade for personal projects, and professionally for half that time. While there are many prominent Australian FreeBSD contributors, sysadmins, and users, we’ve always had to venture overseas for conferences. We’re always told Australians are among the most ardent travellers, but I always wondered if we could do a domestic event as well. And on Tuesday, we did! Deb Goodkin and the FreeBSD Foundation graciously organised and chaired a dedicated FreeBSD miniconf at the long-running linux.conf.au event held each year in a different city in Australia and New Zealand. A practical guide to containers on FreeNAS for a depraved psychopath (https://medium.com/@andoriyu/a-practical-guide-to-containers-on-freenas-for-a-depraved-psychopath-c212203c0394) This is a simple write-up to setup Docker on FreeNAS 11 or FreeBSD 11. But muh jails? You know that jails are dope and you know that jails are dope, yet no one else knows it. So here we are stuck with docker. Two years ago I would be the last person to recommend using docker, but a whole lot of things has changes past years… So jails are dead then? No, jails are still dope, but jails lack tools to manage them. Yes, there are a few tools, but they meant for hard-core FreeBSD users who used to suffering. Docker allows you to run applications without deep knowledge of application you’re running. It will also allow you to run applications that are not ported to FreeBSD. Why you should migrate everything from Linux to BSD (https://www.unixsheikh.com/articles/why-you-should-migrate-everything-from-linux-to-bsd.html) As an operating system GNU/Linux has become a real mess because of the fragmented nature of the project, the bloatware in the kernel, and because of the jerking around by commercial interests. Response Should you migrate from Linux to BSD? It depends. (https://fediverse.blog/~/AllGoodThings/should-you-migrate-from-linux-to-bsd-it-depends) Beastie Bits Using the OpenBSD ports tree with dedicated users (https://dataswamp.org/~solene/2020-01-11-privsep.html) broot on FreeBSD (https://vermaden.wordpress.com/2020/01/10/run-broot-on-freebsd/) A Trip down Memory Lane (https://svnweb.freebsd.org/base/head/share/misc/bsd-family-tree?view=co) Running syslog-ng in BastilleBSD (https://www.syslog-ng.com/community/b/blog/posts/running-syslog-ng-in-bastillebsd) NASA : Using Software Packages in pkgsrc (https://www.nas.nasa.gov/hecc/support/kb/using-software-packages-in-pkgsrc_493.html) Feedback/Questions All of our questions this week were pretty technical in nature so I'm going to save those for the next episode so Allan can weigh in on them, since if we cover them now we're basically going to be deferring to Allan anyway. 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.

Red Hat Linux is a staple of most enterprise IT organization's software diets. Developers and IT leaders all over the world took notice when IBM acquired Red Hat. Will IBM Red Hat change? Will Red Hat continue to operate as it does today or will it be subsumed and disappear into some IBM business unit? Will IBM Red Hat still contribute to projects and tools like Kubernetes, JBoss, Fuse, OpenJDK, Eclipse IDE, and many others (https://redhatofficial.github.io/#!/main)? All are important questions. Brad Micklea, Lead of the Developer Program and Tools at IBM, joins DevOps Chat to talk about the future of Red Hat as part of IBM. Brad sends a strong message that Red Hat will remain focused on the developer community and tools for Linux, Kubernetes, Java, DevOps, and others. Join us as we talk with Brad about the future of Red Hat, DevOps, and open source developer tools.

The Open Source CEO Bob Young’s journey from renting typewriters to co-founding an open-source software company to founding a self-publishing platform. Entrepreneurship carries a lot of prestige these days. But back in the 1970s, when one freshly minted, Canadian college grad decided to start his own business, the only real perk was a business card that read, “Bob Young: President” that he could show to his mom. This, Young explains, was the single greatest benefit of starting a business back then. It wasn’t about the money, the eager investors, or the thousands of devoted fans (he didn’t have any of those). He just hoped he could reassure his mom that she didn’t have to worry about him anymore. “We now have the smartest kids in our high schools going to college to study entrepreneurship,” he says. “Whereas, back in my day, all the smart kids went and got ‘real jobs’ as lawyers or accountants or whatever and became CEOs of big corporations, and it was us dumb kids who started businesses because no one would employ us.” For Young, that meant printing up a fancy business card and, with a little money from friends and family, buying a small, failing typewriter rental business for cheap. From there, though, things got interesting. Young quickly pivoted from typewriters to computers, until a mid-career stumble led him to the world of open source software, a field in which he thrived. Young has since gone on to found Red Hat, a multinational company that offers non-proprietary software solutions to businesses. In 2018, IBM announced it would acquire Red Hat for around $34 billion. Today, Young is at the helm of a few businesses, including self-publishing platform Lulu.com, continuing his passion for democratic, open distribution models that favor the little guy. But despite his 40 years in entrepreneurship, he still lists just a single skill under “Specialties” in his LinkedIn bio: typewriter sales. “I’m a typewriter salesman, and that is the value I bring to the companies that I’m involved with,” Young says. “I’m a sales and marketing guy, and I have to hire smart accountants and smart engineers and smart product managers, because those are skills that I don’t have. My one contribution is in the sales and marketing side of the projects I’m involved in.” When Success Turns Sour Young realized almost immediately that his first business had to evolve, and fast. Shortly after he bought the typewriter rental business, he dug through old customer records to find those listed as inactive, and began calling them to try and entice them back into the fold. One of the businesses that had often rented typewriters from the previous owner was a phone company called Bell Canada. After speaking with the office manager, a sweet woman who invited him to come visit even though, “when you come by all I’m going to do is show you why I don’t need your services anymore,” Young headed off to downtown Toronto to meet with her. As she walked him through the open-plan office building, he saw several hundred employees, who only four years previously had used rented typewriters, at work in their cubicles. They were all staring into computer screens. “We then, immediately of course, got into the computer equipment rental business,” Young says, laughing. He managed Hamilton Rentals from 1979 until he sold it in 1984. He then founded Vernon Computer Source, another equipment rental business, that same year. In 1992, Young was on cloud nine. He had just sold his second computer rental business to technology services company Greyvest Capital, Inc., mostly for shares in the company, and took a stable, comfortable job there. Then came NAFTA (the North American Free Trade Agreement), which eliminated tariffs between the United States, Mexico, and Canada. That led to financial troubles for Greyvest, and suddenly Young’s life ceased to be as stable as he’d expected. “In ’93, I found myself in Westport, CT, unemployed with a net worth of something less than it had been when I graduated college 15 years earlier, only now I had three children, a wife and a big mortgage.” Just as Young had made his next big step forward in his career, it had all come crashing down around him. But looking back on this time in his life, Young is grateful for this heartbreaking failure, because he links it directly to the birth of Red Hat, Inc. Trying on a New Hat Shortly before its demise, Greyvest sent Young to New York to pursue the Unix workstation (a special computer designed specifically for scientific or technical endeavors) market, asking him to get to know the users in the big financial services companies and engineering companies in and around the city. Greyvest was in pursuit of new rental and leasing customers, and this was precisely what Young did best. To accomplish this, he had been attending evening user group meetings and offering a helping hand. He had even started a modestly sized newsletter. But when the bankruptcy of Greyvest forced him to walk away from the computer rental business for good, his goals shifted. What if, he wondered, he could transform his newsletter into something more? As Young explains, the true value of an online newsletter doesn’t lie in the subscriptions. It’s all about the mailing list. Products of value to those particular customers can be marketed and sold using the list. And so, ACC Corp. was born, and through it, Young transformed his mailing list into a catalog filled with programs and software that catered to his audience: the ACC PC Unix and Linux Catalog. Linux and Unix were two similar but competing operating systems initially released in the early 1970s. The major difference? Linux was free and open sourced. Unix was not. Through the catalog, he had the greatest success in the sale of Linux-based products, so when he asked his customers to share what else he could add to his catalog, and they directed him to a tiny project filled with potential called Red Hat Linux, he was intrigued. Red Hat Linux promised to be a new and improved version of the Linux Young’s customers already knew and loved, so Young knew he needed to check it out. Young called the creator, Mark Ewing, who was working out of his spare bedroom and his own bank account, and asked him to send over 300 copies of Red Hat Linux for him to sell through the catalog. Silence. Young questioned Ewing’s hesitation to do business with him. Ewing explained that he had only planned to manufacture 300 copies of Red Hat Linux in total. Young meshed his big dreaming style with Ewing’s engineering prowess, and the two co-founded the version of Red Hat, Inc. that still thrives today. He had taken a circuitous route to the software industry, but he was grateful that he finally arrived when he did. “Whether it was Steve Jobs or Bill Gates, they’re both contemporaries of mine and it’s been fun sort of growing up in the industry watching those guys be successful,” he says. “I was late to the party of success, but I was pleased with Red Hat’s success.” Young served as the company’s CEO from its founding in 1993 until shortly after the company went public in 1999. “Once we became a public company, and we had 400 employees, I realized I’d never worked for a company of 400 employees, much less managed one,” he says. As he faced down the wild host of new rules, regulations, and responsibilities that came with being CEO of a public company, Young recognized that the best thing he could do to ensure the company’s success was to embrace his own weaknesses and step away. “One of the tricks to being successful is to be self-aware,” Young says. “None of us—no human being—is anywhere close to being perfect. In fact, I’d argue that most of us are barely adequate, even among the most successful of us. But if you know what you’re good at, and you know what you’re not good at, then you can build organizations that protect themselves from your failings.” Young also recognized an entrepreneurial wanderlust stirring in his heart. “I’m an early stage startup guy,” he says. “I really, really like the big idea, and I really like selling the big idea, but once I convince people that the big idea is worth pursuing, I lose interest in it and I’m looking for the next big idea.” He explains that this is an excellent quality when you’re just starting a business and hunting for your great, big idea, but that, once a company is off and running, it can become a serious problem. “Repetition and precision are things I do not do,” he says with a chuckle. “I never have done. This is why I was such a terrible student as a kid. My mind just doesn’t work that way. My mind works always on the next idea.” So, he decided to call Matthew Szulik, who would become the next leader of Red Hat, into his office for a chat. “Probably the biggest single contribution I made to Red Hat’s success was getting out of Matthew’s way and letting him turn our fledgling Red Hat business into the billion-dollar enterprise it is today.” Although the time had come to bid Red Hat farewell, Young is still incredibly proud of their ongoing success. “It was this wonderful adventure that worked out astoundingly well,” he says. “We weren’t sure if we could build a business there, but we knew if we could it was going to be a huge business, because open source—sharing your software, sharing binaries with your customers—was simply a better way of building software than the previous proprietary model that all the other software companies were pursuing at the time. “To have that vision come true has been a bit of an out of body experience, and it gives me great pleasure,” he says. And just like that, the co-founder of Red Hat was off on a journey to find his next big idea and turn it into a reality. Open Source Publishing Today, at just shy of 60 years old, Young owns the Canadian football team the Hamilton Tiger-Cats and serves as CEO of craft marketplace Needlepoint.com and chairman of drone company PrecisionHawk. But the endeavor he says he is currently most passionate about was one he founded in 2002—Lulu.com. Through this print-on-demand self-publishing and distribution platform, Young wanted to revolutionize the publishing industry. He wanted to serve authors who write on niche subjects and catered to niche audiences. In other words, the ones that would be turned away by the traditional publishing industry, no matter the value the book offered to the market it intended to serve. “We serve the interests of the author,” he explains. “The publishing industry is set up to serve the interest of the readers, and the author is just a cog in their machine.” Young has a special passion for creators would otherwise get chewed up by “the machine,” no matter their industry. This is partly why he recommends founders consider platforms like Shopify to sell their products rather than relying on the “FANGs” (Facebook, Amazon, Netflix and Google). “The consolidation we are seeing on the internet is making early internet pioneers nervous,” Young says, “because the whole point of the Internet was to bring more democracy—to put more control in the hands of the consumer, of the user of the internet—and we are seeing it move away from there.” When a business owner sets up an Amazon store or a Facebook page to sell from, those customers no longer belong to the business owner. They belong to Amazon or Facebook. “You want your customers to have loyalty,” he says. “The problem with setting up your shop on Amazon is Amazon is competing with you for the brand and the attention of the customers you’re sending to Amazon, and that’s not in your interest of building a strong brand for your product and your service.” Young explains that when an author sends their customers to Amazon to buy their book, Amazon immediately begins recommending other titles in that subject to the customer before they have even been able to purchase the title they originally intended to buy. “Amazon has just absconded with your customer,” he says. “Amazon is happy to have you as a merchant, because they want you to bring all your customers to Amazon so they can sell them other things. Shopify is the exact opposite of that.” Rather than sending new customers to Facebook.com/YourBusiness, he urges business owners to start sending customers to YourBusiness.com. He also encourages founders to “pay attention to the principles behind the internet, not just the buttons that Facebook and Google give you.” “The internet itself is this great, open vista, and if you build your market using the foundational elements of the internet, no one can ever take that away from you.” He’s hopeful that the rising generation of founders and business owners will be savvy enough to navigate these stormy seas. “As this next generation of entrepreneurs get going, they’re going to understand…you’ve got to be really careful about surrendering your customer to your supplier,” he says. “You want to find suppliers who are going to partner with you to build your business, not using you to build their business.” Whether in the computer rental space, the arena of open source coding or his current realm of self-publishing, Young has always lived by the principal of democratizing access to the tools that build success. Through collaboration and inviting more voices to the table, advancements come more swiftly, and this is a principal that even Young, a self-proclaimed “dumb kid” who started out selling typewriters, can embrace. Bob Young’s Tips on Cultivating Self-Awareness Bob Young says that he owes much of his success to self-awareness. By leaning into what he is good at and hiring others to cover areas where he struggles, this self-proclaimed typewriter salesman has found remarkable success. Young insists that even those who struggle with self-awareness can develop it, and these are three of his tips for harnessing that growth: 1. Put the Pride Aside “So many of us are prideful,” Young says. “We worry about being criticized.” But as founders, and as humans, there is always room for growth. Rejecting that evolution in favor of belief in our own mythology only prevents us from reaching our greatest potential. Young says that, in order to achieve any increased level of self-awareness, pride first has to be eliminated from the equation. 2. Listen to Critiques More Than Compliments Once pride is silenced, it’s time to let the criticisms reach our eyes and ears, even though it may sting a little. “We worry that people think we’ve made a mistake or that we’ve done something dumb,” Young says. “If you can flip that around and look at your mistakes as your biggest single learning opportunity that day or that week or that year, now when people criticize you, they’re more valuable to you than the people who compliment you.” Choosing to embrace our own failings today, no matter who brings them to our attention, is the only way to make sure those same failures don’t repeat tomorrow. 3. Be Honest With Yourself Young is comfortable with sharing the skills he lacks, especially in the area of customer support. He explains that, although he loves his customers, he cannot find the patience to help a new customer struggle through a problem he’s solved for 600 customers who came before. He says that it took many years, and many, many customers pointing out this flaw, for him to internalize the criticism, but once he did, and once he genuinely considered the critique, he recognized that he and his customers would be better served if left that work to someone else. He says his brain simply isn’t wired for customer service, so he relies on those around him who are. To maximize self-awareness, Young says we should accept what we are great at, grow where we are able, and rely on the talents of others to support us where we perpetually fall short. Key Takeaways How Bob got his start in entrepreneurship by selling typewriters How a visit to Bell Canada convinced Bob to make the transition from typewriter rentals to computer rentals How his net worth got wiped out and what he did next His transition from equipment leasing to software when he cofounded Red Hat Why he decided to step away and hire a CEO for Red Hat The project he cares most about now: print-on-demand self-publishing and distribution platform Lulu.com Why he’s paying a lot of attention to Shopify Why the next wave of entrepreneurs needs to be wary of relying on big tech companies How to cultivate more self-awareness as a founder His thoughts on Red Hat being acquired by IBM for $34 billion  

We scale the Red Hat Summit and come back with a few stories to share.

In this special episode of This Week in Linux, we’re creating the ultimate episode for the ultimate Linux GNews podcast . . . this is episode 42 of This Week in Linux! On this episode we cover the release of Linux 4.19, the Return of Linus Torvalds to the Linux kernel, the BIG news of… Read more

Charlotte Williams from Naked Security talks to Sophos experts Matt Boddy and Paul Ducklin about the EFAIL in email, a gift-horse bug in Red Hat Linux, and what happens when sniffer dogs join your cybersecurity team. (Music: purple-planet.com and codices.bandcamp.com)

Would you like to hear today how I am hiring freelancers to collaborate in building all of our businesses together by creating more helpful video tutorials for the world? If you would like to apply, please visit https://jerrybanfield.com/jobs/ for this and any new jobs added. Even if you are not interested in making the tutorials, you might enjoy the discussion related to how I ended up doing this today! Here are the details from the job posting! Would you be willing to make me screen capture tutorials that I would then upload to YouTube on the topics listed below in 1920 x 1080 with good audio? Ethical hacking, penetration testing, IT security, Python, Java, Kali Linux, Red Hat Linux, machine learning, Swift, PHP, MySQL, AngularJS, node.js, 3D rendering, natural language processing, and data science. Will you make the videos for me by naturally speaking and showing your experience with the topics above and more similar to it? If so, I am willing to pay you by the hour to make me videos indefinitely! For every hour paid, I hope to receive about 30 minutes in video because this is what I currently am capable of! If you would like to have me hire you for this job, would you please complete the screening questions? When I like your answers, I will immediately make an offer for you to start and I plan to hire several people while keeping the best indefinitely! Thank you for reading about this episode of Happier People podcast and I hope you enjoyed it! --- Support this podcast: https://anchor.fm/jerrybanfield/support

Today is the first episode with 2 guests — Darrin Stephens & Chris Sideroff — business partners in Applied CCM, based in Australia & Canada respectively. Whilst Applied CCM have several CFD-related activities, this interview is essentially all about Caelus, their CFD software derived from OpenFOAM®. I really wanted to take this opportunity to dig into the whys & wherefores of Caelus, including: • what makes Caelus different to OpenFOAM, both in terms of features & philosophy; • why forks/derivatives detract from their parent open-source project & what they signify; • what “industrially-hardened” means in a CFD context & why Red Hat Linux was a source of inspiration; • why they have "a thing" about validation; Shownotes Applied CCM — http://www.appliedccm.com/ Caelus — https://www.caelus-cml.com/

Hack Naked coversthis week, CompTIA Security, CISSP, CEH v9, and Red Hat Linux. All that and more on Hack Naked TV! Visit http://hacknaked.tv to get all the latest episodes!

Hack Naked coversthis week, CompTIA Security, CISSP, CEH v9, and Red Hat Linux. All that and more on Hack Naked TV! Visit http://hacknaked.tv to get all the latest episodes!

Hack Naked coversthis week, CompTIA Security, CISSP, CEH v9, and Red Hat Linux. All that and more on Hack Naked TV! Visit http://hacknaked.tv to get all the latest episodes!

Hack Naked coversthis week, CompTIA Security, CISSP, CEH v9, and Red Hat Linux. All that and more on Hack Naked TV! Visit http://hacknaked.tv to get all the latest episodes!

This week we take a look at the most recent release of Fedora- the development branch of the vernerable Red Hat Linux. (Hint: We don't like it very much.)

Recovering data from corrupted flash drive, securing compromised hotmail account, Profiles in IT (Matthew Szulik, CEO of Red Hat Linux), Device of the Week (Barnes and Noble Nook e-reader, color, wi-fi, Android browser, e-book loaning, $249), Large Hadron Collider update (low power test successful, full power in a few months, seeking Higgs boson, fear of mini-blackholes), Website of the Week (www.criticalthinking.org), anatomy of thinking (eight elements of reasoning, standards of thinking, transformation of education, Socratic questioning), and eBay to sell Skype (settles dispute with Skype founders). This show originally aired on Saturday, November 28, 2009, at 9:00 AM EST on WFED (1500 AM).

Recovering data from corrupted flash drive, securing compromised hotmail account, Profiles in IT (Matthew Szulik, CEO of Red Hat Linux), Device of the Week (Barnes and Noble Nook e-reader, color, wi-fi, Android browser, e-book loaning, $249), Large Hadron Collider update (low power test successful, full power in a few months, seeking Higgs boson, fear of mini-blackholes), Website of the Week (www.criticalthinking.org), anatomy of thinking (eight elements of reasoning, standards of thinking, transformation of education, Socratic questioning), and eBay to sell Skype (settles dispute with Skype founders). This show originally aired on Saturday, November 28, 2009, at 9:00 AM EST on WFED (1500 AM).