Podcasts about bsd

BSD a Charles Oliveira dans le viseur ! 15€ offerts sur votre premier achat Whatnot via ce lien https://whatnot.pxf.io/JkzzRv ✌ Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

This show has been flagged as Clean by the host. We'll explain why we're doing it, what it is, and cover some useful tools along the way. I've been watching movies recommended to me by my colleagues. As I work for a global company, the recommendations are often “Foreign Language”, which by definition is every movie to someone. It's often difficult to read the subtitles, or they are distracting from the acting. So I thought of converting the subtitles to speech for inclusion as an audio track, to produce a Voice Over or Lectoring audio track. Lectoring aka Voice Over Translations First used is soviet countries to read the news and propaganda from a lectors - the first podcasts ? In Polish, lektor is also used to mean “off-screen reader” or “voice-over artist”. A lektor is a (usually male) reader who provides the Polish voice-over on foreign-language programmes and films where the voice-over translation technique is used. This is the standard localization technique on Polish television and (as an option) on many DVDs; full dubbing is generally reserved for children's material. https://en.wikipedia.org/wiki/Lector#Television Example: Night of the Living Dead To give you an idea of what this sounds like I'm going to play you an example of the out of copyright movie, Night of the Living Dead . In the United States, Night of the Living Dead was mistakenly released into the public domain because the original distributor failed to replace the copyright notice when changing the film's name Original First the original sound track, then the same clip with the voice over track. Voice Over Proof of Concept As a native English speaker I find it difficult to follow those Voice Over tracks as I am trying to focus on the underlying audio. In discussions with Polish friends, it seems that this is not a problem when Polish is your native language. To put that to the test I wanted to try it out on a movie to see if that were indeed the case. I asked on Mastodon for a non English movie that was Creative Commons but did have English Subtitles, and HPR host Windigo had the answer. 2009 Nasty Old People is a 2009 Swedish film directed by Hanna Sköld, Tangram Film. It premiered on 10 October 2009 at Kontrapunkt in Malmö, and on file sharing site The Pirate Bay. The film is available as an authorized and legal download under the Creative Commons license CC BY-NC-SA. So my idea was to take each bit of subtitle text, convert it to audio, then have the generated audio play at the same time the subtitle appears on the screen. We use piper to process shows here on HPR, and we also generate srt, or SubRip subtitle files for each show. SRT or SubRip files are the easiest subtitle file to work with. From https://en.wikipedia.org/wiki/SubRip The SubRip file format is described on the Matroska multimedia container format website as “perhaps the most basic of all subtitle formats.” SubRip (SubRip Text) files are named with the extension .srt , and contain formatted lines of plain text in groups separated by a blank line. Subtitles are numbered sequentially, starting at 1. The timecode format used is hours:minutes:seconds,milliseconds with time units fixed to two zero-padded digits and fractions fixed to three zero-padded digits (00:00:00,000). The comma (,) is used for fractional separator . A numeric counter identifying each sequential subtitle The time that the subtitle should appear on the screen, followed by –> and the time it should disappear Subtitle text itself on one or more lines A blank line containing no text, indicating the end of this subtitle I downloaded the movie from the Internet Archive , and then used Piper voice to convert a minutes worth of subtitles. piper_voice: A fast and local neural text-to-speech engine that embeds espeak-ng for phonemization. GPL-3.0 license Once I had the audio prepared for a sample of the subtitles, it was over to audacity to create a new subtitle audio track. Audacity is the world's most popular audio editing and recording app GPL v2 or later, Timing the segments would be a problem, if it were not for the fact that Audacity supports srt files as Labels. File > Import > Lables. Then select the srt file The subtitle track with the text of the audio will be displayed. I could then Import each Audio segment and line them up with the subtitle track for to get the correct timing. Each subtitles segment created a new separate audio file which I then exported. I then used Kdenlive to open the video and import the audio and subtitle tracks. Kdenlive: is the acronym for KDE Non-Linear Video Editor. It works on Linux, Windows, macOS, and BSD. GPL-3.0-or-later There is a good article on adding by Jean-Marc on How to Add Subtitles Easily in Kdenlive Project > Subtitles > Add Subtitle Track Select the Subtitle file Align the subtitle and audio track. After rendering the segment out I was satisfied that this was something worth doing. The script The script can be found on the episode page for this show on the HPR site, and I put it together as a proof of concept. It creates a new audio track for the subtitles, and merges this with the original sound track to create a new selectable sound track. It begins by creating a length of silent audio that is as long as up to the first subtitle time segment begin timestamp. The first subtitle segment is converted from text to speech using Piper voice That segment of audio is added to the initial silence track. We check the total length so far, and then see if there is supposed to be silence between the last and next subtitle segment begin timestamp. If there is, then a filler piece of silence is added until the next subtitle should appear. If not then the audio for both subtitles play immediately after one another. I was worried that the subtitle audio would then lag behind the on screen dialogue but it works surprisingly well. Even long series of dialogue sort themselves out after a bit. We do this over and over again for each subtitle, right up to the very end of the movie. This new subtitle to speech audio track is then merged back into the media file as a new audio track. 96 00:15:06,240 --> 00:15:10,640 It will be two years before it's this big 97 00:15:12,840 --> 00:15:17,840 But don't you bother. By then I'll be long gone 98 00:15:19,840 --> 00:15:22,400 It was just a question 99 00:15:22,880 --> 00:15:25,480 Porridge? Original First the original sound track, then the same clip with the voice over track. Voice Over Lessons learned Now that I have done this for a lot of movies, there a few tips for getting the best output. The creation of the audio track usually goes well, but you can run into issues with the merging of the new track back into the movie. Preparation The first thing you need is a subtitle file which will be the basis of the voice you will be listening to. It should be good quality so that it matches when the actors speak. It's important to clean up this before you use it, fixing spelling mistakes and removing html that will get rendered. Listening to three hours of “I L Zero ve y Zero u”, or “less than forward slash I, greater than”, or “L am from Lndia” can get a bit tedious. You should also try and get versions that translate the songs as well. Getting a SRT file from the media. As many Subtitles are taken from a DVDs they can often be poor Optical character recognition versions of the bitmap-based streams. So a picture of string “Hello World” rather than the letters. ffmpeg By far the easiest and best way to get the subtitles is to extract it from the movie itself, provided it's a separate track. ffmpeg is a complete, cross-platform solution to record, convert and stream audio and video. LGPL-2.1-or-later, GPL-2.0-or-later https://ffmpeg.org/ ffmpeg -y -hide_banner -loglevel error -txt_format text -i "${this_movie_file}" "${this_srt_file}" Getting a SRT file from the web. If that fails you can try to get the subtitle files from the Internet. https://www.opensubtitles.org Select your language with the highest subtitle rating. You can check the media using the mpv media player. mpv is a media player based on MPlayer and mplayer2. It supports a wide variety of video file formats, audio and video codecs, and subtitle types. GPLv2+, parts under LGPLv2.1+, some optional parts under GPLv3 https://mpv.io/manual/master/ Name the srt file with the same prefix as the movie and mpv will play it. You can also use the --sub-files= option as well. mpv "${this_movie_file}" --sub-files="${this_srt_file}" Scrub through the file to see if the timing is correct. The subtitles can be toggled using the j key. Fixing Timing issues It's very important to get the subtitles to align, otherwise the voices will be out of sync. When the subtitles don't match up, it's usually that they need to have the start offset corrected. ffsubsync will automatically try and adjust the offset of the first subtitle to the first use of speech in a movie. ffsubsync: Language-agnostic automatic synchronization of subtitles with video, so that subtitles are aligned to the correct starting point within the video. MIT license https://github.com/smacke/ffsubsync pip install ffsubsync ffs video.mp4 -i unsynchronized.srt -o synchronized.srt LosslessCut will allow you to quickly remove additional trailers, or ads, at the beginning, so that ffsubsync will have a better chance of working if they are trimmed away. LosslessCut: aims to be the ultimate cross platform FFmpeg GUI for extremely fast and lossless operations on video, audio, subtitle and other related media files. GPL-2.0 license https://github.com/mifi/lossless-cut If that fails to match up the subtitles, you can use mpv keyboard shortcuts , move to the first speech segment an then press the Ctrl+Shift+Left and Ctrl+Shift+Right to adjust subtitle delay so that the next or previous subtitle is displayed. It will also show a number giving the miliseconds the delay is, eg -148416 miliseconds or -148.416 seconds. You can use many tools to adjust the subtitles, and I tried out SRT Offset . srt-offset: A simple command-line tool to offset SRT subtitle files. This tool allows you to adjust the timing of subtitles in SRT files, which can be useful when subtitles are out of sync with the video. MIT license srt-offset -i input.srt -offset -148.416 -o output.srt Manually adding the new subtitle to speech audio track If that presents an issue then you can use avidemux to just add the new audio track. Avidemux: is a free video editor designed for simple cutting, filtering and encoding tasks. GPL V2 Open Avidemux, and select “File > Open”, to select the movie. Then go to “Audio > Select Track” Select the next unselected track and tick “Enabled”, “Add Audio Track” Then pick the new mixed track, in this example .~NastyOldPeople_mixed.mp3 Conclusion I now find it much easier to watch a movie with the voice over track. It gets to a point where I don't even notice it is there and just hear the actors speak in their own language, and I just know what they are saying. Links 2009 Nasty Old People A Spanish voice-over translation avidemux by Jean-Marc on How to Add Subtitles Easily in Kdenlive container format Decimal separator extension ffmpeg ffmpeg on wikipedia ffsubsync GPL-3.0 license GPL v2 or later Kdenlive LGPL-2.1 LosslessCut Matroska MIT license Movie on Archive.org mpv mpv keyboard shortcuts mpv wikipedia Nasty Old People from the Internet Archive Night of the Living Dead Noc żywych trupów | Film grozy | Polski lektor OpenSubtitles opensubtitles.org Optical character recognition Piper voice SRT Offset srt, or SubRip subtitle files SubRip Timecode Voice-over translation Whisper Provide feedback on this episode.

Pool and Vdev topology for promox, KDE Plasma is not forcing systemd, Running a 2.11 BSD system, Booting NetBSD from a wedge and more... NOTES This episode of BSDNow is brought to you by Tarsnap and the BSDNow Patreon Headlines Pool and VDEV Topology for Proxmox Workloads News Roundup KDE Plasma 6.6 is Not Forcing systemd(1) but Arguments Rage On. An old article with covering : Running and administrating a 2.11 BSD system Booting NetBSD from a wedge, the hard way Beastie Bits The NetBSD Foundation will participate in Google Summer of Code 2026! Solaris 11.4 SRU90: Preserve Boot Environments zfs-2.4.1 Hardening OPNsense: Using Q-Feeds to Block Malicious Traffic 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 Gary - A nice blog Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv Join us and other BSD Fans in our BSD Now Telegram channel

In this episode of Linux Out Loud, Wendy, Nate, and Bill start in the server room and end up staring down new “for the children” age‑verification laws aimed squarely at your operating system. They talk through wrangling tablets and printers with CUPS, why Framework laptops keep surviving industrial abuse, and how Deskflow brings Synergy/Barrier‑style magic to Wayland setups. From there, they dig into the new FIRST LEGO League robotics kits and what might be lost when classroom‑friendly AI kits replace hands‑on engineering. Finally, they unpack California and Colorado's OS‑level age‑verification bills, what “OS providers” really means, and why small Linux and BSD projects are already threatening to block entire states rather than bolt surveillance rails onto their distros. Show Links: CUPS (Common UNIX Printing System) – https://www.cups.org/ LibreNMS – network and printer monitoring – https://www.librenms.org/ Framework Laptop – https://frame.work/ Deskflow – seamless multi‑computer control – https://cubiclenate.com/2026/02/13/deskflow-seamless-multi-computer-control/ Third Reality Zigbee devices – https://3reality.com/ LEGO Education Computer Science & AI kit (new FLL robots) – https://education.lego.com/en-us/products/lego-education-computer-science-and-ai-45522 LEGO Education SPIKE Prime set – https://education.lego.com/en-us/products/lego-education-spike-prime-set-45678 California AB 1043 – Digital Age Assurance Act overview – https://calmatters.digitaldemocracy.org/bills/ca/2025-2026/ab1043 Nate – Data has weight (but only on SSDs) – https://cubiclenate.com/2026/03/04/data-has-weight-but-only-on-ssds-blathering/ Chapters: 00:00:00 Intro 00:00:52 Bill is a pro, trust me bro! 00:02:19 Printer monitoring, SNMP & copier contracts 00:07:01 Framework laptops in industrial environments 00:09:24 Framework durability, cases & drop protection 00:14:14 Deskflow – Wayland-friendly Synergy/Barrier 00:19:59 New FLL robots – kits, AI & concerns 00:33:10 Age verification laws hit Linux & BSD 00:38:58 Fines, liability & open-source maintainers 00:40:02 What counts as an “OS provider”? 00:44:43 Surveillance, mission creep & “for the children” 00:46:22 Future of OS compliance & responses 00:50:54 Guard rails 00:55:16 Wrap-up, jokes & closing banter 00:57:30 Data has weight 01:00:27 Outro Connect with the Hosts on Discord: Matt – @Dark1ltg Wendy – @Wendy.sh Nate – CubicleNate.com @CubicleNate Bill – @ctlinux on MastodonSpecial Guest: Bill.

NOTES This episode of BSDNow is brought to you by Tarsnap and the BSDNow Patreon Headlines ZFS vs BTRFS Architects features and stability RHEL on ZFS Root: An Unholy Experiment News Roundup Slackware on Encrypted ZFS Root. https://tumfatig.net/2026/slackware-on-encrypted-zfs-root/ OpenIndiana Is Porting Solaris' IPS Package Management To Rust FreeBSD Jail Memory Metrics Tcl: The Most Underrated, But The Most Productive Programming Language How to Setup WireGuard on OpenBSD: The Ultimate Self-Hosted VPN Guide (2026) 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 Join us and other BSD Fans in our BSD Now Telegram channel

