B (2:32)

Are there any local small town businesses anymore? It seems like not very many. There's a few. Well anyway, that is not what we're here to talk about. We're here to talk about Linux and Rob is Going to start out with a story that is not about Linux. That's all right. We love him anyways.

A (2:54)

50 50.

B (2:56)

I love you man. I love you.

A (2:57)

Rob, don't tell me the odds.

D (3:00)

Yeah, this runs on an OS that is Linux.

B (3:05)

It probably can.

E (3:07)

I'm sure it's fine.

D (3:07)

It's designed specifically for that.

B (3:10)

Oh really? Okay, Rob, take it away and tell us what have you done in your house that is presumably reportedly Linux related?

D (3:19)

So this is pretty much my review of the ZWA2. So a few weeks ago I co hosted Floss Weekly with Jonathan Bennett.

E (3:32)

And.

D (3:32)

We interviewed the home assistant founder Paulus Schausson. One of the things he talked about was the new Z Wave antenna for home Assistant. That is a Linux operating system. Home Assistant OS is a Linux operating system for home automation. And this, this antenna is called the ZWA2 obviously. So it's something they, they just came out with and they're selling. At that time I said that I unfortunately I went all zigbee instead of Z Wave, you know, not for any technical reasons. You know, when I set up my stuff I need to pick one as they seem pretty equal. So I just picked one and I couldn't find any real big tech technical reasons to go one or the other. Well, my zigbee devices have been hit or miss. You know, some would lose connections and I have to reset them to get them back and others would never get back on. The setup for zigbee was problematic all the time, even from the beginning. The, the process is to hold normally you hold a bun for like 10 seconds or 15 seconds until some light flashes and then you hope the home assistant would detect it. Sometimes it would. Sometimes one. Sometimes you're doing that over and over for a long time. So I finally decided, okay, I'm just going to buy the ZWA2 a few weeks ago and, and I bought a few Z Wave devices. I probably should just started with one, but I bought a few. So fortunately it worked out well. But I'll get into that because so far it's been a much better experience. And so, so my experience so far with the ZWe2 antenna, when I first hooked it up and passed through the USB through Proxmox to my home assistant vm Home assistant was supposed to automatically detect it. Now I did have a few problems here. I, I don't think it was, I don't think it was anything to do with the, the antenna, but get into that so because for whatever reason it wasn't just automatically detecting it, you know, it would pop up when I tried to add it through the interface manually. It would say, what location is this? Like DEV TTY01 or whatever. You know, I had some options or I could type it in. It's like, well, I don't know where it's at. So I looked into it and you know, I went to look, you know, the place I should be able to see where it was for a USB Device is dev/dev/serial/by Dash ID. The location, you know, I should be able to do it to find it, but that directory just didn't even exist. So I went into the system settings to reboot Home Assistant to the software way and went down, it came back up. So I'm not, but I'm not sure if this just resets the container that's on there and doesn't actually do a full system reset because that didn't work either. So after a couple times trying that and poking around, I'm like, okay, let's just do a hard reboot on the whole VM in it. And then after I did that, it just showed up automatically. I went, even after it showed up automatically, I went in there and the dev/dev/serial/ by id it showed it right in there that the USB device was there and it showed me where it was over in, in the dev location. So whatever reason just wasn't showing up the first time. So that I think, I think that might have just been somewhere glitch at the moment. Not anything against, not anything negative necessarily to Home Assistant or to the antenna. I think my, my Linux just being weird at that moment. So after that add a device, you know, I click add and then you just scan a QR code on the device and you know, you scan it into Home Assistant with the app and then it just showed up and worked way better than zigbee was. You know, since then I've already, you know, this hasn't been very long and I've already replaced most of my zigbee devices with Z Wave. Now one thing I didn't know is if, if the zigbee issues were with my cheap zigbee hub that I have or maybe the devices were cheap though is multiple different brands and everything just were goofy or, or if it's a protocol itself, I don't know. That was my experience. But the funny thing is after I had all set up, I went looking for some more Z Wave things to connect to my Home assistant and then I found they now have a Zigbee antenna called the ZBT2. So if I wait a little bit, I could have just gotten one of them and see if my ZigBee devices I had would work better with that. You know, maybe if the thing will just work great. I would have not have to swap everything out. I didn't have too many zigbee devices yet, just because it's flaky, but have.

B (8:55)

You dumped all of your zigbee stuff?

D (8:58)

So I'm down to three. I only have three zigbee devices left to replace.

B (9:02)

What you need to do. I think you know what you need to do. You need to buy the zigbee antenna now and see if you can run them side by side.

D (9:10)

So. Well, I know I could run it side by side.

B (9:14)

Well, there you go.

D (9:16)

Well, I am running them side by side, just not with the antenna. You know, I'll tell you what. If people donate a few copies, you don't need to donate the full price. Donate something towards it, and I'll chip in the rest and do it because I'm curious. But I also don't want to throw the money into it. And then, I don't know. I like the Z Wave so far better. But all of this is just to say I highly recommend the Z Wave antenna from Home Assistant. It reaches from the basement corner of my basement to the upstairs corner, far end of the house. No problem. And, you know, even if my zigbee were the issues with my hardware and not the protocol, like I said, the setup process was just so much nicer.

B (10:06)

So, yeah, interesting. It's a. The. The antenna. It is an ESP32 S3. It's the little microcontroller inside of there that's doing the. Essentially, it's just a USB serial bridge, but that's a lot of horsepower for just that. We're going to talk about that microcontroller later today.

D (10:25)

By the way, the antenna, I measured it. It's hooked up, so I didn't bring it over here, but I did measure before. It goes from my elbow to the knuckle right here. So it's more than a foot tall. So that's a decent antenna. It has a little glowing tip.

B (10:38)

Nice. Very cool.

D (10:39)

That you can turn off on and off in the interval.

B (10:42)

That's good.

D (10:42)

I don't like it.

B (10:42)

Yeah, that's good. You need to be able to map something because there's so many things inside of Home Assistant. You could map. Map the glowing antenna to, like you have a message waiting for you.

D (10:54)

I could, except for right now. It's like in a corner Where I'm not going to see it, but if I had that more in more of a visible place, yeah, that'd be great. You could map all kinds of stuff.

B (11:03)

To it, make it flash when the AI talks to you something.

A (11:08)

And just FYI, antenna length a lot of times has to do with the frequency and what pattern you want to come out of your signal.

B (11:18)

So overall length RF is such black magic. Oh, my goodness.

A (11:23)

No, it's just a lot of math.

B (11:25)

No, it's black magic. I am pretty sure when you start seeing antennas that AI design that actually work and all of the RF engineers look at it and go, we can't figure out how it works. That's when you know that you're talking about black magic and not just math.

A (11:43)

Anyway, back in my day, all we had was math. Well, I mean, that's calculus and that's the way we liked it.

B (11:50)

That's really all the AI is too. It's just really fancy math. Let's talk about some of the hardware that does all of that math and the software that lets you math the math on the hardware. Jeff has got a story about, about nouveau. I'm going to pronounce it right because apparently it's insulting when I call it no view on. On Nvidia hardware. What is the state of the art, Jeff?

D (12:14)

I think we call it no view because there was a time when, when you had. When you're using that one, there was no viewing.

B (12:21)

Yes, that's where, that's where the joke comes from. The. The only person growing up, the only person I had to talk about Open Source stuff, he called it no view. And I think he was in on the joke. He just never told me that. And so I was like a year into doing this show that finally we had a disgruntled listener said, you know that's not how it's actually pronounced, right? No, I didn't know that.

A (12:43)

Well, and we're not French, so that. That a lot of vowels in there can confuse us.

B (12:51)

That's true. We Americans get confused by vowels.

A (12:54)

I do think the show title should be Jonathan wasn't in on the joke.

B (12:59)

That works. All right, Jeff, take it away.

A (13:02)

