Skip to main content
LawHub
Sign In
About LawHub Advantage Thinking About a Career in Law Applying to Law School Thriving in Law School and Beyond Listen to I Am The Law Podcast Trends Sign In
Search

Linus' NT Surprise

Mar 30, 2025
Listen to this episode

Linux 6.14 lands with big improvements for gaming, laptops, and filesystems—but why is a Windows feature sneaking into our kernel?

Sponsored By:

Support LINUX Unplugged

Links:

Transcript

WEBVTT 00:00:11.549 --> 00:00:16.249 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.409 --> 00:00:17.049 My name is Wes. 00:00:17.249 --> 00:00:18.009 And my name is Brent. 00:00:18.949 --> 00:00:23.409 Hello, gentlemen. Coming up on the show today, Linux 6.14 is landing, 00:00:23.429 --> 00:00:27.949 and there are big improvements in there for gaming, file systems, and a lot more. 00:00:28.349 --> 00:00:31.649 But you might have noticed there's a Windows feature that's sneaking into Linux 00:00:31.649 --> 00:00:33.469 kernel. We'll dig into what that's all about. 00:00:33.709 --> 00:00:36.449 We'll round out the show with some great boosts and feedback, 00:00:36.629 --> 00:00:41.109 some picks, and more. So before we get into all of that, let's say hello to 00:00:41.109 --> 00:00:44.129 our virtual lugtime appropriate greetings, Mumble Room. Hello, hello. 00:00:45.449 --> 00:00:47.309 Hey, Chris. Hey, Wes. And hello, Brent. 00:00:47.789 --> 00:00:53.089 Hi. Hello. Got a handful of you in the on-air and a handful of you in the quiet listening. 00:00:53.149 --> 00:00:57.509 The Mumble Room, of course, is always going when we get our stream up and running on a Sunday morning. 00:00:57.829 --> 00:01:02.769 And a big good morning to our friends at Tailscale. Tailscale.com slash unplugged. 00:01:02.769 --> 00:01:08.369 Tailscale is the easiest way to connect your devices and services to each other, wherever they are. 00:01:08.549 --> 00:01:12.429 It's modern networking the way you really, really want it, protected by... 00:01:12.429 --> 00:01:16.029 Great for companies, great for self-hosters. 00:01:16.189 --> 00:01:19.829 It's secure remote access to your production systems, your mobile systems. 00:01:19.929 --> 00:01:24.229 You can combine complex network infrastructures into a flat mesh network. 00:01:24.409 --> 00:01:27.709 Maybe you got multiple VPSs, you got some on-premises stuff. 00:01:27.949 --> 00:01:31.349 All of that can come together, and it's really, really fast. 00:01:31.349 --> 00:01:34.389 It's easy to deploy. It's zero config. It is a no fuss VPN. 00:01:34.649 --> 00:01:39.169 And then there are things like ACLs and additional feature sets that you can 00:01:39.169 --> 00:01:42.129 build on top of like integrated in with your company's authentication infrastructure. 00:01:42.249 --> 00:01:45.489 So when you really need to take it to the next level, tail scales there and 00:01:45.489 --> 00:01:46.569 it works like nothing else. 00:01:46.729 --> 00:01:49.829 But the real magic is if you go to tailscale.com slash unplug, 00:01:50.009 --> 00:01:53.529 they're going to give it to you for free for up to 100 devices and three users, 00:01:53.649 --> 00:01:55.709 no credit card required, not a trial. 00:01:56.669 --> 00:02:01.669 That's the starting plan. And like me, you'll start using it and it will change your network. game. 00:02:02.229 --> 00:02:04.289 It is really something else to 00:02:04.289 --> 00:02:07.829 now have everything on my own tail net and nothing on the public internet. 00:02:08.049 --> 00:02:12.409 All my devices sync over my tail net. We access and manage all of the Jupyter 00:02:12.409 --> 00:02:14.349 broadcasting infrastructure over our tail net. 00:02:14.469 --> 00:02:17.629 And even some of our public traffic is actually tunneled through our tail net 00:02:17.629 --> 00:02:20.689 to infrastructure on the back end and then displayed to the public. 00:02:20.949 --> 00:02:24.069 It really is very powerful. That's why thousands of companies like Instacart, 00:02:24.129 --> 00:02:26.329 Hugging Face, and Duolingo have switched to using Tailscale. 00:02:26.709 --> 00:02:28.549 And so many in our audience love it too. 00:02:29.129 --> 00:02:31.989 So try it for yourself or for your business, but support the show and get started 00:02:31.989 --> 00:02:35.649 by going to talescale.com slash unplugged. 00:02:36.189 --> 00:02:38.649 Go there, get it for free on 100 devices. 00:02:39.289 --> 00:02:41.409 Talescale.com slash unplugged. 00:02:44.390 --> 00:02:51.110 Brace yourself. We have 25 days until LinuxFest Northwest, if you can believe it. 00:02:51.290 --> 00:02:55.190 Now, of course, the schedule is live. We'll have a link in the show notes. 00:02:55.630 --> 00:02:59.950 Linux Unplugged is going to be live at 10 a.m. in HC108 on Sunday. 00:03:01.630 --> 00:03:06.770 Live from LinuxFest. And I just heard from Noah that he'll be joining us from the Ask Noah program. 00:03:07.650 --> 00:03:13.510 And also Wes has a talk after the live show in the same area, 00:03:13.950 --> 00:03:15.350 maybe not the same room but the same building. 00:03:15.350 --> 00:03:16.230 Definitely the same conference. 00:03:16.230 --> 00:03:20.630 Same conference, same building I think but maybe upstairs Linux powered payments 00:03:20.630 --> 00:03:23.590 running the Lightning Node with Nix Bitcoin at 1.30pm. 00:03:23.590 --> 00:03:28.230 Yeah trying to just share some of the stuff we found useful if you do want to 00:03:28.230 --> 00:03:31.950 engage with the Lightning Network probably the best way to run a node at least 00:03:31.950 --> 00:03:35.850 if you want full control is something like Nix Bitcoin powered by Nix and Nix OS Also. 00:03:35.930 --> 00:03:38.030 You can just come say hi to us because probably a lot of us will be there. 00:03:38.590 --> 00:03:42.630 We're going to have to figure that out because there's no way we are done with 00:03:42.630 --> 00:03:44.930 the show by 1.30. I mean, we might be done streaming. 00:03:45.990 --> 00:03:48.590 There's no way we're done with the show by 1.30. 00:03:48.590 --> 00:03:51.330 Yeah, maybe it publishes a bit later. It publishes after my talk. 00:03:51.870 --> 00:03:55.470 I don't even know what we're doing. It's going to be crazy, but we've got 25 00:03:55.470 --> 00:03:58.690 days to figure it out. And we'd love to see it, LinuxFest Northwest. 00:03:59.010 --> 00:04:01.210 I'm feeling like it's going to be a good weather year. 00:04:02.370 --> 00:04:04.010 I'm hoping. We'll see. 00:04:04.010 --> 00:04:05.590 Yeah, we've earned that after last year. 00:04:05.770 --> 00:04:07.310 Is it like a seven-year cycle? 00:04:07.690 --> 00:04:12.250 I think it's a two-year cycle. I don't know. We'll see. This will be the trendsetter. 00:04:12.350 --> 00:04:15.150 Yeah, if Brent doesn't do his cloud seeding like last year. 00:04:15.150 --> 00:04:17.110 Stupid lobes. Weather lobes. 00:04:17.370 --> 00:04:21.410 Hey, it worked well. I think we got good seed funds from that one. 00:04:23.503 --> 00:04:27.083 Well, speaking of funds, I just want to take a moment up front in the show and 00:04:27.083 --> 00:04:29.663 thank our members and our boosters who have been supporting the show. 00:04:30.443 --> 00:04:32.983 The show really is trying to do something unique in this space. 00:04:33.183 --> 00:04:35.263 We're trying to make the highest quality product we know how. 00:04:35.803 --> 00:04:39.463 We aspire to make a magazine's worth of content in nearly every episode, 00:04:39.683 --> 00:04:41.603 every single week, for free. 00:04:42.163 --> 00:04:45.683 And we're doing it for a market, the Linux listener base, that historically 00:04:45.683 --> 00:04:50.683 has failed to make this kind of thing sustainable via sponsorships alone. 00:04:51.643 --> 00:04:57.523 And of course, we seem to prefer to do things the hard way. So we're not leaning 00:04:57.523 --> 00:04:58.823 into where the money is these days. 00:05:00.503 --> 00:05:04.903 YouTube, clickbait drama topics. We're using an open platform with an open standard 00:05:04.903 --> 00:05:07.083 that doesn't have an algo that pushes us in front of you. 00:05:07.943 --> 00:05:12.263 And one of the things we would like to do in the next couple of months is raise 00:05:12.263 --> 00:05:17.043 some funds to buy some gear, some headsets that we can use on our LinuxFest 00:05:17.043 --> 00:05:21.303 Northwest coverage and the BangBus trip to rescue Brent's new BangBus, 00:05:21.963 --> 00:05:25.863 which we expect to be doing live shows from the van on the road. 00:05:29.303 --> 00:05:32.523 And you know our standards are fairly high, and I've been researching this for weeks. 00:05:32.643 --> 00:05:36.183 I've asked around to people's opinions that I respect to see what they suggest, 00:05:36.763 --> 00:05:41.863 and I've landed on a set of headphone-microphone combos that I would like to buy for the boys. 00:05:42.463 --> 00:05:46.263 It's the Sennheiser HMD-26 dual ear broadcast headset. 00:05:46.543 --> 00:05:49.883 Now, these things are not cheap. They're $500 each, and they don't even come 00:05:49.883 --> 00:05:52.083 with their proprietary cable, which is also another $100. 00:05:52.843 --> 00:05:57.363 So it's not that I come to this conclusion easily, and I have ordered one for 00:05:57.363 --> 00:06:01.163 myself already, just so I can get some experience and test it. 00:06:02.293 --> 00:06:05.573 You know, these are really in the sweet spot for a quality that I think we could 00:06:05.573 --> 00:06:07.993 accept on air that are under $1,000. 00:06:09.453 --> 00:06:12.933 And we should be able to EQ and process them. I'm going to talk to Editor Drew 00:06:12.933 --> 00:06:14.173 on his opinion about that. 00:06:14.873 --> 00:06:19.373 And we hope to make them sound decent. And I'd love for each of the boys to 00:06:19.373 --> 00:06:22.033 be able to get one too. So it's around $1,300 we're going to raise. 00:06:22.153 --> 00:06:25.393 And I'm comfortable buying them with BoostSats or something like that. 00:06:25.393 --> 00:06:28.993 So if you would like to help support us getting that gear and getting us ready 00:06:28.993 --> 00:06:33.993 for the van trip and for LinuxFest Northwest, please consider boosting the next few weeks episodes. 00:06:34.593 --> 00:06:37.093 We do come to the audience from time to time with these kinds of things. 00:06:37.193 --> 00:06:39.613 Not always, but with fewer sponsors out there, this is kind of how we have to 00:06:39.613 --> 00:06:40.753 finance these types of things. 00:06:41.433 --> 00:06:44.793 The show goes on if we don't reach our goal, but it is about trying to make 00:06:44.793 --> 00:06:46.653 the show as good as possible on the road. 00:06:46.873 --> 00:06:50.513 Not just from an audio quality standpoint, but I'm also looking for something 00:06:50.513 --> 00:06:54.133 that we can reasonably manage in a small backpack gear kind of thing. 00:06:54.133 --> 00:06:55.533 Something compact, on the go. 00:06:56.213 --> 00:06:59.213 And again, like when we're at a booth at LinuxFest, something where we don't 00:06:59.213 --> 00:07:01.993 have to have a bunch of microphone stands and all of that. 00:07:02.173 --> 00:07:04.573 And if you think about it from a gear piece, it's a microphone, 00:07:04.573 --> 00:07:09.133 it's the stand, it's the cable, and then it's another set of headphones. 00:07:09.133 --> 00:07:14.433 And if you can slim all that down into one device, it makes it just a lot easier 00:07:14.433 --> 00:07:16.473 from an operational standpoint. 00:07:16.673 --> 00:07:20.653 Yeah, investing in simplicity, which makes it cheaper in a variety of ways, 00:07:20.653 --> 00:07:25.073 less gear to bring around, less complex, and hopefully makes it easier for us 00:07:25.073 --> 00:07:27.313 to be able to do this at more places or more events. 00:07:27.673 --> 00:07:31.673 Yeah, so if you'd like to, that's probably about 1.3 million sats. 00:07:31.733 --> 00:07:34.453 So if you'd like to boost in for the next few weeks and have a go to that, 00:07:34.553 --> 00:07:36.993 just note it in your boost, and we'd appreciate that. 00:07:37.033 --> 00:07:39.893 And of course, the members, your support keeps the show going there, 00:07:39.913 --> 00:07:41.113 and we really appreciate that as well. 00:07:41.713 --> 00:07:44.213 And the show will go on if we don't raise the funds, but I wanted to put it 00:07:44.213 --> 00:07:47.833 out there as it's a goal of ours, and we'll have more if it works out. 00:07:47.873 --> 00:07:50.173 And thank you, everybody who does support the show, in either way you do, 00:07:50.313 --> 00:07:54.013 either through treasury, through time, or through your talent. 00:07:54.153 --> 00:07:54.973 We really appreciate it. 00:07:57.413 --> 00:08:00.973 Well, just as we're sitting here recording, Linux 6.14 is cooking, 00:08:01.193 --> 00:08:04.953 and it is a major release. 00:08:05.193 --> 00:08:09.973 It's 2025, it's got some barn burners, and this particular release is going 00:08:09.973 --> 00:08:13.353 to be in the next Fedora and Ubuntu releases, as well as a bunch of other distros. 00:08:13.513 --> 00:08:16.593 So it's an important release, and it's a banger release. 00:08:17.133 --> 00:08:21.393 Also, should we just note at the top that it was the rare event where, 00:08:21.693 --> 00:08:24.893 in a way that didn't matter at all, Linus Torvalds released a day late, 00:08:26.751 --> 00:08:30.331 I'd love to have some good excuse for why I didn't do the 6.14 release yesterday 00:08:30.331 --> 00:08:32.731 on my regular Sunday afternoon release schedule. 00:08:33.091 --> 00:08:36.511 I'd like to say that some important last-minute thing came up and delayed things. 00:08:36.531 --> 00:08:39.971 But no, it's just pure incompetence. 00:08:40.051 --> 00:08:41.451 I love it. After all this time. 00:08:42.411 --> 00:08:45.491 Because absolutely nothing last-minute happened, and I was just cleaning up 00:08:45.491 --> 00:08:47.871 some unrelated things in order to be ready for the merge window. 00:08:47.871 --> 00:08:51.171 And in the process, just entirely forgot to cut the release. 00:08:51.291 --> 00:08:51.691 That's all right. 00:08:51.851 --> 00:08:54.211 Yeah, it's still, it turns out, a great kernel. 00:08:54.451 --> 00:08:59.331 It really is. and we're going to get into some of our favorite improvements and updates. 00:08:59.531 --> 00:09:04.451 There's a lot more to this kernel, and we could do a three-part episode series on it. 00:09:04.611 --> 00:09:07.671 So please feel free to nerd out with the links in the show notes. 00:09:07.791 --> 00:09:09.471 We have, I think, links to some of the best coverage. 00:09:10.971 --> 00:09:15.611 But let's start with the one that's close to our heart. Wes is running it on his laptop right now. 00:09:17.291 --> 00:09:20.851 BcacheFS saw a major step towards stability in Linux 6.14. 00:09:21.111 --> 00:09:24.071 Yeah, well, it was kind of the catch-up release, right? So there was a good, 00:09:24.271 --> 00:09:30.331 lots of good stuff in 6.12 and then 6.13 due to the code of conduct ruling, 00:09:30.711 --> 00:09:31.771 Kent could not contribute. 00:09:32.011 --> 00:09:37.111 So we didn't see any updates in 6.13. So now we're getting a lot of good stuff in 6.14. 00:09:37.351 --> 00:09:44.791 In particular, there is hopefully the last planned big, major, 00:09:44.971 --> 00:09:51.551 expensive, but still automatic and required on-disk format upgrade coming with 6.14. 00:09:51.551 --> 00:09:54.511 So it just happens automatically in the background. But if you have like a giant 00:09:54.511 --> 00:09:56.451 array, that could be some work to do. 00:09:56.571 --> 00:09:57.911 So you might not even notice. Yeah. 00:09:58.251 --> 00:10:01.411 In the past, I have not for just running as my root of S. 00:10:01.571 --> 00:10:05.331 Okay. So with that comes major scalability enhancements. 00:10:05.551 --> 00:10:09.111 Yeah. And that's the thing, right? A lot of this stuff is as, 00:10:09.231 --> 00:10:15.671 you know, the file system gets used in actual scenarios and can't go through bug reports. 00:10:16.231 --> 00:10:19.611 You kind of find out, oh, it turns out we wanted to slightly tweak this structure 00:10:19.611 --> 00:10:24.011 or a lot of times it's adding points where they can keep more information or 00:10:24.011 --> 00:10:27.771 more statistics or metrics or like information or back pointers. 00:10:27.891 --> 00:10:30.911 A lot of times where you kind of have more of the structure preserved to make 00:10:30.911 --> 00:10:34.851 it faster when you're trying to do some repair operation so that you don't have 00:10:34.851 --> 00:10:36.551 to like go scan as much data. 00:10:36.671 --> 00:10:40.051 To that point, they say in here there's a dramatic speed up for FSCK. 00:10:40.651 --> 00:10:40.751 Yeah. 00:10:40.931 --> 00:10:42.991 And they tested it on. Do you see that in there? 00:10:43.171 --> 00:10:46.191 Yeah, right. 10 petabyte file systems. They. 00:10:46.191 --> 00:10:49.811 Have 10 petabyte file systems out there running bcachefs right now. 00:10:49.811 --> 00:10:54.291 Yeah so i don't think my like 500 gig root fs is really gonna sweat that. 00:10:54.291 --> 00:10:55.111 So good to know. 00:10:55.111 --> 00:10:58.611 Yeah good to know and it's just if you do ever get that it's a good reminder 00:10:58.611 --> 00:11:02.751 right like if you're not willing to test on disk format upgrades uh with giant 00:11:02.751 --> 00:11:06.691 arrays then bcachefs is not yet for you which is totally fine it's still uh 00:11:06.691 --> 00:11:12.291 experimental but also this is good good signs i think of um you know signs of 00:11:12.291 --> 00:11:14.151 stability going forward they were hitting places where, 00:11:15.215 --> 00:11:20.075 Once you get to a point of not, at least not even expecting on disk format changes, 00:11:20.235 --> 00:11:22.795 there still could be some if like a major issue needs it. 00:11:23.275 --> 00:11:28.555 But this is the first step towards it being more trustworthy for like actual serious data arrays. 00:11:28.755 --> 00:11:32.955 Very much so. I should have looked more into this. I just noticed in my notes 00:11:32.955 --> 00:11:36.035 here, the default runtime has been set to self-healing enabled. 00:11:36.395 --> 00:11:39.115 Yeah, there's been a lot of self-healing work going on, right? 00:11:39.175 --> 00:11:41.415 There was already ways that you could trigger that. 00:11:41.515 --> 00:11:45.135 We don't yet have a full scrub, but we do have self-healing. 00:11:45.215 --> 00:11:51.995 Uh and coming in 6.15 it's already merged upstream i think in 6.15 we should see, 00:11:52.715 --> 00:11:56.235 full scrub support it's already also in the upstream userland 00:11:56.235 --> 00:11:59.055 utils but i think in a future release so again right 00:11:59.055 --> 00:12:02.655 you need you need the self-healing capability at all having it happen when it 00:12:02.655 --> 00:12:05.695 detects things on the fly and then from there you can have scrub that just sort 00:12:05.695 --> 00:12:09.535 of walks the whole file system to trigger that checking it's a bones release 00:12:09.535 --> 00:12:15.455 maybe not one that you'll see a ton of changes from a user perspective but that's 00:12:15.455 --> 00:12:17.415 a sign of where we're at with the infrastructure it's. 00:12:17.415 --> 00:12:20.335 It was interesting so like the moment the 614 window 00:12:20.335 --> 00:12:25.075 opens kent he does a poll that is just like here's syncing everything up and 00:12:25.075 --> 00:12:28.235 then here is here's all these improvements too so it's really fascinating just 00:12:28.235 --> 00:12:31.215 to read through his description of all of it and to see him just right back 00:12:31.215 --> 00:12:35.595 at it and i wouldn't be surprised if by the end of the year or before the end 00:12:35.595 --> 00:12:37.515 of the year, the experimental flag is removed. 00:12:38.515 --> 00:12:41.195 Yeah, I like that as a 2025 prediction. 00:12:41.395 --> 00:12:41.695 Could be. 00:12:41.955 --> 00:12:42.715 A little low-key predict. 00:12:42.755 --> 00:12:45.055 I can't remember if I actually made that in the actual predictions episode. 00:12:45.135 --> 00:12:46.775 Do you have the lock it in sound somewhere? 00:12:49.835 --> 00:12:53.375 All right, well, the file system that's actually shipping right now that a lot 00:12:53.375 --> 00:12:55.895 of folks are using is ButterFS. 00:12:56.515 --> 00:12:59.935 And there has been some really good improvements landing in ButterFS, 00:13:00.155 --> 00:13:05.535 including three new RAID 1 read balancing methods, which improves how reads 00:13:05.535 --> 00:13:07.675 are distributed across devices. So you have rotation... 00:13:08.973 --> 00:13:11.533 Which actively rotates and reads to keep all devices engaged. 00:13:11.733 --> 00:13:14.113 That's the preferred default going forward. 00:13:14.353 --> 00:13:18.813 You have latency, which optimizes for unstable or failing device transports. 00:13:18.953 --> 00:13:23.033 And then there's dev ID, which gives you manual control over which device handles 00:13:23.033 --> 00:13:26.053 the reads, which I could definitely see workflows where that would be useful. 00:13:26.093 --> 00:13:29.053 Yeah, absolutely. And maybe even just as like an operational thing for, 00:13:29.273 --> 00:13:31.793 you know, while you're having issues with the disk you're going to replace or something. 00:13:32.793 --> 00:13:37.893 And of course, not just like changes to RAID 1, but also other improvements 00:13:37.893 --> 00:13:42.213 to ButterFS have landed, which includes support for uncached buffered I.O. 00:13:42.493 --> 00:13:45.993 And here's a bit from kernel newbies. They say this release adds support for 00:13:45.993 --> 00:13:47.953 optionally sending buffered I.O. 00:13:48.033 --> 00:13:52.373 Whose pages will be dropped from the page cache once the data is read or written. 00:13:52.613 --> 00:13:57.593 The reason for this feature are fast storage devices that can and do fill the 00:13:57.593 --> 00:14:00.353 RAM with too much page cache that will not be needed. 00:14:00.953 --> 00:14:05.453 With this feature, it is possible for the read and write data and to drop it 00:14:05.453 --> 00:14:10.433 from the cache without facing the disadvantages and complexity of dealing with direct I.O. 00:14:11.153 --> 00:14:16.193 Man, I wish I had that problem. Where my disk I.O. was so fast that I was overfilling 00:14:16.193 --> 00:14:17.473 my RAM with stuff I didn't need. 00:14:17.633 --> 00:14:21.253 But isn't it great that the file systems in the kernel are attempting to keep 00:14:21.253 --> 00:14:24.933 up with the latest and greatest hardware? Or at least, you know, a version ago of that? 00:14:25.193 --> 00:14:26.253 Mm-hmm. Mm-hmm. 00:14:26.273 --> 00:14:29.853 I think there's actually been some work generally around on cache buffer I.O. 00:14:29.873 --> 00:14:32.733 In the latest couple of kernels to just make that better. 00:14:33.493 --> 00:14:37.373 Okay, one last file system thing. You had to get the file system things out 00:14:37.373 --> 00:14:40.593 of the way because these probably really impact the most of us, some of these features. 00:14:41.133 --> 00:14:45.393 And the one that really sees some love is actually your Fuse file systems. 00:14:45.473 --> 00:14:48.693 They're going to get a big performance boost via IOU ring. 00:14:49.564 --> 00:14:54.064 So this is a fascinating story. A gentleman who works at DDN Storage, 00:14:54.764 --> 00:14:59.944 he had a talk at the 2023 Linux Storage Summit and also at BPF Summit, 00:15:00.524 --> 00:15:05.924 and he talked about discovering an odd issue when really taxing his MVME disk. 00:15:06.024 --> 00:15:09.944 He says, I was looking at an MVME driver and was wondering why it was able to 00:15:09.944 --> 00:15:13.264 avoid the bottlenecks, why it wasn't or was, I'm not sure, able to avoid the 00:15:13.264 --> 00:15:14.444 bottlenecks I was seeing. 00:15:14.644 --> 00:15:19.664 Oh, it was. It was because it was using Ioring, Uring, but it was in the wrong direction, he says. 00:15:19.824 --> 00:15:23.564 It was going from user space to the kernel, but what Fuse really needed was 00:15:23.564 --> 00:15:26.704 for it to go the other way. Can you help me make sense of that, Wes? 00:15:27.204 --> 00:15:31.684 Yeah, I think they were investigating issues with Fuse and noticed that the 00:15:31.684 --> 00:15:35.164 NVMe driver wasn't having the same problems. 00:15:35.504 --> 00:15:35.944 Okay. 00:15:36.384 --> 00:15:40.704 And the way it was using IOU ring, which is a new I.O. 00:15:40.944 --> 00:15:45.284 Mechanism in the kernel that makes it really fast and cheap to be able to have 00:15:45.284 --> 00:15:49.864 the kernel, you know like fill a section of memory with data say coming off 00:15:49.864 --> 00:15:51.304 of a network driver or something i. 00:15:51.304 --> 00:15:54.424 Think our last kernel deep dive episode we did go into that a little. 00:15:54.424 --> 00:15:59.044 We did yeah and then user space can read from that and then avoids a whole bunch 00:15:59.044 --> 00:16:04.284 of context switching between the two which is always expensive uh so now we're 00:16:04.284 --> 00:16:07.584 having some of these techniques being able to be applied, 00:16:08.164 --> 00:16:12.364 to fuse to speed up basically whatever you're doing with fuse which is a whole 00:16:12.364 --> 00:16:14.404 bunch of stuff because Fuse is, as a reminder, 00:16:14.904 --> 00:16:16.764 file systems in user space. 00:16:16.944 --> 00:16:21.784 So you can have a user space process managing things, but the kernel and other 00:16:21.784 --> 00:16:25.544 programs, crucially, treat it like it's a kernel file system, 00:16:25.644 --> 00:16:28.044 right? And this is where you can have stuff like SSHFS. 00:16:28.344 --> 00:16:30.584 And there's a whole bunch of very, very cool Fuse file systems. 00:16:30.764 --> 00:16:36.084 But because you have to have, right, you're talking the kernel API for file 00:16:36.084 --> 00:16:41.544 systems, but then the kernel has to go and talk to the user space thing managing the Fuse file system, 00:16:42.204 --> 00:16:45.864 that's a ripe area where you need a whole bunch of data exchange that can be 00:16:45.864 --> 00:16:48.584 expensive if you're doing context switches but with iou ring, 00:16:49.626 --> 00:16:50.446 It can be faster. 00:16:50.566 --> 00:16:54.226 You avoid some of that. One of the interesting insights to this is this could 00:16:54.226 --> 00:16:57.066 have broad ramifications for all types of Fuse file systems. 00:16:57.186 --> 00:17:03.266 We use one that's essentially a WebDAV Fuse file system for managing the files on our next cloud. 00:17:03.406 --> 00:17:07.326 And this could be really nice to see something we've considered generally a 00:17:07.326 --> 00:17:10.566 little bit slower than a real native file system actually get a nice little boost here. 00:17:10.706 --> 00:17:14.226 And we're seeing IOU ring, which we talked about before, really kind of come 00:17:14.226 --> 00:17:18.226 in and change the game, which is fascinating to see it kind of get rolled out 00:17:18.226 --> 00:17:19.226 in different areas. And I think 00:17:19.226 --> 00:17:23.006 the discovery here is probably going to be applicable in other areas. 00:17:23.146 --> 00:17:27.646 Like Fuse is where they're starting, but I bet you this idea ends up kind of 00:17:27.646 --> 00:17:28.886 spreading out in other places. 00:17:29.666 --> 00:17:30.646 Yeah, usually it does. 00:17:31.466 --> 00:17:34.466 Now, that is all the file system stuff. Great job, everybody. 00:17:35.986 --> 00:17:41.126 There's more in there, of course, including there's a fascinating history with Fuse. 00:17:41.406 --> 00:17:46.006 There has been a couple of goes at replacing Fuse to try to solve some of these problems. 00:17:46.006 --> 00:17:50.506 And a couple of different attempts at like fuse two and a different type of 00:17:50.506 --> 00:17:54.366 fuse all together to specifically try to solve these problems they never really 00:17:54.366 --> 00:17:58.486 got adoption and then we kind of came along and solved it at the kernel level i. 00:17:58.486 --> 00:18:02.426 Have good news and bad news we're actually not done with file systems. 00:18:02.426 --> 00:18:04.146 Oh we're not no okay because. 00:18:04.146 --> 00:18:06.646 Xfs gained enhanced real-time device support. 00:18:06.646 --> 00:18:11.526 Oh you're right you're right you're right xfs got some love this cycle Yeah, 00:18:11.646 --> 00:18:15.446 and it's, you know, I think this is particularly worth noting just because last 00:18:15.446 --> 00:18:19.106 year we covered the XFS maintainer swap, or maybe it was a little bit longer than that. 00:18:19.566 --> 00:18:23.806 And that maintainer that stepped down was a long-time really trusted maintainer. 00:18:23.966 --> 00:18:26.846 And the person coming in, we weren't quite sure what direction they would take 00:18:26.846 --> 00:18:31.246 the project. And what we've seen is just impressive development after impressive development. 00:18:31.806 --> 00:18:37.366 So the XFS developer Derek Wong explained on some of the real-time reverse mapping 00:18:37.366 --> 00:18:39.866 and reeling support that's landing in this patch series. 00:18:39.866 --> 00:18:43.526 He says, Christoph and I have been working on getting the long-delayed port 00:18:43.526 --> 00:18:48.486 of reverse mapping and reflink to the real-time device into a manageable shape. 00:18:49.338 --> 00:18:53.658 With these changes, the real-time volume finally reaches the feature parity with the data device. 00:18:53.898 --> 00:18:58.738 This is the base for building more functionality into XFS, such as the zone 00:18:58.738 --> 00:19:01.898 storage support that Christoph posted about last week. 00:19:02.058 --> 00:19:05.318 I think it continues the story of, I mean, just XFS being a great, 00:19:05.598 --> 00:19:08.858 you know, if you don't need the kind of things that things like Butterfess and 00:19:08.858 --> 00:19:12.438 ZFS and Bcache address, XFS is just a great file system. 00:19:12.578 --> 00:19:16.118 And they're really pressing to keep up with, in the ways that its architecture 00:19:16.118 --> 00:19:20.438 supports, It's an impressive subset of modern file system functionality. 00:19:20.998 --> 00:19:26.598 Okay, now that is all of the file system stuff. And this next category is, 00:19:26.738 --> 00:19:29.978 holy crap, there's a lot of AMD stuff landing. 00:19:30.238 --> 00:19:33.878 But first, we should acknowledge the very important addition, 00:19:34.158 --> 00:19:40.338 at the kernel level, support for the Microsoft Copilot key on modern laptops. 00:19:40.838 --> 00:19:42.458 Hey, did you know that was the thing? 00:19:42.858 --> 00:19:46.178 There you go, Brent. And so if you get a framework now and, you know, 00:19:46.178 --> 00:19:49.218 some of those new frameworks come with a copilot key, don't worry, it's going to work. 00:19:49.378 --> 00:19:51.938 So is this in addition to the existing Windows key? 00:19:52.318 --> 00:19:55.918 Yeah, it's on the other side now. You know, so you got the on the other side 00:19:55.918 --> 00:19:58.938 of the keyboard on the right side, I guess. I don't know what it does on Linux. 00:19:59.958 --> 00:20:01.478 Maybe you can just map it to something. 00:20:01.618 --> 00:20:03.578 Maybe it'll trigger your home assistant for you. 00:20:03.798 --> 00:20:04.118 Sure. 00:20:04.418 --> 00:20:07.338 I think it should be your compose key. But if you don't know what that is, 00:20:07.398 --> 00:20:08.478 then maybe it's not useful for you. 00:20:10.318 --> 00:20:15.518 All right. Well, let's talk about the plethora of AMD GPU driver updates. 00:20:16.038 --> 00:20:20.458 New DRM Panic supports. You get the fancy blue screen now with AMD devices. 00:20:20.818 --> 00:20:24.718 Yeah, we talked about that a whole bunch. But as a reminder, 00:20:25.018 --> 00:20:28.678 to take advantage of some of that new functionality, there needed to be per 00:20:28.678 --> 00:20:29.958 graphics driver support. 00:20:30.118 --> 00:20:32.618 So now we're finally seeing that on the AMD side. It was already in a bunch 00:20:32.618 --> 00:20:34.318 of like the base ones and the Intel side. 00:20:34.318 --> 00:20:41.198 We're seeing early support LAN for the RX90 Zero Series GPUs and beyond. 00:20:41.538 --> 00:20:46.578 And the big one is the AMD P-State driver update, which makes big improvements 00:20:46.578 --> 00:20:51.118 for laptop power management and efficiency for AMD systems. But there's an interesting twist in here. 00:20:52.078 --> 00:20:55.198 The maintainer of the Linux power management subsystem, 00:20:56.659 --> 00:21:05.859 is an intel employee uh and you know this release was just a lot of amd code and so the intel guy, 00:21:06.959 --> 00:21:11.019 is the one that is you know actually going through this and submitting it upstream 00:21:11.019 --> 00:21:15.639 and this is what he wrote for the patch for 614 he writes the majority of changes 00:21:15.639 --> 00:21:20.799 are cpu frequency updates which are dominated by amdp state driver changes like 00:21:20.799 --> 00:21:22.639 in the previous cycle Moreover, 00:21:22.959 --> 00:21:27.439 changes related to AMD P-State are also the majority of the CPU power utility updates. 00:21:27.819 --> 00:21:30.919 Indeed, there are some pieces of new hardware support, like the addition of 00:21:30.919 --> 00:21:33.359 the Clearwater Forest processors to support the Intel idle. 00:21:33.779 --> 00:21:36.519 And there are some other improvements for other Intel chips in there. 00:21:36.919 --> 00:21:44.119 But the vast majority of the updates for this 613 and 614 kernel have been from AMD. 00:21:44.439 --> 00:21:47.919 And this Intel maintainer is doing his job, doing a great job, 00:21:48.079 --> 00:21:51.779 is submitting all of this upstream. And I just find that to be a beautiful irony 00:21:51.779 --> 00:21:52.819 of free software development. 00:21:52.999 --> 00:21:57.639 It also makes me think, I mean, A, there's probably a lot of nice benefits for 00:21:57.639 --> 00:22:00.339 these employees of diverse companies working together on some of this stuff. 00:22:00.439 --> 00:22:02.759 Maybe there's insights or, you know, learnings from each other. 00:22:03.019 --> 00:22:06.399 But also, like, in a way, just open source sort of erodes some of the, 00:22:07.379 --> 00:22:09.999 artificial's too strong of a word, but I'm going to say artificial boundaries 00:22:09.999 --> 00:22:12.159 imposed by, like, the corporate structure of things. 00:22:12.179 --> 00:22:16.379 Like, here are a bunch of CPU nerds who are now nerding out together to make 00:22:16.379 --> 00:22:17.539 all of the CPUs work better. 00:22:17.539 --> 00:22:22.839 Seeing what common problems they're solving and also both actively contributing 00:22:22.839 --> 00:22:25.219 to these release cycles, Intel and AMD, 00:22:25.439 --> 00:22:29.959 and both actively preemptively contributing bits before the products are even 00:22:29.959 --> 00:22:33.359 in the marketplace, which is so critical when you think about the time delay. 00:22:33.359 --> 00:22:38.179 So Linux 6.14 is going to be in the most recent Fedora and Ubuntu, 00:22:38.339 --> 00:22:42.939 but it'll be quite a while before 6.14 is in any of the LTSs or RHEL. 00:22:43.779 --> 00:22:48.199 So when they get that groundwork in there now, people that take advantage of 00:22:48.199 --> 00:22:51.479 the in-between distribution releases get to use the drivers, 00:22:51.479 --> 00:22:54.939 but it takes years before it's in the enterprise-grade stuff. 00:22:55.359 --> 00:22:59.339 And so it's really incumbent upon them to try to get this stuff in as early 00:22:59.339 --> 00:23:03.179 as possible and that's why before they've even finished all of the driver work 00:23:03.179 --> 00:23:07.199 they're getting the primitives in now as early as they can so that way the next 00:23:07.199 --> 00:23:09.899 cycle they can just get you know a little bit more in there and then, 00:23:10.659 --> 00:23:15.519 hopefully get it out to end users as fast as possible we'll see but that's the 00:23:15.519 --> 00:23:19.339 that's the interesting game that they both have to play and both AMD and Intel 00:23:19.719 --> 00:23:23.759 just by watching this do seem very committed to that process they're getting it done. 00:23:27.552 --> 00:23:33.992 1Password.com slash unplugged. That's the number 1Password.com and then unplugged all lowercase. 00:23:34.192 --> 00:23:38.272 You want to go there to support the show and to learn more about 1Password. 00:23:38.652 --> 00:23:41.712 Here's how I like to think about this. I have a question for you. 00:23:41.892 --> 00:23:44.032 Do your end users always, and 00:23:44.032 --> 00:23:49.012 I mean to always use the IT approved applications, services, and devices? 00:23:49.772 --> 00:23:52.932 I don't know if any users do. I think there's just so much out there now. 00:23:53.032 --> 00:23:56.912 There's so much getting pushed at them from a consumer level from a this is 00:23:56.912 --> 00:23:58.212 going to change how you work level. 00:23:58.552 --> 00:24:02.912 So how do you keep your company's data safe when it's sitting in all these unmanaged apps or devices? 00:24:03.792 --> 00:24:07.452 That's where 1Password comes in. Again, it's 1Password.com slash unplug. 00:24:07.612 --> 00:24:11.632 They have the answer to this question, extended access management. 00:24:12.312 --> 00:24:16.332 1Password extended access management helps you secure every sign-in for every 00:24:16.332 --> 00:24:20.472 app on every device because it solves the problems that traditional IAMs and 00:24:20.472 --> 00:24:22.212 MDMs just weren't built to touch. 00:24:22.772 --> 00:24:28.932 You secure every app, every device, and every identity, even the unmanaged ones, 00:24:28.932 --> 00:24:30.632 like when I was a contractor coming in. 00:24:30.872 --> 00:24:35.612 You go to 1Password.com slash unplugged, check it out. This really does change 00:24:35.612 --> 00:24:38.632 the game. Now, 1Password's famous, of course, for their beautiful password management. 00:24:39.292 --> 00:24:42.972 Now they've taken it up to the next level, from that award-winning product to 00:24:42.972 --> 00:24:44.552 extended access management. 00:24:45.312 --> 00:24:48.752 They're really bringing everything they've learned, including their best practices. 00:24:48.992 --> 00:24:51.272 You know, they undergo regular third-party audits. 00:24:51.532 --> 00:24:53.752 They have the industry's largest bug bounty. 00:24:54.512 --> 00:24:57.672 And it's really great to say that 1Password exceeds those standards that are 00:24:57.672 --> 00:25:02.952 just set by other authorities and whatever the letter of the law might be. 00:25:03.072 --> 00:25:05.972 They go above and beyond. I love to see that. 00:25:06.432 --> 00:25:10.032 It's really the first security solution that brings all these unmanaged devices 00:25:10.032 --> 00:25:12.352 and apps and identities under your control. 00:25:13.112 --> 00:25:17.712 That's the big deal. That's the big shift. So go check it out and support the show. 00:25:17.892 --> 00:25:21.132 Go make sure every app, every device, every identity is secure, 00:25:21.292 --> 00:25:22.492 even the unmanaged ones. 00:25:23.752 --> 00:25:29.172 Go to onepassword.com slash unplugged. That's onepassword.com slash unplugged. 00:25:32.944 --> 00:25:39.604 Now, as with many previous kernels, we do see a little bit of gaming love in Linux 6.14 as well. 00:25:39.944 --> 00:25:44.804 Looks like the Linux 6.14 kernel will officially include the completed NTSync 00:25:44.804 --> 00:25:49.304 driver, which is a major improvement for Linux gamers using Wine and Proton, 00:25:49.444 --> 00:25:52.324 especially via Steam Play or SteamOS. 00:25:52.824 --> 00:25:56.684 An NTSync feature in our Linux kernel? 00:25:57.184 --> 00:26:02.164 Yeah, that's right. It's kind of neat, right? Now we have a specific synchronization 00:26:02.164 --> 00:26:05.144 primitive enabled inside the 00:26:05.144 --> 00:26:09.844 kernel specifically to support compatibility with Windows applications. 00:26:10.164 --> 00:26:14.584 Very fascinating. They say here, The driver enhances the emulation of Windows 00:26:14.584 --> 00:26:19.184 NT synchronization primitives, which are critical for accurately replicating 00:26:19.184 --> 00:26:22.984 Windows behavior and improving performance in many Windows games running on Linux. 00:26:23.344 --> 00:26:27.644 Though NTSync was introduced in Linux 13, it was initially incomplete and not functional. 00:26:28.264 --> 00:26:30.884 6.14 marks its full implementation and usability. 00:26:31.724 --> 00:26:35.524 As for the motivation behind the work, well, it's clear in the benchmarks. 00:26:35.984 --> 00:26:39.384 The gains vary widely depending on the application and the user's hardware, 00:26:39.464 --> 00:26:42.644 but for some games, anti-synchronization is not a bottleneck, 00:26:42.684 --> 00:26:43.724 and so no change will be noticed. 00:26:44.064 --> 00:26:49.404 Some other games, though, improvements 50% to even 150% are normal. 00:26:50.084 --> 00:26:53.144 Yeah, okay, so there is some nuance here as well. 00:26:53.144 --> 00:26:58.464 Right now, this is specifically helpful for, or going to be, for Upstream Wine, 00:26:58.684 --> 00:27:05.164 and it is the newest and shiniest and most compatible with Windows implementation, 00:27:05.164 --> 00:27:06.984 but there's been earlier attempts, 00:27:07.184 --> 00:27:13.324 specifically eSync and fSync, which have basically been gaming-focused mechanisms 00:27:13.324 --> 00:27:17.324 to enable improvements to emulating games specifically. 00:27:17.324 --> 00:27:22.584 And since I think like kernel 514, we've had Futex 2 in the kernel, 00:27:22.784 --> 00:27:27.004 which Proton is patched Upstream Wine to take advantage of. 00:27:27.124 --> 00:27:31.324 But I think Upstream Wine does not, partially because it was kind of gaming 00:27:31.324 --> 00:27:34.884 focused and there were some thoughts that it was kind of a hack and didn't really 00:27:34.884 --> 00:27:38.024 like the specific interface being created for Wine and Proton. 00:27:38.024 --> 00:27:40.824 And it doesn't solve it for all games, like solves it for some of the games, 00:27:40.884 --> 00:27:42.564 which is why some of these games won't see an improvement. 00:27:43.575 --> 00:27:48.095 And the root of this is, okay, so in the Windows world, you've got the Windows NT kernel. 00:27:48.295 --> 00:27:53.975 It's pretty different than a Unix-y, Linux-style kernel influenced by stuff like VMS. 00:27:54.195 --> 00:27:57.955 And there's a whole bunch of objects, and you have handles to these objects, 00:27:58.015 --> 00:28:01.355 which if you've ever done Windows programming, you've seen handles freaking everywhere, right? 00:28:02.095 --> 00:28:06.155 And if you're a game or just a program, often you need to wait for things, right? 00:28:06.235 --> 00:28:09.935 So like in a game, it might be wait to be told that like the frame I wanted 00:28:09.935 --> 00:28:13.695 to draw is done painting or copying to the GPU memory or whatever it is. 00:28:13.815 --> 00:28:17.515 Or I need to wait for a keyboard or a mouse event for the user to do my next thing. 00:28:17.655 --> 00:28:21.175 Or maybe a network package shows up telling you what the enemy participant did 00:28:21.175 --> 00:28:22.495 and how to update their game state. 00:28:22.815 --> 00:28:25.735 And so there's oftentimes where you've done your immediate work and so you want 00:28:25.735 --> 00:28:30.395 to say like, hey, wake me up when any of these things happens and then based 00:28:30.395 --> 00:28:33.915 on what it is, I know what to do next to advance the process. 00:28:34.955 --> 00:28:38.735 And due to the way Windows is designed, they've got some pretty nice APIs for this, 00:28:38.735 --> 00:28:43.055 including wait for multiple objects so you can kind of just hand it a whole 00:28:43.055 --> 00:28:47.195 smattering of things that you want to wait for regardless of it's like a file 00:28:47.195 --> 00:28:51.635 handle or a network thing or some status update to a particular process or thread, 00:28:52.555 --> 00:28:59.355 and Windows will set that up for you and while Linux has things like ePoll and 00:28:59.355 --> 00:29:02.475 other mechanisms to specifically wait for things like file handles there's various. 00:29:03.399 --> 00:29:06.479 Equivalencies of course because right ultimately windows and 00:29:06.479 --> 00:29:09.519 linux make your computer work in roughly the same way but the 00:29:09.519 --> 00:29:12.719 apis are different enough that like originally 00:29:12.719 --> 00:29:15.799 wine had to have kind of like a helper thread or process that 00:29:15.799 --> 00:29:18.839 could sort of translate between the windows system call 00:29:18.839 --> 00:29:21.899 in user space and then implement it under the hood with 00:29:21.899 --> 00:29:25.579 the right kernel features and as you can imagine like 00:29:25.579 --> 00:29:28.559 that's not going to perform super great some of it was fine 00:29:28.559 --> 00:29:31.579 for some things it did work but like it was just going to hit bottlenecks 00:29:31.579 --> 00:29:34.699 especially with games and so that's where we've had multiple attempts 00:29:34.699 --> 00:29:37.579 with esync and then fsync which has been the most successful and widely 00:29:37.579 --> 00:29:40.919 used with proton but now finally we're getting 00:29:40.919 --> 00:29:44.179 ntsync which is it prioritizes compatibility so 00:29:44.179 --> 00:29:48.219 it's like the best translation in the kernel for this style 00:29:48.219 --> 00:29:53.019 of synchronization primitive but it also looks like it has some quite nice performance 00:29:53.019 --> 00:29:55.899 gains so especially for upstream wine you're going to see those big numbers 00:29:55.899 --> 00:29:59.719 that you're seeing reported if you're doing proton it there's still it has not 00:29:59.719 --> 00:30:03.019 yet adapted in theory in the future they'll probably switch to ntsync and there'll 00:30:03.019 --> 00:30:05.939 be some slight performance improvements and compatibility improvements. 00:30:05.939 --> 00:30:09.879 And like from a practical standpoint for end users they're going to get essentially 00:30:09.879 --> 00:30:14.239 a new device a new virtual device right like a slash dev slash ntsync device. 00:30:14.239 --> 00:30:17.799 Yeah and that's uh the mechanism for how things can sort of go request that 00:30:17.799 --> 00:30:19.519 and wait on it from the kernel yeah. 00:30:19.519 --> 00:30:22.919 And each each time each process opens up the device they get a unique instance 00:30:22.919 --> 00:30:27.659 but it's shared across threads which is so they get like their own id but there's 00:30:27.659 --> 00:30:28.739 some shared space there too. 00:30:28.739 --> 00:30:31.899 Yeah and that's usually the case right so for processes they have different 00:30:31.899 --> 00:30:35.019 memory space and threads get to share so that way you can have multiple threads 00:30:35.019 --> 00:30:38.819 that are doing things but they can all be they can like share waiting or locks 00:30:38.819 --> 00:30:43.139 or use that use that for a shared synchronization primitive to like communicate between threads. 00:30:43.139 --> 00:30:47.539 Sort of like the fuse iou ring improvements we talked about earlier in the show 00:30:47.539 --> 00:30:53.859 This NTSync that is definitely targeted at gaming right now seems like there 00:30:53.859 --> 00:30:57.979 would be other complex Windows applications that would benefit this. 00:30:59.080 --> 00:31:03.180 From this. And so while it is initially useful for gaming, I could see in a 00:31:03.180 --> 00:31:06.420 year or two, we've discovered some other application that didn't work before 00:31:06.420 --> 00:31:07.960 is now working because of this too. 00:31:08.140 --> 00:31:11.540 Yeah. Right. In the big picture, it's just like a big, nice step up for our 00:31:11.540 --> 00:31:15.760 Linux's ability to be compatible with Windows applications through Wine. 00:31:15.880 --> 00:31:18.740 It's just cool because, I mean, there's already, again, there's already been 00:31:18.740 --> 00:31:22.840 some of these kinds of efforts, but just the idea that the kernel is being adapted 00:31:22.840 --> 00:31:28.320 to support this non-emulation user space thing of wine that somehow seems to 00:31:28.320 --> 00:31:29.300 work surprisingly well. 00:31:29.760 --> 00:31:34.960 That's just that takes a lot of coordination and planning and years of effort 00:31:34.960 --> 00:31:36.220 to get across the finish line. 00:31:36.400 --> 00:31:40.160 And like, you know, folks had to make the case that, hey, you know, 00:31:40.200 --> 00:31:43.320 people are trying to run programs not even intended for the operating system 00:31:43.320 --> 00:31:45.240 you designed, but can you make this change, please? 00:31:45.600 --> 00:31:47.560 That we're going to sell on this proprietary hardware. 00:31:47.760 --> 00:31:48.220 Yeah, right. 00:31:48.760 --> 00:31:53.340 But it does show you that if you've got good code that works and you're willing 00:31:53.340 --> 00:31:55.980 to do the work and you show up to the Linux community, 00:31:56.160 --> 00:32:00.360 kernel community with you know proof of receipts they're probably going to take 00:32:00.360 --> 00:32:05.480 it uh they're they're they're really pretty much down to take most things if 00:32:05.480 --> 00:32:09.300 you're doing the maintenance you're doing the the legwork you know like yeah. 00:32:09.300 --> 00:32:12.480 And you have you can point to real you know use cases or people who want it. 00:32:12.480 --> 00:32:16.240 This is how samsung got a samba server in the kernel west jeff. 00:32:16.240 --> 00:32:18.460 Makes a good point too and this is definitely true right through the history 00:32:18.460 --> 00:32:20.680 of computing games have often been one of the best ways. 00:32:20.680 --> 00:32:21.180 To sort of. 00:32:21.180 --> 00:32:23.320 Like push the limits for how to make these things happen. 00:32:23.320 --> 00:32:26.900 I agree i agree and And that's why I think we'll fix it for gaming. 00:32:27.520 --> 00:32:30.760 And then we'll discover some other complicated application. 00:32:31.120 --> 00:32:33.680 Just in time so Brent can switch back to Lightroom. 00:32:36.319 --> 00:32:41.019 Now, we were thinking, and we'd like to hear your thoughts, about maybe doing 00:32:41.019 --> 00:32:43.919 a gaming episode next week. Nothing crazy. 00:32:44.439 --> 00:32:47.379 Maybe just one or two games, and then also a bit of a hardware update. 00:32:47.439 --> 00:32:49.899 So even if you're not a gaming person, there'll be some hardware talk in there, too. 00:32:50.799 --> 00:32:54.279 So if you have thoughts on gaming on Linux, a game you're loving right now, 00:32:54.399 --> 00:32:58.079 particularly those that support co-op, send them in to us. 00:32:58.299 --> 00:33:02.539 Boost them in, or go to linuxunplugged.com slash contact and let us know. 00:33:02.599 --> 00:33:05.799 Because we've been thinking about doing a gaming episode literally for about two years. 00:33:06.559 --> 00:33:08.699 So maybe we'll do it next week. We've got a couple of things. 00:33:08.879 --> 00:33:10.339 I got a new device in-house. 00:33:11.279 --> 00:33:13.699 Remind me to show it to you after the episode. It's pretty slick. 00:33:14.219 --> 00:33:16.899 I want to talk about that next week. So that's been on our mind. 00:33:17.019 --> 00:33:19.679 It's been a long time. The gaming episodes tend not to be super popular. 00:33:19.899 --> 00:33:22.439 So if you don't want us to do it, you can let us know too. 00:33:23.119 --> 00:33:25.539 I don't know. It's like, it's always hit and miss. 00:33:25.699 --> 00:33:28.419 You know, if we really got ahead of it, we could do like a gaming meetup. 00:33:28.579 --> 00:33:31.279 If we were playing a game, people could join. 00:33:31.519 --> 00:33:34.939 Well, okay. How about this is a goal. We come up with a co-op LAN style game 00:33:34.939 --> 00:33:38.439 that we could try that we could use at Linux Fest. And we demo it. 00:33:38.939 --> 00:33:41.679 So we would love some suggestions for that because I literally don't know. 00:33:42.559 --> 00:33:43.919 Maybe producer Jeff could help. 00:33:44.079 --> 00:33:50.179 The other thing to kind of just sort of think on for Linux Fest is where we, 00:33:50.319 --> 00:33:51.579 oh, maybe in the room where we do luck. 00:33:51.719 --> 00:33:54.019 Maybe we could do it in the room. That could be interesting. 00:33:54.539 --> 00:33:57.159 Anyways, something that's been on our mind, new hardware and all of that. 00:33:57.339 --> 00:33:58.639 So let us know your thoughts there. 00:33:58.899 --> 00:34:02.799 And I don't think anything's ready yet to try out this new NTSync thing. 00:34:02.919 --> 00:34:05.559 I wish we had an opportunity to test it with a game. 00:34:06.019 --> 00:34:10.119 But when one does, I'm already going to be on 614, so I'll be ready. 00:34:13.401 --> 00:34:17.781 Did you know your ad could be right here, right now? I could be talking about your company. 00:34:18.101 --> 00:34:21.701 Your Linux Unplugged podcast is looking to book a sponsor, and we're running 00:34:21.701 --> 00:34:24.141 a special for the second half of Q2. 00:34:24.421 --> 00:34:28.521 Now, you know we're kind of picky who we work with, which has limited us, 00:34:28.621 --> 00:34:32.801 but if you're listening to this show, well, that's a good start. 00:34:33.021 --> 00:34:36.761 Chances are you could be a great fit. So if you want to reach the world's largest 00:34:36.761 --> 00:34:41.421 Linux audience on a show that never misses a week and has been going for nearly 00:34:41.421 --> 00:34:44.941 12 years strong, Reach out to me, chris at jupiterbroadcasting.com. 00:34:45.061 --> 00:34:48.261 I'd love to work out a deal with somebody who's in the community that has a 00:34:48.261 --> 00:34:50.601 business or a product or a service that they'd like to reach. 00:34:51.241 --> 00:34:52.361 We'll make a pretty good deal. 00:34:53.261 --> 00:34:56.781 And I think it could be neat. I don't know. Chris at jupiterbroadcasting.com. 00:34:57.121 --> 00:34:57.941 That's all you need to know. 00:35:01.141 --> 00:35:05.741 Well, we got a special little piece of mail here from Grant who asks a little 00:35:05.741 --> 00:35:07.521 for some advice, let's say. 00:35:07.661 --> 00:35:11.941 It says, greetings, Chris, Wes, and Brent. I keep hearing you guys talk about 00:35:11.941 --> 00:35:14.461 this Nix thing, so I'm finally going for it. 00:35:14.601 --> 00:35:19.401 I was wondering if you have any tips for Nix OS configs on a laptop specifically. 00:35:19.841 --> 00:35:25.061 From what I research, so far most of it has to do with power optimization while on battery. 00:35:25.401 --> 00:35:31.201 Since using Linux on a laptop is literally Linux Unplugged, maybe another question 00:35:31.201 --> 00:35:35.821 is what are some community recommendations for Linux on a laptop? 00:35:35.821 --> 00:35:41.121 Love to hear what the best Linux community around, Linux Unplugged, has to say about this. 00:35:41.361 --> 00:35:43.701 And thanks in advance from Grant. 00:35:43.981 --> 00:35:47.941 That's a good question, Grant. I feel like I'm going to be in the laptop market 00:35:47.941 --> 00:35:48.881 towards the end of the year. 00:35:49.061 --> 00:35:52.781 It has been interesting living on Asahi on the MacBook and very limiting. 00:35:53.101 --> 00:35:57.421 And I eventually want to get something, but I want a very nice laptop experience. 00:35:58.121 --> 00:36:01.181 Something real smooth. Framework's a contender. Of course, I'm going to look 00:36:01.181 --> 00:36:02.301 at System76. I'm going to be 00:36:02.301 --> 00:36:05.741 looking at ThinkPads too. But I think Grant's asking two questions here. 00:36:06.576 --> 00:36:12.316 Number one, what is a great distro hardware combo? 00:36:12.876 --> 00:36:17.316 And, like, what should he look into for Nix to pre-set up his Nix for the best 00:36:17.316 --> 00:36:18.156 chances on that hardware? 00:36:18.256 --> 00:36:23.456 Like, I know Brent has looked at a config specifically for framework laptops. 00:36:23.736 --> 00:36:28.416 Yeah, well, there's the NixOS hardware community repo. So that's one place you can pull in stuff. 00:36:28.556 --> 00:36:29.016 That's the thing. 00:36:29.256 --> 00:36:32.616 You know, because, right, a lot of it is going to be making sure you're fully enabled, 00:36:32.616 --> 00:36:37.736 whatever settings or kernel parameters or driver options for your specific rig 00:36:37.736 --> 00:36:41.356 because after that honestly you know the linux world's gotten a little bit better 00:36:41.356 --> 00:36:44.916 i've been pretty pleased with the power management options at least in things 00:36:44.916 --> 00:36:46.656 like plasma and gnome very. 00:36:46.656 --> 00:36:49.256 True and even in the last couple of releases there's been some nice improvements. 00:36:49.256 --> 00:36:54.276 So there are you know various uh demons and things like power top and tools 00:36:54.276 --> 00:36:58.696 to monitor but for the most part i'm not currently fussing with those as much as i used to yeah. 00:36:58.696 --> 00:37:02.336 I just leave mine in balanced mode for the most part and then power saver when 00:37:02.336 --> 00:37:04.456 I need it and boost when I need it. 00:37:04.616 --> 00:37:09.556 I just, what I'm looking for is, it's Brent, he has the framework with, 00:37:09.636 --> 00:37:11.356 I think it's the 12th gen MOBO, right Brent? 00:37:11.436 --> 00:37:12.136 Yes, it is. 00:37:12.276 --> 00:37:15.916 And you have this problem that I witness all the time when you're around where 00:37:15.916 --> 00:37:20.356 you close up the laptop and then you come back to it a couple hours later and it's hot. 00:37:20.756 --> 00:37:27.896 Yeah, I have to say like maybe two out of 10 times. I guess that's one out of five. 00:37:28.576 --> 00:37:32.596 I will pick my laptop out of my bag and it'll be roasting. The rest of the time 00:37:32.596 --> 00:37:34.196 it kind of behaves as it should. 00:37:35.342 --> 00:37:40.922 I've been trying to figure out what is the combination of what I'm doing that causes that to happen. 00:37:41.242 --> 00:37:43.482 Now, Jeff, I know you've struggled with this kind of thing before, 00:37:43.542 --> 00:37:48.202 and you probably have a bunch of advice for me. But it has, I would say, gotten better. 00:37:48.442 --> 00:37:53.182 So there's constantly tweaks happening where Wes suggested in the Nixos hardware 00:37:53.182 --> 00:37:56.682 repo to try to solve some of these common problems. 00:37:57.282 --> 00:38:02.162 But it seems, I don't know, suspend is just in not so great a place as it was 00:38:02.162 --> 00:38:05.082 like, let's say, on an old ThinkPad laptop from back in the day. 00:38:05.082 --> 00:38:09.562 So it is something that's getting better, and there are some tweaks you can 00:38:09.562 --> 00:38:15.822 do, but I got to say, like, as a warning, part of the reality is sometimes it just doesn't go so hot. 00:38:16.242 --> 00:38:19.702 PJ, I'd like to hear your thoughts, but I would think if he's on a pretty modern 00:38:19.702 --> 00:38:23.482 kernel and he's using a 12th gen system, which has been out for a few years, 00:38:24.002 --> 00:38:26.382 shouldn't that be best? And it's all Intel. Shouldn't that be best case scenario? 00:38:26.382 --> 00:38:32.142 I think the framework specifically does have S3 sleep and that's one of the 00:38:32.142 --> 00:38:37.662 biggest problems that we're seeing with modern laptops is Intel and AMD have 00:38:37.662 --> 00:38:40.182 kind of pushed away from that and it's up to the motherboard, 00:38:40.822 --> 00:38:46.722 really the upstream, you know, laptop maker to put it back in and everything 00:38:46.722 --> 00:38:49.562 defaults to S5 sleep, which doesn't fully shut down. 00:38:49.562 --> 00:38:53.602 With the frameworks i've seen that you 00:38:53.602 --> 00:38:56.602 need to go into the bios and turn off usb power 00:38:56.602 --> 00:38:59.542 because all the little dongles will just sit there and suck suck power down 00:38:59.542 --> 00:39:03.442 when it's trying to sleep even even if it is an s3 so you might be seeing that 00:39:03.442 --> 00:39:10.402 but it's a problem my lenovo does it my last hp did it it's all s5 these things 00:39:10.402 --> 00:39:15.442 aren't actually going to suspend a ram they're just basically shutting the screen off tiny. 00:39:15.442 --> 00:39:18.642 On the other end though you're on a framework using fedora. 00:39:18.642 --> 00:39:26.442 Yes um fedora is just switched from using ppb ppd to toondy and it's really 00:39:26.442 --> 00:39:31.582 nice because you can nest profiles so you could have the uh default balancer 00:39:31.582 --> 00:39:34.942 laptop profile and then make your own little changes on top. 00:39:36.136 --> 00:39:39.876 Yeah, okay. So that's, you know, maybe the advantage to having a distribution, 00:39:40.556 --> 00:39:43.756 tune that stuff for you. Something Brent could look into, I suppose. 00:39:44.076 --> 00:39:50.296 On NixOS, I see there's a power management option, which has stuff like CPU 00:39:50.296 --> 00:39:53.516 frequencies in here, power top, you know, all kinds of stuff. 00:39:53.636 --> 00:39:57.096 Power profiles, daemon's an option as well. So there's various things in NixOS too. 00:39:57.456 --> 00:40:00.916 Boy, I'd love a great experience on my next laptop. Something really, 00:40:01.096 --> 00:40:04.816 you know, hassle-free, works with distros, just great, has some decent little 00:40:04.816 --> 00:40:08.876 performance for maybe some basic gaming and sleeps. 00:40:09.516 --> 00:40:12.856 I was going to say, in general for laptops, I think we've all been pretty happy. 00:40:13.036 --> 00:40:15.976 I mean, it's not laptop-specific, but happy with things like ZRAMP. 00:40:16.276 --> 00:40:22.116 Yeah, yeah. I think there are also compromises to be made. 00:40:23.196 --> 00:40:28.376 If I could get it to boot super fast, I could possibly live without sleep, I suppose. 00:40:28.876 --> 00:40:33.096 I don't love that, but that could always be a route I could explore if it meant 00:40:33.096 --> 00:40:37.356 I could have a fantastic laptop that I really love, that might be a compromise I could make. 00:40:37.616 --> 00:40:39.816 By fantastic, you mean loud fans, right? 00:40:40.016 --> 00:40:43.256 Yeah, no, I do not, sir. I do not. 00:40:48.137 --> 00:40:54.637 Yes, it is, and we start with our baller booster this week, who is the tech geek with 45,000 sats. 00:40:58.237 --> 00:41:01.577 And he just sends along, hey, JB team, keep up the good work. 00:41:01.737 --> 00:41:02.997 Well, thank you for the value. 00:41:07.237 --> 00:41:11.577 Turd Ferguson boosts in with 41,088 sats. 00:41:13.677 --> 00:41:15.237 Oh, this is a triple turd. 00:41:15.357 --> 00:41:16.397 Oh, gosh. 00:41:16.397 --> 00:41:18.297 Boosting the 2i challenge. 00:41:18.297 --> 00:41:19.217 Uh-oh envy. 00:41:19.217 --> 00:41:24.837 Top it's not just for nvidia did you know intel amd and even at least sorta 00:41:24.837 --> 00:41:27.797 the m1 and m2 gpus are supported. 00:41:27.797 --> 00:41:31.797 Envy top huh it sounds like it's for nvidia okay. 00:41:31.797 --> 00:41:35.737 Another trip here brent's traveling uh we could just if it was a website is brent. 00:41:35.737 --> 00:41:37.397 Traveling it'd just be yes yeah uh. 00:41:37.397 --> 00:41:41.957 Pack trippy the 2i love child of ping and trace route. 00:41:41.957 --> 00:41:43.017 Sounds like you could have used. 00:41:43.017 --> 00:41:44.317 This just the other day actually. 00:41:44.317 --> 00:41:45.857 Do we know about trippy i. 00:41:45.857 --> 00:41:46.557 Don't know if we do. 00:41:46.557 --> 00:41:52.637 It's a 2e huh let's go look this up trippy uh a network diagnostic tool oh my 00:41:52.637 --> 00:41:57.877 god it's a riff it's a riff on the clippy logo too which is funny oh i like 00:41:57.877 --> 00:42:03.397 this i like this a lot brent i think you could use that i could use this actually what's. 00:42:03.397 --> 00:42:03.797 It written in. 00:42:03.797 --> 00:42:07.677 The question oh look at that did you know this already no. 00:42:07.677 --> 00:42:08.517 I just wanted to know. 00:42:08.517 --> 00:42:12.597 Yeah 99.6 rest it's. 00:42:12.597 --> 00:42:13.677 Not 100 but i'll take it. 00:42:13.677 --> 00:42:20.197 Yeah it's pretty close so that's trippy all right that's good um now do we have 00:42:20.197 --> 00:42:21.277 you said there was three of them. 00:42:21.277 --> 00:42:27.637 Yes i did there's one more worried you might get bored during the two-week challenge 00:42:27.637 --> 00:42:32.357 try tty solitaire now with mouse support. 00:42:32.357 --> 00:42:36.497 Tty solitaire all right solid. 00:42:36.497 --> 00:42:40.577 You know they told you your flight would have wi-fi it doesn't but you already 00:42:40.577 --> 00:42:42.957 downloaded tty solitaire turd. 00:42:42.957 --> 00:42:47.817 Ferguson coming in with some good two-y picks. I'm feeling the two-y energy. 00:42:48.037 --> 00:42:50.877 I'm feeling like this challenge is going to happen, boys. I'm feeling it. 00:42:50.957 --> 00:42:53.497 Are there any two-y games we can combine these two things? 00:42:53.757 --> 00:42:55.977 Well, there's the Solitaire, I suppose. I suppose. 00:42:56.817 --> 00:43:01.217 You know, on my flight to this here continent, there was someone the entire 00:43:01.217 --> 00:43:05.837 flight that played Solitaire, and I could not believe it, but maybe... 00:43:05.837 --> 00:43:06.257 With cards? 00:43:06.717 --> 00:43:09.477 No, no, no, no, no. On their phone. 00:43:09.817 --> 00:43:13.377 My wife could do it with cards. She brings a deck of cards in her purse. 00:43:13.517 --> 00:43:14.497 It's a great idea to have. 00:43:14.757 --> 00:43:18.177 We were out and about last night, and we had a half hour to kill with the shuttle, 00:43:18.237 --> 00:43:21.777 so she just busts out the cards. She just goes to it. Great battery life. 00:43:23.977 --> 00:43:28.237 Wakangaroo Paradox came in with 30,000 sats across three boosts. 00:43:32.272 --> 00:43:36.272 Great coverage of the rust drama recently i really appreciated the objective 00:43:36.272 --> 00:43:44.572 breakdown of events and your take on it also loved the deep dive sorry brent he says i think oh. 00:43:44.572 --> 00:43:46.512 You know brent you know hold on brent's. 00:43:46.512 --> 00:43:47.472 Got a reputation. 00:43:47.472 --> 00:43:55.652 No i was trying to speed right past that one so you wouldn't have a chance to play it, 00:43:56.472 --> 00:43:59.332 shakes fist at you both he continues 00:43:59.332 --> 00:44:02.232 here i think you could sprinkle these once 00:44:02.232 --> 00:44:05.652 in a while and that could be enjoyable for people who aren't super technical 00:44:05.652 --> 00:44:08.712 good way to learn things too also plus 00:44:08.712 --> 00:44:12.632 one for the tui challenge i'm all for spending as much time as possible in the 00:44:12.632 --> 00:44:16.812 terminal versus the browser i think a tui challenge with a point penalty for 00:44:16.812 --> 00:44:22.772 mouse usage could be a fun spin oh love the planet nix coverage could not justify 00:44:22.772 --> 00:44:27.512 flying from europe to go for a couple days over 1,000 euros total for that trip. 00:44:28.272 --> 00:44:33.292 Can we expect you guys to make the trip to NixCon EU, maybe, in the coming years? 00:44:33.372 --> 00:44:37.612 These usually take place October-ish in Germany or around there. 00:44:37.792 --> 00:44:41.412 I imagine the price would be an issue, but, you know, the beer here is worth it. 00:44:43.052 --> 00:44:43.512 Yes. 00:44:43.932 --> 00:44:47.252 The truthful answer is, I imagine when my kids are a bit older, 00:44:47.272 --> 00:44:50.912 I'll probably be traveling on longer trips, where I could go somewhere I could 00:44:50.912 --> 00:44:53.232 spend like two weeks, or a week. 00:44:53.232 --> 00:44:56.492 You know that would be really great but that'll probably 00:44:56.492 --> 00:44:59.152 still be a couple of years maybe every now and then you know i never want to say 00:44:59.152 --> 00:45:02.012 never you never know right maybe wes could talk me into something i think 00:45:02.012 --> 00:45:07.672 you guys can be pretty convincing when you put your minds to it thank you for 00:45:07.672 --> 00:45:11.492 the boost congo it's good to hear from you the musa came in with 5 000 sats 00:45:11.492 --> 00:45:16.132 firstly i finally got around to say in my own bitcoin note with nick's bitcoin 00:45:16.132 --> 00:45:20.572 hey that's great to hear and i'm using AlbiHub, 00:45:20.652 --> 00:45:24.092 thanks to Wes and the community for providing a good starting point to do so. 00:45:24.432 --> 00:45:28.952 I am personally excited for GNOME 48, as controlling the Orca screen reader 00:45:28.952 --> 00:45:31.492 under Waylon has taken a big step forward. 00:45:32.052 --> 00:45:34.932 I've wanted to get XOR off for ages now. 00:45:35.412 --> 00:45:41.312 Come May and Nix2505, I may just be able to do that. That's great to hear. 00:45:41.392 --> 00:45:41.972 Yeah, that's rad. 00:45:42.292 --> 00:45:44.492 Yeah, there is some nice changes there. And Wes, look at you, 00:45:44.812 --> 00:45:46.232 helping people get AlbiHub up and going. 00:45:46.492 --> 00:45:51.912 Yeah, and props to folks like the muso and draca who uh have taken the leads 00:45:51.912 --> 00:45:56.112 on getting the module going i got a base flake happening but also i've been 00:45:56.112 --> 00:45:59.812 negligent so this is a great reminder uh i'll go try to see if i can spend some 00:45:59.812 --> 00:46:04.392 time in that repo adversary 17 boosts in with 5 000 sats, 00:46:07.050 --> 00:46:10.330 The Dynamic We Don't Even Knows are pretty funny. 00:46:10.710 --> 00:46:15.670 Oh, yeah. The members version somehow got set up with Dynamic AI inserted ads 00:46:15.670 --> 00:46:16.930 for all kinds of crazy things. 00:46:17.210 --> 00:46:19.090 We got a good kick out of them the whole show. 00:46:19.290 --> 00:46:19.550 Thank you. 00:46:19.770 --> 00:46:25.590 Of course, the only proper song to play on the Clinton sexy saxophone is Careless Whisper. 00:46:25.750 --> 00:46:27.990 That was true. Yeah, that would have been, yeah, that's true. 00:46:28.430 --> 00:46:29.850 Nice to hear from you adversaries. Thank you. 00:46:30.410 --> 00:46:34.690 Well, Brooke Loves You sent in 3,535 sets. 00:46:35.970 --> 00:46:39.030 Hey jb have y'all tried kd plasma 00:46:39.030 --> 00:46:45.050 mobile yet i'm daily driving that thing on my minis forum v3 with fedora and 00:46:45.050 --> 00:46:50.270 it's pretty awesome i recommend giving linux on a tablet a try if y'all haven't 00:46:50.270 --> 00:46:55.010 in a while or even at all keep up the good work and thanks for making my work 00:46:55.010 --> 00:46:57.470 travel more enjoyable this. 00:46:57.470 --> 00:47:01.570 Is a great suggestion brooke and you're kind of reading my mind, 00:47:01.810 --> 00:47:06.350 this Friday I was browsing Amazon looking to see if there's like quote-unquote 00:47:06.350 --> 00:47:10.050 Linux x86 tablets or even Linux ARM tablets. 00:47:10.350 --> 00:47:14.090 You know, I do this thing where I have tablets around the home and I want to 00:47:14.090 --> 00:47:17.470 have more in the studio to like control home assist in different areas and why 00:47:17.470 --> 00:47:20.370 have Android on there when I could have Linux on there and it would give me 00:47:20.370 --> 00:47:25.030 an excuse to play with Plasma Mobile properly which I've only ever done in emulators. 00:47:25.230 --> 00:47:27.730 And it's probably more realistic. I was going to say we pressured Brent because 00:47:27.730 --> 00:47:28.830 it seems like his kind of thing. 00:47:28.970 --> 00:47:29.650 Yeah, yeah, you're right. 00:47:29.650 --> 00:47:31.770 If you're already doing it. Or we get double cores. 00:47:31.850 --> 00:47:34.630 Well, I could take my learnings and use that to pressure him. 00:47:34.690 --> 00:47:36.450 Or Flash's stuff and set them up. 00:47:36.570 --> 00:47:40.570 With me, if you get me in right, you know, the right mode, I'll do it in a Flash. 00:47:40.670 --> 00:47:42.670 But with Brent, it's going to take like two years, you know, 00:47:42.770 --> 00:47:45.190 before Brent gets an Android tablet that runs Linux. 00:47:45.730 --> 00:47:49.170 Well, you know, only one of us carries two devices in their pockets. 00:47:49.170 --> 00:47:53.190 So I think, you know, having a backup built in, you're more suited for this thing. 00:47:54.790 --> 00:48:01.550 Thank you for the boost, Brooke. Appreciate it. Ambient Noise comes in with 3,930 sats. 00:48:03.813 --> 00:48:07.813 And they say, sorry, this took so long, but here is my write-up on how to control 00:48:07.813 --> 00:48:11.333 the front gate via MeshTastic and MQTT. 00:48:12.533 --> 00:48:13.493 Oh, yes. 00:48:13.833 --> 00:48:14.313 Awesome. 00:48:14.553 --> 00:48:20.033 This was one of the things we wondered would be, could you do IoT control with MeshTastic? 00:48:20.193 --> 00:48:23.893 He sends us his GitHub repo, which we will include in the show notes, 00:48:23.993 --> 00:48:28.153 and it's instructions to create an MQTT controlled input and output board that 00:48:28.153 --> 00:48:32.293 runs its own logic on low power radio instances. 00:48:33.113 --> 00:48:36.853 And you can use it to control your gate. 00:48:37.013 --> 00:48:37.433 Neat. 00:48:37.573 --> 00:48:38.433 That is so... 00:48:38.433 --> 00:48:40.053 A whole bunch of comments in here too. 00:48:40.293 --> 00:48:45.913 I'm saving that. I am saving that. That was really great. Thank you for sending that in, AmbientNoise. 00:48:46.333 --> 00:48:50.473 And well done. Well done. Thank you, everybody who participated, 00:48:50.693 --> 00:48:53.473 including you SAT streamers. 25 of you stream SATs. 00:48:53.573 --> 00:48:57.373 We stacked a humble 22,923 SATs. 00:48:57.593 --> 00:49:00.153 Not too bad for those of you just sitting back and enjoying the show. 00:49:00.313 --> 00:49:01.393 Thank you very much for doing that. 00:49:01.793 --> 00:49:05.133 Then we combined that with all the people that generously boosted in with the 00:49:05.133 --> 00:49:08.333 message. We read the ones above the 2,000-sat cutoff line. 00:49:08.853 --> 00:49:15.433 And we stacked 156,476 sats. Not our strongest week. 00:49:16.573 --> 00:49:21.253 I'm not going to say it's a total loss, though. But, you know, it could be better. 00:49:21.413 --> 00:49:23.993 It could be better, especially with some of our ambitious plans we have coming 00:49:23.993 --> 00:49:25.033 up for the rest of the year. 00:49:25.413 --> 00:49:28.353 So if you'd like to get in on the fun, there's a few ways to do it. 00:49:28.413 --> 00:49:29.393 But you've got to get some sats. 00:49:29.913 --> 00:49:34.393 Strike is a great way to do it. in over 110 countries, River in the US, Bitcoin Well in Canada. 00:49:34.733 --> 00:49:38.153 Get those sats, send them over to Lightning to a podcasting 2.0 app like Fountain. 00:49:38.533 --> 00:49:41.793 The workflows also in Fountain are really simple too now. They're getting easier 00:49:41.793 --> 00:49:44.093 and easier to just do it within all one app. 00:49:44.613 --> 00:49:47.433 And it just keeps getting better. You can send your message in and we'll read 00:49:47.433 --> 00:49:48.873 it on the show above 2,000 sats. 00:49:49.193 --> 00:49:53.753 Thank you everybody who supports this episode and all 31 of you who boosted 00:49:53.753 --> 00:49:58.533 in and supported episode 608 of your Unplugged program. It really does mean a lot to us. 00:49:58.793 --> 00:50:02.753 We appreciate it. And of course, Big shout out to our members who keep us going, too. 00:50:03.153 --> 00:50:05.413 You are all fantastic and much appreciated. 00:50:07.702 --> 00:50:12.102 Well, moving right along, gentlemen, moving right along, we have a pick that 00:50:12.102 --> 00:50:14.482 may help some of you break your grammarly habit. 00:50:15.002 --> 00:50:15.482 Oh. 00:50:16.062 --> 00:50:18.942 Have you wondered what are you going to do to get over your grammarly habit? 00:50:19.162 --> 00:50:21.482 Finally, take back your freedom from big grammar. 00:50:21.702 --> 00:50:26.482 Yep. Well, that's where Eloquent comes in. It runs as a local service in the 00:50:26.482 --> 00:50:30.602 background to do local offline, I guess, proofreading. 00:50:30.822 --> 00:50:34.962 It uses a language tool server, and it's available as a backend instance to 00:50:34.962 --> 00:50:39.982 Firefox, LibreOffice, and others. It is GPL 3. 00:50:40.002 --> 00:50:45.782 It does also have a little standalone desktop GUI where you can paste your text 00:50:45.782 --> 00:50:50.242 in and then it gives you a Grammarly-esque pop-up to do spelling. 00:50:50.482 --> 00:50:50.602 Neat. 00:50:51.182 --> 00:50:53.382 No, if people have never used Grammarly, they have no idea what I'm talking 00:50:53.382 --> 00:51:00.342 about, but it's sort of like grammar and spelling and sentence structure all in one. 00:51:00.742 --> 00:51:03.582 And it's a good service, but to do this, 00:51:03.762 --> 00:51:07.082 they're reading everything you write and they want to integrate into everything 00:51:07.082 --> 00:51:10.722 constantly and the fact that you could actually run this as a back-end instance 00:51:10.722 --> 00:51:15.722 for firefox which i have not done well it looks really great like that is the 00:51:15.722 --> 00:51:19.502 perfect combination for me um and it is also available as a flat hub. 00:51:19.502 --> 00:51:24.442 Well and this backing tool is cool language tool open source proofreading software. 00:51:24.442 --> 00:51:25.302 Yeah english. 00:51:25.302 --> 00:51:29.382 Spanish french german portuguese polish dutch and more than 20 other languages. 00:51:29.382 --> 00:51:29.702 Yeah. 00:51:30.723 --> 00:51:33.323 Finds many errors that a simple spell checker cannot detect. 00:51:33.803 --> 00:51:38.703 There's a collection of tooling out there right now, like this language tool, 00:51:39.263 --> 00:51:44.743 and Piper from the Homosystem folks in Whisper, which do text-to-speech and 00:51:44.743 --> 00:51:48.883 speech-to-text, and then they have their Wyoming protocol, which lets it communicate. 00:51:49.383 --> 00:51:55.063 All of it is open source, all of it running on Linux, and we're not doing anything 00:51:55.063 --> 00:51:56.503 with it. It's really weird. 00:51:57.163 --> 00:51:59.623 Maybe that's some show projects we need to get ahead of. 00:52:00.023 --> 00:52:04.283 You can actually even train your own voices with it. You can have it model on 00:52:04.283 --> 00:52:06.483 your own voice and generate stuff. 00:52:06.623 --> 00:52:08.483 It's just right there for the taking. 00:52:08.723 --> 00:52:12.143 And some project just needs to integrate it into some sort of application or something. 00:52:12.423 --> 00:52:14.583 I mean, it's very useful in Home Assistant. 00:52:14.763 --> 00:52:15.323 Right, of course. 00:52:15.403 --> 00:52:21.863 But Piper alone and Whisper alone just feels like there's a lot of potential there. 00:52:22.363 --> 00:52:25.883 Anyways, today we're talking about Eloquent, and we'll have a link to that in 00:52:25.883 --> 00:52:28.123 the show notes should you want to check it out. 00:52:28.123 --> 00:52:32.083 I also see it looks like there's some stuff that does makes like a language 00:52:32.083 --> 00:52:37.623 or an LSP implementation on top of language tool so you can get this kind of 00:52:37.623 --> 00:52:39.003 stuff in your VS code too baby. 00:52:40.003 --> 00:52:43.243 And don't forget we're trying to raise some funds for headset for the boys so 00:52:43.243 --> 00:52:46.163 if you got any tips for gaming or games you love or co-op games something we 00:52:46.163 --> 00:52:51.063 can do at Linux Fest do boost in and support the show with a contribution towards 00:52:51.063 --> 00:52:54.283 the headsets and a message we could read we really do appreciate that and then, 00:52:54.943 --> 00:52:57.783 we'd love to see you at Linux Fest in just 25 days. 00:52:59.163 --> 00:53:02.483 Link to the schedule and all of that is in the show notes as well and 00:53:02.483 --> 00:53:06.743 you know where you find that get ready for this linuxunplugged.com 00:53:06.743 --> 00:53:10.423 slash 608 that's all you need to know linuxunplugged.com 00:53:10.423 --> 00:53:18.703 slash 608 and of course we love it when you join us live it just gives it a 00:53:18.703 --> 00:53:24.283 vibe and we make it a tuesday on a sunday it begins at 10 a.m pacific of course 00:53:24.283 --> 00:53:27.703 we have it in your local time at jupiterbroadcasting.com slash calendar. 00:53:27.943 --> 00:53:33.223 If you're enjoying a podcasting 2.0 app, I try to get it marked as pending 24 hours ahead of time. 00:53:33.403 --> 00:53:36.163 So you can just tap play in your podcasting app of choice. 00:53:36.783 --> 00:53:40.543 It's pretty cool. It's pretty nice. That mumble room gets fired up too. 00:53:40.663 --> 00:53:45.263 It's cranking now that we're going and details for that are jupiterbroadcasting.com slash mumble. 00:53:45.523 --> 00:53:47.923 Last but not least, if you're looking for a little something extra, 00:53:48.163 --> 00:53:52.723 go check out The Launch. It's on the JB site and weeklylaunch.rocks. It's a brand new show. 00:53:53.003 --> 00:53:55.643 Thanks so much for joining us. See you next Sunday.
Previous episode

Related episodes

Search

Search

Listen on

Apple Podcasts Spotify RSS feed

Tags

Business Partner