Bryan Cantrill is the co-founder and CTO of Oxide Computer Company. We discuss why the biggest cloud providers don't use off the shelf hardware, how scaling data centers at samsung's scale exposed problems with hard drive firmware, how the values of NodeJS are in conflict with robust systems, choosing Rust, and the benefits of Oxide Computer's rack scale approach. This is an extended version of an interview posted on Software Engineering Radio. Related links Oxide Computer Oxide and Friends Illumos Platform as a Reflection of Values RFD 26 bhyve CockroachDB Heterogeneous Computing with Raja Koduri Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Bryan Cantrill. He's the co-founder and CTO of Oxide computer company, and he was previously the CTO of Joyent and he also co-authored the DTrace Tracing framework while he was at Sun Microsystems. [00:00:14] Jeremy: Bryan, welcome to Software Engineering radio. [00:00:17] Bryan: Uh, awesome. Thanks for having me. It's great to be here. [00:00:20] Jeremy: You're the CTO of a company that makes computers. But I think before we get into that, a lot of people who built software, now that the actual computer is abstracted away, they're using AWS or they're using some kind of cloud service. So I thought we could start by talking about, data centers. [00:00:41] Jeremy: 'cause you were. Previously working at Joyent, and I believe you got bought by Samsung and you've previously talked about how you had to figure out, how do I run things at Samsung's scale. So how, how, how was your experience with that? What, what were the challenges there? Samsung scale and migrating off the cloud [00:01:01] Bryan: Yeah, I mean, so at Joyent, and so Joyent was a cloud computing pioneer. Uh, we competed with the likes of AWS and then later GCP and Azure. Uh, and we, I mean, we were operating at a scale, right? We had a bunch of machines, a bunch of dcs, but ultimately we know we were a VC backed company and, you know, a small company by the standards of, certainly by Samsung standards. [00:01:25] Bryan: And so when, when Samsung bought the company, I mean, the reason by the way that Samsung bought Joyent is Samsung's. Cloud Bill was, uh, let's just say it was extremely large. They were spending an enormous amount of money every year on, on the public cloud. And they realized that in order to secure their fate economically, they had to be running on their own infrastructure. [00:01:51] Bryan: It did not make sense. And there's not, was not really a product that Samsung could go buy that would give them that on-prem cloud. Uh, I mean in that, in that regard, like the state of the market was really no different. And so they went looking for a company, uh, and bought, bought Joyent. And when we were on the inside of Samsung. [00:02:11] Bryan: That we learned about Samsung scale. And Samsung loves to talk about Samsung scale. And I gotta tell you, it is more than just chest thumping. Like Samsung Scale really is, I mean, just the, the sheer, the number of devices, the number of customers, just this absolute size. they really wanted to take us out to, to levels of scale, certainly that we had not seen. [00:02:31] Bryan: The reason for buying Joyent was to be able to stand up on their own infrastructure so that we were gonna go buy, we did go buy a bunch of hardware. Problems with server hardware at scale [00:02:40] Bryan: And I remember just thinking, God, I hope Dell is somehow magically better. I hope the problems that we have seen in the small, we just. You know, I just remember hoping and hope is hope. It was of course, a terrible strategy and it was a terrible strategy here too. Uh, and the we that the problems that we saw at the large were, and when you scale out the problems that you see kind of once or twice, you now see all the time and they become absolutely debilitating. [00:03:12] Bryan: And we saw a whole series of really debilitating problems. I mean, many ways, like comically debilitating, uh, in terms of, of showing just how bad the state-of-the-art. Yes. And we had, I mean, it should be said, we had great software and great software expertise, um, and we were controlling our own system software. [00:03:35] Bryan: But even controlling your own system software, your own host OS, your own control plane, which is what we had at Joyent, ultimately, you're pretty limited. You go, I mean, you got the problems that you can obviously solve, the ones that are in your own software, but the problems that are beneath you, the, the problems that are in the hardware platform, the problems that are in the componentry beneath you become the problems that are in the firmware. IO latency due to hard drive firmware [00:04:00] Bryan: Those problems become unresolvable and they are deeply, deeply frustrating. Um, and we just saw a bunch of 'em again, they were. Comical in retrospect, and I'll give you like a, a couple of concrete examples just to give, give you an idea of what kinda what you're looking at. one of the, our data centers had really pathological IO latency. [00:04:23] Bryan: we had a very, uh, database heavy workload. And this was kind of right at the period where you were still deploying on rotating media on hard drives. So this is like, so. An all flash buy did not make economic sense when we did this in, in 2016. This probably, it'd be interesting to know like when was the, the kind of the last time that that actual hard drives made sense? [00:04:50] Bryan: 'cause I feel this was close to it. So we had a, a bunch of, of a pathological IO problems, but we had one data center in which the outliers were actually quite a bit worse and there was so much going on in that system. It took us a long time to figure out like why. And because when, when you, when you're io when you're seeing worse io I mean you're naturally, you wanna understand like what's the workload doing? [00:05:14] Bryan: You're trying to take a first principles approach. What's the workload doing? So this is a very intensive database workload to support the, the object storage system that we had built called Manta. And that the, the metadata tier was stored and uh, was we were using Postgres for that. And that was just getting absolutely slaughtered. [00:05:34] Bryan: Um, and ultimately very IO bound with these kind of pathological IO latencies. Uh, and as we, you know, trying to like peel away the layers to figure out what was going on. And I finally had this thing. So it's like, okay, we are seeing at the, at the device layer, at the at, at the disc layer, we are seeing pathological outliers in this data center that we're not seeing anywhere else. [00:06:00] Bryan: And that does not make any sense. And the thought occurred to me. I'm like, well, maybe we are. Do we have like different. Different rev of firmware on our HGST drives, HGST. Now part of WD Western Digital were the drives that we had everywhere. And, um, so maybe we had a different, maybe I had a firmware bug. [00:06:20] Bryan: I, this would not be the first time in my life at all that I would have a drive firmware issue. Uh, and I went to go pull the firmware, rev, and I'm like, Toshiba makes hard drives? So we had, I mean. I had no idea that Toshiba even made hard drives, let alone that they were our, they were in our data center. [00:06:38] Bryan: I'm like, what is this? And as it turns out, and this is, you know, part of the, the challenge when you don't have an integrated system, which not to pick on them, but Dell doesn't, and what Dell would routinely put just sub make substitutes, and they make substitutes that they, you know, it's kind of like you're going to like, I don't know, Instacart or whatever, and they're out of the thing that you want. [00:07:03] Bryan: So, you know, you're, someone makes a substitute and like sometimes that's okay, but it's really not okay in a data center. And you really want to develop and validate a, an end-to-end integrated system. And in this case, like Toshiba doesn't, I mean, Toshiba does make hard drives, but they are a, or the data they did, uh, they basically were, uh, not competitive and they were not competitive in part for the reasons that we were discovering. [00:07:29] Bryan: They had really serious firmware issues. So the, these were drives that would just simply stop a, a stop acknowledging any reads from the order of 2,700 milliseconds. Long time, 2.7 seconds. Um. And that was a, it was a drive firmware issue, but it was highlighted like a much deeper issue, which was the simple lack of control that we had over our own destiny. [00:07:53] Bryan: Um, and it's an, it's, it's an example among many where Dell is making a decision. That lowers the cost of what they are providing you marginally, but it is then giving you a system that they shouldn't have any confidence in because it's not one that they've actually designed and they leave it to the customer, the end user, to make these discoveries. [00:08:18] Bryan: And these things happen up and down the stack. And for every, for whether it's, and, and not just to pick on Dell because it's, it's true for HPE, it's true for super micro, uh, it's true for your switch vendors. It's, it's true for storage vendors where the, the, the, the one that is left actually integrating these things and trying to make the the whole thing work is the end user sitting in their data center. AWS / Google are not buying off the shelf hardware but you can't use it [00:08:42] Bryan: There's not a product that they can buy that gives them elastic infrastructure, a cloud in their own DC The, the product that you buy is the public cloud. Like when you go in the public cloud, you don't worry about the stuff because that it's, it's AWS's issue or it's GCP's issue. And they are the ones that get this to ground. [00:09:02] Bryan: And they, and this was kind of, you know, the eye-opening moment. Not a surprise. Uh, they are not Dell customers. They're not HPE customers. They're not super micro customers. They have designed their own machines. And to varying degrees, depending on which one you're looking at. But they've taken the clean sheet of paper and the frustration that we had kind of at Joyent and beginning to wonder and then Samsung and kind of wondering what was next, uh, is that, that what they built was not available for purchase in the data center. [00:09:35] Bryan: You could only rent it in the public cloud. And our big belief is that public cloud computing is a really important revolution in infrastructure. Doesn't feel like a different, a deep thought, but cloud computing is a really important revolution. It shouldn't only be available to rent. You should be able to actually buy it. [00:09:53] Bryan: And there are a bunch of reasons for doing that. Uh, one in the one we we saw at Samsung is economics, which I think is still the dominant reason where it just does not make sense to rent all of your compute in perpetuity. But there are other reasons too. There's security, there's risk management, there's latency. [00:10:07] Bryan: There are a bunch of reasons why one might wanna to own one's own infrastructure. But, uh, that was very much the, the, so the, the genesis for oxide was coming out of this very painful experience and a painful experience that, because, I mean, a long answer to your question about like what was it like to be at Samsung scale? [00:10:27] Bryan: Those are the kinds of things that we, I mean, in our other data centers, we didn't have Toshiba drives. We only had the HDSC drives, but it's only when you get to this larger scale that you begin to see some of these pathologies. But these pathologies then are really debilitating in terms of those who are trying to develop a service on top of them. [00:10:45] Bryan: So it was, it was very educational in, in that regard. And you're very grateful for the experience at Samsung in terms of opening our eyes to the challenge of running at that kind of scale. [00:10:57] Jeremy: Yeah, because I, I think as software engineers, a lot of times we, we treat the hardware as a, as a given where, [00:11:08] Bryan: Yeah. [00:11:08] Bryan: Yeah. There's software in chard drives [00:11:09] Jeremy: It sounds like in, in this case, I mean, maybe the issue is not so much that. Dell or HP as a company doesn't own every single piece that they're providing you, but rather the fact that they're swapping pieces in and out without advertising them, and then when it becomes a problem, they're not necessarily willing to, to deal with the, the consequences of that. [00:11:34] Bryan: They just don't know. I mean, I think they just genuinely don't know. I mean, I think that they, it's not like they're making a deliberate decision to kind of ship garbage. It's just that they are making, I mean, I think it's exactly what you said about like, not thinking about the hardware. It's like, what's a hard drive? [00:11:47] Bryan: Like what's it, I mean, it's a hard drive. It's got the same specs as this other hard drive and Intel. You know, it's a little bit cheaper, so why not? It's like, well, like there's some reasons why not, and one of the reasons why not is like, uh, even a hard drive, whether it's rotating media or, or flash, like that's not just hardware. [00:12:05] Bryan: There's software in there. And that the software's like not the same. I mean, there are components where it's like, there's actually, whether, you know, if, if you're looking at like a resistor or a capacitor or something like this Yeah. If you've got two, two parts that are within the same tolerance. Yeah. [00:12:19] Bryan: Like sure. Maybe, although even the EEs I think would be, would be, uh, objecting that a little bit. But the, the, the more complicated you get, and certainly once you get to the, the, the, the kind of the hardware that we think of like a, a, a microprocessor, a a network interface card, a a, a hard driver, an NVME drive. [00:12:38] Bryan: Those things are super complicated and there's a whole bunch of software inside of those things, the firmware, and that's the stuff that, that you can't, I mean, you say that software engineers don't think about that. It's like you, no one can really think about that because it's proprietary that's kinda welded shut and you've got this abstraction into it. [00:12:55] Bryan: But the, the way that thing operates is very core to how the thing in aggregate will behave. And I think that you, the, the kind of, the, the fundamental difference between Oxide's approach and the approach that you get at a Dell HP Supermicro, wherever, is really thinking holistically in terms of hardware and software together in a system that, that ultimately delivers cloud computing to a user. [00:13:22] Bryan: And there's a lot of software at many, many, many, many different layers. And it's very important to think about, about that software and that hardware holistically as a single system. [00:13:34] Jeremy: And during that time at Joyent, when you experienced some of these issues, was it more of a case of you didn't have enough servers experiencing this? So if it would happen, you might say like, well, this one's not working, so maybe we'll just replace the hardware. What, what was the thought process when you were working at that smaller scale and, and how did these issues affect you? UEFI / Baseboard Management Controller [00:13:58] Bryan: Yeah, at the smaller scale, you, uh, you see fewer of them, right? You just see it's like, okay, we, you know, what you might see is like, that's weird. We kinda saw this in one machine versus seeing it in a hundred or a thousand or 10,000. Um, so you just, you just see them, uh, less frequently as a result, they are less debilitating. [00:14:16] Bryan: Um, I, I think that it's, when you go to that larger scale, those things that become, that were unusual now become routine and they become debilitating. Um, so it, it really is in many regards a function of scale. Uh, and then I think it was also, you know, it was a little bit dispiriting that kind of the substrate we were building on really had not improved. [00:14:39] Bryan: Um, and if you look at, you know, the, if you buy a computer server, buy an x86 server. There is a very low layer of firmware, the BIOS, the basic input output system, the UEFI BIOS, and this is like an abstraction layer that has, has existed since the eighties and hasn't really meaningfully improved. Um, the, the kind of the transition to UEFI happened with, I mean, I, I ironically with Itanium, um, you know, two decades ago. [00:15:08] Bryan: but beyond that, like this low layer, this lowest layer of platform enablement software is really only impeding the operability of the system. Um, you look at the baseboard management controller, which is the kind of the computer within the computer, there is a, uh, there is an element in the machine that needs to handle environmentals, that needs to handle, uh, operate the fans and so on. [00:15:31] Bryan: Uh, and that traditionally has this, the space board management controller, and that architecturally just hasn't improved in the last two decades. And, you know, that's, it's a proprietary piece of silicon. Generally from a company that no one's ever heard of called a Speed, uh, which has to be, is written all on caps, so I guess it needs to be screamed. [00:15:50] Bryan: Um, a speed has a proprietary part that has a, there is a root password infamously there, is there, the root password is encoded effectively in silicon. So, uh, which is just, and for, um, anyone who kind of goes deep into these things, like, oh my God, are you kidding me? Um, when we first started oxide, the wifi password was a fraction of the a speed root password for the bmc. [00:16:16] Bryan: It's kinda like a little, little BMC humor. Um, but those things, it was just dispiriting that, that the, the state-of-the-art was still basically personal computers running in the data center. Um, and that's part of what, what was the motivation for doing something new? [00:16:32] Jeremy: And for the people using these systems, whether it's the baseboard management controller or it's the The BIOS or UF UEFI component, what are the actual problems that people are seeing seen? Security vulnerabilities and poor practices in the BMC [00:16:51] Bryan: Oh man, I, the, you are going to have like some fraction of your listeners, maybe a big fraction where like, yeah, like what are the problems? That's a good question. And then you're gonna have the people that actually deal with these things who are, did like their heads already hit the desk being like, what are the problems? [00:17:06] Bryan: Like what are the non problems? Like what, what works? Actually, that's like a shorter answer. Um, I mean, there are so many problems and a lot of it is just like, I mean, there are problems just architecturally these things are just so, I mean, and you could, they're the problems spread to the horizon, so you can kind of start wherever you want. [00:17:24] Bryan: But I mean, as like, as a really concrete example. Okay, so the, the BMCs that, that the computer within the computer that needs to be on its own network. So you now have like not one network, you got two networks that, and that network, by the way, it, that's the network that you're gonna log into to like reset the machine when it's otherwise unresponsive. [00:17:44] Bryan: So that going into the BMC, you can are, you're able to control the entire machine. Well it's like, alright, so now I've got a second net network that I need to manage. What is running on the BMC? Well, it's running some. Ancient, ancient version of Linux it that you got. It's like, well how do I, how do I patch that? [00:18:02] Bryan: How do I like manage the vulnerabilities with that? Because if someone is able to root your BMC, they control the system. So it's like, this is not you've, and now you've gotta go deal with all of the operational hair around that. How do you upgrade that system updating the BMC? I mean, it's like you've got this like second shadow bad infrastructure that you have to go manage. [00:18:23] Bryan: Generally not open source. There's something called open BMC, um, which, um, you people use to varying degrees, but you're generally stuck with the proprietary BMC, so you're generally stuck with, with iLO from HPE or iDRAC from Dell or, or, uh, the, uh, su super micros, BMC, that H-P-B-M-C, and you are, uh, it is just excruciating pain. [00:18:49] Bryan: Um, and that this is assuming that by the way, that everything is behaving correctly. The, the problem is that these things often don't behave correctly, and then the consequence of them not behaving correctly. It's really dire because it's at that lowest layer of the system. So, I mean, I'll give you a concrete example. [00:19:07] Bryan: a customer of theirs reported to me, so I won't disclose the vendor, but let's just say that a well-known vendor had an issue with their, their temperature sensors were broken. Um, and the thing would always read basically the wrong value. So it was the BMC that had to like, invent its own ki a different kind of thermal control loop. [00:19:28] Bryan: And it would index on the, on the, the, the, the actual inrush current. It would, they would look at that at the current that's going into the CPU to adjust the fan speed. That's a great example of something like that's a, that's an interesting idea. That doesn't work. 'cause that's actually not the temperature. [00:19:45] Bryan: So like that software would crank the fans whenever you had an inrush of current and this customer had a workload that would spike the current and by it, when it would spike the current, the, the, the fans would kick up and then they would slowly degrade over time. Well, this workload was spiking the current faster than the fans would degrade, but not fast enough to actually heat up the part. [00:20:08] Bryan: And ultimately over a very long time, in a very painful investigation, it's customer determined that like my fans are cranked in my data center for no reason. We're blowing cold air. And it's like that, this is on the order of like a hundred watts, a server of, of energy that you shouldn't be spending and like that ultimately what that go comes down to this kind of broken software hardware interface at the lowest layer that has real meaningful consequence, uh, in terms of hundreds of kilowatts, um, across a data center. So this stuff has, has very, very, very real consequence and it's such a shadowy world. Part of the reason that, that your listeners that have dealt with this, that our heads will hit the desk is because it is really aggravating to deal with problems with this layer. [00:21:01] Bryan: You, you feel powerless. You don't control or really see the software that's on them. It's generally proprietary. You are relying on your vendor. Your vendor is telling you that like, boy, I don't know. You're the only customer seeing this. I mean, the number of times I have heard that for, and I, I have pledged that we're, we're not gonna say that at oxide because it's such an unaskable thing to say like, you're the only customer saying this. [00:21:25] Bryan: It's like, it feels like, are you blaming me for my problem? Feels like you're blaming me for my problem? Um, and what you begin to realize is that to a degree, these folks are speaking their own truth because the, the folks that are running at real scale at Hyperscale, those folks aren't Dell, HP super micro customers. [00:21:46] Bryan: They're actually, they've done their own thing. So it's like, yeah, Dell's not seeing that problem, um, because they're not running at the same scale. Um, but when you do run, you only have to run at modest scale before these things just become. Overwhelming in terms of the, the headwind that they present to people that wanna deploy infrastructure. The problem is felt with just a few racks [00:22:05] Jeremy: Yeah, so maybe to help people get some perspective at, at what point do you think that people start noticing or start feeling these problems? Because I imagine that if you're just have a few racks or [00:22:22] Bryan: do you have a couple racks or the, or do you wonder or just wondering because No, no, no. I would think, I think anyone who deploys any number of servers, especially now, especially if your experience is only in the cloud, you're gonna be like, what the hell is this? I mean, just again, just to get this thing working at all. [00:22:39] Bryan: It is so it, it's so hairy and so congealed, right? It's not designed. Um, and it, it, it, it's accreted it and it's so obviously accreted that you are, I mean, nobody who is setting up a rack of servers is gonna think to themselves like, yes, this is the right way to go do it. This all makes sense because it's, it's just not, it, I, it feels like the kit, I mean, kit car's almost too generous because it implies that there's like a set of plans to work to in the end. [00:23:08] Bryan: Uh, I mean, it, it, it's a bag of bolts. It's a bunch of parts that you're putting together. And so even at the smallest scales, that stuff is painful. Just architecturally, it's painful at the small scale then, but at least you can get it working. I think the stuff that then becomes debilitating at larger scale are the things that are, are worse than just like, I can't, like this thing is a mess to get working. [00:23:31] Bryan: It's like the, the, the fan issue that, um, where you are now seeing this over, you know, hundreds of machines or thousands of machines. Um, so I, it is painful at more or less all levels of scale. There's, there is no level at which the, the, the pc, which is really what this is, this is a, the, the personal computer architecture from the 1980s and there is really no level of scale where that's the right unit. Running elastic infrastructure is the hardware but also, hypervisor, distributed database, api, etc [00:23:57] Bryan: I mean, where that's the right thing to go deploy, especially if what you are trying to run. Is elastic infrastructure, a cloud. Because the other thing is like we, we've kinda been talking a lot about that hardware layer. Like hardware is, is just the start. Like you actually gotta go put software on that and actually run that as elastic infrastructure. [00:24:16] Bryan: So you need a hypervisor. Yes. But you need a lot more than that. You, you need to actually, you, you need a distributed database, you need web endpoints. You need, you need a CLI, you need all the stuff that you need to actually go run an actual service of compute or networking or storage. I mean, and for, for compute, even for compute, there's a ton of work to be done. [00:24:39] Bryan: And compute is by far, I would say the simplest of the, of the three. When you look at like networks, network services, storage services, there's a whole bunch of stuff that you need to go build in terms of distributed systems to actually offer that as a cloud. So it, I mean, it is painful at more or less every LE level if you are trying to deploy cloud computing on. What's a control plane? [00:25:00] Jeremy: And for someone who doesn't have experience building or working with this type of infrastructure, when you talk about a control plane, what, what does that do in the context of this system? [00:25:16] Bryan: So control plane is the thing that is, that is everything between your API request and that infrastructure actually being acted upon. So you go say, Hey, I, I want a provision, a vm. Okay, great. We've got a whole bunch of things we're gonna provision with that. We're gonna provision a vm, we're gonna get some storage that's gonna go along with that, that's got a network storage service that's gonna come out of, uh, we've got a virtual network that we're gonna either create or attach to. [00:25:39] Bryan: We've got a, a whole bunch of things we need to go do for that. For all of these things, there are metadata components that need, we need to keep track of this thing that, beyond the actual infrastructure that we create. And then we need to go actually, like act on the actual compute elements, the hostos, what have you, the switches, what have you, and actually go. [00:25:56] Bryan: Create these underlying things and then connect them. And there's of course, the challenge of just getting that working is a big challenge. Um, but getting that working robustly, getting that working is, you know, when you go to provision of vm, um, the, all the, the, the steps that need to happen and what happens if one of those steps fails along the way? [00:26:17] Bryan: What happens if, you know, one thing we're very mindful of is these kind of, you get these long tails of like, why, you know, generally our VM provisioning happened within this time, but we get these long tails where it takes much longer. What's going on? What, where in this process are we, are we actually spending time? [00:26:33] Bryan: Uh, and there's a whole lot of complexity that you need to go deal with that. There's a lot of complexity that you need to go deal with this effectively, this workflow that's gonna go create these things and manage them. Um, we use a, a pattern that we call, that are called sagas, actually is a, is a database pattern from the eighties. [00:26:51] Bryan: Uh, Katie McCaffrey is a, is a database reCrcher who, who, uh, I, I think, uh, reintroduce the idea of, of sagas, um, in the last kind of decade. Um, and this is something that we picked up, um, and I've done a lot of really interesting things with, um, to allow for, to this kind of, these workflows to be, to be managed and done so robustly in a way that you can restart them and so on. [00:27:16] Bryan: Uh, and then you guys, you get this whole distributed system that can do all this. That whole distributed system, that itself needs to be reliable and available. So if you, you know, you need to be able to, what happens if you, if you pull a sled or if a sled fails, how does the system deal with that? [00:27:33] Bryan: How does the system deal with getting an another sled added to the system? Like how do you actually grow this distributed system? And then how do you update it? How do you actually go from one version to the next? And all of that has to happen across an air gap where this is gonna run as part of the computer. [00:27:49] Bryan: So there are, it, it is fractally complicated. There, there is a lot of complexity here in, in software, in the software system and all of that. We kind of, we call the control plane. Um, and it, this is the what exists at AWS at GCP, at Azure. When you are hitting an endpoint that's provisioning an EC2 instance for you. [00:28:10] Bryan: There is an AWS control plane that is, is doing all of this and has, uh, some of these similar aspects and certainly some of these similar challenges. Are vSphere / Proxmox / Hyper-V in the same category? [00:28:20] Jeremy: And for people who have run their own servers with something like say VMware or Hyper V or Proxmox, are those in the same category? [00:28:32] Bryan: Yeah, I mean a little bit. I mean, it kind of like vSphere Yes. Via VMware. No. So it's like you, uh, VMware ESX is, is kind of a key building block upon which you can build something that is a more meaningful distributed system. When it's just like a machine that you're provisioning VMs on, it's like, okay, well that's actually, you as the human might be the control plane. [00:28:52] Bryan: Like, that's, that, that's, that's a much easier problem. Um, but when you've got, you know, tens, hundreds, thousands of machines, you need to do it robustly. You need something to coordinate that activity and you know, you need to pick which sled you land on. You need to be able to move these things. You need to be able to update that whole system. [00:29:06] Bryan: That's when you're getting into a control plane. So, you know, some of these things have kind of edged into a control plane, certainly VMware. Um, now Broadcom, um, has delivered something that's kind of cloudish. Um, I think that for folks that are truly born on the cloud, it, it still feels somewhat, uh, like you're going backwards in time when you, when you look at these kind of on-prem offerings. [00:29:29] Bryan: Um, but, but it, it, it's got these aspects to it for sure. Um, and I think that we're, um, some of these other things when you're just looking at KVM or just looks looking at Proxmox you kind of need to, to connect it to other broader things to turn it into something that really looks like manageable infrastructure. [00:29:47] Bryan: And then many of those projects are really, they're either proprietary projects, uh, proprietary products like vSphere, um, or you are really dealing with open source projects that are. Not necessarily aimed at the same level of scale. Um, you know, you look at a, again, Proxmox or, uh, um, you'll get an OpenStack. [00:30:05] Bryan: Um, and you know, OpenStack is just a lot of things, right? I mean, OpenStack has got so many, the OpenStack was kind of a, a free for all, for every infrastructure vendor. Um, and I, you know, there was a time people were like, don't you, aren't you worried about all these companies together that, you know, are coming together for OpenStack? [00:30:24] Bryan: I'm like, haven't you ever worked for like a company? Like, companies don't get along. By the way, it's like having multiple companies work together on a thing that's bad news, not good news. And I think, you know, one of the things that OpenStack has definitely struggled with, kind of with what, actually the, the, there's so many different kind of vendor elements in there that it's, it's very much not a product, it's a project that you're trying to run. [00:30:47] Bryan: But that's, but that very much is in, I mean, that's, that's similar certainly in spirit. [00:30:53] Jeremy: And so I think this is kind of like you're alluding to earlier, the piece that allows you to allocate, compute, storage, manage networking, gives you that experience of I can go to a web console or I can use an API and I can spin up machines, get them all connected. At the end of the day, the control plane. Is allowing you to do that in hopefully a user-friendly way. [00:31:21] Bryan: That's right. Yep. And in the, I mean, in order to do that in a modern way, it's not just like a user-friendly way. You really need to have a CLI and a web UI and an API. Those all need to be drawn from the same kind of single ground truth. Like you don't wanna have any of those be an afterthought for the other. [00:31:39] Bryan: You wanna have the same way of generating all of those different endpoints and, and entries into the system. Building a control plane now has better tools (Rust, CockroachDB) [00:31:46] Jeremy: And if you take your time at Joyent as an example. What kind of tools existed for that versus how much did you have to build in-house for as far as the hypervisor and managing the compute and all that? [00:32:02] Bryan: Yeah, so we built more or less everything in house. I mean, what you have is, um, and I think, you know, over time we've gotten slightly better tools. Um, I think, and, and maybe it's a little bit easier to talk about the, kind of the tools we started at Oxide because we kind of started with a, with a clean sheet of paper at oxide. [00:32:16] Bryan: We wanted to, knew we wanted to go build a control plane, but we were able to kind of go revisit some of the components. So actually, and maybe I'll, I'll talk about some of those changes. So when we, at, For example, at Joyent, when we were building a cloud at Joyent, there wasn't really a good distributed database. [00:32:34] Bryan: Um, so we were using Postgres as our database for metadata and there were a lot of challenges. And Postgres is not a distributed database. It's running. With a primary secondary architecture, and there's a bunch of issues there, many of which we discovered the hard way. Um, when we were coming to oxide, you have much better options to pick from in terms of distributed databases. [00:32:57] Bryan: You know, we, there was a period that now seems maybe potentially brief in hindsight, but of a really high quality open source distributed databases. So there were really some good ones to, to pick from. Um, we, we built on CockroachDB on CRDB. Um, so that was a really important component. That we had at oxide that we didn't have at Joyent. [00:33:19] Bryan: Um, so we were, I wouldn't say we were rolling our own distributed database, we were just using Postgres and uh, and, and dealing with an enormous amount of pain there in terms of the surround. Um, on top of that, and, and, you know, a, a control plane is much more than a database, obviously. Uh, and you've gotta deal with, uh, there's a whole bunch of software that you need to go, right. [00:33:40] Bryan: Um, to be able to, to transform these kind of API requests into something that is reliable infrastructure, right? And there, there's a lot to that. Uh, especially when networking gets in the mix, when storage gets in the mix, uh, there are a whole bunch of like complicated steps that need to be done, um, at Joyent. [00:33:59] Bryan: Um, we, in part because of the history of the company and like, look. This, this just is not gonna sound good, but it just is what it is and I'm just gonna own it. We did it all in Node, um, at Joyent, which I, I, I know it sounds really right now, just sounds like, well, you, you built it with Tinker Toys. You Okay. [00:34:18] Bryan: Uh, did, did you think it was, you built the skyscraper with Tinker Toys? Uh, it's like, well, okay. We actually, we had greater aspirations for the Tinker Toys once upon a time, and it was better than, you know, than Twisted Python and Event Machine from Ruby, and we weren't gonna do it in Java. All right. [00:34:32] Bryan: So, but let's just say that that experiment, uh, that experiment did ultimately end in a predictable fashion. Um, and, uh, we, we decided that maybe Node was not gonna be the best decision long term. Um, Joyent was the company behind node js. Uh, back in the day, Ryan Dahl worked for Joyent. Uh, and then, uh, then we, we, we. [00:34:53] Bryan: Uh, landed that in a foundation in about, uh, what, 2015, something like that. Um, and began to consider our world beyond, uh, beyond Node. Rust at Oxide [00:35:04] Bryan: A big tool that we had in the arsenal when we started Oxide is Rust. Um, and so indeed the name of the company is, is a tip of the hat to the language that we were pretty sure we were gonna be building a lot of stuff in. [00:35:16] Bryan: Namely Rust. And, uh, rust is, uh, has been huge for us, a very important revolution in programming languages. you know, there, there, there have been different people kind of coming in at different times and I kinda came to Rust in what I, I think is like this big kind of second expansion of rust in 2018 when a lot of technologists were think, uh, sick of Node and also sick of Go. [00:35:43] Bryan: And, uh, also sick of C++. And wondering is there gonna be something that gives me the, the, the performance, of that I get outta C. The, the robustness that I can get out of a C program but is is often difficult to achieve. but can I get that with kind of some, some of the velocity of development, although I hate that term, some of the speed of development that you get out of a more interpreted language. [00:36:08] Bryan: Um, and then by the way, can I actually have types, I think types would be a good idea? Uh, and rust obviously hits the sweet spot of all of that. Um, it has been absolutely huge for us. I mean, we knew when we started the company again, oxide, uh, we were gonna be using rust in, in quite a, quite a. Few places, but we weren't doing it by fiat. [00:36:27] Bryan: Um, we wanted to actually make sure we're making the right decision, um, at, at every different, at every layer. Uh, I think what has been surprising is the sheer number of layers at which we use rust in terms of, we've done our own embedded firmware in rust. We've done, um, in, in the host operating system, which is still largely in C, but very big components are in rust. [00:36:47] Bryan: The hypervisor Propolis is all in rust. Uh, and then of course the control plane, that distributed system on that is all in rust. So that was a very important thing that we very much did not need to build ourselves. We were able to really leverage, uh, a terrific community. Um. We were able to use, uh, and we've done this at Joyent as well, but at Oxide, we've used Illumos as a hostos component, which, uh, our variant is called Helios. [00:37:11] Bryan: Um, we've used, uh, bhyve um, as a, as as that kind of internal hypervisor component. we've made use of a bunch of different open source components to build this thing, um, which has been really, really important for us. Uh, and open source components that didn't exist even like five years prior. [00:37:28] Bryan: That's part of why we felt that 2019 was the right time to start the company. And so we started Oxide. The problems building a control plane in Node [00:37:34] Jeremy: You had mentioned that at Joyent, you had tried to build this in, in Node. What were the, what were the, the issues or the, the challenges that you had doing that? [00:37:46] Bryan: Oh boy. Yeah. again, we, I kind of had higher hopes in 2010, I would say. When we, we set on this, um, the, the, the problem that we had just writ large, um. JavaScript is really designed to allow as many people on earth to write a program as possible, which is good. I mean, I, I, that's a, that's a laudable goal. [00:38:09] Bryan: That is the goal ultimately of such as it is of JavaScript. It's actually hard to know what the goal of JavaScript is, unfortunately, because Brendan Ike never actually wrote a book. so that there is not a canonical, you've got kind of Doug Crockford and other people who've written things on JavaScript, but it's hard to know kind of what the original intent of JavaScript is. [00:38:27] Bryan: The name doesn't even express original intent, right? It was called Live Script, and it was kind of renamed to JavaScript during the Java Frenzy of the late nineties. A name that makes no sense. There is no Java in JavaScript. that is kind of, I think, revealing to kind of the, uh, the unprincipled mess that is JavaScript. [00:38:47] Bryan: It, it, it's very pragmatic at some level, um, and allows anyone to, it makes it very easy to write software. The problem is it's much more difficult to write really rigorous software. So, uh, and this is what I should differentiate JavaScript from TypeScript. This is really what TypeScript is trying to solve. [00:39:07] Bryan: TypeScript is like. How can, I think TypeScript is a, is a great step forward because TypeScript is like, how can we bring some rigor to this? Like, yes, it's great that it's easy to write JavaScript, but that's not, we, we don't wanna do that for Absolutely. I mean that, that's not the only problem we solve. [00:39:23] Bryan: We actually wanna be able to write rigorous software and it's actually okay if it's a little harder to write rigorous software that's actually okay if it gets leads to, to more rigorous artifacts. Um, but in JavaScript, I mean, just a concrete example. You know, there's nothing to prevent you from referencing a property that doesn't actually exist in JavaScript. [00:39:43] Bryan: So if you fat finger a property name, you are relying on something to tell you. By the way, I think you've misspelled this because there is no type definition for this thing. And I don't know that you've got one that's spelled correctly, one that's spelled incorrectly, that's often undefined. And then the, when you actually go, you say you've got this typo that is lurking in your what you want to be rigorous software. [00:40:07] Bryan: And if you don't execute that code, like you won't know that's there. And then you do execute that code. And now you've got a, you've got an undefined object. And now that's either gonna be an exception or it can, again, depends on how that's handled. It can be really difficult to determine the origin of that, of, of that error, of that programming. [00:40:26] Bryan: And that is a programmer error. And one of the big challenges that we had with Node is that programmer errors and operational errors, like, you know, I'm out of disk space as an operational error. Those get conflated and it becomes really hard. And in fact, I think the, the language wanted to make it easier to just kind of, uh, drive on in the event of all errors. [00:40:53] Bryan: And it's like, actually not what you wanna do if you're trying to build a reliable, robust system. So we had. No end of issues. [00:41:01] Bryan: We've got a lot of experience developing rigorous systems, um, again coming out of operating systems development and so on. And we want, we brought some of that rigor, if strangely, to JavaScript. So one of the things that we did is we brought a lot of postmortem, diagnos ability and observability to node. [00:41:18] Bryan: And so if, if one of our node processes. Died in production, we would actually get a core dump from that process, a core dump that we could actually meaningfully process. So we did a bunch of kind of wild stuff. I mean, actually wild stuff where we could actually make sense of the JavaScript objects in a binary core dump. JavaScript values ease of getting started over robustness [00:41:41] Bryan: Um, and things that we thought were really important, and this is the, the rest of the world just looks at this being like, what the hell is this? I mean, it's so out of step with it. The problem is that we were trying to bridge two disconnected cultures of one developing really. Rigorous software and really designing it for production, diagnosability and the other, really designing it to software to run in the browser and for anyone to be able to like, you know, kind of liven up a webpage, right? [00:42:10] Bryan: Is kinda the origin of, of live script and then JavaScript. And we were kind of the only ones sitting at the intersection of that. And you begin when you are the only ones sitting at that kind of intersection. You just are, you're, you're kind of fighting a community all the time. And we just realized that we are, there were so many things that the community wanted to do that we felt are like, no, no, this is gonna make software less diagnosable. It's gonna make it less robust. The NodeJS split and why people left [00:42:36] Bryan: And then you realize like, I'm, we're the only voice in the room because we have got, we have got desires for this language that it doesn't have for itself. And this is when you realize you're in a bad relationship with software. It's time to actually move on. And in fact, actually several years after, we'd already kind of broken up with node. [00:42:55] Bryan: Um, and it was like, it was a bit of an acrimonious breakup. there was a, uh, famous slash infamous fork of node called IoJS Um, and this was viewed because people, the community, thought that Joyent was being what was not being an appropriate steward of node js and was, uh, not allowing more things to come into to, to node. [00:43:19] Bryan: And of course, the reason that we of course, felt that we were being a careful steward and we were actively resisting those things that would cut against its fitness for a production system. But it's some way the community saw it and they, and forked, um, and, and I think the, we knew before the fork that's like, this is not working and we need to get this thing out of our hands. Platform is a reflection of values node summit talk [00:43:43] Bryan: And we're are the wrong hands for this? This needs to be in a foundation. Uh, and so we kind of gone through that breakup, uh, and maybe it was two years after that. That, uh, friend of mine who was um, was running the, uh, the node summit was actually, it's unfortunately now passed away. Charles er, um, but Charles' venture capitalist great guy, and Charles was running Node Summit and came to me in 2017. [00:44:07] Bryan: He is like, I really want you to keynote Node Summit. And I'm like, Charles, I'm not gonna do that. I've got nothing nice to say. Like, this is the, the, you don't want, I'm the last person you wanna keynote. He's like, oh, if you have nothing nice to say, you should definitely keynote. You're like, oh God, okay, here we go. [00:44:22] Bryan: He's like, no, I really want you to talk about, like, you should talk about the Joyent breakup with NodeJS. I'm like, oh man. [00:44:29] Bryan: And that led to a talk that I'm really happy that I gave, 'cause it was a very important talk for me personally. Uh, called Platform is a reflection of values and really looking at the values that we had for Node and the values that Node had for itself. And they didn't line up. [00:44:49] Bryan: And the problem is that the values that Node had for itself and the values that we had for Node are all kind of positives, right? Like there's nobody in the node community who's like, I don't want rigor, I hate rigor. It's just that if they had the choose between rigor and making the language approachable. [00:45:09] Bryan: They would choose approachability every single time. They would never choose rigor. And, you know, that was a, that was a big eye-opener. I do, I would say, if you watch this talk. [00:45:20] Bryan: because I knew that there's, like, the audience was gonna be filled with, with people who, had been a part of the fork in 2014, I think was the, the, the, the fork, the IOJS fork. And I knew that there, there were, there were some, you know, some people that were, um, had been there for the fork and. [00:45:41] Bryan: I said a little bit of a trap for the audience. But the, and the trap, I said, you know what, I, I kind of talked about the values that we had and the aspirations we had for Node, the aspirations that Node had for itself and how they were different. [00:45:53] Bryan: And, you know, and I'm like, look in, in, in hindsight, like a fracture was inevitable. And in 2014 there was finally a fracture. And do people know what happened in 2014? And if you, if you, you could listen to that talk, everyone almost says in unison, like IOJS. I'm like, oh right. IOJS. Right. That's actually not what I was thinking of. [00:46:19] Bryan: And I go to the next slide and is a tweet from a guy named TJ Holloway, Chuck, who was the most prolific contributor to Node. And it was his tweet also in 2014 before the fork, before the IOJS fork explaining that he was leaving Node and that he was going to go. And you, if you turn the volume all the way up, you can hear the audience gasp. [00:46:41] Bryan: And it's just delicious because the community had never really come, had never really confronted why TJ left. Um, there. And I went through a couple folks, Felix, bunch of other folks, early Node folks. That were there in 2010, were leaving in 2014, and they were going to go primarily, and they were going to go because they were sick of the same things that we were sick of. [00:47:09] Bryan: They, they, they had hit the same things that we had hit and they were frustrated. I I really do believe this, that platforms do reflect their own values. And when you are making a software decision, you are selecting value. [00:47:26] Bryan: You should select values that align with the values that you have for that software. That is, those are, that's way more important than other things that people look at. I think people look at, for example, quote unquote community size way too frequently, community size is like. Eh, maybe it can be fine. [00:47:44] Bryan: I've been in very large communities, node. I've been in super small open source communities like AUMs and RAs, a bunch of others. there are strengths and weaknesses to both approaches just as like there's a strength to being in a big city versus a small town. Me personally, I'll take the small community more or less every time because the small community is almost always self-selecting based on values and just for the same reason that I like working at small companies or small teams. [00:48:11] Bryan: There's a lot of value to be had in a small community. It's not to say that large communities are valueless, but again, long answer to your question of kind of where did things go south with Joyent and node. They went south because the, the values that we had and the values the community had didn't line up and that was a very educational experience, as you might imagine. [00:48:33] Jeremy: Yeah. And, and given that you mentioned how, because of those values, some people moved from Node to go, and in the end for much of what oxide is building. You ended up using rust. What, what would you say are the, the values of go and and rust, and how did you end up choosing Rust given that. Go's decisions regarding generics, versioning, compilation speed priority [00:48:56] Bryan: Yeah, I mean, well, so the value for, yeah. And so go, I mean, I understand why people move from Node to Go, go to me was kind of a lateral move. Um, there were a bunch of things that I, uh, go was still garbage collected, um, which I didn't like. Um, go also is very strange in terms of there are these kind of like. [00:49:17] Bryan: These autocratic kind of decisions that are very bizarre. Um, there, I mean, generics is kind of a famous one, right? Where go kind of as a point of principle didn't have generics, even though go itself actually the innards of go did have generics. It's just that you a go user weren't allowed to have them. [00:49:35] Bryan: And you know, it's kind of, there was, there was an old cartoon years and years ago about like when a, when a technologist is telling you that something is technically impossible, that actually means I don't feel like it. Uh, and there was a certain degree of like, generics are technically impossible and go, it's like, Hey, actually there are. [00:49:51] Bryan: And so there was, and I just think that the arguments against generics were kind of disingenuous. Um, and indeed, like they ended up adopting generics and then there's like some super weird stuff around like, they're very anti-assertion, which is like, what, how are you? Why are you, how is someone against assertions, it doesn't even make any sense, but it's like, oh, nope. [00:50:10] Bryan: Okay. There's a whole scree on it. Nope, we're against assertions and the, you know, against versioning. There was another thing like, you know, the Rob Pike has kind of famously been like, you should always just run on the way to commit. And you're like, does that, is that, does that make sense? I mean this, we actually built it. [00:50:26] Bryan: And so there are a bunch of things like that. You're just like, okay, this is just exhausting and. I mean, there's some things about Go that are great and, uh, plenty of other things that I just, I'm not a fan of. Um, I think that the, in the end, like Go cares a lot about like compile time. It's super important for Go Right? [00:50:44] Bryan: Is very quick, compile time. I'm like, okay. But that's like compile time is not like, it's not unimportant, it's doesn't have zero importance. But I've got other things that are like lots more important than that. Um, what I really care about is I want a high performing artifact. I wanted garbage collection outta my life. Don't think garbage collection has good trade offs [00:51:00] Bryan: I, I gotta tell you, I, I like garbage collection to me is an embodiment of this like, larger problem of where do you put cognitive load in the software development process. And what garbage collection is saying to me it is right for plenty of other people and the software that they wanna develop. [00:51:21] Bryan: But for me and the software that I wanna develop, infrastructure software, I don't want garbage collection because I can solve the memory allocation problem. I know when I'm like, done with something or not. I mean, it's like I, whether that's in, in C with, I mean it's actually like, it's really not that hard to not leak memory in, in a C base system. [00:51:44] Bryan: And you can. give yourself a lot of tooling that allows you to diagnose where memory leaks are coming from. So it's like that is a solvable problem. There are other challenges with that, but like, when you are developing a really sophisticated system that has garbage collection is using garbage collection. [00:51:59] Bryan: You spend as much time trying to dork with the garbage collector to convince it to collect the thing that you know is garbage. You are like, I've got this thing. I know it's garbage. Now I need to use these like tips and tricks to get the garbage collector. I mean, it's like, it feels like every Java performance issue goes to like minus xx call and use the other garbage collector, whatever one you're using, use a different one and using a different, a different approach. [00:52:23] Bryan: It's like, so you're, you're in this, to me, it's like you're in the worst of all worlds where. the reason that garbage collection is helpful is because the programmer doesn't have to think at all about this problem. But now you're actually dealing with these long pauses in production. [00:52:38] Bryan: You're dealing with all these other issues where actually you need to think a lot about it. And it's kind of, it, it it's witchcraft. It, it, it's this black box that you can't see into. So it's like, what problem have we solved exactly? And I mean, so the fact that go had garbage collection, it's like, eh, no, I, I do not want, like, and then you get all the other like weird fatwahs and you know, everything else. [00:52:57] Bryan: I'm like, no, thank you. Go is a no thank you for me, I, I get it why people like it or use it, but it's, it's just, that was not gonna be it. Choosing Rust [00:53:04] Bryan: I'm like, I want C. but I, there are things I didn't like about C too. I was looking for something that was gonna give me the deterministic kind of artifact that I got outta C. But I wanted library support and C is tough because there's, it's all convention. you know, there's just a bunch of other things that are just thorny. And I remember thinking vividly in 2018, I'm like, well, it's rust or bust. Ownership model, algebraic types, error handling [00:53:28] Bryan: I'm gonna go into rust. And, uh, I hope I like it because if it's not this, it's gonna like, I'm gonna go back to C I'm like literally trying to figure out what the language is for the back half of my career. Um, and when I, you know, did what a lot of people were doing at that time and people have been doing since of, you know, really getting into rust and really learning it, appreciating the difference in the, the model for sure, the ownership model people talk about. [00:53:54] Bryan: That's also obviously very important. It was the error handling that blew me away. And the idea of like algebraic types, I never really had algebraic types. Um, and the ability to, to have. And for error handling is one of these really, uh, you, you really appreciate these things where it's like, how do you deal with a, with a function that can either succeed and return something or it can fail, and the way c deals with that is bad with these kind of sentinels for errors. [00:54:27] Bryan: And, you know, does negative one mean success? Does negative one mean failure? Does zero mean failure? Some C functions, zero means failure. Traditionally in Unix, zero means success. And like, what if you wanna return a file descriptor, you know, it's like, oh. And then it's like, okay, then it'll be like zero through positive N will be a valid result. [00:54:44] Bryan: Negative numbers will be, and like, was it negative one and I said airo, or is it a negative number that did not, I mean, it's like, and that's all convention, right? People do all, all those different things and it's all convention and it's easy to get wrong, easy to have bugs, can't be statically checked and so on. Um, and then what Go says is like, well, you're gonna have like two return values and then you're gonna have to like, just like constantly check all of these all the time. Um, which is also kind of gross. Um, JavaScript is like, Hey, let's toss an exception. If, if we don't like something, if we see an error, we'll, we'll throw an exception. [00:55:15] Bryan: There are a bunch of reasons I don't like that. Um, and you look, you'll get what Rust does, where it's like, no, no, no. We're gonna have these algebra types, which is to say this thing can be a this thing or that thing, but it, but it has to be one of these. And by the way, you don't get to process this thing until you conditionally match on one of these things. [00:55:35] Bryan: You're gonna have to have a, a pattern match on this thing to determine if it's a this or a that, and if it in, in the result type that you, the result is a generic where it's like, it's gonna be either the thing that you wanna return. It's gonna be an okay that contains the thing you wanna return, or it's gonna be an error that contains your error and it forces your code to deal with that. [00:55:57] Bryan: And what that does is it shifts the cognitive load from the person that is operating this thing in production to the, the actual developer that is in development. And I think that that, that to me is like, I, I love that shift. Um, and that shift to me is really important. Um, and that's what I was missing, that that's what Rust gives you. [00:56:23] Bryan: Rust forces you to think about your code as you write it, but as a result, you have an artifact that is much more supportable, much more sustainable, and much faster. Prefer to frontload cognitive load during development instead of at runtime [00:56:34] Jeremy: Yeah, it sounds like you would rather take the time during the development to think about these issues because whether it's garbage collection or it's error handling at runtime when you're trying to solve a problem, then it's much more difficult than having dealt with it to start with. [00:56:57] Bryan: Yeah, absolutely. I, and I just think that like, why also, like if it's software, if it's, again, if it's infrastructure software, I mean the kinda the question that you, you should have when you're writing software is how long is this software gonna live? How many people are gonna use this software? Uh, and if you are writing an operating system, the answer for this thing that you're gonna write, it's gonna live for a long time. [00:57:18] Bryan: Like, if we just look at plenty of aspects of the system that have been around for a, for decades, it's gonna live for a long time and many, many, many people are gonna use it. Why would we not expect people writing that software to have more cognitive load when they're writing it to give us something that's gonna be a better artifact? [00:57:38] Bryan: Now conversely, you're like, Hey, I kind of don't care about this. And like, I don't know, I'm just like, I wanna see if this whole thing works. I've got, I like, I'm just stringing this together. I don't like, no, the software like will be lucky if it survives until tonight, but then like, who cares? Yeah. Yeah. [00:57:52] Bryan: Gar garbage clock. You know, if you're prototyping something, whatever. And this is why you really do get like, you know, different choices, different technology choices, depending on the way that you wanna solve the problem at hand. And for the software that I wanna write, I do like that cognitive load that is upfront. With LLMs maybe you can get the benefit of the robust artifact with less cognitive load [00:58:10] Bryan: Um, and although I think, I think the thing that is really wild that is the twist that I don't think anyone really saw coming is that in a, in an LLM age. That like the cognitive load upfront almost needs an asterisk on it because so much of that can be assisted by an LLM. And now, I mean, I would like to believe, and maybe this is me being optimistic, that the the, in the LLM age, we will see, I mean, rust is a great fit for the LLMH because the LLM itself can get a lot of feedback about whether the software that's written is correct or not. [00:58:44] Bryan: Much more so than you can for other environments. [00:58:48] Jeremy: Yeah, that is a interesting point in that I think when people first started trying out the LLMs to code, it was really good at these maybe looser languages like Python or JavaScript, and initially wasn't so good at something like Rust. But it sounds like as that improves, if. It can write it then because of the rigor or the memory management or the error handling that the language is forcing you to do, it might actually end up being a better choice for people using LLMs. [00:59:27] Bryan: absolutely. I, it, it gives you more certainty in the artifact that you've delivered. I mean, you know a lot about a Rust program that compiles correctly. I mean, th there are certain classes of errors that you don't have, um, that you actually don't know on a C program or a GO program or a, a JavaScript program. [00:59:46] Bryan: I think that's gonna be really important. I think we are on the cusp. Maybe we've already seen it, this kind of great bifurcation in the software that we writ