So for a long time Nvidia has been in one controversy or another in, you know, recent Linux history. Well, longer than that. But we're just sticking it to recent. The latest issue was the driver was not open source and they didn't help the open source version of the driver. Novu never got any love from Nvidia. Not in recent history. Anyway. I mean there's some old cards that would they helped out. But again, recent history for more recent cards. Nova driver was missing a lot of features. You know, it was stuck at a lower speed, you know, it could never really ramp up the cards. There was a whole lot of issues and it just could not keep up with a proprietary driver in any way, shape or form. Well, in the not too distant past Nvidia opened up their driver kind of a little sort of the code they put into the kernel is now open source, but there's still a lot of closed source bits which are loaded in as firmware. So source concerning Nvidia Open source concerning Nvidia is still kind of a very gray area and yeah, meets the letter of the law maybe, if not the spirit of it. But I digress. The article in the show notes is dealing with benchmarking the open source Nova kernel driver using the open source Nvidia driver stack versus the closed source driver. Now there is an open source Nova driver from Nvidia for the kernel, but it isn't ready for end users yet. Still a little rough around the edges. The open source testing was also done. It includes the latest MESA NVK driver which is the open source Vulkan API support code and the NVK Vulkan driver is also used for looking into the OpenGL performance using the Zinc OpenGL on Vulkan driver which is now used for OpenGL on modern Nvidia GPUs rather than using the Novu Gallium 3D driver. So the the Rustcl driver for OpenGL compute is atop the NVK driver as well. And this is fully open source and the latest Nvidia Linux driver support. So that was all compared to Nvidia's official 580 series Linux driver. So both 40 series and 50 series cards were used on three different with three different drivers. There was the NVK which is the out of the box driver is found in Ubuntu 2510 with the 6.17 kernel and Mesa 25.2 there's an NVK git which is like it sounds the latest greatest code from November 24th it's got the 6.6.18 git kernel and because we don't have the 618 released yet and Mesa 26.0 development. So this is all the latest greatest code he that Michael Erbal could pull out of the git repository. So it's not released, it's not in a final finished state. And finally we had the Nvidia 5809505 driver. So Ubuntu 2510 was the OS that these all ran on. And unless I otherwise stated, like I said, like the, like the kernel, everything was out of the box how it installs. So the out of the box NVK driver was just straight up Ubuntu 2510 NVK kit was 2510 and then adding the latest git source and then the Nvidia driver was just how it installs on 2510. Well, is it good news? Well, kind of. If you look at the long term right now you can expect overall about a 50, 50% less performance out of the open source driver than the proprietary driver. Compute is one area where some of the benchmarks in the open source held. Held right in there with the closed driver, but others didn't fare so well. Now why did I start out with good news if. Well, if you look at the long term first, if you go back to the benchmarks like this that were ran In July, the 50 Series cards couldn't even run. So there's been a lot of progress there. The second thing is out of the box driver is about 20% slower than the latest git code. So that means that the, the latest code coming there, there's substantial performance improvements in the pipeline. Now there were a few benchmarks on the 470 which had some issues with the git code where the 480 ran just fine. The 5000 series card was a 5080. But this git code, not full release, like I said, there's going to be issues. So the fact it didn't run on a few benchmarks, not a ton, just a few, shouldn't be surprising. But if you look through where we were and where we're at, there's more working hardware and just from the official release, I mean there's a 20% increase improvement. So that's quite a bit. And there's headway being made and things are getting a lot better. So not where we want it, but the gap is closing and noticeable progress is being made. So I think the future is going to look pretty bright for the open source driver.

B (18:39)

Yeah, very cool. And there's also Nova from Nvidia. How does that fit into this? That's like their new next generation driver, right? The Nova?

A (18:49)

Yeah, they're kind of the way I, the way I'm understanding is the, the Novu is what's kind of used to the. It's the interim open source solution until the Nova driver is Fully ready because like I said, it's not, it's not ready for end users yet. So they're still. Still working on it, but my understanding that'll kind of be the replacement for Novu.

B (19:11)

Yeah, makes sense. Very cool. All right, Rob, did you want to comment on this or are you still not enough of an Nvidia fan to have anything to say?

A (19:24)

Good luck.

B (19:25)

There you go.

A (19:27)

Well, and AMD now has a little more pressure on Nvidia because they basically went to the open source driver as their, you know, that's, that's what they're. So everybody can get in and help optimize and yeah make things better.

D (19:43)

One day you Nvidia folks will be with the cool crowd.

B (19:49)

It's coming.

D (19:50)

Yeah.

A (19:50)

And that's, and that's why I hope COMPUTE fully catches up to speed. I hope their hardware catches Nvidia's hardware for compute.

B (19:58)

Yeah. All right. One of the other things we've been tracking for a while is the troubles at intel and how they have. They've dropped lots of positions, not just open source stuff, but it has hit their open source teams pretty hard at intel. And so I saw this and I thought oh well this is good news and we should celebrate it. There is a. There are two positions open. Kristen Accardi talked about this on LinkedIn. Hiring two fairly senior kernel engineers in Oregon actually. So your stateside looking for basically people to work on intel optimized system software for the Linux ecosystem. That one's a senior level position and then another kernel engineer for various OS internals for unnamed intel device drivers. And both are rather nice as far as their salaries. Nice six figures but I just found and so obviously if anyone listening is an OS driver writer, if you have patches in the kernel and this is something interesting to you, go reach out to them and see if you are the right fit. It would be extremely fun to have a fan of the show there. But other than that I just thought it was pretty neat to see that intel and at least some of their places are on the hiring path and looking to bulk out their numbers as it were to bulk up the their Linux chops once again. So not all is bad news. There was good to see.

A (21:42)

Hiring at intel. That's definitely a good thing. And I do want to preface that that we say there was huge cuts but there was also some voluntary packages and depending on where you're at in your career or if you think oh maybe I might get cut, you were better off to take the package than you were to stick around and then get cut where you didn't get a package. So there are some people that left that probably would never have been cut, but they either said now's a good time to get out because I'm worried about it, or, you know, sometimes you have a developer or anybody in that's been there for, you know, maybe 20 years, 30 years, and go, I'm ready for something else. Oh, I get a bonus for leaving. Perfect time to jump ship.

B (22:27)

I mean, sometimes folks just need a break.

D (22:29)

Yeah, yeah.

B (22:30)

That whole. The idea of a sabbatical, like let me work for seven years and then take a year off, like there's something to that. There is something to be said for finding a time to let yourself rest if you've been going 247 for too long.

D (22:44)

Yeah, yeah. I wonder where these, these two roles where they fit. And I assume they must be people who weren't necessarily pushed out unless they weren't doing a good job, but maybe people who kind of fall under that umbrella where they just want to leave or chose to leave for one reason or another.

B (23:03)

Yeah, it's hard to say. We don't even know for sure that there was someone filling these roles previously. Maybe they're new roles as part of the restructuring. Not, not a whole lot of insight into this, but, you know, just get to see that it's there and it's a thing. Yeah, I just saw something pop and I'm trying to figure out if we need to talk about it and where. I think this might be a good place to slot it in. And that is that this weekend. So possibly before the majority of our listeners get to the show, 618 is going to release. So it is the kernel weekend, which is always fun and, you know, kind of, kind of on point for talking about intel hiring on more people to work on this. Of course, there are some intel stuff that have landed in 618. There's not a whole lot of really, really huge news in the 618 kernel. It's not going to say it's boring, but it's boring.

D (23:59)

Is a good place to be an lts. When did they decide that? They decide that later. Right now.

A (24:06)

It'Ll probably be this one because it's the last kernel released in the year and the next kernel will carry over into January sometime. So 18, I'm pretty sure is going to be the LTS.

B (24:18)

This article says that Linux 6.18 is anticipated to become this year's LTS kernel. So we're about to open the 6.19 merge window. And then the other anticipation that people are saying is that we're probably not going to have a 6.20 because Linus Torvalds does not like big numbers. So we're probably going to have a 7.0 pretty soon next year. And so that will be fun to see. Do the kernel numbers mean less than they used to? But it's still fun to see them?

D (24:48)

Yeah, they mean more than other numbers and some other software applications that they choose to use.

A (24:54)

It's true for, for anybody newer. It used to be that the, the whole numbers and you know, like if you went from a 2 kernel to a 3 kernel that was huge. That meant there's a big rewrite in there and then they had the next number was the. It was, it was only the evens were actually released kernels and then so you might have a, a 2.2 kernel that was released and then you have 2.3 that was like your RCS are today. And when the 2.3 was kernel was ready to be released, it turned into a 2.4, for example.

B (25:28)

Yep.

A (25:28)

Then they said, yeah, we're not doing any of that.

B (25:30)

Who care? Who cares? Semantic versioning. Who needs it? It's for the birds. All right, so up next we've got Rob talking about another office option. We're going to let him get to it. Ready for this?