OpenZFS monitoring, hellosystems 0.8, GhostBSD and XLibre, Bhyve Exporters and 30 year old LibC issues. NOTES This episode of BSDNow is brought to you by Tarsnap and the BSDNow Patreon Headlines OpenZFS Monitoring and Observability: What to Track and Why It Matters helloSystem 0.8 Released FreeBSD Based OS Inspired by macOS. https://itsfoss.gitlab.io/post/hellosystem-08-released-freebsd-based-os-inspired-by-macos/ News Roundup [Default GhostBSD to XLibre](https://github.com/ghostbsd/ghostbsd-build/pull/259] Addressing XLibre Change and GhostBSD Future Bhyve Prometheus Exporter for Sylve on FreeBSD. Linux GNU C Library Fixes Security Issue Present Since 1996 Beastie Bits NetBSD 11.0 RC1 available! The Book of PF, 4th Edition is now available December 2025 Finance Report LLDB improvements on FreeBSD Any desire for OnmiOS/Illumos Support : Now's your chance to convince me 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 Join us and other BSD Fans in our BSD Now Telegram channel

Michael Bisping and Paul Felder discuss an incredible main card at UFC Houston including a dominant KO win for Sean Strickland, a star making KO from Uros Medic, Melquizael Costa being the first to KO Dan Ige and more plus a preview of UFC Mexico City next weekend, a big fight announced between Sean Brady and Joaquin Buckley, Paddy Pimblett calling out BSD for a fight and more plus interviews with Uros Medic about his win, who he wants next and why his style is so fan friendly then Jacobe Smith joins to discuss his huge win, his close relationship with Daniel Cormier, his attempted quick turnaround and more and so much more! Support Our Sponsors: UNDERDOG: Download the app today and use promo code BISPING to score SEVENTY-FIVE DOLLARS in Bonus Entries when you play your first FIVE dollars FUM: Head to ⁠⁠⁠⁠⁠https://www.tryfum.com/BELIEVE⁠⁠⁠⁠⁠ and use promo code BELIEVE to get your free gift with purchase, and start The Good Habit today! SHOPIFY: Sign up for your one-dollar-per-month trial today at https://www.shopify.com/believe Follow the show on social media: Twitter: https://twitter.com/BYMPod Subscribe on YouTube: https://bit.ly/3drq6ps Follow the hosts on social: Michael Bisping Twitter https://twitter.com/bisping Michael Bisping Instagram https://www.instagram.com/mikebisping/ Michael Bisping YouTube https://www.youtube.com/channel/UCDrG2_1TcVkXKXXsD6Kjwig Paul Felder Twitter: https://twitter.com/felderpaul Paul Felder Instagram: https://www.instagram.com/felderpaul/ Follow The Guests On Social: Uros Medic Twitter: https://x.com/urketaraketa Uros Medic Instagram: https://www.instagram.com/medicu/ Jacobe Smith Twitter: https://x.com/smith_cobe Jacobe Smith Instagram: https://www.instagram.com/cobe1423/ Follow the team on social: Brian MacKay Instagram: https://www.instagram.com/bmackayisright Brian MacKay Twitter: https://twitter.com/bmackayisright Mike Harrington Twitter: https://twitter.com/TheMHarrington Mike Harrington Instagram https://www.instagram.com/themharrington Mike Harrington YouTube: https://www.youtube.com/@themharrington Learn more about your ad choices. Visit megaphone.fm/adchoices

This show has been flagged as Explicit by the host. Note: The following code `:(){ :|:& };:` was replaced with Fork Bomb in the title. Ever wanted to hear a middle age man waffle on incoherently for half an hour about how he went from BMX bum to BSD botherer (1) ???? Well then, you've come to the right place :-) Behold my banal FLOSS adventure of 15 very odd years in all it's hax & glory! You're got to give it away to keep it ;-) Weirdly there is a wonderful Scottish BMX brand called BSD... If you ever want some cool BSD stickers or T-Shirts they make some funky stuff... P.S. Apologies for the endless extravagant sharp intakes of breath... to be fair it's a better filler than "like" or "do you know what I mean"... :-/ Provide feedback on this episode.

GeoIP PF FreeBSD, ZFs in production, linuxulator feels like magic, XFCE is great, the scariest boot code, and more... NOTES This episode of BSDNow is brought to you by Tarsnap and the BSDNow Patreon Headlines GeoIP-Aware Firewalling with PF on FreeBSD ZFS in Production: Real-World Deployment Patterns and Pitfalls News Roundup Xfce is great Linuxulator on FreeBSD Feels Like Magic The scariest boot loader code OpenBSD-current now runs as guest under Apple Hypervisor 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 Matt - Audio Levels Interviews can be troublesome because there's only so much we can do with multiple guests with multiple feeds, and mulitple audio conditions. We can try to normalize but sometimes it's just not easy to do without editing taking an entire day.. Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv Join us and other BSD Fans in our BSD Now Telegram channel