A (25:42)

Imagine you're a business owner relying on a dozen different software programs. Each one is expensive, overly complicated, and worst of all, none of them are connected. It can be incredibly stressful right now.

B (25:55)

Picture Odoo CRM, accounting, inventory, manufacturing, marketing, HR and more. Odoo brings all the tools your business.

A (26:04)

Needs into one simple platform. And all seamlessly connected. Everything works together, giving you the peace of mind that your business is running smoothly from every angle. Odoo's open source applications are user friendly and designed to scale with your business, saving you time and money. Say goodbye to juggling multiple platforms and hello to efficient integrated management. Stop wasting resources on complicated systems and make the switch to odoo today. Visit odoo.com o d o o.com and discover how Odoo can simplify and streamline your business operations. Odoo Modern Management Made simple.

D (26:42)

Okay, only 10 more presents to wrap. You're almost at the finish line.

B (26:48)

But first, There the last one. Enjoy a Coca Cola for a pause that refreshes.

C (27:12)

Hey, it's Ryan Seacrest for Albertsons and Safeway. As winter approaches, make sure you set aside some time for self care. Now through December 2nd, get great savings on personal care essentials. When you shop in store or online, buy two participating self care items and save $3. Shop for items like Tresemme Shampoo, Dove Shampoo, Dove Men's Care Body Wash, Dove Body Wash and Axe Shower gel and save $3 when you buy two or more items. Offer ends December 2nd. Restrictions apply. Offers may vary. Visit albertsons or safeway.com for more details.

E (27:43)

Hi, I'm Leo Laporte, host of this Week in Tech and many other shows on the Twit Podcast network. Can you believe it? 2026 is around the corner. So this, my friends is the best time to grow your brand. With Twit, nobody understands the tech audience better than we do. We love our audience and we know how to effectively message to them. We develop genuine relationships with brands, creating authentic promotions that resonate with our highly engaged community of tech enthusiasts. You know over 90% of Twitch audience is involved in their company's tech and IT decision making. Can you believe that 90%, 88% have actually made a purchase based on a Twit post read ad. No one comes close. We're the best at this. As one Twit fan said, I've bought from Twitt TV sponsors because I trust Leo and his team's knowledge of the latest in tech. If Twit supports it, I know I can trust it. You cannot buy trust like that. Well, actually you can.

D (28:47)

You can buy an ad on Twitter.

E (28:48)

All our ads are unique. They're read live by our expert host, Micah Sargent me. We simulcast all during the shows on our social platforms so everybody can be watching live. You know one of our customers, Harun Meer, the founder of ThinksCanary, he's been with us since 2016. Since 2016. He said we expected Twit to work well for us because we were longtime listeners and who over the years bought many of the products and services we learned about on various Twitch shows and we were not disappointed. The combination of the very personal ad reads and the careful selection of products that Twit largely believes in gives the ads an authentic, trusted voice that works.

D (29:29)

Really well for our products.

E (29:31)

10 out of 10 we'll use again. Thank you Harun. We love you. And it's been nine years. That's kind of. That's the proof, right? Partnerships with Twit offer valuable benefits including over delivery of impressions. You get presence on show episode pages. So there's a link right there that our audience can click on. We're in the RSS feed descriptions, a link there too. And social Media Promotion. Our full service team will craft compelling creative to elevate your brand and support you throughout your entire campaign. I work on the copy myself to make it authentic, to make it real. If you want to reach a passionate tech audience through a network that consistently over delivers, please contact us directly. PartnerWIT TV that's the email address PartnerWIT TV let's talk about how we can help grow your brand. Or just go to Twit TV advertise for more information. I look forward to working with you.

D (30:31)

Thanks for listening. So all right, so there are already a lot of good open source Office solutions available for Linux, but there are often aspects about them that people don't like, things that people have trouble with that it's a deal breaker for them for some reason to move over. Well now there is a new kind of new option to try. New to the desktop at least, but not a new Office solution. Exactly. So Collabora has been providing a web based Office solution for years and has been the choice partner for solutions like Nextcloud. Collabora Online is based on the core technologies in LibreOffice and is one of LibreOffice's largest contributors. You could almost think of it as a distribution based on LibreOffice but online? Well no longer is it limited to being online only as they now have released a desktop app for Windows Mac and of course that's why we're here Linux. So if you know if based on LibreOffice why Collabora? You know first what they say is a simpler stack while still based on the labor Office core technologies. Collabora Office has no Java dependencies which means a cleaner install, smaller footprint and a single self contained download. A quote from Frank Karlachchick, CEO and founder of nextcloud. Quote says nextcloud has a long standing close partnership with Collabora and we are pleased to have been able to bring our UX Engineer engineering expertise to help make collaborative Office more ergonomic and intuitive. This combined with a strong privacy first design and document interoperability powers nextcloud Office as an excellent match for our users and customers needs. So in the past the biggest complaint with open source options has been compatibility with Microsoft Suite, but these days that's it's pretty solid for the most part. You know there's some things here and there but I think a lot of people now just complain about the look and the user interface. You know LibreOffice is is getting better but I think the look is still kind of looks out. Excuse me, looks outdated. You know that is one area Collaborate seems to shine. So let's have a look at the new app. So for those watching here on the screen here, this is a collaborative, the tech space. So it has, has the ribbon. A very clean design. You know, if I want to Compare this with LibreOffice, this is what LibreOffice looks like and it looks like icons from about 2001. I know there's themes and stuff, but default is king. Going back to Collaborate, you know, here's the spreadsheets, very clean look. Somebody coming from Microsoft Office. It's not identical, but the look would be very comfortable to them. And it's very, very, very streamlined, very sleek.

A (34:10)

I believe I was gonna say it reminded me. It reminds me a lot of Excel, the spreadsheet program. You have a very similar.

B (34:18)

Yeah.

D (34:18)

And I haven't played with the PowerPoint alternative they have, but they also have that. So it's basically their word processor, their spreadsheet and a PowerPoint alternative. If you hit file open, oops, I didn't want to do that file. And then right here you can do a blank document, blank spreadsheet, blank presentation. They have a template so that already in there. So I think it's something that could be very, a very comfortable alternative for Windows users. And this is, I forgot it's, it's not like it's not their final release yet. This is our first initial. I don't know what they're calling it, beta maybe, but I think it looks very promising. It has a very clean, modern look. And now with a desktop and web based offering, you know, that could make it more and more like a Microsoft 365 contender. So that's new this week.

B (35:24)

Yeah. Interesting. I'm glad that LibreOffice still exists because I don't want my desktop to look like a Microsoft product. So kind of a, kind of a downer for me. But that's all right. It's cool that it's out there.

A (35:36)

I kind of like the interface because one of the things is I use LibreOffice all the time and sometimes it's like, oh my gosh, there's 600 icons here. It's like, which thing do I need? And it, you know, it's cleaner. Yeah. Now was there any feature loss or.

D (35:52)

Is it just between the web interface.

A (35:56)

Or between, between the core LibreOffice and this new.

D (36:03)

I don't know, I don't know necessarily between the core LibreOffice between the web interfaces. There are minor changes here and there, but it's early days.

B (36:14)

So one other interesting Little tidbit. You talked about getting away from Java, which is nice not only for smaller download and fewer system dependencies, but it also gets you away from Oracle. And it's sort of having anything to do with that weird, potentially problematic whole licensing scheme. I know Rob has probably run into this. We used to be able to just grab Oracle's Java Java SE and install it for people and then suddenly they said, nope, you don't get to do that anymore. And the world sort of had to scramble to go, oh no, what, what Java do we use? And you know there's open jdk, you can install that on Windows. And of course it's easy, easy on Linux. But yeah, not, not being dependent upon that mess is kind of a good thing.

D (37:01)

I've always hated Java, even long before that. The only thing Java ever had going for it is its cross platform compatibility, in my opinion, the fact that you could write once and pretty much run the same app everywhere. But other than that speed and everything about it. And I tried to learn, at one point I had a class on it. I did great in the class. But I took the class on in college and thinking maybe if I have a formal class I'll actually like it. And no, I still hated it. It's horrible.

B (37:36)

I have, I have not found that having a formal class on something has ever made me love something.

D (37:42)

No, well, I mean I, I, I'm like, I gotta try to learn it. I was like, God, it's horrible. Maybe, maybe the books just aren't. Maybe I need somebody to, to formally teach me. It's like, nope, this is still stupid.