AT&T's $2000 shell, ZFS Scrubs and Data Integrity, FFS Backups, FreeBSD Home Nas, and more. NOTES This episode of BSDNow is brought to you by Tarsnap and the BSDNow Patreon Headlines One too many words on AT&T's $2,000 Korn shell and other Usenet topics Understanding ZFS Scrubs and Data Integrity News Roundup FFS Backup FreeBSD: Home NAS, part 1 – configuring ZFS mirror (RAID1) 8 more parts! Beastie Bits The BSD Proposal UNIX Magic Poster Haiku OS Pulls In Updated Drivers From FreeBSD 15 FreeBSD 15.0 VNET Jails Call for NetBSD testing 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 Gary - Links Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv Join us and other BSD Fans in our BSD Now Telegram channel

This show has been flagged as Clean by the host. This series is dedicated to exploring little-known—and occasionally useful—trinkets lurking in the dusty corners of UNIX-like operating systems. As the zeroth entry of this series, we'll have a little introduction to what it is supposed to be about and why you might want to listen. So that you don't leave without getting at least one piece of useful information, it will end with a little curio that you might find helpful someday. Back in 2010, I was the editor of the newsletter, titled The Open Pitt, for the Western Pennsylvania Linux Users Group in Pittsburgh. We distributed it as a two-page PDF, so had to have enough material to fill each issue. Because we were having some trouble getting contributions, I started writing columns in a series called "UNIX Curio" to occupy the empty space. They were inspired in large part by examples I had seen of people re-inventing ways to do things when utilities for the same purpose had already existed for a long time. The obvious question is: just what is a UNIX Curio? Let's start with the first word, UNIX. While a lot of people write it "Unix" instead, I have chosen to put it in all capitals because that is the way The Open Group, which controls the trademark and the certification process to use it, spells the word 1 . The history of UNIX is complex (search online for more details 2 )—the short version is that many variants emerged, often introducing incompatibilities. Even within AT&T/Bell Laboratories, two major branches came out. The Research UNIX lineage, which includes Seventh Edition (sometimes called Version 7), was often used in universities and government while System III and its more popular successor System V were clearly intended as commercial products 3 . The University of California's BSD was also very influential. My intention is to talk about things that are relatively common; ideally, they would be present on a large majority of systems so you can actually use them. Luckily, there were people who recognized the value in compatibility, so in the mid-1980s they initiated the development of the POSIX standards 4 . Publication of these not only caused commercial UNIX versions to aim for conformance—it gave Free Software implementations of utilities and operating systems a stable base to shoot for rather than having to chase multiple moving targets. As a result, today's GNU/Linux, FreeBSD, NetBSD, and OpenBSD systems generally behave as specified in POSIX, even if they haven't officially earned the UNIX or POSIX labels, so I treat them as part of the UNIX world. Moving on to the second word, "curio," it just means "an object of curiosity, often one considered novel, rare, or bizarre." There are many well-used utilities in the UNIX world, but people forget about others because they are only useful in specific circumstances. And when those circumstances arise, these obscure ones don't always get remembered. One purpose of this series is to point out some of them and describe where they can be appropriately put to use. With the flexible tools available on UNIX systems and the ability to string them together, it shouldn't be surprising that people come up with new ways to accomplish a task. I don't want to claim that these curios are always the best way to do something, just that it can be helpful to know they exist and see the way someone else solved the problem. Also, if you're using an unfamiliar system, sometimes programs you are accustomed to employing might not be installed so it's good to know about options that are widely available. So why am I the person to talk about this subject? I am not a UNIX graybeard with decades of professional computing experience. If I did grow a beard, it would only be partially gray, and my working life has been spent in the engineering world mainly around safety equipment. Sadly, there I have been forced to use Windows almost exclusively. However, in my academic and personal pursuits, I have been involved with using UNIX and Linux for more than 30 years, so I do have a bit of a historical perspective. For some reason, when I encounter an unusual or obscure tool, I want to learn more about it, especially so if I find it to be useful in some way. After gaining that information, I might as well share it with you. In addition, I have been involved with Toastmasters International, a public speaking organization, for about 15 years so I have experience in presenting things orally. I was inspired to turn this article series into podcasts by murph 5 , who delivered a presentation at the 2025 OLF Conference describing how and why to contribute to Hacker Public Radio 6 . The show notes for curios 1 through 3 will consist of the articles as they were originally written (though with references added). Because some examples, especially code, can be difficult to understand when they are read out loud, the podcasts will sometimes present the information in a different way. Show notes for this curio 0 and for curios 4 and later will be written with the podcast format in mind, so they will more closely match what I say. Let's end with an actual curio to kick off the series. Have you ever needed a quick reminder about whether the file you're looking for can be found under the /usr or /var directories? On many UNIX systems, man hier will give you an overview of how the file hierarchy is organized. This manual page is not a standard, but was present in Seventh Edition UNIX 7 and many descendents, direct and indirect, including every Linux distribution I have ever used. There are attempts to standardize the layout; in the Linux world, the Filesystem Hierarchy Standard (FHS) 8 , now hosted by Freedesktop.org 9 , intends to set a path to be followed. It should be noted that systemd has its own idea of how things should be laid out based on the FHS; if it is in use, try man file-hierarchy instead as it will likely be a more accurate description. I hope this gives you a good idea of what to expect in future episodes. The first one will be about shell archives, so keep an eye on Hacker Public Radio's schedule for it to appear. References: The Open Group Trademarks https://www.opengroup.org/trademarks History of Unix https://en.wikipedia.org/wiki/History_of_Unix The Unix Tutorial, Part 3 https://archive.org/details/byte-magazine-1983-10/page/n133/mode/2up POSIX Impact https://sites.google.com/site/jimisaak/posix-impact Correspondent: murph https://hackerpublicradio.org/correspondents/0444.html OLF Conference - December 6th, 2025 https://www.youtube.com/watch?v=hyEunLtqbrA&t=25882 File system hierarchy https://man.cat-v.org/unix_7th/7/hier Finding a successor to the FHS https://lwn.net/Articles/1032947/ Freedesktop.org now hosts the Filesystem Hierarchy Standard https://lwn.net/Articles/1045405/ Provide feedback on this episode.

Le RMC Fighter Club reçoit un homme qui était encore à Sydney, il y a quelques jours, pour accompagner Benoît Saint-Denis sur le chemin de sa victoire contre Dan Hooker. Ancien combattant chez les amateurs en boxe anglaise, Anthony Bret est aujourd'hui coach dans cette discipline. Pour les deux derniers combats de BSD, il a participé aux camps qui ont finalement propulsés le Français vers le top 5 chez les -70kg à l'UFC. Dans cet épisode, Anthony nous raconte les coulisses de cette collaboration ainsi que son analyse, à froid, sur les performances de Saint-Denis dans la cage.

BSD veut prendre la place de numéro 1 d'Arman Tsarukyan : pas de problème.

Tipeee : https://fr.tipeee.com/tatami-connexion/Import Fight : https://import-fight.com/?srsltid=AfmBOorPLaRoGMlD5TMi_ToZnEBnkq6Mr3p_RFLl7lU5Idm0R0ySUfQdCode : TATAMI10Bienvenu sur le format actualité MMA et JJB du podcast TATAMI Connexion : Restons Connecté !Chaque semaine nous allons parler des sujets qui anime nos sports et qui attise toutes les conversation !Cette semaine programme chargé avec :- BSD top 5- Gaethje répond à Poirier- Ruffy vs McGregor à la White House- La carte de Londres- UFC 326 : Forfait de Ortega- Shavkat et Khamzat Blessés - PFL Dubai- Question auditeur Bonne écoute !!

ZFS Scrubs and Data integrity, Propolice, FreeBSD vs Slackware and more. NOTES This episode of BSDNow is brought to you by Tarsnap and the BSDNow Patreon Headlines Understanding ZFS Scrubs and Data Integrity The story of Propolice Desk reviews describe comment ask questions No reponses, no justications. [Tj's Desk](media/bsdnow649-tjs-desk.jpg) [Ruben's Desk](media/bsdnow649-rubens-desk.jpg) News Roundup FreeBSD vs. Slackware: Which super stable OS is right for you? Prometheus, Let's Encrypt, and making sure all our TLS certificates are monitored Wait, a repairable ThinkPad!? 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 Join us and other BSD Fans in our BSD Now Telegram channel

Fightminds interviewe Nicolas Ott après l'UFC 325 ! Il revient sur le combats de BSD, sur ses méthodes de coaching ainsi que sur le lancement de sa structure ! Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

The gang comes together to discuss UFC 325. They talk about Volk's repeat victory over Lopes and big wins from Ruffy and BSD. The gang then talks about the fight announcements for the UK fight night and the UFC 324 views. They then make their predictions for this weekend's warehouse fights before giving their top 5 live performances. All that and another edition of "Stuff We Like."

Make sure to subscribe and follow the show for new weekly episodes. Visit https://kalshi.com/sign-up?referral=P4P or download the Kalshi App and use code P4P for $10. Sign up and trade today. They guys break down UFC 325 and some hot news from the weekend. Enjoy. 2:02 Volk vs Lopez 2, same same 9:19 BSD beats Hooker, Paddy's Gladdy 17:00 Ruffy vs Fiziev, Camp Dramas 27:08 Tuivasa and heavyweight outlook 31:50 Quillan Salkilld does it again 34:31 Speed Round 37:02 Shakur vs Teofimo reaction 38:30 Jarrell Miller Wins, but at what cost 46:22 Khamzat vs Pereira Follow the Show on Social Instagram: https://www.instagram.com/pound4pound/ Twitter/X: https://twitter.com/Pound4poundshow Tik Tok: https://www.tiktok.com/@pound4pound A Shadow Lion Production. Learn more about your ad choices. Visit megaphone.fm/adchoices

C'était une tendance, c'est désormais une confirmation. Benoît Saint-Denis est dans la course à la ceinture des -70kg à l'UFC. Vainqueur autoritaire de Dan Hooker à Sydney, le Français va se rapprocher du top 5 de sa catégorie. Mais alors qui affrontera-t-il en 2026 ? Avec 4 victoires de rang, dont 3 face à des combattants classés, BSD continue d'imposer son style ultra-spectaculaire. Il peut désormais prétendre à n'importe quel adversaire : Topuria, Gaethje, Holloway, Oliveira, Pimblett ou Tsarukyan... Saint-Denis fait maintenant partie de ce gratin. L'UFC le sait et lui donnera certainement dans les mois à venir, le combat qu'il mérite. Baba Diagne et Charles Chevallier débriefent l'UFC 325 avec les yeux déjà tournés vers l'avenir de BSD.

UFC 325 had some really great moments and finishes throughout the card. Ruffy over Fiziev, BSD over Dan Hooker and some not so great. Chief of the worst was just the booking in the main event, Diego Lopes vs Alexander Volkanovski looked like Lopes vs Volk 1. It was a dominant performance the first time and it was only 9 months ago. What was even the point?

Chris et Brian reviennent sur l'UFC 325 et la performance de BSD qui a su s'imposer face à Dan Hooker au 2nd round ! Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

UFC 325 wasn't built the same as its predecessor, sacrificing quality to ensure local favorites were featured prominently on the card, and having a main event that kind of makes no sense. But that doesn't mean the event was a bust—quite the opposite. The undercard saw an even mix of finishes to decisions, and some fresh ROAD to UFC talent to keep our eye on in the future.The main portion of the card bore witness to Quillan Salkilld embarrass Jamie Mullarkey in about three minutes flat, proving the gigantic gulf in the odds was justified. Tai Tuivasa took his sixth, straight loss at the hands of Tallison Teixeira, and it was as depressing as you might assume, for those that didn't watch. UFC has to let Tai go and stop embarrassing him in front of his people.Mauricio Ruffy took Fiziev nearly to the end of round two, then decided he would end Rafael's suffering, scoring the TKO and sending the Azerbaijani back to the L side of the column. Benoit Saint-Denis put a whooping on Dan “Prostituta” ← (IYKYK) after a first round of Hooker besting him with body kicks and guillotine attempts. The second round was a different story once BSD got the Aussie down, raining down elbows and strikes of all kinds, bloodying the man to the point that Herb Dean stepped in to wave the fight off.Alexander Volkanovski proved once again that he's the featherweight kingpin. He damned near got a shutout, but I gave Diego Lopes a narrow round 2, as did two of the judges. The third judge gave Volk a perfect 50-45, which was also acceptable, as many fans and pundits did. It was a terrific contest, though, and Lopes never looked like he was out of it. He never gave up trying to get the fight finished, yet still couldn't solve the riddle. On to the next one. Now that we've reviewed the highlights, let's check out the results and bonuses while we're here.MMA Vivisection & 6th Round is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.UFC 325 Results* 145 lbs.: Alexander Volkanovski def. Diego Lopes by unanimous decision (49-46, 49-46, 50-45)* 155 lbs.: Benoit Saint-Denis def. Dan Hooker by TKO (elbows), round 2 (4:45)* 155 lbs.: Mauricio Ruffy def. Rafael Fiziev by TKO (punches), round 2 (4:30)* 265 lbs.: Tallison Teixeira def. Tai Tuivasa by unanimous decision (29-28, 29-28, 29-28)* 155 lbs.: Quillan Salkilld def. Jamie Mullarkey by submission (rear naked choke), round 1 (3:02)* 205 lbs.: Billy Elekana def. Junior Tafa by submission (rear naked choke), round 2 (3:18)* 185 lbs.: Cam Rowston def. Cody Brundage by TKO (ground and pound), round 2 (4:08)* 185 lbs.: Jacob Malkoun def. Torrez Finney by unanimous decision (30-27, 30-26, 30-26)* 170 lbs.: Jonathan Micallef def. Oban Elliot by technical submission (rear naked choke), round 2 (3:31)* 145 lbs.: Kaan Ofli def. Yizha by majority decision (29-28, 28-29, 29-28)* 155 lbs.: Don Mar Fan def. Sangwook Kim by unanimous decision (30-27. 30-27. 30-27)* 145 lbs.: Keiichiro Nakamura def. Sebastian Szalay by TKO (knee), round 3 (3:28)* 135 lbs.: Lawrence Lui def. Sulangrangbo by split decision (29-28, 28-29, 29-28)UFC 325 Bonuses * $100K each FOTN: Alexander Volkanovski vs. Diego Lopes* $100K each POTN: Quillan Salkilld, Mauricio Ruffy* $25K each to the other fighters that got a finish:Keiichiro Nakamura, Jonathan Micallef, Cam Rowston, Billy Elekana, Benoit Saint-DenisThank you for reading this article and listening to the podcast. Please consider subscribing to The MMA Vivisection & 6th Round Post-fight Show podcast Substack to enjoy our premium content. Your paid subscriptions are keeping hope alive that we can continue on with our shows. If you haven't already, please pledge with a paid subscription today. If you have, please share this post far and wide.Thanks for reading MMA Vivisection & 6th Round! This post is public so feel free to share it. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit themmadrawpodcast.substack.com/subscribe

FreeBSD's Future, 18 years of greytrapping, PF vs Linux firewalls, and more. NOTES This episode of BSDNow is brought to you by Tarsnap and the BSDNow Patreon Headlines Powering the Future of FreeBSD Eighteen Years of Greytrapping - Is the Weirdness Finally Paying Off? BSDCan Organisating committee Interview News Roundup How I, a non-developer, read the tutorial you, a developer, wrote for me, a beginner BSD PF versus Linux nftables for firewalls for us 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 Join us and other BSD Fans in our BSD Now Telegram channel

Support weekly episodes. Subscribe and follow the show. Click the link  http://kalshi.com/r/P4P or download the Kalshi App and use code P4P to sign up and trade today! UFC 325 is here and we break down the main card AND talk with bantamweight sharp shooter Lerone Murphy. The guys break down every major matchup on the main card. Alexander Volkanovski vs Diego Lopes and what this fight means for the featherweight division, breaking down styles, experience, and what really matters when the cage door closes. Also up: Bantamweight matchmaking, rising contenders, speed round, Question from a Casual and Meme of the week. THEN, Lerone opens up about being passed over for a featherweight title shot, whether the UFC ever reached out, and how he's approaching his career at this stage. He talks about his late start in MMA, his development as a complete fighter, the evolution of UK MMA, and how he stays patient while continuing to win at the highest level. Real insight, honest opinions, and fighter-to-fighter conversation you won't hear anywhere else. Enjoy. 00:00 Intro 00:30 Prediction markets explained 02:05 UFC 325 overview 06:45 Volkanovski vs Diego Lopes II 13:00 Dan Hooker vs BSD 19:00 Fiziev vs Gamrot 22:00 Tuivasa vs Tybura 25:15 Fight of the Night sleeper pick 29:35 Bantamweight division matchmaking talk 35:20 Speed Round! 38:35 Question from a Casual: Paddy Pimblett's next fight debate 43:00 Meme of the week 46:10 Lerone Murphy Interview Start 47:55 Being passed over for the title shot 56:40 Lerone's background and late start in MMA 1:02:45 Training, grappling evolution, and UK MMA perception 1:06:45 Volkanovski, Diego Lopes, and future title outlook 1:10:30 Lerone's mindset, patience, and next steps Follow the Show on Social Instagram: https://www.instagram.com/pound4pound/ Twitter/X: https://twitter.com/Pound4poundshow Tik Tok: https://www.tiktok.com/@pound4pound A Shadow Lion Production. Learn more about your ad choices. Visit megaphone.fm/adchoices

Podcast available on Spotify "Keep It a Buck Daily"LIKE - COMMENT - PLEASE SUBSCRIBETIMESTAMPS:(0:01) - Intro / Thoughts on Paramount + Production for UFC 324(15:07) - UFC Bonuses / Betting Scandals / Fights dropped from UFC 324 Card(30:00) - UFC 324 Recap / Discussion (30:30) - Paddy vs Gaethje (44:00) - O'Malley vs Song (49:45) - Cortes-Acosta vs Lewis(55:35) - Silva vs Namajunas (56:06) - Silva vs Allen (1:01:40) - UFC 324 Prelims (Skim Through)(1:10:20) - Batbayar vs Tau (1:12:46) - Lui vs Sulangrangbo (1:14:00) - Szalay vs Nakamura (1:15:50) - Mar Fan vs Kim (1:17:07) - Ofli vs Yizha (1:20:30) - Micallef vs Elliott (1:24:10) - Malkoun vs Finney (1:28:10) - Rowston vs Brundage (1:30:45) - Tafa vs Elekana UFC 325 MAIN CARD(1:33:05) Salkilld vs Mullarkey (1:34:40) Tuivasa vs Teixeira(1:39:50) Fiziev vs Ruffy (1:46:42) CO MAIN: Hooker vs BSD(1:53:20) MAIN: Volkanovski vs Lopes I post all my final picks on my social media accounts down below. FOLLOW AND SUB THE Social Media accountsTWITTER / X Account: @KIABmediaInstagram: @keepitabuck_mediaTik Tok: @ kiabmedia_