B (37:54)

Yeah, yeah.

A (37:57)

Well now unless they changed it, you could get Java from Oracle. You just had to create like an account and say that it was personal and not going to be used for business and non commercially used. Yeah, which it was. It wasn't just like, oh, downloaded, it was.

B (38:12)

Which by definition means it is not open source. That is a violation of one of the tenants of the open source model. So therefore that is not an open source license to source available license. Get that out of here. We don't want that.

A (38:27)

I never got into Java programming, but I will say Python I wasn't a fan of at first until I got some training on it and then I went, oh, I get a lot of this stuff now. And it, I love it. So learning more about it has improved certain things for me.

B (38:43)

Oh now don't, don't misconstrue what I said. Learning more about something can make you fall in love with it. Yes, getting A formal class on it has never made me fall in love with something. I very much enjoy learning about things, but not going to lectures with a bunch of other people in a formal classroom that I have trouble with.

D (39:03)

For my degree, I needed a class and I'm like, well, let's take this one. I've always wanted to figure out how to learn Java and I just struggled by myself.

B (39:13)

There you go. All right, Jeff, let's talk about colors. What's new in colors in Linux?

A (39:21)

So what do we say? A ton on this show and it seems to be creeping into everything and a lot of people don't take advantage of it. When you were thinking of two vowels. No, I'm thinking HDR. Valve has jumped on the trend and is now supporting a color pipeline API and it's finally ready for upstream entry into the kernel. The major amount of work has been on the AMD Radeon driver for a couple of reasons. One is the Steam hardware and the Steam deck and the Steam machine, you know, both use AMD hardware. There's also been some hardware capabilities which are recent in the AMD hardware, so they they've just added some hardware features in this last generation or so. They've had 13 revisions of this code to make sure it was working as intended before waiting to submit it into the kernel. So initial implementations are for the AMD GPU DRM driver as well as the virtual KMS or VKMS driver. And Valve had a note describing this which I won't read because it's describing hardware functions in the amd dcn version 3 or later. Unless you're a a driver coder, I don't think any of it will mean anything to you. I know it sure didn't for me. Also I will say the DCN is the display core next, and it's the architecture for AMD's modern display engine found in their GPUs and APUs. It's a flexible hardware pipeline designed to handle display related tasks, from processing pixel data and managing color to outputting signals to various monitors, things like that. The code is in the DRM next, so that's where you put your code to get included into the kernel. But it's late in the cycle and normally the cutoff for making it into the kernel is at the previous kernels RC6 stage, so it probably isn't going to make it into 6. 19. The thought is it will probably hit kernel 7 or like we said, but what everybody thinks is probably going to be seven, you know, unless Linus changes his mind, which has happened. So what does this do? You know? H. Now this is something that I'm not sure everybody realizes. HDR is not just a switch you can turn on because there's a lot of different color content sources, there's a lot of different color profiles, different color gamuts, and the support still needs to be there for the standard dynamic range. So it's not just, oh, going to open it up to 32 bit color and away we go. No, there's also a wide range of display devices and they don't all show color the same way. So this, this code also handles an interface to. To be able to handle a wide range of color profiles. So basically that means when you see a specific shade of green, it will show up on different hardware and for others as the same shade of green. There's also other benefits to handling color which are a lot faster than the current software methods. The API is already supported in Valve's GameScope, which is a compositor which is built to optimize games. Because it's so focused, it's sometimes referred to as a mini compositor. KDE Kwin and Whalen Weston implementations also support the new API. Now that the color API interface has been solidified, expect a lot more compositors to support the new color interface. So you can take a look at the article linked in the Show Notes for more details and links to the original presentations on what's happening in the hardware stack with the different supported features. And they go in and explain in there how all this other stuff and what building blocks in the hardware it interfaces with and. But again, unless you're really kind of into the driver stuff, I don't know as you get much out of it. But you know, the information is there if you care to look. So I think I can say that the future is looking bright and colorful.

B (43:33)

The future is looking bright. This is. This is mainly to do hardware based HDR rendering. Right? Like, yes, Accelerated hdr.

A (43:44)

Yeah. Right now there's kind of some software. It's handled a lot in software, but hardware can do it just about instantly for almost no overhead. So it'll speed things up there. And it's just a common interface for HDR is not just HDR because there's so many different variations of it. Right, right, right. Yeah.

B (44:08)

It's unfortunate that we will probably not ever see what is it Dolby Vision or if we do, it'll be half of forever until we see it on the Linux desktop. That's another one of those HDR implementations. Probably not going to happen anytime soon.

A (44:22)

I'm going to talk about why, because that's probably licensing.

B (44:27)

I'm going to talk about why. We'll get there. Let's, let's unpack this right after this.

C (44:32)

Hey, it's Ryan Seacrest for Albertsons and Safeway. As winter approaches, make sure you set aside some time for self care now through December 2nd. Get great savings on personal care essentials when you shop in store or online. Buy two participating self care items and save $3. Shop for items like Tresemme Shampoo, Dove Shampoo, Dove Men's Care Body Wash, Dove Body Wash, and Axe Shower gel, and save $3 when you buy two or more items. Offer ends December 2nd. Restrictions apply. Offers may vary. Visit albertsons or safeway.com for more details.

D (45:03)

Okay, only 10 more presents to wrap. You're almost at the finish line.

B (45:09)

But first, There the last one. Enjoy a Coca Cola for a pause that refreshes High interest debt is one of the toughest opponents you'll face unless you power up with a SOFI personal loan. A SoFi personal loan could repackage your.

A (45:42)

Bank bad debt into one low fixed rate monthly payment.

B (45:45)

It's even got super speed since you.

A (45:47)

Could get the funds as soon as.

B (45:48)

The same day you sign. Visit sofi.compower to learn more. That's S O F I.com P-O-W-E-R loans originated by SoFi Bank NA member FDIC. Terms and conditions apply.

A (46:01)

NMLS 696891 hey everybody, it's Leo Laporte.

E (46:05)

You know about Mac Break Weekly, right? You don't? Oh, if you're a Macintosh fan or you just want to keep up what's going on with Apple, this is the show for you. Every Tuesday, Andy Inocco, Alex Lindsey, Jason Snell, and I get together and talk about the week's Apple news.

B (46:21)

It's an easy subscription.

E (46:22)

Just go to your favorite podcast client and search for Mac Break Weekly or visit our website Twit TV mbw. You don't want to miss a week of Mac Break Weekly.

B (46:32)

All right, so as I was hinting about, we're actually talking about patents this time. And for those of us that have been around the Linux desktop for a while, software patents are not our friends. So let's think back through this history of software patents and the things that you couldn't do on Linux for the longest time because of them. One of the ones that annoyed me the most for years and years, and this still will get you Depending upon what you want to do. You couldn't listen to MP3s because MP3s were patented and most of the distros for legal reasons were not willing to ship code that, you know, in theory violated those patents. It was not that very many years ago that finally the lawyers at places like Red Hat signed off on it and said, okay, it's been long enough that no matter what legal shenanigans, you know, Impeg La or whatever licensing group used, no matter what legal shenanigans they used, those patents are finally old enough, we don't have to worry about them. So now, hey, we can listen to MP3s on our Linux desktop. It's really, it's really great. Now that, you know the entire world has moved past MP3s, we finally have support for them. Another one was compressed texture uploads for video cards. It was another bit of patented technology and that was a problem in WINE for the longest time. WINE and also your video card driver is these games would have compressed textures and you just for legal reasons weren't allowed to upload them. We still have some problems with patents and if you dive into things like the, the HDMI, what is it? Is it 2.1 I think, I don't remember the exact numbering, but AMD cards just can't support it because of the licensing. And well, guess what it is that's behind a lot of those licensing issues is the patents that get used. So it's still a thing that is with us and is painful from time to time. Well, what's the news today? The news today is, or this week is that the US Patent Office is making a change that unfortunately is going to make it a little bit harder to challenge bad patents. So this is one of the things that companies have done, companies and individuals, open source people have done over the years is when one of these patents gets written and granted, that is an obviously bad patent, they're able to challenge it through an ipr, an inter parties review, which basically is where someone says, hey, I have documented evidence that says that they were not the inventor of that patent. And you can do an ipr, you can send it into the patent office. The poor overworked people at the patent office will look at that and make a determination of either, you know, yes, this is sufficient evidence or no, it's not. And bad patents have gotten dismissed and thrown out as a result. The new change is the change to that IPR which says two things. One, if someone files an IPR against a patent, they give up their right to litigate about that patent. So it's, it's a, they, they sort of dismiss their future claims with prejudice. And the other change is that if a patent has been tried, if there's an exist, if there's existing case law regarding a patent, then you cannot do an IPR to challenge it. You can only challenge it in court. And so this really narrows the ability to use this particular. And an IPR is basically free. There may be a small charge, but it's not anywhere compared to the huge cost that it is to challenge a patent in a full court. That is expensive. And so what this change does is it narrows the usability of this IPR process, which again, unfortunately is one of the few ways that individuals and small companies have to challenge a patent. It doesn't make it impossible, but what it does is it means that if you're going to do this, there has to be some strategic thinking, let's say, because what you would need to do is make sure that the IPR challenges come first. And then if they get thrown out, you have to. IPR challenges has to come first and not from the people that would then want to litigate the patent. Right. It has to come from like third parties. And then if that fails, then you would have to go into litigation against the patent to try to get it removed. And so it just, it, it turns the whole thing into even more of a minefield. And it absolutely is, which is really unfortunate because software patents are such a terrible idea and have always been a problem. So that's my, that's my legal, legal rant for the day. Hardware patents, not so bad. Software patents, garbage and need to go away.