Benoît Saint Denis revient de loin. Après deux défaites d'affilées en 2024, ses rêves de titre s'éloignaient. En 2025, ses succès sur Prepolec, Ruffy et Dariush lui ont permis de se relancer dans la course. Aujourd'hui classé 8ème de sa catégorie, BSD a une occasion unique de continuer sa progression. À l'UFC 325, il affronte le redoutable Dan Hooker. Un match-up qui, sur le papier, pourrait profiter au Français. Le RMC Fighter Club analyse ce combat, ainsi que le main-event qui oppose la légende Alexander Volkanovski à son challenger, Diego Lopes. 

À mains nues, il est l'un des hommes les plus dangereux du monde.Un mois avant l'un des plus gros combats de sa carrière, Benoît Saint Denis nous ouvre les portes de son univers.En seulement 6 ans, il s'est imposé dans la ligue très fermée des meilleurs combattants de MMA au monde.Avant même de commencer sa carrière sportive, sa vie tournait déjà autour d'une seule quête : devenir le meilleur guerrier possible.Benoît s'engage à 18 ans dans les forces spéciales de l'armée de Terre française. Avec le 1er régiment de parachutistes d'infanterie de marine de Bayonne, il remplit pendant 5 ans des missions d'anti-terrorisme, de libération d'otages et de protection de personnalités sur des théâtres de guerre.Ces années le forgent, lui apprennent la rigueur, la discipline et la recherche d'excellence. Trois qualités sur lesquelles il s'appuiera quand il prend la décision de quitter l'armée pour se donner une chance d'exceller dans son sport : le MMA.Il se laisse alors 2 ans pour tenter d'en vivre, mais ne met que quelques mois pour gagner ses premiers combats amateurs et arriver à pleine vitesse sur le circuit professionnel.S'ensuit une série de victoires qui le propulse à l'UFC (Ultimate Fighting Championship), la plus prestigieuse organisation de MMA au monde.Malgré 2 défaites, celui que le public appelle désormais “God of War” entre rapidement dans le top 10 et peut aujourd'hui rêver de combattre un jour pour la ceinture de sa catégorie.Dans cet épisode exceptionnel Benoît Saint Denis se livre sur :Les 5 années de forces spéciales qui ont fait naître “God of War”Ce que personne ne dit jamais sur les primes à plusieurs millionsLes pertes de poids drastiques (perdre 5 kilos en 12 heures)Comment faire cohabiter sa foi et la violence de sa disciplinePourquoi personne ne parle de bien-être en sports de combatUn échange fort, avec un homme franc, pour mieux comprendre la vie des combattants de haut niveau, leurs doutes et leur détermination — et apprendre comment se mettre en marche vers de grands objectifs.Vous pouvez suivre Benoît sur Instagram.Il y a 40% de réduction pour le lancement de BSD Method et le code “DOIT” vous donne 20% de réduction supplémentaires donc foncez, il n'y aura plus de meilleur timing.TIMELINE:00:00:00 : Les catégories stars en MMA00:10:33 : 5 ans d'armée qui ont forgé Benoît00:19:27 : Rejoindre les forces spéciales à 17 ans00:30:08 : “Les premiers mois de ma carrière, j'avais une vie de moine guerrier”00:37:55 : Entrer dans un octogone pour la première fois00:46:33 : Par où commencer pour faire du MMA ?00:55:20 : Pourquoi un spécialiste peut battre un combattant complet01:04:23 : Le protocole minutieux avant chaque combat01:13:32 : Comment un combat peut basculer en quelques dixièmes de seconde01:22:33 : La place du show dans le MMA01:33:33 : Combien gagne vraiment un combattant de l'UFC ?01:45:41 : Perdre 5 kilos en 12 heures01:53:38 : La noblesse de l'affrontement à mains nues02:02:30 : “J'ai envie que tous ceux que j'embarque soient heureux”Les anciens épisodes de GDIY mentionnés : #502 - Thomas Sammut - Préparateur Mental - Faut-il forcément souffrir pour réussir ?#479 - Nikola Karabatic - Champion de Handball - 22 titres sur 23 : la légende du sport françaisNous avons parlé de :UFC de Paris Bercy1er régiment de parachutistes d'infanterie de marineVenumLe premier combat de BSD à l'UFC et aussi sa première défaiteBSD vs MoicanoZelimkhan Khadjiev, lutteur français avec qui Benoît s'entraîneLe KO en 16 secondes de Benoît sur Beneil DariushBSD MethodThe Last DanceLes recommandations de lecture :Les récits chevaleresques de LancelotLe colonel Chabert - Honoré de BalzacL'homme qui plantait des arbres - Jean GionoVous souhaitez sponsoriser Génération Do It Yourself ou nous proposer un partenariat ?Contactez mon label Orso Media via ce formulaire.Hébergé par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

Why use BSD, 2025, the year of advocacy, community and growth, RiscV silicon, and more. NOTES This episode of BSDNow is brought to you by Tarsnap and the BSDNow Patreon Headlines Why BSDs? 2025: A Year of Advocacy, Community, and Growth What are we excited for in tech in 2026? Almost Completley Open riscv32 silicon with BaoChip and Xous The death of vmware and the possibilites for diversity that creates Capabilities arriving in FreeBSD main NetBSD on the WiiU and open hardware for retro computing Capabilities arriving with CheriIOT News Roundup Wireguard The FreeBSD Way Beastie Bits BastilleBSD 2025 User Survey Re: ZFS status on NetBSD 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 Albin- Foss-North Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv Join us and other BSD Fans in our BSD Now Telegram channel

Chris et Brian analysent le prochain combat de BSD qui aura lieu lors de l'UFC 325 face à Dan Hooker ! Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