A (51:56)

Hardware patents even need a limited shelf life. But I can tell you a lot of cutting edge stuff. There's companies that don't patent things because once you patent it, it's public knowledge. So they just keep it internal and keep it hidden and.

B (52:12)

Well, because there are companies in other countries, I won't exactly name which one. We know which country they don't care if you have a patent on. They'll still make it in their factories.

D (52:22)

Yeah, yeah. Trade secrets.

A (52:25)

Yep, yep, yep.

B (52:26)

Absolutely.

A (52:27)

That's why you won't find Colonel Sanders 11 herbs and spices on the patent anywhere. Patented, indeed.

D (52:35)

Yeah. You had to go to TikTok for that.

A (52:37)

Yeah.

B (52:41)

Yes. Yeah. I don't, I don't know if we would ever be able to do it. Goodness. Right now we can't, we can't get our politicians to agree on the color of the sky. It seems like in the United States and around the. What's that, Jeff?

A (52:57)

Well, I was gonna say we couldn't get him degree on daylight removing daylight savings time.

B (53:01)

Indeed. Yeah. The United States and around the world. We could really use a review on intellectual property because copyright is insanely too long and there, you know, there are works that are literally being lost because you can't preserve them because it would be a copyright violation.

D (53:22)

Off topic. I don't think the real problem with daylight savings time is that they can't agree to get rid of it. I think they can't agree which way to go.

A (53:32)

Yeah, that's true, but they can't agree.

B (53:34)

Yeah, indeed, indeed.

A (53:37)

And that's one company that kept copyright going longer and longer and longer. Yeah, it was until they realized that they could trademark things. And trademarks don't have a limitation like copyrights do. But you're right, Google tried to save a bunch of books and digitize some old ones and there were people that oh, you're, you're the rights holder to this book. And they had no idea because they're. Their great uncle twice removed had written something in 1935 and it was a little book that never went much of anywhere. And through people dying and natural, you know, oh, here's a family tree. Oh, I guess you're the next in line. You own this and no idea, you know.

B (54:17)

Yep, yep.

A (54:18)

Or they can't even find who now is the rights holder, so it blocks them.

B (54:23)

Yep, absolutely. All right, well that's enough of that kind of a macabre topic. Let's move on to something a little bit more cheery. No, it's not more cheery, is it, Rob?

D (54:39)

No, something at least a little bit more Linuxy. Somebody who's trying to call out people for doing non Linux shows as a law segment.

B (54:51)

Well, it's Linux adjacent. I was hoping for some cheer though, Rob, and you're not bringing any cheer at all.

D (54:57)

No cheer. We are losing a popular Linux distro. So this is a. It's a Linux story. It's an Android story in what I'm talking about. It's, it's the future of Chrome os. So Chrome OS is about to. About as close to a Linux distro as you can get without being called a Linux distro. It's much closer than Android for sure, because Android is based on the Linux kernel, but it pretty much ends there. It's, it's, it's never listed in the official numbers, but unofficially Chrome OS adds a few percentage points to The Linux desktop base. So I like to call Linux Desktop. But if Google's plans work out for them, we will be losing Chrome OS as Linux distro as Google's new aluminum OS or Aluminium OS as some of you out there might call it project brings Android to the PC so well again. It's not like we haven't had Android x86 available for PCs for years, but this time Google is doing it. A year ago, Google quietly began reshaping its desktop ambitions. Instead of keeping Chrome OS and Android on separate tracks, the company decided to fuse them into a single platform and push Android directly into the piece into the PC world. A recent Google job listing spells out that this is an Android based operating system for laptops, tablets, detachables and small box PCs built with AI at its core. It's a. It's.

B (56:50)

Yeah, that's exactly what we need. That's what the world needs is desktops with AI at their core. Because that's working out so well for Microsoft right now.

A (56:58)

Sorry, avoid those two letters we tried.

D (57:02)

Yeah, so anyway it's, it's tightly linked to Qualcomm, with both companies pitching this as a way to merge mobile and desktop computing and bring Google's full AI stack to them. Or my opinion, they could just go straight Linux on the desktop and phones, you know, merging them together. You know, if you build it, they will come do the right thing. Google, remember your old mantra. But let's continue to continue with the story here. The plan for Aluminum OS or Aluminium os. It's not just for cheap hardware. The roadmap calls out several tiers Al Entry, Al Mass Premium and Al Premium alongside their Chromebook and Chromebook plus tiers. That tells us Google wants Android PCs that span from budget to high end machines, directly challenging Windows, Mac OS and Linux. That wasn't called on this article, but I had to throw in there. Obviously it's challenging Linux too. Maybe it's not really, but instead of saying, you know, instead of staying in the low cost Chromebook niche where they have been but you know, it's not like they haven't tried the premium market before with their premium Pixel books. That mostly failed though I know Jeff Jarvis loved his so the same job listing says the role will manage both Chrome OS and Luminous while also developing a strategy to move Google from Chrome OS to Aluminum without disrupting businesses and schools that rely on Chromebooks. In practice, that likely means legacy Chrome OS devices get maintained until their normal end of life. Some newer Chromebooks, like those with MediaTek Companion 520 or Intel Alder like chips may be eligible for an optional upgrade. New devices, though, will eventually ship with aluminum OS outside of the box and will hopefully fail boo to aluminum os. Internally, engineers are already labeling using the label like Chrome OS classic and non aluminum Chrome os, hinting that Google might keep the Chrome OS name even if the underlying system becomes Android based or alternatively marketed as some form of Android desktop. The exact branding still is undecided, but what is clear is the timing. Google is testing Android 16 builds on development hardware now and has confirmed a 2026 launch window for Android on piece. Given that schedule, the first public aluminum OS release will likely arrive on top of Android 17, making the marking the moment Google tries to turn Android into a full spectrum desktop platform. You know, much of the story reminds me of the Apple memes, you know, where iOS comes out with a great new feature that Android already has and they pretend that, hey, we invented this new thing, you know, because almost a decade ago when I was working in a computer sales and repair store, we sold an Android desktop computer. Well, okay, we sold like one. We only sold one. That's all that anyone ever bought. We had a few more in stock, but you know, we, we really sold. We sold one to an older guy. It worked out really well for him, but it never became popular. So it's not like it hasn't been done before. Android X86 has been a thing anyone could install and play with for years that never really took off. Anyway, my point is it's been done. It's never really took off before. And I hope this initiative doesn't take off either. Just go pure Linux. Stop the insanity. Do the right thing, Google.

B (60:56)

So I'm imagining the way that this meeting went at Google's corporate level. Some very excited somebody up there in the halls of power went, I know the perfect name for our new AI. Did you know that there's an element on the periodic table that uses AI that's, it's, it's elemental symbol is AI and it's big. No, no, it's, it's Al. But your font, you just can't tell the difference. We have this all the time over on Hackaday because we have Al Williams and Al looks like AI. And so this, this article written by Al, not AI, gets us all the time.

A (61:36)

And that should be aluminium. It's, it's spelled the British way.