The Unix v4 recovery, webzfs, openbgpd 9.0, MidnightBSD 4.0, 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 University of Utah team discovers rare computer relic (https://ksltv.com/science-technology/university-of-utah-discovers-rare-computer-relic/853296/) The attempt to read the UNIX V4 tape is underway! (https://mastodon.social/redirect/statuses/115747843746305391) UNIX V4 Tape from University of Utah (https://archive.org/details/utah_unix_v4_raw) UNIX V4 tape successfully recovered: First ever version of UNIX written in C is running again (https://www.theregister.com/2025/12/23/unix_v4_tape_successfully_recovered/) An initial analysis of the discovered Unix V4 tape (https://www.spinellis.gr/blog/20251223/) WebZFS (https://github.com/webzfs/webzfs) News Roundup OpenBGPD 9.0 released (https://www.undeadly.org/cgi?action=article;sid=20251231070524) MidnightBSD 4.0 (https://www.midnightbsd.org/notes/4.0/index.html) Let's run FreeBSD 15.0-RELEASE on a Raspberry Pi Zero 2 W (https://briancallahan.net/blog/20251216.html) Figuring out how I want to set up the TVPC (https://vulcanridr.mataroa.blog/blog/figuring-out-how-i-want-to-set-up-the-tvpc/) TVPC update (https://vulcanridr.mataroa.blog/blog/tvpc-update/) C&C Red Alert2 in your browser (https://chronodivide.com) 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 rick - shout out.md (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/646/feedback/rick%20-%20shout%20out.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

No décimo oitavo episódio do Hipsters.Talks, PAULO SILVEIRA , CVO do Grupo Alura, conversa com EDUARDO SANTOS , especialista em inteligência artificial na Lopti, sobre O VERDADEIRO SIGNIFICADO DE SOFTWARE LIVRE, a diferença entre free software e open source e POR QUE LLAMA E OUTROS MODELOS NÃO SÃO TÃO “ABERTOS” QUANTO PARECEM. Uma discussão sobre licenças (GPL, MIT, BSD), comunidades brasileiras e o futuro do código aberto na era da IA! Sinta-se à vontade para compartilhar suas perguntas e comentários. Vamos adorar conversar com você!

Holidays 2025 - What you been do'in? 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 What tech did we enjoy playing with or found interesting in 2025? 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 - Gary - Storage Is Cheap (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/644/feedback/Gary%20-%20Storage%20Is%20Cheap.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

Upwrapping OpenZFS gifs, Propolice the OpenBSD Stack Protector, refreshing zpools, and the FreeBSD 15.0 release. 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 Unwrapping ZFS: Gifts from the Open Source Community (https://klarasystems.com/articles/zfs-community-contributions-2025/?utm_source=BSD%20Now&utm_medium=Podcast) Who wins when we filter the open web through an opaque system? (https://hidde.blog/filtered-open-web/) News Roundup We can't fund our way out of the free and open source maintenance problem (https://utcc.utoronto.ca/~cks/space/blog/tech/OpenSourceFundingNotSolution) The story of Propolice, the OpenBSD stack protector (https://www.undeadly.org/cgi?action=article;sid=20251212094310) Copying everything off a zpool, destroying it, creating a new one, and copying everything back (https://dan.langille.org/2025/12/11/copying-everything-off-a-zpool-destroying-it-creating-a-new-one-and-copying-everything-back/) All aboard the 15.0-RELEASE train! (https://vulcanridr.mataroa.blog/blog/all-aboard-the-150-release-train/) Beastie Bits Running A PDP-8 From 1965 (https://www.youtube.com/watch?v=S2r_GujSc6w) The library of time (https://libraryoftime.xyz) OPNsense 25.7.9 released (https://forum.opnsense.org/index.php?topic=49986.0) - OPNsense 25.10.1 business edition released (https://forum.opnsense.org/index.php?topic=50052.0) 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 Martin - recordings (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/643/feedback/Martin%20-%20recording%20of%20bsdnow.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

This week on Destination Linux, we are joined by a special guest host: Craig Rowland, the CEO of Sandfly Security! We're diving deep into the reality of modern security—specifically when third-party code knocks over your castle. From malicious VSCode extensions to the "React2Shell" vulnerability, we discuss why "Open Source" doesn't automatically mean "Safe" and how to protect your supply chain. Then, is it possible to have the macOS experience without the Apple ecosystem? Ryan explores ravynOS, a daring new project with "macOS vibes and a BSD soul." It's attempting to bring the Aqua interface—and eventually Mac app compatibility—to the open-source world. Plus, Jill brings us massive news from Canonical and AMI. You might soon be installing Ubuntu directly from your motherboard's BIOS without ever needing a USB drive. We break down how this partnership changes the game for hardware. Finally, we read an incredible listener story. Show Notes: 00:00:00 Intro 00:02:39 Extended Intro: Open Source or Bust 00:03:08 Community Feedback: A Pentester's Origin Story 00:10:03 Guest Host: Sandfly Security & Agentless Protection 00:15:53 Security Deep Dive: Supply Chain Attacks, Malicious VSCode Extensions & React2Shell 00:44:31 ravynOS: The Open Source Mac Killer? 00:56:05 News: Canonical + AMI: Installing Ubuntu from the BIOS 01:08:07 Outro 01:09:33 Post-Show Shenanigans Support the Show: Sponsored by Sandfly Security: destinationlinux.net/sandfly - Get 50% off the Home Edition with code DESTINATION50 Special Guest: Craig Rowland.

FreeBSD 15 release, moving from OpenBSD to FreeBSD, ZFS Boot Environments explained, 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 Welcome to the world FreeBSD 15.0-RELEASE Announcement (https://www.freebsd.org/releases/15.0R/announce/) and Release Notes (https://www.freebsd.org/releases/15.0R/relnotes/) We're (now) moving from OpenBSD to FreeBSD for Firewalls (https://utcc.utoronto.ca/~cks/space/blog/sysadmin/OpenBSDToFreeBSDMove) - Submitted by listener Gary News Roundup ZFS Boot Environments Explained (https://vermaden.wordpress.com/2025/11/25/zfs-boot-environments-explained/) Why I (still) love Linux (https://it-notes.dragas.net/2025/11/24/why-i-still-love-linux/) rocinante - A configuration management tool by the BastilleBSD team (https://github.com/BastilleBSD/rocinante) A Grown-up ZFS Data Corruption Bug (https://github.com/oxidecomputer/oxide-and-friends/blob/master/2025_11_24.md) and YouTube (https://www.youtube.com/watch?v=srKYxF66A0c) 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 Claudio - A Silent Reflection (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/641/feedback/Claudio%20-%20Reflection.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

FreeBSD is an OCI runtime, ZFS Disaster Recovery, Cleaning up Hammer, and some historical information, 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 FreeBSD Officially Supported in OCI Runtime Specification v1.3 (https://freebsdfoundation.org/blog/freebsd-officially-supported-in-oci-runtime-specification-v1-3) ZFS Enabled Disaster Recovery for Virtualization (https://klarasystems.com/articles/zfs-enabled-disaster-recovery-virtualization?utm_source=BSD%20Now&utm_medium=Podcast) News Roundup How I think OpenZFS's 'written' and 'written@' dataset properties work (https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWrittenPropertyHowItWorks) Make sure your Hammer cleanup cleans up (https://www.dragonflydigest.com/2025/11/13/make-sure-your-hammer-cleanup-cleans-up) [TUHS] David C Brock of CHM: 2024 oral history with Ken Thompson + Doug McIlroy (https://www.tuhs.org/pipermail/tuhs/2025-November/032751.html) Special Issue “Celebrating 60 Years of ELIZA? Critical Pasts and Futures of AI” (https://ojs.weizenbaum-institut.de/index.php/wjds/announcement/view/8) Source and state limiters introduced in pf (https://undeadly.org/cgi?action=article;sid=20251112132639) 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 Göran - grafana (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/640/feedback/G%C3%B6ran%20-%20grafana.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

Reproducible builds, Highly available ZFS Pools, Self Hosting on a Framework Laptop, 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 FreeBSD now builds reproducibly and without root privilege (https://freebsdfoundation.org/blog/freebsd-now-builds-reproducibly-and-without-root-privilege) How to Set Up a Highly Available ZFS Pool Using Mirroring and iSCSI (https://klarasystems.com/articles/highly-available-zfs-pool-setup-with-iscsi-mirroring?utm_source=BSD%20Now&utm_medium=Podcast) News Roundup Self hosting 10TB in S3 on a framework laptop + disks (https://jamesoclaire.com/2025/10/05/self-hosting-10tb-in-s3-on-a-framework-laptop-disks/) Crucial FreeBSD Toolkit (https://vermaden.wordpress.com/2025/07/08/crucial-freebsd-toolkit/) Some notes on OpenZFS's 'written' dataset property (https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSSnapshotWrittenProperty) vi improvements on Dragonfly (https://www.dragonflydigest.com/2025/10/28/vi-improvements) Big news for small /usr partitions (https://undeadly.org/cgi?action=article;sid=20251112121631) 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 Patrick - Feedback (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/639/feedback/patrick%20-%20notes.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

New Open Indiana Release, Understanding Storage Performance, a Unix OS for the TI99, FreeBSD Tribal knowledge, 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 Signifier flotation devices (https://davidyat.es/2025/09/27/signifier-flotation-devices) Open Indiana Hipster Announcement (https://openindiana.org/announcements/openindiana-hipster-2025-10-announcement/) Understanding Storage Performance Metrics (https://klarasystems.com/articles/understanding-storage-performance-metrics?utm_source=BSD%20Now&utm_medium=Podcast) News Roundup UNIX99, a UNIX-like OS for the TI-99/4A (https://forums.atariage.com/topic/380883-unix99-a-unix-like-os-for-the-ti-994a) Making the veb(4) virtual Ethernet bridge VLAN aware (https://undeadly.org/cgi?action=article;sid=20251029114507) FreeBSD tribal knowledge: minor version upgrades (https://vulcanridr.mataroa.blog/blog/freebsd-tribal-knowledge-minor-version-upgrades) It's been 10 years since ZFS's 10th aniversary its integration into Solaris - A Reflection (https://blogs.oracle.com/oracle-systems/post/happy-10th-birthday-zfs) 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) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

#UFCQatar full card breakdown and picks and we also do a full recap of #ufc322 talk about possible fights, rankings at 170, etc.! LIKE - COMMENT - PLEASE SUBSCRIBETIMESTAMPS:(01:00) - UFC 322 RECAP(01:34) - JDM vs Islam / (08:47) - Shevchenko vs Weili (17:00) - Brady vs Morales (19:00) - Edwards vs Prates / 170 Rankings / 170 talk(24:03) - BSD vs Benny / What's next for BSD?(34:50) - UFC 322 Prelims(47:16) - UFC Qatar Breakdown(48:10) - Bujlo vs Freeman (49:54) - Dalby vs Izagakhmaev(52:30) - Aliev vs Rock(54:04) - Naurdiev vs Loder (56:32) - Almakhan vs Topuria (59:02) - Ulanbekov vs Horiguchi (1:01:33) - Yakhyaev vs Cerqurira (1:04:33) - Grad vs Riley (1:07:45) - Perez vs Almabayev (1:11:18) - Spivac vs Gaziev (1:13:20) - Hermansson vs Orolbai (1:15:20) - Oezdemir vs Menifield (1:18:00) - Muhammad vs Garry (1:32:15) - Tsarukyan vs HookerI post all my final picks on my social media accounts down below. FOLLOW AND SUB THE Social Media accountsTWITTER / X Account: @KIABmediaInstagram: @keepitabuck_mediaTik Tok: @ kiabmedia_#ufcpicks #worththeweightmma

SleepyJ and Mean Gene talk UFC betting for UFC 322 Madalena vs Makachev headlines a stacked UFC 322 card from MSG, with Sleepy J and Mean Gene breaking down eight fights. They agree early on Erin Blanchfield vs Tracy Cortez, both backing Blanchfield due to improved striking, strength, and ability to control exchanges despite Cortez winning their pre-UFC meeting. They also align on Roman Kopylov as a live underdog over Gregory “Robocop” Rodrigues, citing Rodrigues' shaky chin, tendency to brawl despite having grappling advantages, and Kopylov's power and durability after facing an elite Paulo Costa. Next, both pick Bo Nickal over Rodolfo Vieira, expecting Nickal to lean on his elite wrestling in a measured, mistake-free game plan after his setbacks, likely controlling the ground without risking unnecessary stand-up exchanges. Their first disagreement comes with Beneil Dariush vs Benoit Saint-Denis: Gene picks BSD, trusting his pressure, power, and revived momentum, while Sleepy prefers Dariush's superior skill and grappling if he can avoid big shots. Another split follows with Carlos Prates vs Leon Edwards; Sleepy sides with Edwards' championship experience and durability, while Gene believes Prates' relentless forward pressure and destructive power will break Edwards as others have recently. They reunite on Sean Brady over Michael Morales, expecting Brady's grappling, control, and veteran savvy to neutralize Morales' explosive striking and deliver a “vet lesson” in a key contender matchup. In the co-main event, Gene backs Zhang Weili moving up for two-division glory, praising her evolution, volume, and ability to capitalize on Shevchenko's occasional grappling mistakes, while Sleepy takes Valentina Shevchenko as the stronger, cleaner, more technical striker with superior size and takedown defense. In the main event, both predict Islam Makachev dominates Jack Della Maddalena early, with Makachev's wrestling, control, and improved striking overwhelming a dangerous but out-classed champion who still has defensive gaps against elite grapplers. They expect an early submission or dominant finish as Makachev pursues champ-champ status. The show wraps with confidence in the card's quality, a few strategic disagreements to help bettors evaluate both sides, and reminders to use code HOOK50 at Pregame. Learn more about your ad choices. Visit megaphone.fm/adchoices

Toujours avec @ManuelFerraraTV , on fait le tour de l'UFC 322 Islam Makhachev vs Jack Della Maddalena et BSD vs Dariush. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

A deep dive into cathedral roof design and insulation strategy. The team compares solid-sawn rafters vs. scissor trusses, smart vapor retarders vs. poly, and discusses optimal roof pitches. You'll learn when to vent from the topside, from below, or go unvented entirely—and why those choices matter.In the last 10 minutes, the crew unpacks one of building science's trickiest topics: 6-sided containment of air-permeable insulation—and how it impacts attic R-values and energy performance. PETE'S RESOURCES:1. GBA "Five Cathedral Ceilings That Work:"2. BSD-149: Unvented Roof Assemblies for All Climates3. "Convection in Loose-Fill Attic Insulation - Measurements and Numerical Simulations"

Thunderbolt on FreeBSD, ZFS on Illumos and Linux and FreeBSD, ZFS Compression, Home networking monitoring, LibreSSH and OpenSSH releases 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 Thunderbolt on FreeBSD (https://blog.feld.me/posts/2025/10/thunderbolt-on-freebsd) The broad state of ZFS on Illumos, Linux, and FreeBSD (as I understand it) (https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSOnIllumosLinuxAndFreeBSD) News Roundup zfs: setting compression and adding new vdevs (https://dan.langille.org/2025/10/18/zfs-setting-compression-and-adding-new-vdevs) The hunt for a home network monitoring solution (https://vulcanridr.mataroa.blog/blog/the-hunt-for-a-home-network-monitoring-solution) LibreSSL 4.2.0 Released (https://www.undeadly.org/cgi?action=article;sid=20251015043527) OpenSSH 10.2 released (https://www.undeadly.org/cgi?action=article;sid=20251010131052) - Related to 10.x versions : Post-Quantum Cryptography (https://www.openssh.com/pq.html) Check your IP infos using nginx (https://www.tumfatig.net/2025/check-your-ip-infos-using-nginx) Experimenting with Compression (just given an overview, I dont exepect you to read the all three writeups fully) Experimenting with compression off (https://dan.langille.org/2025/10/06/experimenting-with-compression-off/) Experimenting with compression=lz4 (https://dan.langille.org/2025/10/06/experimenting-with-compressionlz4/) Experimenting with compression=zstd (https://dan.langille.org/2025/10/06/experimenting-with-compressionzstd/) Compression results (https://dan.langille.org/2025/10/06/compression-results) 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 Anton - Boxybsd (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/636/feedback/anton%20-%20boxybsd.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

In this episode, we dive into Canaan's surprising GitHub drop and what it could mean for open-source mining, license tangles and all. We unpack the inclusion of CGMiner, the BSD-3 vs GPLv3 conflict, and Canaan's RISC-V K230 SDK. We also explore the Nano 3/Nano 3S design, home-mining momentum, and the practical realities of certification (FCC/UL/CE/RoHS) for miners and heater-integrations. From local vs remote control to insurance implications, we discuss the gauntlet that open hardware must run and why decentralization requires openness. We spotlight Intel BZM2 progress: Bitaxe Bonanza's lessons, the new BIRDS dev board, nine-bit serial hurdles, and a call for builders to leverage upcoming chip availability. Hydra Pool hits a milestone with public Dockerized releases and coinbase payout flexibility, while we test live at test.hydropool.org (and note Bitmain firmware limits). We cover Pluto's HRF grant for fleet management, ESPminer stewardship funding, and D++'s Lightning-powered gamification for community builds. We also discuss Support for the Samourai Wallet devs, including context around sentencing and broader implications for open-source freedom. We preview Bitcoin++ Durham on Nov 15, share updates on the Samurai Wallet developers' impending sentencing, and talk product integrity, copying, and the push to re-shore manufacturing. Finally, we tee up HeatPunk Summit 2026; bringing HVAC pros and open-source miners together, and have fun with Lightning “thermo-zaps” for live heating control.

OpenBSD 7.8, Building Enterprise Storage with Proxmox, SSD performance, Virtual Machines 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 OpenBSD 7.8 Released (https://www.openbsd.org/78.html) also (https://undeadly.org/cgi?action=article;sid=20251022025822) and (https://bsd.network/@brynet/115403567146395679) Building Enterprise-Grade Storage on Proxmox with ZFS (https://klarasystems.com/articles/building-enterprise-grade-storage-on-proxmox-with-zfs) News Roundup [TUHS] Was artifacts, now ethernet (https://www.tuhs.org/pipermail/tuhs/2025-July/032268.html) I wish SSDs gave you CPU performance style metrics about their activity (https://utcc.utoronto.ca/~cks/space/blog/tech/SSDWritePerfMetricsWish) Migrate a KVM virtual machine to OmniOS bhyve (https://www.tumfatig.net/2025/migrate-a-kvm-virtual-machine-to-omnios-bhyve) 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 brad - bhyve (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/635/feedback/brad%20-%20bhyve.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

Why Self-host?, Advanced ZFS Dataset Management, Building a Simple Router with OpenBSD, Minimal pkgbase jails / chroots, WSL-For-FreeBSD, Yubico yubikey 5 nfc on FreeBSD, The Q3 2025 Issue of the FreeBSD Journal, 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 Why Self-host? (https://romanzipp.com/blog/why-a-homelab-why-self-host) Advanced ZFS Dataset Management: Snapshots, Clones, and Bookmarks (https://klarasystems.com/articles/advanced-zfs-dataset-management/) News Roundup Building a Simple Router with OpenBSD (https://btxx.org/posts/openbsd-router/) Minimal pkgbase jails / chroots (https://forums.FreeBSD.org/threads/minimal-pkgbase-jails-chroots-docker-oci-like.99512/) WSL-For-FreeBSD (https://github.com/BalajeS/WSL-For-FreeBSD) Yubico yubikey 5 nfc on FreeBSD (https://forums.freebsd.org/threads/yubico-yubikey-5-nfc-on-freebsd.99529) The Q3 2025 Issue of the FreeBSD Journal is Now Available (https://freebsdfoundation.org/blog/the-q3-2025-issue-of-the-freebsd-journal-is-now-available/) 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. Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

ZFS Features, Roadmap, and Innovations, Magical systems thinking, How VMware's Debt-Fueled Acquisition Is Killing Open Source, OpenSSH 10.1 Released, KDE Plasma 6 Wayland on FreeBSD, Unix Co-Creator Brian Kernighan on Rust, Distros and NixOS, Balkanization of the Internet, GhostBSD 25.02 adds 'Gershwin' desktop for a Mac-like twist, 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 What the Future Brings – ZFS Features, Roadmap, and Innovations (https://klarasystems.com/articles/zfs-new-features-roadmap-innovations?utm_source=BSD%20Now&utm_medium=Podcast) Magical systems thinking (https://worksinprogress.co/issue/magical-systems-thinking) The $69 Billion Domino Effect: How VMware's Debt-Fueled Acquisition Is Killing Open Source, One Repository at a Time (https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time) News Roundup OpenSSH 10.1 Released (https://www.openssh.com/txt/release-10.1) KDE Plasma 6 Wayland on FreeBSD (https://euroquis.nl/kde/2025/09/07/wayland.html) Unix Co-Creator Brian Kernighan on Rust, Distros and NixOS (https://thenewstack.io/unix-co-creator-brian-kernighan-on-rust-distros-and-nixos) GhostBSD 25.02 adds 'Gershwin' desktop for a Mac-like twist (https://www.theregister.com/2025/08/27/ghostbsd_2502/) Beastie Bits Adventures in porting a Wayland Compositor to NetBSD and OpenBSD by Jeff Frasca (https://www.youtube.com/watch?v=oo_8gnWQ4xo) 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 Kylen - CVEs (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/633/feedback/Kylen%20-%20CVEs.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

zipbomb defeated, Optimizing ZFS for High-Throughput Storage Workloads, Open Source is one person, Omada SDN Controller on FreeBSD, Building a Simple Router with OpenBSD, Back to the origins, Enhancing Support for NAT64 Protocol Translation in NetBSD, 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 zipbomb defeated (https://www.reddit.com/r/openzfs/comments/1niu6h7/when_a_decompression_zip_bomb_meets_zfs_19_pb/) Optimizing ZFS for High-Throughput Storage Workloads (https://klarasystems.com/articles/optimizing-zfs-for-high-throughput-storage-workloads?utm_source=BSD%20Now&utm_medium=Podcast) News Roundup Open Source is one person (https://opensourcesecurity.io/2025/08-oss-one-person) Omada SDN Controller on FreeBSD (https://blog.feld.me/posts/2025/08/omada-on-freebsd) Back to the origins (https://failsafe.monster/posts/another-world/) Google Summer of Code 2025 Reports: Enhancing Support for NAT64 Protocol Translation in NetBSD (http://blog.netbsd.org/tnf/entry/gsoc2025_nat64_protocol_translation) Undeadly Bits j2k25 - OpenBSD Hackathon Japan 2025 (http://undeadly.org/cgi?action=article;sid=20250601104254) OpenSSH will now adapt IP QoS to actual sessions and traffic (http://undeadly.org/cgi?action=article;sid=20250818113047) Preliminary support for Raspberry Pi 5 (https://undeadly.org/cgi?action=article;sid=20250903064251) OpenBSD enters 7.8-beta (https://undeadly.org/cgi?action=article;sid=20250911045955) Full BSDCan 2025 video playlist(s) available (https://undeadly.org/cgi?action=article;sid=20250912124932) OpenBGPD 8.9 released (https://undeadly.org/cgi?action=article;sid=20250926141610) 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 Brad - a few things (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/632/feedback/Brad%20-%20a%20few%20things.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

Welcome to a Morning Kombat Monday, live in studio! Brian Campbell and Luke Thomas are back to discuss the latest headlines in combat sports. First up, Nassourdine Imavov made his case for a middleweight title shot by outclassing Caio Borralho at UFC Paris. Did Imavov show enough to believe he's a threat for Chimaev's title? Also, Benoit Saint Denis took apart Mauricio Ruffy. Did this result prove that BSD is still a relevant force in the 155-pound title picture? Plus, the guys go over the latest storylines surrounding UFC Noche and Canelo-Crawford fight week.See omnystudio.com/listener for privacy information.