D (61:40)

Oh, is it spelled the British way?

B (61:42)

Probably because of chromium, right? Chromium intended to rhyme. Yeah, yeah, like I said, somebody thought they Were being super clever with this.

D (61:52)

So much cleverness going on here. Yeah, it's so much clever.

A (61:57)

The English ends in N u m and the British version ends in ni u M. And that's how they have it spelled, at least in the article anyway, is with the. The extra.

B (62:07)

I beat you, Rob. I beat you. I heard him start typing like, oh.

D (62:13)

He did beat me. I was scrolled up so I didn't see it. I was exactly that.

B (62:22)

Oh, that's fun. That's fun. All right. Ye. I'm not super excited over the aluminium desktop either. It's bad enough running Android on my phones. I will at some point look, I think, a little harder into the Linux phone idea.

D (62:40)

Well, sure. And we've had stories earlier this year about how they're making Android worse.

B (62:46)

So, yeah, it's not coming from my desktop. Not anytime soon. All right, we have a story here in just a second from Jeff about desktop stuff that we can absolutely get behind. Behind.

A (62:58)

And it's Linux.

B (62:59)

And it's Linux this time. We talk about that right after this.

D (63:03)

Okay, only 10 more presents to wrap. You're almost at the finish line.

B (63:09)

But first. There, the last one. Enjoy a Coca Cola for a pause that refreshes.

C (63:33)

Hey, it's Ryan Seacrest for Albertsons and Safeway. As winter approaches, make sure you set aside some time for self care now through December 2nd. Get great savings on personal care essentials when you shop in store or online. Buy two participating self care items and save $3. Shop for items like Tresemme Shampoo, Dove Shampoo, Dove Men's Care Body Wash, Dove Body Wash and Axe Shower gel. And save $3 when you buy two or more items. Offer ends December 2nd. Restrictions apply. Offers may vary. Visit albertsons or safeway.com for more details.

E (64:05)

Hey everybody, Leo Laporte here and I'm going to bug you one more time to join Club Twit. If you're not already a member, I want to encourage you to support what we do here at Twitter. You know, 25% of our operating costs comes from membership in the club. That's a huge portion and it's growing all the time. That means we can do more. We can have more fun. You get a lot of benefits ad free versions of all the shows. You get access to the Club Twit discord and special programming like the keynotes from Apple and Google and Microsoft and others that we don't stream otherwise in public. Please join the club. If you haven't done it yet, we'd love to have you find out more at TWIT TV Club Twit and thank you so much.

A (64:52)

So KDE has had an announcement this week that they're going to drop support for X11 in Plasma 6.8. Now we're currently on Plasma 6.5 and 6.6 should be released in February if the schedule holds. Now this means that X11 will be supported if you extrapolate out the suggested timelines into early 2027 Again, if the schedule holds, I mean, you know that's just projected timelines. There could always be a shift in releases, you know, technical errors, whatever. But KDE has been fairly decent about holding pretty close to that. There's even talk that maybe they would support 6.7 a little longer with some X11 bug fixes and patches, but that's not been full decided. So right now early 2027 is the end of X11 on KDE. Now if you really need to have X11, you know, they, they suggest there are still long term support releases which you'll be able to run. And the example in the article they give is Alma Linux 9, which includes X11 and it'll be supported until 2032. So if you, if you have X11 application and if you have app X11 applications, they'll still work using X Wayland and they're not removing that. They're only removing the ability to run on anything other than Wayland. So your favorite X11 application will still work. It's just running a compatibility layer, kind of like Wine does for Windows programs. You know, you can think of it that way. Accessibility is one area where Wayland is working hard to make sure there are no gaps. KDE says they're up to, to the X11 standards for accessibility features, but if you have third party programs, the same can't be said. There's some 30 third party application accessibility apps that may or may not work. The article linked in the show notes does ask that if you have accessibility features that you need and it isn't already covered, let them know because they're very interested in improving this aspect of kde. They want to make sure that KDE is accessible for everyone, no matter what disability you might have. So you know, if you, if you see a gap they, they definitely want to know. Now for those who don't know Plasma 6 point in Plasma 6.4 they split Kwin into two programs. They've got Kwin, Wayland and K win x11. So it, it makes this split easier because what they'll do is they'll just stop including Kwin x11. So why are they doing it? So they're, they're saying that While split, splitting K1 into two pieces helped development a lot, there's still many other areas of the desktop which are held back because of X11. So there's a lot of, you know, like the frameworks for example, they, there's just having to always include the X11 code that's causing them kind of some heartaches. So they say that dropping x11 will help them be more nimble and agile and save on resources as they have last back less black ends they need to support now. It's also going to get harder and harder as more distributions keep dropping this and yes, you have your LTSs, but they won't have the latest kernels. And so as, as X11 kind of fades out through a lot of distributions, even testing, this is going to become more of a challenge. You take a look at the first article in the show Notes for more details and you can see links to the reference documents and a lot more information on, on what's going on and why they're doing this and some behind the scenes stuff. Now I have a second article which is talking about KDE 6.6 because you know, we had a couple stories without Linux and I thought you guys need some more linux news. So 6.6 is coming. They're not at a feature freeze yet. So what I'm telling you here is kind of the foreshadowing what's coming. But there could be more because it's, it's about. I think it's mid January if I remember correctly. When the feature freeze happens there's, there's several things to look forward to though. You know, there's global actions going forward for going Forwards or backwards 5 or 30 seconds in playing media. There does need to be support built into the app, but a lot of them already support the API. It's now possible to configure order of the icons on the logout screen. There's more polish in the XDG portal dialogues. The screen and window chooser has been simplified and improved. The kicker application no longer quickly flashes no matches found after you search for things. Even if it did find something, if you have a QR code in the clipboard and it happens to be showing and if you clear the clipboard it will now also dismiss the QR code as well. It didn't previously. There are several other fixes improvements overall bug squash. So take a look at the second link in the show Notes to see them and as there are a ton I didn't cover for just the sake of brevity. And they even cover in their frameworks 6.21 fixes and changes. And they do mention that framework 6.2.1 is really going to start showing some of its feature set in 6.6.

D (70:08)

So.

A (70:08)

So a lot of good things coming. And I must say, you know, I'm continually impressed with the continuous improvements in kde. They're really doing a lot of code work.

B (70:22)

Yeah, so I remember, and you may as well, there was a blog post over on Pointed Stick from Nate Graham talking about when is Plasma going to lose the X11 session? I couldn't help but think about that. I went back and I looked and he says, yes, it'll eventually happen. At the time there was no firm plan as to win. This was July of this year, by the way. It wasn't actually that long ago. It was like five months. Six. Five months ago. Yeah, like five months ago. He says, yes, the writing is on the wall, it'll eventually happen. But as for when Plasma will drop support for X11, there's currently no firm timeline for this. I certainly don't expect it to happen in next year. Well, it's happening in the next year. Early in the next year even. Certainly don't expect it to happen in the next two years. But that's just a guess. Depends upon how long everything works. And then I want to say that they talked somewhere in here. You talked about 7.0, but I'm not sure I can't find it at the moment. Maybe we just mused at the time that that meant that they were going to stay with X11 as long as they had the 6X releases. But anyway, all that to say this happened a lot quicker than people expected. Even KDE people expected. And I wonder why. There's the obvious reasons, and we've talked about here a time OR 2, that X11 is losing its few paid contributors. That may have a lot to do with this. Actually, Red Hat was employing some people that because they were still actively supporting Red Hat Enterprise Linux that shipped with X11, they were still paying some people to find and fix bugs in it. And that is, I think, no longer the case, or is about to no longer be the case. They may have a lot to do with this.

A (72:25)

But yeah, I think also as the feature sets diverge, like HDR, it's not trivial to try to wedge HDR into X11.

B (72:35)

Yeah, it becomes more and more of a burden to make the old code continue to work while you're adding new features for sure.

A (72:44)

So I think it wouldn't surprise me. That's driving a lot of it. And with a lot of distributions at least hinting in the background they're going to start dropping x11. I think it was just kind of like, hey, you know what, let's get on this bandwagon too. And there's just that much less that we have to support.

B (73:01)

Yep.

A (73:02)

And like I said, it's going to get harder to test is a lot of distributions start going, okay, we're dropping, dropping X. So, okay, how do we test it? But we need the new kernel and new libraries, which a lot of this, you know, version whatever is going to need required to build off of.

B (73:21)

Yeah, it's. It's going to settle some debates about whether your distro should support it or not. Well, should, Should Fedora continue to have an x11 build of KDE? Nope, not after this.

D (73:35)

I don't know if it settles debate if they should. They may still say they shouldn't even after they go to it. But yeah, well, it's, it's amazing. Like, when I saw this online, how many people is like, well, I guess I'm leaving kde. It's like, I don't know, I. I advocate for Waylon maybe too harshly on the Internet. I'm like that Internet guy who, who argues and just keeps jumping into the conversation, saying over and over, I really need just copy and paste this because I say the same thing over and over 100 times a week. But there's just so many reasons to move on.

B (74:19)

So what we'll eventually have is it's the same thing. Like, you have some people that really don't like systemd. And so there are distros that are formed around this idea of I don't want system D, I want to use one of the old INIT systems. And that's fine. Like, I have nothing against those dish. I don't want to run one of them, but I have nothing against them existing. It's like, I have nothing against X11 code running out there. People just need to acknowledge that it's not actually being fixed. There's not actually security vulnerabilities getting patched. And so.

D (74:52)

For the niches, well, what, you know, mainstream should, you know, do the right thing.

A (74:58)

Yeah. You know what, what sold me on Whalen, though, was because, and I mentioned this before, the X11 people that were working on it said we have to totally tear it down and rebuild this to put these features and security in. And they're the ones that started Wayland. And I. I remember some of those early talks and stuff. And it kind of boiled down to a lot of people saying, well, you need to do this. It's like you don't understand the architecture. It is. It's such a convoluted mess. You can't, you know, it's a house of cards and you can't touch anything without breaking 20 others.

B (75:31)

Yeah.

A (75:31)

And Waylon was a result of that. And even if you're not a fan of Wayland, people that were working at X11, that's who built it, and that's where they went. Nobody's, you know, Everybody abandoned the X11 house.

D (75:45)

If you can't believe the developers of X11 and Waylon, who are you going to believe?

B (75:51)

Yeah, the Internet.

D (75:54)

And not me on the Internet.

B (75:56)

Not me on the Internet. Yeah.

A (75:59)

Well, they talked about it one time. X11 had its own printer driver and was halfway to becoming its own operating system. And they're like, oh, my gosh, this is just.

B (76:06)

We gotta stop. Yes, yes.

A (76:09)

Sorry, Jonathan, I cut you off.

B (76:10)

No, no, I was just. I was thinking, like, what was it? If you don't want to trust these guys, what was it before X11? Was it the. The old X windowing system before it was X11? Something like that?

A (76:20)

Yeah.

B (76:22)

Yeah, that's right. XF86. Yep. Yeah, I see. I heard that. You know what that sound was from, Rob? That was the sound of. I remember that, but that was a long time ago.

A (76:36)

And there was a lot of manually going in in the command line and editing files to get a real graphical display going other than your basic.

B (76:47)

That was the same sound. That was the same sound that old Ben Kenobi said. Obi Wan Kenobi. I have not heard that name for a very long. Is the exact same sound what Rob just made?

D (76:58)

Well, the fact that it started with X, I guess I didn't realize that it was something different. But I definitely remember xf86 and the configurations. I just thought they made it better and then changed the name a little bit. Fork.

B (77:17)

It was a fork. Yeah.

D (77:18)

Is that what it was?

B (77:20)

X386 forked into x.org I'm trying to remember. I think X386 was a fork of something else.

D (77:29)

So it's still kind of based on the same code. It's just forked.

B (77:33)

Yeah.

D (77:34)

Okay. But, yeah, those are the fun days.

A (77:38)

Now that X11 code is really forked.

E (77:43)

Yes.

B (77:44)

Yes, it is. Okay, I got to stop this. I started going down the Rabbit Hole of tracing out the history of X. I'm Wikipedia and that's. That is. I don't have time for that tonight. All right, we do have one more pair of stories to cover. These are a couple that I found. One is. One is a bit troubling and the other one is pretty cool. So we're gonna, we're gonna get the bad news first. It's not that bad, but it could cause problems. So the bad news here is that the Rust for Linux co maintainers formally stepped down. Alex Gaynor and is formally no longer a Rust for Linux maintainer. He has sent in the patches to remove his name from it. And that means that we are down to a single maintainer for the Rust for Linux project, and that's Miguel Ojeda. Now, this is actually not as big of a change as it sounds like because Alex has not really had the spare time to be able to work on this code for quite some time. That's why we say formally steps down. But it is even, even that being said, it is a bit of a problem that there's only one project leader for this rather large and important bit of code in the kernel. There are a few other people that help review patches, but at this point Miguel is the only one that really is a maintainer of it. And that's a lot. It's a lot of code for one person to be responsible for. So one of the things as we sort of look forwards that's going to be interesting to think about and look at is where is the Rust for Linux project going to go? What direction is it going to take? Because you can imagine a future scenario where Miguel steps down as well and the Rust code starts to bit rot. And we know that Torvalds has no, no problem pulling out code that's bit rotted. And so, well, nobody's using this anymore. So out it goes. That is very much a possible future for the Rust for Linux code. It's not necessarily where things are going, but it would be good to see more people stepping up to both write and help maintain that code. So that is the bit of the downer news. And then there's something pretty cool. For me, this is, for me, it's cool. I don't know. There's only a few of you out there that really will get excited about this. In Fedora 44 we are getting the Nix packaging tool and I believe that is going to then open the ability to install all of these NIX packages. And Nix is interesting in that it's package Manager it has the ability to run single user package installs which essentially it's almost like how an app image or a flatpak gets installed where you just install it for the local user. So really interesting. And so this is coming to fedora officially in Fedora 44 you'll be able to DNF install nix and then you'll be able to nix install the various things that are out there. So it'll work like a PIP for Python and those sorts of things. One of the reasons that this is particularly interesting for me is that right now there is someone that is trying to officially package meshtasticd. That's the one of the other projects I work on for Nix. And so once that happens, it'll be just a couple of commands to be able to get that officially installed on Fedora. And so that's fun. I'm looking forward to that. But there's a lot of other NIX related things that are out there that'll be fun to be able to get on Fedora. It's just cool, it's cool to see crazy stuff like this working. And someone said, well, why don't we do it?

A (81:39)

And does any distribution by default use Nix?

D (81:42)

Nixos.

B (81:44)

Nixos, yeah, it's the only one.

D (81:47)

But yeah, NIX OS and the NIX package managers, not anything I've ever tried. Something I definitely should because. Like what?

B (81:54)

Put it on your coffee list?

D (81:55)

What? I'll wait, I'll wait to put out that challenge. But yeah, I mean, what's awesome that I've read about it is that it's a, you know, it's a reproducible declarative configuration. So when you install all your packages, you know, at least with Nix OS, NixOS. I'm assuming it's the same if you have the package manager somewhere else. Once you install everything and have it configured, you take that configuration to your next nixaus and have it be reproducible. Just the same thing. And I don't know if it's. If, if that's a feature of the package manager, meaning that anywhere you have that package manager you can run that configuration or if there's something missing in just a package manager that limits you from having that the nixos has. Like I said, I never tried it, but I should.

B (82:49)

Yeah, the way I read this is you're going to be able to install the NIX packages as they're compiled by Nix inside of Fedora if you want to. So I mean, I would think that that would give you the same reproducible builds.

D (83:05)

So yeah, 2020. I'll throw it out there now. 20, 26 challenge for me. Throwing, throwing the coffees. If you, if you want me to do it and.

B (83:17)

You got to put on there in the fine print, this coffee buys a nick sauce.

D (83:21)

Yes. It's actually a one that I've wanted to try.

A (83:26)

Well, there you go. If you do that, also put in there this. I want you to try the nix os, but I want this coffee to go to either Jeff or Jonathan. Make him work for it.

B (83:40)

Make him work for it. Yeah. All right. That is our news for the week. Quite a bit of it. Some good stuff in there. We've got some tips. We have got some command line tips and we're going to get to them right after this.

D (83:56)

Okay. Only 10 more presents to wrap. You're almost at the finish line.

B (84:02)

But first. There, the last one. Enjoy a Coca Cola for a pod that refreshes.

C (84:26)

Hey, it's Ryan Seacrest for Albertsons and Safeway. As winter approaches, make sure you set aside some time for self care now through December 2nd. Get great savings on personal care essentials when you shop in store or online. Buy two participating self care items and save $3. Shop for items like Tresemme shampoo, Dove Shampoo, Dove men's care body Wash, Dove body Wash and Axe shower gel. And save $3 when you buy two or more items. Offer ends December 2nd. Restrictions apply. Offers may vary. Visit albertsons or safeway.com for more details.

B (84:57)

Okay, so on the tips, Rob is up first. Rob, you don't have one. Is it a surprise? Did you intentionally do this? You want to surprise us with what your tip is?

D (85:07)

I forgot to put my tip on there.

B (85:08)

Huh. Did you forget to pick a tip, though?

D (85:11)

I did not forget to pick the tip.

B (85:13)

That's good.

A (85:14)

All right. Looks through his notes.

B (85:17)

It's here somewhere. I know it is. I can't remember what it was. Where'd it go?

D (85:21)

Yeah, I have it opened already. I just. Okay, I forgot what it was. I'm like, what is it called? I'm drawing a blank. It's on my notes, so. And I'll have to add it to the show notes. So my surprise tip of the day is a command line tip. It is called pod liner. So I'm just going to bring this up here. I already have it open. So this is a. I don't know if it's TUI or what, but it's in the command line with the, you know, command line graphical kind of interface, something like tui. Whether or not they use that technology or not to do podcasts. So for those watching, I've already loaded the Untitled Linux show and Floss Weekly into this. And also, this is kind of like the. The VI or VIM of podcast. It's of podcast applications. It took me a little bit to actually realize this. And, you know, you guys can't see that because my name is there, but there's a little command line spot right at the bottom, which I'm going to adjust this.

B (86:30)

There you go.

D (86:32)

Oh, okay, you got that?

B (86:33)

Okay, I have a button. I push the button.

D (86:35)

That'll work. So there's a little command line here at the bottom. So at first I was having a hard time figuring this out. So because I'm running this in a gui, I can actually click around on stuff. But being a command line, I need to know how to use this in the command line. So I figured out that if you do colon H, it's going to bring up your commands. It tells you all the things to do.

B (87:01)

It's the illegitimate son of VI and Midnight Commander, Right?

D (87:06)

So it's not even necessarily all the commands, now that I think about it, because to add, it's like colon add and then you put the URL to the RSS feed. And that's how I added these already. But to play, I figured I have this first one selected. I hit spacebar, it's going to play. And I don't have my audio piped over to the show here, but you can see the. No, you can't see the whole tavern because I'm in the way now. Let me get me out of the way here.

B (87:42)

You can see the bar going across on the bottom.

D (87:44)

Okay, you can see that. Let's just get me out of the way here, though. So also you can see the little timer going now, 11 minutes, 23 seconds in. So that said, it takes a bit to figure out the navigation house. I haven't figured it all out myself yet, but I figured out how to get it to play a podcast. So if you're making some kind of device and you want text space only or whatever, you got podliner, and that can be used for your. To play your podcast in the command line.

B (88:24)

For extra geek points, do it over ssh. So have your Raspberry PI connected to a Bluetooth speaker and SSH into the PI to run pod liner. Yeah, there you go.

D (88:37)

That's. I mean, that's the way to do it. You have a little Raspberry PI hooked up to a speaker, and then you SSH in and do what you Do.

B (88:48)

Voila. That's fun. That's a lot of fun. All right, let's see. Jeff, you are up next with ss.

A (88:57)

Yeah. And you know something funny? I was going to put in a joke command line tip for Rob and I looked it up and it's like, oh, that's a real command. So I added one into the pile to go. Oh, I accidentally stumbled across.

D (89:11)

Okay, what's the joke? Why is it a command line tip for me though, before you.

A (89:15)

Because it was blank. Oh, I had a blank and I was going to fill it in the show notes for you. Yeah, it's like, well, that's real. I'm keeping that for myself. But my command line tip this week is ss and in the man page it's listed as another utility to investigate sockets. SS stands for socket statistics. Basically, it's used to dump socket statistics and it allows showing information similar to. Net stat. It can be. It though can display a lot more TCP and state information than other tools. Usage is pretty simple. For example, to see all TCP sockets, just type SS space dash t space dash A. And if you wanted to do something like find all local processes connected to the X server, it would. It would be SS space dash x space src space slash temp x11 Unix *. And you could even filter by ports using sspace sport s p o r t space equals space colon 80. And if you even want want really more, a lot more filters, you can do things like list all the TCP stock sockets in state fin dash wait one for our Apache server to network 193-223-24 and look at their timers. Yes, I cut down the IP address. You don't need to hear me say that. And I'm not going to read that command because it's a little bit long. But you can do very specialized things. And actually SS is the. Net. They say it's the. NET stat replacement. And it works faster than netstat because it doesn't parse the log files or large files, but it talks directly with the kernel, which now it's not an issue on a small machine, but like if you have a large enterprise server and maybe you got a hundred thousand connections, netstat can be a little slow and take a lot of CPU cycles. So if you take a look at the man page for SS as it should be in most distributions, or look at the link in the show notes for more information on this handy little networking.

B (91:32)

Tool. Very cool. I like it. Always useful to have more tools for doing that sort of Thing. All right. My command line tip comes from kind of a weird spot. So I got sent to the mail a couple of these things. This is the SuperCon badge from the latest hackaday superconduct. And this is an ESP32 S3 and a LoRa chip. And as soon as I heard what was going to be in it, I said, oh, send me a couple. I'll put Meshtastic on it. And we have indeed ported Meshtastic to it. Probably can't see that, but it is indeed. There. There you go. It's a good one to show the time. The time. The ding. The time is. Anyway, one of the other guys hacking on this badge, though sent in, yeah, I'm ssh'd into mine. And we went, you're what? Oh, yeah, you can run Linux on these now. And I went, wait, you could? That's what my wife said. Wizarding badge. That's not a badge. No, it's not really a badge. Anyway, I went down this rabbit hole. Wait a second. You can run Linux on the ESP32S3? And apparently, yes, you actually can. And there is a. I've not done it yet, but there is a guide here on how to compile Linux for the thing and actually make it happen. And apparently it is indeed possible to compile Linux and run it on one of these, which blew my mind. And I figured that the folks here would be sufficiently geeky enough to really appreciate that fact as well. So, not exactly a normal command line tip, but still very, very cool to be able to do that. So, Rob, your antenna can probably run.

D (93:12)

Linux. So when I buy the Zigbee one, just to test out and then decide I don't really want to use it, I'll figure out how to get Linux on.

B (93:25)

It. There you.

D (93:26)

Go. So dual reasons to.

B (93:30)

Donate. Exactly. Would be fun. All right, it's been a blast of a show. Thank you guys for being here. Doing a little bit of double duty today, but it has been a lot of fun. I'm going to let each of the guys get in the last word on something if they want to, or maybe tell us some poetry or maybe remind us where to go to donate coffee. Jeff gets to go.

A (93:52)

First. Nothing to cover, so it's going to be Poetry Corner. This one's short but sweet. Keyboards are violent, rodents are green. Rtfm, if you know what I mean. Have a great week, everybody. I like.

B (94:08)

It. I like it. All right.

D (94:09)

Rob. All right. Roses are red, violets are blue. Linux is fun. And so are you. Just made that up on the spot. I.

B (94:19)

Am. We could tell. We could.

D (94:20)

Tell. All right. But for those who want more poetry like that.

B (94:25)

One, not the greatest sell.

D (94:29)

Man. Or to find out how to donate a coffee to get me to you do one of those crazy wild things, you can go to my website robertp Campbell.com on the website near the top there are links to my LinkedIn, my, my Twitter Blue Sky Mastodon and a little coffee cup where you can donate coffees which is five dollar increments so, so you don't have to donate a whole like $8 coffee, just a $5 coffee or two five dollar coffees.

B (94:58)

Or ten as many coffees as you want. All right, very cool. Thank you guys. You can find me at mainly Hackaday these days. We've got Floss Weekly there and that's a whole lot of fun. There's also the security column goes live on Friday mornings and you can find probably going to take another week off around Christmas time. But other than that you can find me there covering the Linux and otherwise security news. Other than that, just want to say thank you, appreciate everybody that's here and those that watch, those that listen, whether you get us live or on the download. And hey, we'll see you next week on the Untitled Linux Show.