Podcasts about Kernel

As we continue our journey through Ordinary Time, Charlette and David guide us through this week's Gospel reading from Luke 17:5-10. With reflections on how even when things are rough, Christ assures us that our faith is enough, and how Jesus tells us to "Just do it." Consider how this passage speaks to you this week!Faith to Go is a ministry of The Episcopal Diocese of San Diego. Click here to learn more about EDSD's great work in our region and how you can support this ministry.Remember to get in contact with us!Email: faithtogo@edsd.orgInstagram: @faithtogo

Elizabeth Figura is a Wine developer at Code Weavers. We discuss how Wine and Proton make it possible to run Windows applications on other operating systems. Related links WineHQ Proton Crossover Direct3D MoltenVK XAudio2 Mesa 3D Graphics Library Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Elizabeth Figuera. She's a wine developer at Code Weavers. And today we're gonna talk about what that is and, uh, all the work that goes into it. [00:00:09] Elizabeth: Thank you Jeremy. I'm glad to be here. What's Wine [00:00:13] Jeremy: I think the first thing we should talk about is maybe saying what Wine is because I think a lot of people aren't familiar with the project. [00:00:20] Elizabeth: So wine is a translation layer. in fact, I would say wine is a Windows emulator. That is what the name originally stood for. it re implements the entire windows. Or you say win 32 API. so that programs that make calls into the API, will then transfer that code to wine and and we allow that Windows programs to run on, things that are not windows. So Linux, Mac, os, other operating systems such as Solaris and BSD. it works not by emulating the CPU, but by re-implementing every API, basically from scratch and translating them to their equivalent or writing new code in case there is no, you know, equivalent. System Calls [00:01:06] Jeremy: I believe what you're doing is you're emulating system calls. Could you explain what those are and, and how that relates to the project? [00:01:15] Elizabeth: Yeah. so system call in general can be used, referred to a call into the operating system, to execute some functionality that's built into the operating system. often it's used in the context of talking to the kernel windows applications actually tend to talk at a much higher level, because there's so much, so much high level functionality built into Windows. When you think about, as opposed to other operating systems that we basically, we end up end implementing much higher level behavior than you would on Linux. [00:01:49] Jeremy: And can you give some examples of what some of those system calls would be and, I suppose how they may be higher level than some of the Linux ones. [00:01:57] Elizabeth: Sure. So of course you have like low level calls like interacting with a file system, you know, created file and read and write and such. you also have, uh, high level APIs who interact with a sound driver. [00:02:12] Elizabeth: There's, uh, one I was working on earlier today, called XAudio where you, actually, you know, build this bank of of sounds. It's meant to be, played in a game and then you can position them in various 3D space. And the, and the operating system in a sense will, take care of all of the math that goes into making that work. [00:02:36] Elizabeth: That's all running on your computer and. And then it'll send that audio data to the sound card once it's transformed it. So it sounds like it's coming from a certain space. a lot of other things like, you know, parsing XML is another big one. That there's a lot of things. The, there, the, the, the space is honestly huge [00:02:59] Jeremy: And yeah, I can sort of see how those might be things you might not expect to be done by the operating system. Like you gave the example of 3D audio and XML parsing and I think XML parsing in, in particular, you would've thought that that would be something that would be handled by the, the standard library of whatever language the person was writing their application as. [00:03:22] Jeremy: So that's interesting that it's built into the os. [00:03:25] Elizabeth: Yeah. Well, and languages like, see it's not, it isn't even part of the standard library. It's higher level than that. It's, you have specific libraries that are widespread but not. Codified in a standard, but in Windows you, in Windows, they are part of the operating system. And in fact, there's several different, XML parsers in the operating system. Microsoft likes to deprecate old APIs and make new ones that do the same thing very often. [00:03:53] Jeremy: And something I've heard about Windows is that they're typically very reluctant to break backwards compatibility. So you say they're deprecated, but do they typically keep all of them still in there? [00:04:04] Elizabeth: It all still It all still works. [00:04:07] Jeremy: And that's all things that wine has to implement as well to make sure that the software works as well. [00:04:14] Jeremy: Yeah. [00:04:14] Elizabeth: Yeah. And, and we also, you know, need to make it work. we also need to implement those things to make old, programs work because there is, uh, a lot of demand, at least from, at least from people using wine for making, for getting some really old programs, working from the. Early nineties even. What people run with Wine (Productivity, build systems, servers) [00:04:36] Jeremy: And that's probably a good, thing to talk about in terms of what, what are the types of software that, that people are trying to run with wine, and what operating system are they typically using? [00:04:46] Elizabeth: Oh, in terms of software, literally all kinds, any software you can imagine that runs on Windows, people will try to run it on wine. So we're talking games, office software productivity, software accounting. people will run, build systems on wine, build their, just run, uh, build their programs using, on visual studio, running on wine. people will run wine on servers, for example, like software as a service kind of things where you don't even know that it's running on wine. really super domain specific stuff. Like I've run astronomy, software, and wine. Design, computer assisted design, even hardware drivers can sometimes work unwind. There's a bit of a gray area. How games are different [00:05:29] Jeremy: Yeah, it's um, I think from. Maybe the general public, or at least from what I've seen, I think a lot of people's exposure to it is for playing games. is there something different about games versus all those other types of, productivity software and office software that, that makes supporting those different. [00:05:53] Elizabeth: Um, there's some things about it that are different. Games of course have gotten a lot of publicity lately because there's been a huge push, largely from valve, but also some other companies to get. A lot of huge, wide range of games working well under wine. And that's really panned out in the, in a way, I think, I think we've largely succeeded. [00:06:13] Elizabeth: We've made huge strides in the past several years. 5, 5, 10 years, I think. so when you talk about what makes games different, I think, one thing games tend to do is they have a very limited set of things they're working with and they often want to make things run fast, and so they're working very close to the me They're not, they're not gonna use an XML parser, for example. [00:06:44] Elizabeth: They're just gonna talk directly as, directly to the graphics driver as they can. Right. And, and probably going to do all their own sound design. You know, I did talk about that XAudio library, but a lot of games will just talk directly as, directly to the sound driver as Windows Let some, so this is a often a blessing, honestly, because it means there's less we have to implement to make them work. when you look at a lot of productivity applications, and especially, the other thing that makes some productivity applications harder is, Microsoft makes 'em, and They like to, make a library, for use in this one program like Microsoft Office and then say, well, you know, other programs might use this as well. Let's. Put it in the operating system and expose it and write an API for it and everything. And maybe some other programs use it. mostly it's just office, but it means that office relies on a lot of things from the operating system that we all have to reimplement. [00:07:44] Jeremy: Yeah, that's somewhat counterintuitive because when you think of games, you think of these really high performance things that that seem really complicated. But it sounds like from what you're saying, because they use the lower level primitives, they're actually easier in some ways to support. [00:08:01] Elizabeth: Yeah, certainly in some ways, they, yeah, they'll do things like re-implement the heap allocator because the built-in heap allocator isn't fast enough for them. That's another good example. What makes some applications hard to support (Some are hard, can't debug other people's apps) [00:08:16] Jeremy: You mentioned Microsoft's more modern, uh, office suites. I, I've noticed there's certain applications that, that aren't supported. Like, for example, I think the modern Adobe Creative Suite. What's the difference with software like that and does that also apply to the modern office suite, or is, or is that actually supported? [00:08:39] Elizabeth: Well, in one case you have, things like Microsoft using their own APIs that I mentioned with Adobe. That applies less, I suppose, but I think to some degree, I think to some degree the answer is that some applications are just hard and there's, and, and there's no way around it. And, and we can only spend so much time on a hard application. I. Debugging things. Debugging things can get very hard with wine. Let's, let me like explain that for a minute because, Because normally when you think about debugging an application, you say, oh, I'm gonna open up my debugger, pop it in, uh, break at this point, see what like all the variables are, or they're not what I expect. Or maybe wait for it to crash and then get a back trace and see where it crashed. And why you can't do that with wine, because you don't have the application, you don't have the symbols, you don't have your debugging symbols. You don't know anything about the code you're running unless you take the time to disassemble and decompile and read through it. And that's difficult every time. It's not only difficult, every time I've, I've looked at a program and been like, I really need to just. I'm gonna just try and figure out what the program is doing. [00:10:00] Elizabeth: It takes so much time and it is never worth it. And sometimes you have to, sometimes you have no other choice, but usually you end up, you ask to rely on seeing what calls it makes into the operating system and trying to guess which one of those is going wrong. Now, sometimes you'll get lucky and it'll crash in wine code, or sometimes it'll make a call into, a function that we don't implement yet, and we know, oh, we need to implement that function. But sometimes it does something, more obscure and we have to figure out, well, like all of these millions of calls it made, which one of them is, which one of them are we implementing incorrectly? So it's returning the wrong result or not doing something that it should. And, then you add onto that the. You know, all these sort of harder to debug things like memory errors that we could make. And it's, it can be very difficult and so sometimes some applications just suffer from those hard bugs. and sometimes it's also just a matter of not enough demand for something for us to spend a lot of time on it. [00:11:11] Elizabeth: Right. [00:11:14] Jeremy: Yeah, I can see how that would be really challenging because you're, like you were saying, you don't have the symbols, so you don't have the source code, so you don't know what any of this software you're supporting, how it was actually written. And you were saying that I. A lot of times, you know, there may be some behavior that's wrong or a crash, but it's not because wine crashed or there was an error in wine. [00:11:42] Jeremy: so you just know the system calls it made, but you don't know which of the system calls didn't behave the way that the application expected. [00:11:50] Elizabeth: Exactly. Test suite (Half the code is tests) [00:11:52] Jeremy: I can see how that would be really challenging. and wine runs so many different applications. I'm, I'm kind of curious how do you even track what's working and what's not as you, you change wine because if you support thousands or tens thousands of applications, you know, how do you know when you've got a, a regression or not? [00:12:15] Elizabeth: So, it's a great question. Um, probably over half of wine by like source code volume. I actually actually check what it is, but I think it's, i, I, I think it's probably over half is what we call is tests. And these tests serve two purposes. The one purpose is a regression test. And the other purpose is they're conformance tests that test, that test how, uh, an API behaves on windows and validates that we are behaving the same way. So we write all these tests, we run them on windows and you know, write the tests to check what the windows returns, and then we run 'em on wine and make sure that that matches. and we have just such a huge body of tests to make sure that, you know, we're not breaking anything. And that every, every, all the code that we, that we get into wine that looks like, wow, it's doing that really well. Nope, that's what Windows does. The test says so. So pretty much any code that we, any new code that we get, it has to have tests to validate, to, to demonstrate that it's doing the right thing. [00:13:31] Jeremy: And so rather than testing against a specific application, seeing if it works, you're making a call to a Windows system call, seeing how it responds, and then making the same call within wine and just making sure they match. [00:13:48] Elizabeth: Yes, exactly. And that is obviously, or that is a lot more, automatable, right? Because otherwise you have to manually, you know, there's all, these are all graphical applications. [00:14:02] Elizabeth: You'd have to manually do the things and make sure they work. Um, but if you write automateable tests, you can just run them all and the machine will complain at you if it fails it continuous integration. How compatibility problems appear to users [00:14:13] Jeremy: And because there's all these potential compatibility issues where maybe a certain call doesn't behave the way an application expects. What, what are the types of what that shows when someone's using software? I mean, I, I think you mentioned crashes, but I imagine there could be all sorts of other types of behavior. [00:14:37] Elizabeth: Yes, very much so. basically anything, anything you can imagine again is, is what will happen. You can have, crashes are the easy ones because you know when and where it crashed and you can work backwards from there. but you can also get, it can, it could hang, it could not render, right? Like maybe render a black screen. for, you know, for games you could very frequently have, graphical glitches where maybe some objects won't render right? Or the entire screen will be read. Who knows? in a very bad case, you could even bring down your system and we usually say that's not wine's fault. That's the graphics library's fault. 'cause they're not supposed to do that, uh, no matter what we do. But, you know, sometimes we have to work around that anyway. but yeah, there's, there's been some very strange and idiosyncratic bugs out there too. [00:15:33] Jeremy: Yeah. And like you mentioned that uh, there's so many different things that could have gone wrong that imagine's very difficult to find. Yeah. And when software runs through wine, I think, Performance is comparable to native [00:15:49] Jeremy: A lot of our listeners will probably be familiar with running things in a virtual machine, and they know that there's a big performance impact from doing that. [00:15:57] Jeremy: How does the performance of applications compare to running natively on the original Windows OS versus virtual machines? [00:16:08] Elizabeth: So. In theory. and I, I haven't actually done this recently, so I can't speak too much to that, but in theory, the idea is it's a lot faster. so there, there, is a bit of a joke acronym to wine. wine is not an emulator, even though I started out by saying wine is an emulator, and it was originally called a Windows emulator. but what this basically means is wine is not a CPU emulator. It doesn't, when you think about emulators in a general sense, they're often, they're often emulators for specific CPUs, often older ones like, you know, the Commodore emulator or an Amiga emulator. but in this case, you have software that's written for an x86 CPU. And it's running on an x86 CPU by giving it the same instructions that it's giving on windows. It's just that when it says, now call this Windows function, it calls us instead. So that all should perform exactly the same. The only performance difference at that point is that all should perform exactly the same as opposed to a, virtual machine where you have to interpret the instructions and maybe translate them to a different instruction set. The only performance difference is going to be, in the functions that we are implementing themselves and we try to, we try to implement them to perform. As well, or almost as well as windows. There's always going to be a bit of a theoretical gap because we have to translate from say, one API to another, but we try to make that as little as possible. And in some cases, the operating system we're running on is, is just better than Windows and the libraries we're using are better than Windows. [00:18:01] Elizabeth: And so our games will run faster, for example. sometimes we can, sometimes we can, do a better job than Windows at implementing something that's, that's under our purview. there there are some games that do actually run a little bit faster in wine than they do on Windows. [00:18:22] Jeremy: Yeah, that, that reminds me of how there's these uh, gaming handhelds out now, and some of the same ones, they have a, they either let you install Linux or install windows, or they just come with a pre-installed, and I believe what I've read is that oftentimes running the same game on both operating systems, running the same game on Linux, the battery life is better and sometimes even the performance is better with these handhelds. [00:18:53] Jeremy: So it's, it's really interesting that that can even be the case. [00:18:57] Elizabeth: Yeah, it's really a testament to the huge amount of work that's gone into that, both on the wine side and on the, side of the graphics team and the colonel team. And, and of course, you know, the years of, the years of, work that's gone into Linux, even before these gaming handhelds were, were even under consideration. Proton and Valve Software's role [00:19:21] Jeremy: And something. So for people who are familiar with the handhelds, like the steam deck, they may have heard of proton. Uh, I wonder if you can explain what proton is and how it relates to wine. [00:19:37] Elizabeth: Yeah. So, proton is basically, how do I describe this? So, proton is a sort of a fork, uh, although we try to avoid the term fork. It's a, we say it's a downstream distribution because we contribute back up to wine. so it is a, it is, it is a alternate distribution fork of wine. And it's also some code that basically glues wine into, an embedding application originally intended for steam, and developed for valve. it has also been used in, others, but it has also been used in other software. it, so where proton differs from wine besides the glue part is it has some, it has some extra hacks in it for bugs that are hard to fix and easy to hack around as some quick hacks for, making games work now that are like in the process of going upstream to wine and getting their code quality improved and going through review. [00:20:54] Elizabeth: But we want the game to work now, when we distribute it. So that'll, that'll go into proton immediately. And then once we have, once the patch makes it upstream, we replace it with the version of the patch from upstream. there's other things to make it interact nicely with steam and so on. And yeah, I think, yeah, I think that's, I got it. [00:21:19] Jeremy: Yeah. And I think for people who aren't familiar, steam is like this, um, I, I don't even know what you call it, like a gaming store and a [00:21:29] Elizabeth: store game distribution service. it's got a huge variety of games on it, and you just publish. And, and it's a great way for publishers to interact with their, you know, with a wider gaming community, uh, after it, just after paying a cut to valve of their profits, they can reach a lot of people that way. And because all these games are on team and, valve wants them to work well on, on their handheld, they contracted us to basically take their entire catalog, which is huge, enormous. And trying and just step by step. Fix every game and make them all work. [00:22:10] Jeremy: So, um, and I guess for people who aren't familiar Valve, uh, softwares the company that runs steam, and so it sounds like they've asked, uh, your company to, to help improve the compatibility of their catalog. [00:22:24] Elizabeth: Yes. valve contracted us and, and again, when you're talking about wine using lower level libraries, they've also contracted a lot of other people outside of wine. Basically, the entire stack has had a tremendous, tremendous investment by valve software to make gaming on Linux work. Well. The entire stack receives changes to improve Wine compatibility [00:22:48] Jeremy: And when you refer to the entire stack, like what are some, some of those pieces, at least at a high level. [00:22:54] Elizabeth: I, I would, let's see, let me think. There is the wine project, the. Mesa Graphics Libraries. that's a, that's another, you know, uh, open source, software project that existed, has existed for a long time. But Valve has put a lot of, uh, funding and effort into it, the Linux kernel in various different ways. [00:23:17] Elizabeth: the, the desktop, uh, environment and Window Manager for, um, are also things they've invested in. [00:23:26] Jeremy: yeah. Everything that the game needs, on any level and, and that the, and that the operating system of the handheld device needs. Wine's history [00:23:37] Jeremy: And wine's been going on for quite a while. I think it's over a decade, right? [00:23:44] Elizabeth: I believe. Oh, more than, oh, far more than a decade. I believe it started in 1990, I wanna say about 1995, mid nineties. I'm, I probably have that date wrong. I believe Wine started about the mid nineties. [00:24:00] Jeremy: Mm. [00:24:00] Elizabeth: it's going on for three decades at this rate. [00:24:03] Jeremy: Wow. Okay. [00:24:06] Jeremy: And so all this time, how has the, the project sort of sustained itself? Like who's been involved and how has it been able to keep going this long? [00:24:18] Elizabeth: Uh, I think as is the case with a lot of free software, it just, it just keeps trudging along. There's been. There's been times where there's a lot of interest in wine. There's been times where there's less, and we are fortunate to be in a time where there's a lot of interest in it. we've had the same maintainer for almost this entire, almost this entire existence. Uh, Alexander Julliard, there was one person starting who started, maintained it before him and, uh, left it maintainer ship to him after a year or two. Uh, Bob Amstat. And there has been a few, there's been a few developers who have been around for a very long time. a lot of developers who have been around for a decent amount of time, but not for the entire duration. And then a very, very large number of people who come and submit a one-off fix for their individual application that they want to make work. [00:25:19] Jeremy: How does crossover relate to the wine project? Like, it sounds like you had mentioned Valve software hired you for subcontract work, but crossover itself has been around for quite a while. So how, how has that been connected to the wine project? [00:25:37] Elizabeth: So I work for, so the, so the company I work for is Code Weavers and, crossover is our flagship software. so Code Weavers is a couple different things. We have a sort of a porting service where companies will come to us and say, can we port my application usually to Mac? And then we also have a retail service where Where we basically have our own, similar to Proton, but you know, older, but the same idea where we will add some hacks into it for very difficult to solve bugs and we have a, a nice graphical interface. And then, the other thing that we're selling with crossover is support. So if you, you know, try to run a certain application and you buy crossover, you can submit a ticket saying this doesn't work and we now have a financial incentive to fix it. You know, we'll try to, we'll try to fix your, we'll spend company resources to fix your bug, right? So that's been so, so code we v has been around since 1996 and crossover, I don't know the date, but it's crossover has been around for probably about two decades, if I'm not mistaken. [00:27:01] Jeremy: And when you mention helping companies port their software to, for example, MacOS. [00:27:07] Jeremy: Is the approach that you would port it natively to MacOS APIs or is it that you would help them get it running using wine on MacOS? [00:27:21] Elizabeth: Right. That's, so that's basically what makes us so unique among porting companies is that instead of rewriting their software, we just, we just basically stick it inside of crossover and, uh, and, and make it run. [00:27:36] Elizabeth: And the idea has always been, you know, the more we implement, the more we get correct, the, the more applications will, you know, work. And sometimes it works out that way. Sometimes not really so much. And there's always work we have to do to get any given application to work, but. Yeah, so it's, it's very unusual because we don't ask companies for any of their code. We don't need it. We just fix the windows API [00:28:07] Jeremy: And, and so in that case, the ports would be let's say someone sells a MacOS version of their software. They would bundle crossover, uh, with their software. [00:28:18] Elizabeth: Right? And usually when you do this, it doesn't look like there's crossover there. Like it just looks like this software is native, but there is soft, there is crossover under the hood. Loading executables and linked libraries [00:28:32] Jeremy: And so earlier we were talking about how you're basically intercepting the system calls that these binaries are making, whether that's the executable or the, the DLLs from Windows. Um, but I think probably a lot of our listeners are not really sure how that's done. Like they, they may have built software, but they don't know, how do I basically hijack, the system calls that this application is making. [00:29:01] Jeremy: So maybe you could talk a little bit about how that works. [00:29:04] Elizabeth: So there, so there's a couple steps to go into it. when you think about a program that's say, that's a big, a big file that's got all the machine code in it, and then it's got stuff at the beginning saying, here's how the program works and here's where in the file the processor should start running. that's, that's your EXE file. And then in your DLL files are libraries that contain shared code and you have like a similar sort of file. It says, here's the entry point. That runs this function, this, you know, this pars XML function or whatever have you. [00:29:42] Elizabeth: And here's this entry point that has the generate XML function and so on and so forth. And, and, then the operating system will basically take the EXE file and see all the bits in it. Say I want to call the pars XML function. It'll load that DLL and hook it up. So it, so the processor ends up just seeing jump directly to this pars XML function and then run that and then return and so on. [00:30:14] Elizabeth: And so what wine does, is it part of wine? That's part of wine is a library, is that, you know, the implementing that parse XML and read XML function, but part of it is the loader, which is the part of the operating system that hooks everything together. And when we load, we. Redirect to our libraries. We don't have Windows libraries. [00:30:38] Elizabeth: We like, we redirect to ours and then we run our code. And then when you jump back to the program and yeah. [00:30:48] Jeremy: So it's the, the loader that's a part of wine. That's actually, I'm not sure if running the executable is the right term. [00:30:58] Elizabeth: no, I think that's, I think that's a good term. It's, it's, it's, it starts in a loader and then we say, okay, now run the, run the machine code and it's executable and then it runs and it jumps between our libraries and back and so on. [00:31:14] Jeremy: And like you were saying before, often times when it's trying to make a system call, it ends up being handled by a function that you've written in wine. And then that in turn will call the, the Linux system calls or the MacOS system calls to try and accomplish the, the same result. [00:31:36] Elizabeth: Right, exactly. [00:31:40] Jeremy: And something that I think maybe not everyone is familiar with is there's this concept of user space versus kernel space. you explain what the difference is? [00:31:51] Elizabeth: So the way I would explain, the way I would describe a kernel is it's the part of the operating system that can do anything, right? So any program, any code that runs on your computer is talking to the processor, and the processor has to be able to do anything the computer can do. [00:32:10] Elizabeth: It has to be able to talk to the hardware, it has to set up the memory space. That, so actually a very complicated task has to be able to switch to another task. and, and, and, and basically talk to another program and. You have to have something there that can do everything, but you don't want any program to be able to do everything. Um, not since the, not since the nineties. It's about when we realized that we can't do that. so the kernel is a part that can do everything. And when you need to do something that requires those, those permissions that you can't give everyone, you have to talk to the colonel and ask it, Hey, can you do this for me please? And in a very restricted way where it's only the safe things you can do. And a degree, it's also like a library, right? It's the kernel. The kernels have always existed, and since they've always just been the core standard library of the computer that does the, that does the things like read and write files, which are very, very complicated tasks under the hood, but look very simple because all you say is write this file. And talk to the hardware and abstract away all the difference between different drivers. So the kernel is doing all of these things. So because the kernel is a part that can do everything and because when you think about the kernel, it is basically one program that is always running on your computer, but it's only one program. So when a user calls the kernel, you are switching from one program to another and you're doing a lot of complicated things as part of this. You're switching to the higher privilege level where you can do anything and you're switching the state from one program to another. And so it's a it. So this is what we mean when we talk about user space, where you're running like a normal program and kernel space where you've suddenly switched into the kernel. [00:34:19] Elizabeth: Now you're executing with increased privileges in a different. idea of the process space and increased responsibility and so on. [00:34:30] Jeremy: And, and so do most applications. When you were talking about the system calls for handling 3D audio or parsing XML. Are those considered, are those system calls considered part of user space and then those things call the kernel space on your behalf, or how, how would you describe that? [00:34:50] Elizabeth: So most, so when you look at Windows, most of most of the Windows library, the vast, vast majority of it is all user space. most of these libraries that we implement never leave user space. They never need to call into the kernel. there's the, there only the core low level stuff. Things like, we need to read a file, that's a kernel call. when you need to sleep and wait for some seconds, that's a kernel. Need to talk to a different process. Things that interact with different processes in general. not just allocate memory, but allocate a page of memory, like a, from the memory manager and then that gets sub allocated by the heap allocator. so things like that. [00:35:31] Jeremy: Yeah, so if I was writing an application and I needed to open a file, for example, does, does that mean that I would have to communicate with the kernel to, to read that file? [00:35:43] Elizabeth: Right, exactly. [00:35:46] Jeremy: And so most applications, it sounds like it's gonna be a mixture. You're gonna have a lot of things that call user space calls. And then a few, you mentioned more low level ones that are gonna require you to communicate with the kernel. [00:36:00] Elizabeth: Yeah, basically. And it's worth noting that in, in all operating systems, you're, you're almost always gonna be calling a user space library. That might just be a thin wrapper over the kernel call. It might, it's gonna do like just a little bit of work in end call the kernel. [00:36:19] Jeremy: [00:36:19] Elizabeth: In fact, in Windows, that's the only way to do it. Uh, in many other operating systems, you can actually say, you can actually tell the processor to make the kernel call. There is a special instruction that does this and just, and it'll go directly to the kernel, and there's a defined interface for this. But in Windows, that interface is not defined. It's not stable. Or backwards compatible like the rest of Windows is. So even if you wanted to use it, you couldn't. and you basically have to call into the high level libraries or low level libraries, as it were, that, that tell you that create a file. And those don't do a lot. [00:37:00] Elizabeth: They just kind of tweak their parameters a little and then pass them right down to the kernel. [00:37:07] Jeremy: And so wine, it sounds like it needs to implement both the user space calls of windows, but then also the, the kernel, calls as well. But, but wine itself does that, is that only in Linux user space or MacOS user space? [00:37:27] Elizabeth: Yes. This is a very tricky thing. but all of wine, basically all of what is wine runs in, in user space and we use. Kernel calls that are already there to talk to the colonel, to talk to the host Colonel. You have to, and you, you get, you get, you get the sort of second nature of thinking about the Windows, user space and kernel. [00:37:50] Elizabeth: And then there's a host user space and Kernel and wine is running all in user, in the user, in the host user space, but it's emulating the Windows kernel. In fact, one of the weirdest, trickiest parts is I mentioned that you can run some drivers in wine. And those drivers actually, they actually are, they think they're running in the Windows kernel. which in a sense works the same way. It has libraries that it can load, and those drivers are basically libraries and they're making, kernel calls and they're, they're making calls into the kernel library that does some very, very low level tasks that. You're normally only supposed to be able to do in a kernel. And, you know, because the kernel requires some privileges, we kind of pretend we have them. And in many cases, you're even the drivers are using abstractions. We can just implement those abstractions kind of over the slightly higher level abstractions that exist in user space. [00:39:00] Jeremy: Yeah, I hadn't even considered the being able to use hardware devices, but I, I suppose if in, in the end, if you're reproducing the kernel, then whether you're running software or you're talking to a hardware device, as long as you implement the calls correctly, then I, I suppose it works. [00:39:18] Elizabeth: Cause you're, you're talking about device, like maybe it's some kind of USB device that has drivers for Windows, but it doesn't for, for Linux. [00:39:28] Elizabeth: no, that's exactly, that's a, that's kind of the, the example I've used. Uh, I think there is, I think I. My, one of my best success stories was, uh, drivers for a graphing calculator. [00:39:41] Jeremy: Oh, wow. [00:39:42] Elizabeth: That connected via USB and I basically just plugged the windows drivers into wine and, and ran it. And I had to implement a lot of things, but it worked. But for example, something like a graphics driver is not something you could implement in wine because you need the graphics driver on the host. We can't talk to the graphics driver while the host is already doing so. [00:40:05] Jeremy: I see. Yeah. And in that case it probably doesn't make sense to do so [00:40:11] Elizabeth: Right? [00:40:12] Elizabeth: Right. It doesn't because, the transition from user into kernel is complicated. You need the graphics driver to be in the kernel and the real kernel. Having it in wine would be a bad idea. Yeah. [00:40:25] Jeremy: I, I think there's, there's enough APIs you have to try and reproduce that. I, I think, uh, doing, doing something where, [00:40:32] Elizabeth: very difficult [00:40:33] Jeremy: right. Poor system call documentation and private APIs [00:40:35] Jeremy: There's so many different, calls both in user space and in kernel space. I imagine the, the user space ones Microsoft must document to some extent, but, oh. Is that, is that a [00:40:51] Elizabeth: well, sometimes, [00:40:54] Jeremy: Sometimes. Okay. [00:40:55] Elizabeth: I think it's actually better now than it used to be. But some, here's where things get fun, because sometimes there will be, you know, regular documented calls. Sometimes those calls are documented, but the documentation isn't very good. Sometimes programs will just sort of look inside Microsoft's DLLs and use calls that they aren't supposed to be using. Sometimes they use calls that they are supposed to be using, but the documentation has disappeared. just because it's that old of an API and Microsoft hasn't kept it around. sometimes some, sometimes Microsoft, Microsoft own software uses, APIs that were never documented because they never wanted anyone else using them, but they still ship them with the operating system. there was actually a kind of a lawsuit about this because it is an antitrust lawsuit, because by shipping things that only they could use, they were kind of creating a trust. and that got some things documented. At least in theory, they kind of haven't stopped doing it, though. [00:42:08] Jeremy: Oh, so even today they're, they're, I guess they would call those private, private APIs, I suppose. [00:42:14] Elizabeth: I suppose. Uh, yeah, you could say private APIs. but if we want to get, you know, newer versions of Microsoft Office running, we still have to figure out what they're doing and implement them. [00:42:25] Jeremy: And given that they're either, like you were saying, the documentation is kind of all over the place. If you don't know how it's supposed to behave, how do you even approach implementing them? [00:42:38] Elizabeth: and that's what the conformance tests are for. And I, yeah, I mentioned earlier we have this huge body of conformance tests that double is regression tests. if we see an API, we don't know what to do with or an API, we do know, we, we think we know what to do with because the documentation can just be wrong and often has been. Then we write tests to figure out what it's supposed to behave. We kind of guess until we, and, and we write tests and we pass some things in and see what comes out and see what. The see what the operating system does until we figure out, oh, so this is what it's supposed to do and these are the exact parameters in, and, and then we, and, and then we implement it according to those tests. [00:43:24] Jeremy: Is there any distinction in approach for when you're trying to implement something that's at the user level versus the kernel level? [00:43:33] Elizabeth: No, not really. And like I, and like I mentioned earlier, like, well, I mean, a kernel call is just like a library call. It's just done in a slightly different way, but it's still got, you know, parameters in, it's still got a set of parameters. They're just encoded differently. And, and again, like the, the way kernel calls are done is on a level just above the kernel where you have a library, that just passes things through. Almost verbatim to the kernel and we implement that library instead. [00:44:10] Jeremy: And, and you've been working on i, I think, wine for over, over six years now. [00:44:18] Elizabeth: That sounds about right. Debugging and having broad knowledge of Wine [00:44:20] Jeremy: What does, uh, your, your day to day look like? What parts of the project do you, do you work on? [00:44:27] Elizabeth: It really varies from day to day. and I, I, a lot of people, a lot of, some people will work on the same parts of wine for years. Uh, some people will switch around and work on all sorts of different things. [00:44:42] Elizabeth: And I'm, I definitely belong to that second group. Like if you name an area of wine, I have almost certainly contributed a patch or two to it. there's some areas I work on more than others, like, 3D graphics, multimedia, a, I had, I worked on a compiler that exists, uh, socket. So networking communication is another thing I work a lot on. day to day, I kind of just get, I, I I kind of just get a bug for some program or another. and I take it and I debug it and figure out why the program's broken and then I fix it. And there's so much variety in that. because a bug can take so many different forms like I described, and, and, and the, and then the fix can be simple or complicated or, and it can be in really anywhere to a degree. [00:45:40] Elizabeth: being able to work on any part of wine is sometimes almost a necessity because if a program is just broken, you don't know why. It could be anything. It could be any sort of API. And sometimes you can hand the API to somebody who's got a lot of experience in that, but sometimes you just do whatever. You just fix whatever's broken and you get an experience that way. [00:46:06] Jeremy: Yeah, I mean, I was gonna ask about the specialized skills to, to work on wine, but it sounds like maybe in your case it's all of them. [00:46:15] Elizabeth: It's, there's a bit of that. it's a wine. We, the skills to work on wine are very, it's a very unique set of skills because, and it largely comes down to debugging because you can't use the tools you normally use debug. [00:46:30] Elizabeth: You have to, you have to be creative and think about it different ways. Sometimes you have to be very creative. and programs will try their hardest to avoid being debugged because they don't want anyone breaking their copy protection, for example, or or hacking, or, you know, hacking in sheets. They want to be, they want, they don't want anyone hacking them like that. [00:46:54] Elizabeth: And we have to do it anyway for good and legitimate purposes. We would argue to make them work better on more operating systems. And so we have to fight that every step of the way. [00:47:07] Jeremy: Yeah, it seems like it's a combination of. F being able, like you, you were saying, being able to, to debug. and you're debugging not necessarily your own code, but you're debugging this like behavior of, [00:47:25] Jeremy: And then based on that behavior, you have to figure out, okay, where in all these different systems within wine could this part be not working? [00:47:35] Jeremy: And I, I suppose you probably build up some kind of, mental map in your head of when you get a, a type of bug or a type of crash, you oh, maybe it's this, maybe it's here, or something [00:47:47] Elizabeth: Yeah. That, yeah, there is a lot of that. there's, you notice some patterns, you know, after experience helps, but because any bug could be new, sometimes experience doesn't help and you just, you just kind of have to start from scratch. Finding a bug related to XAudio [00:48:08] Jeremy: At sort of a high level, can you give an example of where you got a specific bug report and then where you had to look to eventually find which parts of the the system were the issue? [00:48:21] Elizabeth: one, one I think good example, that I've done recently. so I mentioned this, this XAudio library that does 3D audio. And if you say you come across a bug, I'm gonna be a little bit generics here and say you come across a bug where some audio isn't playing right, maybe there's, silence where there should be the audio. So you kind of, you look in and see, well, where's that getting lost? So you can basically look in the input calls and say, here's the buffer it's submitting that's got all the audio data in it. And you look at the output, you look at where you think the output should be, like, that library will internally call a different library, which programs can interact with directly. [00:49:03] Elizabeth: And this our high level library interacts with that is the, give this sound to the audio driver, right? So you've got XAudio on top of, um. mdev, API, which is the other library that gives audio to the driver. And you see, well, the ba the buffer is that XAudio is passing into MM Dev, dev API. They're empty, there's nothing in them. So you have to kind of work through the XAudio library to see where is, where's that sound getting lost? Or maybe, or maybe that's not getting lost. Maybe it's coming through all garbled. And I've had to look at the buffer and see why is it garbled. I'll open up it up in Audacity and look at the weight shape of the wave and say, huh, that shape of the wave looks like it's, it looks like we're putting silence every 10 nanoseconds or something, or, or reversing something or interpreting it wrong. things like that. Um, there's a lot of, you'll do a lot of, putting in print fs basically all throughout wine to see where does the state change. Where was, where is it? Where is it? Right? And then where do things start going wrong? [00:50:14] Jeremy: Yeah. And in the audio example, because they're making a call to your XAudio implementation, you can see that Okay, the, the buffer, the audio that's coming in. That part is good. It, it's just that later on when it sends it to what's gonna actually have it be played by the, the hardware, that's when missing. So, [00:50:37] Elizabeth: We did something wrong in a library that destroyed the buffer. And I think on a very, high level a lot of debugging, wine is about finding where things are good and finding where things are bad, and then narrowing that down until we find the one spot where things go wrong. There's a lot of processes that go like that. [00:50:57] Jeremy: like you were saying, the more you see these problems, hopefully the, the easier it gets to, to narrow down where, [00:51:04] Elizabeth: Often. Yeah. Especially if you keep debugging things in the same area. How much code is OS specific?c [00:51:09] Jeremy: And wine supports more than one operating system. I, I saw there was Linux, MacOS I think free BSD. How much of the code is operating system specific versus how much can just be shared across all of them? [00:51:27] Elizabeth: Not that much is operating system specific actually. so when you think about the volume of wine, the, the, the, vast majority of it is the high level code that doesn't need to interact with the operating system on a low level. Right? Because Windows keeps putting, because Microsoft keeps putting lots and lots of different libraries in their operating system. And a lot of these are high level libraries. and even when we do interact with the operating system, we're, we're using cross-platform libraries or we're using, we're using ics. The, uh, so all these operating systems that we are implementing are con, basically conformed to the posix standard. which is basically like Unix, they're all Unix based. Psic is a Unix based standard. Microsoft is, you know, the big exception that never did implement that. And, and so we have to translate its APIs to Unix, APIs. now that said, there is a lot of very operating system, specific code. Apple makes things difficult by try, by diverging almost wherever they can. And so we have a lot of Apple specific code in there. [00:52:46] Jeremy: another example I can think of is, I believe MacOS doesn't support, Vulkan [00:52:53] Elizabeth: yes. Yeah.Yeah, That's a, yeah, that's a great example of Mac not wanting to use, uh, generic libraries that work on every other operating system. and in some cases we, we look at it and are like, alright, we'll implement a wrapper for that too, on top of Yuri, on top of your, uh, operating system. We've done it for Windows, we can do it for Vulkan. and that's, and then you get the Molten VK project. Uh, and to be clear, we didn't invent molten vk. It was around before us. We have contributed a lot to it. Direct3d, Vulkan, and MoltenVK [00:53:28] Jeremy: Yeah, I think maybe just at a high level might be good to explain the relationship between Direct 3D or Direct X and Vulcan and um, yeah. Yeah. Maybe if you could go into that. [00:53:42] Elizabeth: so Direct 3D is Microsoft's 3D API. the 3D APIs, you know, are, are basically a way to, they're way to firstly abstract out the differences between different graphics, graphics cards, which, you know, look very different on a hardware level. [00:54:03] Elizabeth: Especially. They, they used to look very different and they still do look very different. and secondly, a way to deal with them at a high level because actually talking to the graphics card on a low level is very, very complicated. Even talking to it on a high level is complicated, but it gets, it can get a lot worse if you've ever been a, if you've ever done any graphics, driver development. so you have a, a number of different APIs that achieve these two goals of, of, abstraction and, and of, of, of building a common abstraction and of building a, a high level abstraction. so OpenGL is the broadly the free, the free operating system world, the non Microsoft's world's choice, back in the day. [00:54:53] Elizabeth: And then direct 3D was Microsoft's API and they've and Direct 3D. And both of these have evolved over time and come up with new versions and such. And when any, API exists for too long. It gains a lot of croft and needs to be replaced. And eventually, eventually the people who developed OpenGL decided we need to start over, get rid of the Croft to make it cleaner and make it lower level. [00:55:28] Elizabeth: Because to get in a maximum performance games really want low level access. And so they made Vulcan, Microsoft kind of did the same thing, but they still call it Direct 3D. they just, it's, it's their, the newest version of Direct 3D is lower level. It's called Direct 3D 12. and, and, Mac looked at this and they decided we're gonna do the same thing too, but we're not gonna use Vulcan. [00:55:52] Elizabeth: We're gonna define our own. And they call it metal. And so when we want to translate D 3D 12 into something that another operating system understands. That's probably Vulcan. And, and on Mac, we need to translate it to metal somehow. And we decided instead of having a separate layer from D three 12 to metal, we're just gonna translate it to Vulcan and then translate the Vulcan to metal. And it also lets things written for Vulcan on Windows, which is also a thing that exists that lets them work on metal. [00:56:30] Jeremy: And having to do that translation, does that have a performance impact or is that not really felt? [00:56:38] Elizabeth: yes. It's kind of like, it's kind of like anything, when you talk about performance, like I mentioned this earlier, there's always gonna be overhead from translating from one API to another. But we try to, what we, we put in heroic efforts to. And try, try to make sure that doesn't matter, to, to make sure that stuff that needs to be fast is really as fast as it can possibly be. [00:57:06] Elizabeth: And some very clever things have been done along those lines. and, sometimes the, you know, the graphics drivers underneath are so good that it actually does run better, even despite the translation overhead. And then sometimes to make it run fast, we need to say, well, we're gonna implement a new API that behaves more like windows, so we can do less work translating it. And that's, and sometimes that goes into the graphics library and sometimes that goes into other places. Targeting Wine instead of porting applications [00:57:43] Jeremy: Yeah. Something I've found a little bit interesting about the last few years is [00:57:49] Jeremy: Developers in the past, they would generally target Windows and you might be lucky to get a Mac port or a Linux port. And I wonder, like, in your opinion now, now that a lot of developers are just targeting Windows and relying on wine or, or proton to, to run their software, is there any, I suppose, downside to doing that? [00:58:17] Jeremy: Or is it all just upside, like everyone should target Windows as this common platform? [00:58:23] Elizabeth: Yeah. It's an interesting question. I, there's some people who seem to think it's a bad thing that, that we're not getting native ports in the same sense, and then there's some people who. Who See, no, that's a perfectly valid way to do ports just right for this defacto common API it was never intended as a cross platform common API, but we've made it one. [00:58:47] Elizabeth: Right? And so why is that any worse than if it runs on a different API on on Linux or Mac and I? Yeah, I, I, I guess I tend to, I, that that argument tends to make sense to me. I don't, I don't really see, I don't personally see a lot of reason for, to, to, to say that one library is more pure than another. [00:59:12] Elizabeth: Right now, I do think Windows APIs are generally pretty bad. I, I'm, this might be, you know, just some sort of, this might just be an effect of having to work with them for a very long time and see all their flaws and have to deal with the nonsense that they do. But I think that a lot of the. Native Linux APIs are better. But if you like your Windows API better. And if you want to target Windows and that's the only way to do it, then sure why not? What's wrong with that? [00:59:51] Jeremy: Yeah, and I think the, doing it this way, targeting Windows, I mean if you look in the past, even though you had some software that would be ported to other operating systems without this compatibility layer, without people just targeting Windows, all this software that people can now run on these portable gaming handhelds or on Linux, Most of that software was never gonna be ported. So yeah, absolutely. And [01:00:21] Elizabeth: that's [01:00:22] Jeremy: having that as an option. Yeah. [01:00:24] Elizabeth: That's kind of why wine existed, because people wanted to run their software. You know, that was never gonna be ported. They just wanted, and then the community just spent a lot of effort in, you know, making all these individual programs run. Yeah. [01:00:39] Jeremy: I think it's pretty, pretty amazing too that, that now that's become this official way, I suppose, of distributing your software where you say like, Hey, I made a Windows version, but you're on your Linux machine. it's officially supported because, we have this much belief in this compatibility layer. [01:01:02] Elizabeth: it's kind of incredible to see wine having got this far. I mean, I started working on a, you know, six, seven years ago, and even then, I could never have imagined it would be like this. [01:01:16] Elizabeth: So as we, we wrap up, for the developers that are listening or, or people who are just users of wine, um, is there anything you think they should know about the project that we haven't talked about? [01:01:31] Elizabeth: I don't think there's anything I can think of. [01:01:34] Jeremy: And if people wanna learn, uh, more about the wine project or, or see what you're up to, where, where should they, where should they head? Getting support and contributing [01:01:45] Elizabeth: We don't really have any things like news, unfortunately. Um, read the release notes, uh, follow some, there's some, there's some people who, from Code Weavers who do blogs. So if you, so if you go to codeweavers.com/blog, there's some, there's, there's some codeweavers stuff, uh, some marketing stuff. But there's also some developers who will talk about bugs that they are solving and. And how it's easy and, and the experience of working on wine. [01:02:18] Jeremy: And I suppose if, if someone's. Interested in like, like let's say they have a piece of software, it's not working through wine. what's the best place for them to, to either get help or maybe even get involved with, with trying to fix it? [01:02:37] Elizabeth: yeah. Uh, so you can file a bug on, winehq.org,or, or, you know, find, there's a lot of developer resources there and you can get involved with contributing to the software. And, uh, there, there's links to our mailing list and IRC channels and, uh, and, and the GitLab, where all places you can find developers. [01:03:02] Elizabeth: We love to help you. Debug things. We love to help you fix things. We try our very best to be a welcoming community and we have got a long, we've got a lot of experience working with people who want to get their application working. So, we would love to, we'd love to have another. [01:03:24] Jeremy: Very cool. Yeah, I think wine is a really interesting project because I think for, I guess it would've been for decades, it seemed like very niche, like not many people [01:03:37] Jeremy: were aware of it. And now I think maybe in particular because of the, the Linux gaming handhelds, like the steam deck,wine is now something that a bunch of people who would've never heard about it before, and now they're aware of it. [01:03:53] Elizabeth: Absolutely. I've watched that transformation happen in real time and it's been surreal. [01:04:00] Jeremy: Very cool. Well, Elizabeth, thank you so much for, for joining me today. [01:04:05] Elizabeth: Thank you, Jeremy. I've been glad to be here.

Can't get enough Linux? How about multiple kernels running simultaneously, side by side, not in a VM, all on the same hardware; this week it's finally looking real.Sponsored By:Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:

Can't get enough Linux? How about multiple kernels running simultaneously, side by side, not in a VM, all on the same hardware; this week it's finally looking real.

En este episodio en formato monólogo repasamos lo más relevante de la semana en Linux y hardware: Debian 13.1 (primer point release de Trixie), el salto de Ubuntu 25.10 a Linux 6.17 y su beta inminente, el estado del kernel 6.17-rc5 y los movimientos alrededor de bcachefs. Además, novedades de la pila gráfica (Mesa 25.2.2, Wine 10.15), actualizaciones para Steam Deck/Proton, y en hardware las hojas de ruta de Intel (Arrow Lake Refresh / Nova Lake), el Ryzen 5 9500F de AMD y cambios recientes en drivers de NVIDIA.

Colin Donohue's path from Boston to Georgia weaves together activism, community building, startups, and honoring legacy. A story of resilience, relationships, and global impact—proving that purpose-driven leadership transcends borders.00:29- About Colin M DonohueColin serves as CEO of Kernel Finance, a digital toolkit for microentrepreneurs enabling compliance with E-invoicing mandates, efficiency of digital documents and automations, and access to finance via invoice-based financing.Colin is also cofounder of Global Innovation Dojo, a founder development program operating in Nigeria, Georgia, Japan and other startup ecosystems.

This Week the crew talks about the latest AI in Open Source. Then the new OBS Beta is out, there's a new Init system in town, and Agama 17 is out for SUSE Linux 16. There's kernel drama, with a Btrfs develop stepping back, Bcachefs is maintained outside the kernel, and Rosenzweig is now at Intel. And don't forget the Android bombshell, that sideloading will soon be limited to verified developers. For tips, we have systemctl restart options, wpctl inspect for WirePlumber information, aptitude for more package management, and gdisk for converting an MBR drive to GPT. The show notes are available at https://bit.ly/45T37AJ and enjoy! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Ken McDonald, and Jeff Massie Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

(Some content may not be suitable for sensitive ears.)True love requires true freedom—and that's why understanding the Sixth Commandment is so important. Hey it's Cathy and Jake, and here's another Catholic Kernel of Truth.God actually has a beautiful plan for love, marriage, and sexuality. When we understand His design, we experience real freedom and joy—the kind of love our hearts are craving.In Matthew 5, Jesus says: “You've heard it said, ‘You shall not commit adultery,' but I say to you, everyone who looks at someone with lust has already committed adultery in their heart.” This begins on what is going on inside—our hearts, our desires, the way we see other people. Jesus cares about the whole person.The reason God cares so much about sexuality is because He designed us—male and female—in perfect equality and complementarity.God made us for love in the deepest sense, so that we may be a self-gift. The Catechism of the Catholic Church says that God gave each of us a sexual identity that involves both body and soul. Sexuality is meant to be oriented toward marriage and family, where that love can be total, faithful, fruitful, and free. (CCC 2331-2334)And all baptized Christians are called to chastity—not just single people or priests, but everyone. It looks different depending on your state of life: celibacy, faithfulness in marriage, or living chastity as a widow or widower. Chastity involves self-mastery and the cardinal virtue of temperance. (CCC 2337-2349)Lust is the opposite of love. Love gives; lust takes. Lust sees someone as an object instead of a person.The Catechism points out that sins of pornography, fornication, adultery, and masturbation are ways we can misuse God's gift of sexuality. They isolate sexual pleasure from its real purpose: love and life together. (CCC 2396)The Catechism of the Catholic Church states that "homosexual acts are intrinsically disordered." They are contrary to the natural law. They close the sexual act to the gift of life.” The Catechism goes on to explain that those with same-sex attraction must be accepted with respect, compassion, and sensitivity. Same-sex attraction is a cross and those who choose to live a chaste life are living out this commandment. (CCC 2357-2358)When man and woman give themselves totally to each other in marriage, they become co-creators with God. Marriage has this twofold purpose: the good of the spouses and the transmission of life.And that's why the Church teaches that contraceptives or sterilization go against God's plan—they close off the openness to life. The Church does allow for Natural Family Planning, which is discerning to space out children for just reasons. It involves engaging during certain times of a woman's cycle. (2368-2370)And just like us, some couples struggle with infertility. It's a very heavy cross, yet the Catechism says a child is always a gift, not something “owed.” Techniques like IVF, sperm and ovum donation, surrogate uterus, and artificial insemination sadly separate procreation from the loving union of husband and wife. However even if a couple can't have a biological child, God can bring incredible spiritual fruitfulness when this suffering is united to Him on the Cross. (CCC 2376-2379)So, to live this out practically, we must see people the way God sees them—as whole persons, body and soul. It means being intentional about what we look at online, how we think, and how we talk about love and marriage.And when we mess up... that's what confession is for. God isn't waiting to tear us down; He wants to restore us to freedom and joy.Here's our challenge for you this week: Ask God to help you see others—and yourself—with His eyes. Where do you need healing in the area of love and chastity?And remember, God's plan for love isn't about rules to punish you or make you feel bad about yourself; it's about freedom to love fully. He wants our hearts to be whole. 

De grote belofte van hersenimplantaten lijkt steeds dichterbij te komen. Wat ooit begon als sciencefiction, komt nu steeds meer in beeld als mogelijke realiteit. De vraag die daarbij op tafel ligt is niet langer óf dit ooit kan, maar wanneer technologie zo ver gevorderd is dat iemand simpelweg aan de beurskoers van Nvidia denkt en die koers vervolgens direct in zijn hoofd ziet verschijnen. Het idee van een brain-to-cloud interface roept niet alleen vragen op over techniek, maar ook over toepassingen, snelheid van leren en de mogelijkheid om kennis van de een direct in de hersenen van de ander over te dragen. Voor wetenschappers die werken aan hersenimplantaten begint het vaak met de medische toepassingen. Kun je blinde mensen weer zicht geven, al is het slechts in contouren? Onderzoekers werkten aanvankelijk met duizend elektrodes, maar de voortgang zit niet alleen in aantallen. De rol van software en interpretatie van signalen is minstens zo groot. De vraag is of verbeteringen in hardware en algoritmes ook echt leiden tot bruikbare resultaten bij patiënten. Daarbij spelen klinische proeven met zowel dieren als mensen een rol. In Europa zijn er inmiddels ook voorbeelden, waaronder de bekende casus van een Spaanse patiënte. Tegelijkertijd krijgt het onderwerp een commerciële kant met startups als Phosphoenix, die werken aan concrete toepassingen. De maatschappelijke discussie wordt gevoed door berichtgeving in de media. Zo verschenen recent artikelen over experimenten waarbij hersensignalen worden gebruikt om spraak te vertalen, de publiciteit rond de eerste patiënt van Neuralink, en de ontwikkelingen in China waar een implantaat van 26 millimeter een patiënt in staat stelt met gedachten te schaken. Ook grote bedrijven als Apple kijken naar toepassingen waarbij apparaten zoals iPads en iPhones via hersensignalen kunnen worden bestuurd. De vraag is telkens of dit diepe invasieve technologie vergt, of dat lichtere vormen ook mogelijk zijn. Daarnaast rijst de vraag of dezelfde technieken die nu worden ingezet voor parkinson ook bruikbaar zijn voor de behandeling van depressie of dwangstoornissen. De hardware zelf varieert van standaardprocessors tot chips die de architectuur van het brein proberen na te bootsen. Onderzoek richt zich daarnaast op niet-invasieve methodes zoals TD-fNIRS, terwijl commerciële partijen als Kernel met eigen oplossingen komen. Toch gaat het niet alleen over techniek. Wanneer hersenen direct met de cloud kunnen worden verbonden, komt de vraag wie eigenaar is van die data en welke ethische grenzen getrokken moeten worden. Het gesprek over hersenimplantaten gaat daarmee over veel meer dan medische innovatie of technologische vooruitgang. Gast Pieter Roelfsema Video Youtube Links Hosts Ben van der Burg & Mark Beekhuis Redactie Daniël Mol Rosanne PetersSee omnystudio.com/listener for privacy information.

In this episode of The Cybersecurity Defenders Podcast, we discuss some intel being shared in the LimaCharlie community.• Attackers are actively exploiting CVE-2023-46604, a remote code execution vulnerability in Apache ActiveMQ first disclosed in October 2023, that is used to compromise cloud-hosted Linux servers.• AshES Cybersecurity has publicly disclosed a critical zero-day vulnerability in Elastic's Endpoint Detection and Response (EDR) platform, specifically in the Microsoft-signed kernel driver elastic-endpoint-driver.sys.• At least a dozen ransomware groups are now deploying kernel-level EDR killers - tools designed specifically to disable endpoint detection and response solutions - as part of their malware arsenal.• Microsoft has released an in-depth technical analysis of PipeMagic, a modular backdoor linked to ransomware operations carried out by Storm-2460, a financially motivated threat group associated with RansomEXX.Support our show by sharing your favorite episodes with a friend, subscribe, give us a rating or leave a comment on your podcast platform.This podcast is brought to you by LimaCharlie, maker of the SecOps Cloud Platform, infrastructure for SecOps where everything is built API first. Scale with confidence as your business grows. Start today for free at limacharlie.io.

Phishing Training Effectiveness: A study of over 19,000 employees showed traditional phishing training has limited impact, improving scam detection by just 1.7% over eight months. Despite varied training methods, over 50% of participants fell for at least one phishing email, highlighting persistent user susceptibility and the need for more effective cybersecurity education strategies.Cybersecurity Risks in Modern Cars: Modern connected vehicles are highly vulnerable to cyberattacks. A researcher exploited flaws in a major carmaker's web portal, gaining “national admin” access to dealership data and demonstrating the ability to remotely unlock cars and track their locations using just a name or VIN. This underscores the urgent need for regular vehicle software updates and stronger manufacturer security measures to prevent data breaches and potential vehicle control by malicious actors.Nation-State Cyberattacks on Infrastructure: Nation-state cyberattacks targeting critical infrastructure are escalating. Russian hackers reportedly took control of a Norwegian hydropower dam, releasing water undetected for hours. While no physical damage occurred, such incidents reveal the potential for widespread disruption and chaos, signaling a more aggressive stance by state-sponsored cyber actors and the need for robust infrastructure defenses.AI Regulation in Mental Health Therapy: States like Illinois, Nevada, and Utah are regulating or banning AI in mental health therapy due to safety and privacy concerns. Unregulated AI chatbots risk harmful interactions with vulnerable users and unintended data exposure. New laws require licensed professional oversight and prohibit marketing AI chatbots as standalone therapy tools to protect users.Impact of Surveillance Laws on Privacy Tech: Proposed surveillance laws, like Switzerland's data retention mandates, are pushing privacy-focused tech firms like Proton to relocate infrastructure. Proton is moving its AI chatbot, Lumo, to Germany and considering Norway for other services to uphold its no-logs policy. This reflects the tension between national security and privacy, driving companies to seek jurisdictions with stronger data protection laws.Data Brokers and Privacy Challenges: Data brokers undermine consumer privacy despite laws like California's Consumer Privacy Act. Over 30 brokers were found hiding data deletion instructions from Google search results using specific code, creating barriers for consumers trying to opt out of data collection. This intentional obfuscation frustrates privacy rights and weakens legislative protections.Android pKVM Security Certification: Android's protected Kernel-based Virtual Machine (pKVM) earned SESIP Level 5 certification, the first software security solution for consumer electronics to achieve this standard. Designed to resist sophisticated attackers, pKVM enables secure handling of sensitive tasks like on-device AI processing, setting a new benchmark for consistent, verifiable security across Android devices.VPN Open-Source Code Significance: VP.NET's decision to open-source its Intel SGX enclave code on GitHub enhances transparency in privacy technology. By allowing public verification, users can confirm the code running on servers matches the open-source version, fostering trust and accountability. This move could set a new standard for the VPN and privacy tech industry, encouraging others to prioritize verifiable privacy claims.

Microsoft is rethinking allowing endpoint security software to run in the Windows kernel (including third-party and Microsoft’s own endpoint security software). While there are benefits to running security software in the kernel, there are also serious downsides (see the CrowdStrike outage). Dan Massameno joins JJ and Drew on Packet Protector to talk about the role... Read more »

Microsoft is rethinking allowing endpoint security software to run in the Windows kernel (including third-party and Microsoft’s own endpoint security software). While there are benefits to running security software in the kernel, there are also serious downsides (see the CrowdStrike outage). Dan Massameno joins JJ and Drew on Packet Protector to talk about the role... Read more »

There's drama about the latest RISC-V patches in the kernel, SparkyLinux and Kaisen Linux have updates, and GCC is looking to drop some architectures. Nvidia ships a driver update, ffmpeg and OnlyOffice adds AI, and distros are shipping the soft reboot. For tips we have SystemD-Manager-TUI for managing Systemd, a step-through of auditing a downloadable install script, the timeout bash command, and an interesting question about how to get colors back in grep output. You can find the show notes at http://bit.ly/4mEkufi and have a great week! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Ken McDonald, and Jeff Massie Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

When personalities clash, the users come last. Meanwhile, Chris' hyper-tuned setup stops being a toy and starts looking like a daily driver.Sponsored By:Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:

One of the best things about making a yearly trip to Fyne Ales for FyneFest is that I get to check in on the brewery's Origins side project. It's the vehicle for its wild beers, typically produced using mixed or spontaneously fermented and then barrel-matured beer, and often showing locally grown fruit, or forage herbs. These beers are a long way from cherished Fyne Ale classics like Jarl or Highlander, but they arguably show an even greater ‘sense of place' than the cask beers that put this particular brewery on the map.For the past couple of years the project has been under the stewardship of Dan Wye, an experienced brewer who now lives next door to the brewery in Glen Fyne. When he took the project on he was given carte blanche to make Origins his own, which he did initially by gutting and cleaning the small brewery he uses to produce wort, and even getting rid of a few barrels he felt didn't meet his standards. Any fermentation project such as this needs time, and now we're at the point where Dan has his feet under the table, and Origins is beginning to produce some incredibly special beers. Among these are what Dan likes to refer to as ‘Chimeras'. Named for the mythical beast from the Greek classics, with the body and head of a lion, the head of a goat and a snake for a tail, Dan's Chimera's are far less threatening. Instead he uses the term to describe hybrid beers that are designed to ape beverages like wine or cider, but don't feature any of the ingredients that would be traditionally used to make such drinks.The results are pretty magical, with beers such as Smudan employing Nelson Sauvin hops before being further aged on gooseberries, elderflower, limes, sunflowers, marigolds and borage to imitate both the mouthfeel and flavour of cold climate Sauvignon Blanc. It's a seriously impressive beer, but don't take my word for it. The beer is carried by local restaurant, Inver, which presently holds a Michelin green star. If you recognise Dan's name, it's because he featured on a Pellicle podcast recorded at FyneFest in 2024. On this occasion Dan spoke alongside The Kernel's Evin O'Riordain, Mark Tranter of Burning Sky, and Will Harris of Balance Brewing in Manchester. This year, we figured seeing as he'd been super busy releasing lots of beers, and the fact we're literally on his doorstep, it might be nice to have a one to one conversation about what he's been up to.Speaking of which, keep your eyes out for a forthcoming Origins, Pellicle collab in the not too distant future. I'll be heading to Fyne Ales for non-FyneFest related reasons for the first time ever to help make a foraged beer that helps explore a notion I'm rather cynical about… Terroir. Expect more details soon!We're able to produce The Pellicle Podcast directly thanks to our Patreon subscribers, and our sponsors Loughran Brewers Select. If you're enjoying this podcast, or the weekly articles we publish, please consider taking out a monthly subscription for less than the price of a pint a month.

Another fuel-mileage race, this time at Iowa Speedway, sees one driver stretch his gas tank for the final 144 laps of the race to return to victory lane. Jeff and Jordan break it all down and discuss the latest in the race to the playoffs as well as this week's NASCAR news and more.

The Threadripper leads the conversation this week, with it's impressive Linux performance and many, many cores and PCIe lanes. Then Bcachefs dangles over the precipice, NetworkManager 1.54 has some impressive features, and the Kernel calendar turns the page from 6.16 to the 6.17 merge window. Firewire is still around, KDE gets a day/night mode, and Wayland may never be ready. For tips we have OpenSnitch and a novel use for qemu-img. You can see the show notes at https://bit.ly/40OxbMf and until next week! Host: Jonathan Bennett Co-Host: Jeff Massie Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Kernel 6.16 brings major hardware support upgrades, Ubuntu changes how it handles kernels, Snapdragon X Elite Linux support advances, and an ARM SBC embarrasses x86 in Jellyfin transcoding.

This week it's a duet, with Jonathan and Jeff chatting about Clear Linux' last hurrah, and some other Intel projects. The kernel may be about to adopt an AI code policy, and Fedora debates how to handle BIOS bugs. FFmpeg is about to release 8.0, KDE is adding printer ink monitoring, and Valve has a Steam refresh in the works. Our command line tips are vity for AI help with the command line, and immich for building your own video and image store and timeline. You can catch the show notes at http://bit.ly/4lKOPZz Have a great week! Host: Jonathan Bennett Co-Host: Jeff Massie Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Today… we're tackling a commandment you might be tempted to skip over in your examination of conscience.The fifth commandment: “You shall not kill.”Now if you're anything like me, your first thought might be:“Well, I haven't murdered anyone. I'm good here. Let's move on.”But, Jesus takes this commandment, like He does all the others, and flips the script. He says in Matthew 5:22:“Everyone who is angry with his brother will be liable to judgment.”So it's not just about murder. It's about the heart behind it. It's about the ways we choose death over life in our words, actions, even in the quiet corners of our souls.Life is SacredThe Catechism of the Catholic Church (2258) reminds us that human life is sacred—from the moment of conception to natural death—because we are made in the image of God. You, me, every person we meet carries a divine fingerprint. So to harm another human being is dishonoring the Creator.No one has the right to destroy an innocent human life. And that truth is really the foundation for everything else the Church teaches about life—from abortion, to euthanasia, to suicide, and to war.Life is not ours to take. It's ours to protect.What About Self-Defense?Now someone might ask, “But what if someone is trying to kill me? Or hurt my family?”The Church teaches that self-defense can be permitted. If you're in a situation where force is needed to protect yourself or others, it can be morally justified as long as your intention is to preserve life, and not to kill. But to go beyond what is  necessary crosses a line. (CCC 2263–2265)It's all about intention. Protecting life is the goal—even in conflict.Abortion & EuthanasiaThe fifth commandment also applies to abortion which the US Bishops have delcared as the preeminent issue. The Church teaches clearly (CCC 2270) that human life must be protected from the moment of conception. The unborn child in the womb is not just “potential life”- it is human life, and life, even in its most vulnerable form, has value.The same goes for euthanasia. Ending the life of someone who is sick or disabled—even with good intentions—is not the answer. Every person, no matter their condition, deserves respect and care. That doesn't mean we have to prolong suffering at all costs—sometimes it's okay to stop treatments that are extreme or burdensome. But there's a difference between letting someone die naturally and intentionally causing death. (CCC 2276–2278)Suicide, Mental Health, and MercyThis commandment also brings to mind a very difficult and sensitive topic: suicide. The Church teaches that suicide goes against the love of self, love of neighbor, and love of God. But it also teaches that mental illness, trauma, and deep suffering—can lessen a person's responsibility. (CCC 2280–2283)So, if you've lost someone to suicide know, the Church does not condemn them. In fact, we pray for them. We entrust them to God's mercy—because only He knows the depths of their pain. And if you're struggling yourself, please—reach out. You are loved. You are not alone. Call 988 to talk to someone who can help, or visit the 988 Lifeline. Words That Hurt, Scandal That KillsThe Fifth Commandment also covers what we might call “everyday violence”—not just physical, but emotional and spiritual. Have you ever said something that crushed someone's spirit? Have you ever gossiped, slandered, or lashed out in anger? Anger and hatred can kill, even if no blood is spilled.Then there's scandal—leading someone else into sin. That, too, is a form of spiritual death. If our actions cause someone else to fall away from God, that is serious. (CCC 2284)Caring for Our Own LivesThis commandment includes how we treat our own bodies. Life is a gift entrusted to us, and we're stewards of it. That means taking care of our health, avoiding addiction, being mindful of food, alcohol, tobacco, and drugs. (CCC 2288–2291)God wants us alive—not just physically, but fully alive in Him.Peace Over AngerSo how do we start to live this out?It begins with peace. Jesus tells us to love our enemies and pray for those who persecute us. Not just tolerate them. Love them.Easier said than done, right?But that's the challenge of the 5th Commandment. It's not just a “don't do bad things” rule. It's a call to actively protect and promote life in all its forms.So ask yourself:Do my words build others up—or tear them down?Do I hold onto grudges or offer forgiveness?Am I honoring the gift of my own life—body, mind, and soul?Do I value all life, even the ones society says are disposable?This commandment is so much more than “Don't kill.” It's a lifestyle. A posture. A way of loving that honors the sacredness in every single person—including yourself.So this week, look for ways to choose life:Apologize. Forgive. Speak kindly. Defend the vulnerable. Take care of your body. Be patient. Let go of bitterness.And above all—remember that your life, and the lives around you, are not random or disposable.They are precious, on purpose, and worth protecting.---------------------------------------------------------------------------------------------"music by audionautix.com"Adventures by A Himitsu https://soundcloud.com/a-himitsuMusic released by Argofox https://youtu.be/8BXNwnxaVQEMusic provided by Audio Library https://youtu.be/MkNeIUgNPQ8

The MacVoices Live! panel discusses Meta's controversial AI photo upload feature and growing privacy concerns, Microsoft's AI diagnostic tool that outperforms doctors, and the retirement of Windows' infamous blue screen of death. Chuck Joiner, David Ginsburg, Brian Flanigan-Arthurs, Eric Bolden, Marty Jencius, Jeff Gamet, Web Bixby, and Jim Rea debate the tradeoffs between utility and privacy, AI's evolving role in medicine, and the implications for education, the arts, and everyday tech users.  This MacVoices is supported by Notion. The best AI tool for work. Try it now at notion.com/macvoices. Show Notes: Chapters: 00:11 Introduction to Mac Voices 01:58 Meta's Photo Upload Dilemma 06:38 Concerns About AI in Art 07:10 Microsoft's New AI Diagnostics 16:38 Humor in Medical Procedures 21:15 The End of the Blue Screen of Death 37:04 Closing Thoughts and Community Engagement Links: Meta wants to upload every photo you have to its cloud to give you AI suggestions https://appleinsider.com/articles/25/06/27/meta-wants-to-upload-every-photo-you-have-to-its-cloud-to-give-you-ai-suggestions Microsoft Says Its New AI System Diagnosed Patients 4 Times More Accurately Than Human Doctors https://www.wired.com/story/microsoft-medical-superintelligence-diagnosis/ Windows is getting rid of the Blue Screen of Death after 40 years https://www.theverge.com/news/692648/microsoft-bsod-black-screen-of-death-color-change-official Guests: Web Bixby has been in the insurance business for 40 years and has been an Apple user for longer than that.You can catch up with him on Facebook, Twitter, and LinkedIn. Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him on Twitter, by email at embolden@mac.com, on Mastodon at @eabolden@techhub.social, on his blog, Trending At Work, and as co-host on The Vision ProFiles podcast. Brian Flanigan-Arthurs is an educator with a passion for providing results-driven, innovative learning strategies for all students, but particularly those who are at-risk. He is also a tech enthusiast who has a particular affinity for Apple since he first used the Apple IIGS as a student. You can contact Brian on twitter as @brian8944. He also recently opened a Mastodon account at @brian8944@mastodon.cloud. Jeff Gamet is a technology blogger, podcaster, author, and public speaker. Previously, he was The Mac Observer's Managing Editor, and the TextExpander Evangelist for Smile. He has presented at Macworld Expo, RSA Conference, several WordCamp events, along with many other conferences. You can find him on several podcasts such as The Mac Show, The Big Show, MacVoices, Mac OS Ken, This Week in iOS, and more. Jeff is easy to find on social media as @jgamet on Twitter and Instagram, jeffgamet on LinkedIn., @jgamet@mastodon.social on Mastodon, and on his YouTube Channel at YouTube.com/jgamet. David Ginsburg is the host of the weekly podcast In Touch With iOS where he discusses all things iOS, iPhone, iPad, Apple TV, Apple Watch, and related technologies. He is an IT professional supporting Mac, iOS and Windows users. Visit his YouTube channel at https://youtube.com/daveg65 and find and follow him on Twitter @daveg65 and on Mastodon at @daveg65@mastodon.cloud. Dr. Marty Jencius has been an Associate Professor of Counseling at Kent State University since 2000. He has over 120 publications in books, chapters, journal articles, and others, along with 200 podcasts related to counseling, counselor education, and faculty life. His technology interest led him to develop the counseling profession ‘firsts,' including listservs, a web-based peer-reviewed journal, The Journal of Technology in Counseling, teaching and conferencing in virtual worlds as the founder of Counselor Education in Second Life, and podcast founder/producer of CounselorAudioSource.net and ThePodTalk.net. Currently, he produces a podcast about counseling and life questions, the Circular Firing Squad, and digital video interviews with legacies capturing the history of the counseling field. This is also co-host of The Vision ProFiles podcast. Generally, Marty is chasing the newest tech trends, which explains his interest in A.I. for teaching, research, and productivity. Marty is an active presenter and past president of the NorthEast Ohio Apple Corp (NEOAC). Jim Rea built his own computer from scratch in 1975, started programming in 1977, and has been an independent Mac developer continuously since 1984. He is the founder of ProVUE Development, and the author of Panorama X, ProVUE's ultra fast RAM based database software for the macOS platform. He's been a speaker at MacTech, MacWorld Expo and other industry conferences. Follow Jim at provue.com and via @provuejim@techhub.social on Mastodon. Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

There’s lots of juicy stories in our monthly security news roundup. The Scattered Spider hacking group makes effective use of social engineering to target MSPs, Microsoft pushes for better Windows resiliency by rethinking kernel access policies for third-party endpoint security software, and the US Justice Department files indictments against alleged operators of laptop farms that... Read more »

There’s lots of juicy stories in our monthly security news roundup. The Scattered Spider hacking group makes effective use of social engineering to target MSPs, Microsoft pushes for better Windows resiliency by rethinking kernel access policies for third-party endpoint security software, and the US Justice Department files indictments against alleged operators of laptop farms that... Read more »

SummaryIn this episode of the Blue Security Podcast, hosts Andy and Adam discuss significant updates from Microsoft, focusing on security enhancements, the evolution of the blue screen of death, and new options for consumers regarding extended security updates. They also explore a new update orchestration platform aimed at improving the user experience for application updates on Windows.----------------------------------------------------YouTube Video Link: https://youtu.be/Xknb2FXh1GY----------------------------------------------------Documentation:https://www.crn.com/news/security/upcoming-microsoft-security-resilience-updates-includes-ability-to-run-services-outside-windows-kernelhttps://www.theverge.com/news/692648/microsoft-bsod-black-screen-of-death-color-change-officialhttps://www.windowscentral.com/software-apps/windows-10/windows-10-esu-support-free-updates-cloud-backuphttps://techcommunity.microsoft.com/blog/windows-itpro-blog/introducing-a-unified-future-for-app-updates-on-windows/4416354----------------------------------------------------Contact Us:Website: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://bluesecuritypod.comBluesky: https://bsky.app/profile/bluesecuritypod.comLinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/company/bluesecpodYouTube: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/c/BlueSecurityPodcast-----------------------------------------------------------Andy JawBluesky: https://bsky.app/profile/ajawzero.comLinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/andyjaw/Email: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠andy@bluesecuritypod.com⁠----------------------------------------------------Adam BrewerTwitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/ajbrewerLinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/adamjbrewer/Email: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠adam@bluesecuritypod.com

Welcome to episode 311 of Two Old Men Yelling at Cloud – aka The Cloud Pod, featuring Matt and Ryan who absolutely, definitely did NOT record an aftershow.  This week, they're talking about Cloudflare's new Pay Per Crawler, a new open-source Terraform provider from mkdev, and lots of fabric news that Ryan doesn't understand – plus so much more. Let's get into it!   Titles we almost went with this week: (Show Editor note: There are more show titles than emojis. I give up.)  FSx and the City: When File Systems Meet Object Storage The Great Data Lake Escape: No Movement Required OpenZFS Gets an S3 Degree Without Leaving Home Kernel Sanders: Microsoft’s Recipe for Avoiding Another Fried System Windows Gets a Restraining Order Against Overly Attached Security Software Microsoft Builds a Fence Between Windows and Its Rowdy Security Neighbors Windows Gets a Kernel of Truth After CrowdStrike Meltdown Microsoft Kicks Security Vendors Out of the Kernel Clubhouse The Great Kernel Divorce: When Windows Said “It’s Not You, It’s Your Access Level” Google’s Environmental Report Card: A+ for Effort, C- for Supply Chain The Cloud Pod Goes Green: Google’s 10th Annual Carbon Confession Watts Up Doc? Google’s Energy Efficiency Bugs Bunny Would Approve Terminal Velocity: Google’s AI Gets a Command Performance Ctrl+Alt+Gemini: Google’s New CLI Companion The Prompt and the Furious: Tokyo Terminal AI See What You Did There: Google’s New Compliance Framework Control Yourself: Google Cloud Gets Serious About AI Auditing The Audit-omatic: Teaching Old Compliance New AI Tricks Veo 3: Now Playing in a Cloud Near You Google’s Video Dreams Come True (Audio Included) Lights, Camera, API Action: Veo 3 Takes the Stage Prometheus Unbound: Azure Finally Sees What It’s Been Missing VS Code Gets Fabric-ated: Now With 100% More Workspace Management Ctrl+S Your Sanity: Fabric Items Now Created Where You Code The Extension Cord That Connects Your IDE to the Data Cloud Logic Apps Gets Its Template of Doom (But in a Good Way) Copy-Paste Engineering Just Got an Azure Upgrade Microsoft Introduces the IKEA Model for Workflow Assembly WAF’s Up Doc? Security Copilot Now Speaks Firewall The Firewall Whisperer: When AI Meets Web Application Security WAF and Peace: Microsoft’s Treaty Between Security Tools Azure Goes Wild(card) with Certificate Management Front Door Finally Gets Its Wild Side Microsoft Deals Everyone a Wildcard IP Freely: Azure Takes the Guesswork Out of Address Management No More IP Envy: Azure Catches Up to AWS’s Address Game Azure’s New Feature Has All the Right Addresses Terraform and Chill: When Infrastructure Meets AI DynamoDB Goes Global: Now with 100% Less Eventually The Consistency Chronicles: Return of the Strong Read Breaking: DynamoDB Achieves Peak Table Manners Across All Regions Follow Up 00:47 Microsoft changes Windows in attempt to prevent next CrowdStrike-style catastrophe – Ars Technica Microsoft is creating a new Windows endpoint security platform that allows antivirus vendors to operate outside the kernel, preventing cata

In this episode, we're getting a little corny and taking a closer look at sweet corn—a seasonal staple with a strong presence in summer meals and memories. From its agricultural roots to its place in regional dishes, sweet corn offers more than just flavor. We'll explore how it's been prepared, shared, and celebrated across time, and why it continues to be a highlight of the summer table. See show notes at www.pasingtheplate.org/64ResourcesKeep the learning and exploration going by visiting these websites and resources mentioned in the episode:Visit Storied.com and use code PLATE to save 20% off your first StoriedBook and create something your family will treasure forever.FreekehSous Vide Double Cut Pork Chops with Raw Summer Corn & Tomato SaladBluecoast's Raw Tuna with Pickled Peach & Corn RelishLibby AppGrilled Corn + Cheddar Quinoa from How Sweet EatsSlow Cooker Corn Pudding – RedditCorn zipper/prep peeler toolCollapsible popcorn popperThanks for tuning in to the Passing the Plate podcast! Ready to dig deeper into your kitchen adventures? Make sure to visit: Check out the Passing the Plate website. Check out our webinar and ebook on our Resource page. Ashley at Big Flavors from a Tiny Kitchen: Get inspired by delicious recipes and start cooking delicious food at home no matter your skill level. Lisa at Are You My Cousin?: Learn how to find your ancestors, grow your family tree and uncover fascinating family histories and stories that connect us through food. Stay hungry for knowledge, keep the stories simmering, and join us again for our next delicious episode!

Not all share investing platforms are created equal. In this episode, we compare five of the most popular investing platforms used by Kiwis – Sharesies vs Hatch vs Kernel vs Stake vs Tiger Brokers.Even though property is our main gig, we know a lot of you dabble in shares too. So, we put these platforms head-to-head and asked: Which is the fastest to get started on? Which one has the best fees? And which is best for beginners?You'll learn:Why some platforms are designed for long-term investors – and others for trading on the goThe key difference in how your money is actually held on each platform (and what happens if one goes under)Which app we'd use if we were starting with just $100 todayWant to grow your wealth through more than just shares? Read our ultimate guide to investing in property NZ for practical tips.Don't forget to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠create your free Opes+ account here⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.For more from Opes Partners:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Sign up for the weekly Private Property newsletter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok⁠⁠⁠

This show has been flagged as Clean by the host. After updating the firmware on my Sony Noise Cancelling Headset, and upgrading to Fedora 40 , my A2DP ) profiles stopped working. I did a quick search and found someone with the same issue and it would be fixed in a Kernel upgrade. Common enough on a bleeding edge that is Fedora, however as the months moved on and the kernel upgraded, the problem remained. I tried to implement workarounds several times but eventually came across this passage from hank aka hankuoffroad on the Fedora Forums This is a known behavior when using Bluetooth audio on Linux on hands-free mode: you cannot use A2DP for high-quality audio output while simultaneously using the Bluetooth microphone via HSP/HFP, due to profile limitations in the Bluetooth specification and current Linux audio stack. I knew this of course, but my Sony WH-CH700N Wireless Noise Cancelling Headphones don't have a microphone. ... Hold on how does Noise Cancelling work exactly again ? Active noise control (ANC), also known as noise cancellation (NC), or active noise reduction (ANR), is a method for reducing unwanted sound by the addition of a second sound specifically designed to cancel the first Wikipedia If the first is the background noise, it needs a microphone to capture it so it can be inverted. Ah ha...I had recently also disabled my Zoom H2v2 as it was now sometimes acting as a speaker. So presumably pipewire tries to find any microphone on the system, when it cant find the best one it will resort to the one used for noise canceling in the headset. Once the headset is been used for audio in as well, then there isn't enough bandwidth to do high definition audio, so you end up with the low quality two way profiles. Would the solution be as easy as enabling a proper microphone . . . . Provide feedback on this episode.

Stammhörer, seid stark: Dieses Mal gibt es keine Neuigkeiten rund um die WebPKI. Dafür sprechen Christopher und Sylvester über das angebliche 16-Milliarden-Zugangsdaten-Leck und wie es zum Großereignis überhöht wurde. Außerdem geht es um eine Sicherheitslücke im Linux-Kernel - oder doch woanders? Darüber sind sich die Kernelentwickler und die Distribution Ubuntu uneins und trugen diesen Streit via CVE-Kennungen aus. Außerdem erzählt Christopher über seine Eindrücke zum Sicherheitslücken-Ökosystem und wie es einzelne Verwalter von Opensource-Software überlastet. Und zum Schluß wirft eine Bluetooth-Sicherheitslücke ein Schlaglicht auf eine Industrie, in der die Zulieferkette so unübersichtlich geworden ist, dass man unmöglich sagen kann, welche Geräte betroffen sind. - https://mjg59.dreamwidth.org/71646.html & https://mjg59.dreamwidth.org/71933.html - https://blog.cryptographyengineering.com/2025/06/09/a-bit-more-on-twitter-xs-new-encrypted-messaging/ - DNSSEC KSK Ceremony: https://www.iana.org/dnssec/ceremonies/57 - Greg Kroah-Hartman zur Kernel-CVE-Praxis: https://www.youtube.com/watch?v=u44eMQpGlxA&t=787s - https://heise.de/-9777933 - XKCD Dependancy: https://xkcd.com/2347/ - Folgt uns im Fediverse: * @christopherkunz@chaos.social * @syt@social.heise.de Mitglieder unserer Security Community auf heise security PRO hören alle Folgen bereits zwei Tage früher. Mehr Infos: https://pro.heise.de/passwort

The Kernel drama isn't over, Gaming is just better on Linux, and driver performance is getting better in a FineWine sort of way. KDE is rolling ahead, getting closer to session restore in Wayland, doing accessibility work, and making HDR even better. Speaking of which, Blender has a preview of HDR support on Wayland, with no immediate plans to add support on Windows. Canonical had a great year in 2025, and more! You can find the show notes at https://bit.ly/4kypjFT and Happy Linuxing! Host: Jonathan Bennett Co-Hosts: Rob Campbell and Ken McDonald Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

You might think the fourth commandment “honor your father and mother” is just for kids… but actually it applies to you too. 

Listen as we chat with Kernel, Jay Thomason.

Even though it's bright and sunny, we still like to keep it dark. First up we're treated to a collaboration between great breweries. Stigbergets teamed up with The Kernel to create a traditional English porter. Taking inspiration from an 1800's London Porter recipe, Victorian Porter is a roasted delight. We follow that up with a big imperial stout from Nogne. Also inspired by Victorian times, Ship-Shape and Briston Fashion is a reference to the condition of the ship. Based on this, it was in very good condition. #beer #craftbeer #drinks #englishporter #porter #imperialstout #stout

Fundamentals of Operating Systems Course https://oscourse.winktls is brilliant.TLS encryption/decryption often happens in userland. While TCP lives in the kernel. With ktls, userland can hand the keys to the kernel and the kernel does crypto. When calling write, the kernel encrypts the packet and send it to the NIC.When calling read, the kernel decrypts the packet and handed it to the userspace. This mode still taxes the host's CPU of course, so there is another mode where the kernel offloads the crypto to the NIC device! Host CPU becomes free. Incoming packets to the NIC are decrypted in device before they are DMAed to the kernel. outgoing packets are encrypted before they leave the NIC to the network.ktls still need handshake to happen in userspace. There is also enabling zerocopy in some cases (now that kernel has context) Deserves a video. So much good stuff.0:00 Intro2:00 Userspace SSL Libraries 3:00 ktls 6:00 Kernel Encrypts/Decrypts (TLS_SW)8:20 NIC offload mode (TLS_HW)10:15 NIC does it all (TLS_HW_RECORD)12:00 Write TX Example13:50 Read RX Example17:00 Zero copy (sendfile)https://docs.kernel.org/networking/tls-offload.html

Container-based Linux distributions are gaining traction, especially for edge deployments that demand lightweight and secure operating systems. Talos Linux, developed by Sidero Labs, is purpose-built for Kubernetes with security-first features like a fully immutable file system and disabled SSH access. In a demo, Sidero CTO Andrew Rynhard and Head of Product Justin Garrison explained Talos's design philosophy, highlighting its minimalism and focus on automation. Inspired by CoreOS, Talos removes traditional tools like systemd and Bash, replacing them with machineD, a custom process manager written in Go.Talos emphasizes API-driven management rather than SSH, making Kubernetes cluster operations more scalable and consistent. Its design supports cloud, bare metal, Docker, and edge devices like Raspberry Pi. Kernel immutability is reinforced by ephemeral signing keys. Through Sidero's Omni SaaS, Talos nodes connect securely via WireGuard. The operating system handles all certificates and network connectivity internally, streamlining security and deployment. As Garrison notes, Talos delivers a portable API for “big iron, small iron—no matter what.”Learn more from The New Stack about Sidero Labs:  Is Cluster API Really the Future of Kubernetes Deployment? Choosing a Linux Distribution Join our community of newsletter subscribers to stay on top of the news and at the top of your game. https://thenewstack.io/newsletter/ 

Send us a textJesus is known to refer to himself under a number metaphors that usually pertain to something in the history of Israel or to its system of laws. Leviticus 23 lists the festivals and among them are the Feast of Firstfruits and the Feast of Weeks, known as Pentecost. Both of these festivals concern the firstfruits of a harvest. The first one relates to the barley harvest but the second one relates to the wheat harvest. Jesus in John 12 says that he is the kernel of wheat that falls into the ground and sprouts as a new plant bearing much fruit. His death by crucifixion, burial, and resurrection on the third day was prefigured by the wheat harvest of the Feast of Completion. It is for this purpose he came into the world.Bible Insights with Wayne ConradContact: 8441 Hunnicut Rd Dallas, Texas 75228email: Att. Bible Insights Wayne Conradgsccdallas@gmail.com (Good Shepherd Church) Donation https://gsccdallas.orghttps://www.youtube.com/channel/UCJTZX6qasIrPmC1wQpben9ghttps://www.facebook.com/waconrad or gscchttps://www.sermonaudio.com/gsccSpirit, Truth and Grace MinistriesPhone # 214-324-9915 leave message with number for call backPsalms 119:105 Your word is a lamp for my feet, a light on my path.

Fastfetch and LibreOffice mint new releases, KDE teases Kerton for VM management, and KDE is looking to capture Windows 10 exiles. Bcachefs broke filesystems and then fixed them, AMD releases a couple new GPUs, and there's weird drama in X11 and kernel land. For tips, we have Pipewire node management, notes from Kubuntu beta, and a quick primer on the difference between git fetch and git pull. You can find the show notes at https://bit.ly/4jEM36i Have fun! Host: Jonathan Bennett Co-Hosts: Jeff Massie and Ken McDonald Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

The Wayland-only future is screaming toward us, Mozilla pulls the plug on Pocket, and Steam OS releases Go Country. Microsoft Open Sources WSL; Edit; and more, Gnome needs help with documentation, and Ubuntu goes Chrony. For tips we have zrun for making your own zstd enabled program, more pw-cli howto, y-cruncher for setting number-crunching records, and lsmem and chmem just in case your system has hot-swappable ram. You can see the show notes at https://bit.ly/3H8Ax5P and have fun! Host: Jonathan Bennett Co-Hosts: Rob Campbell, Jeff Massie, and Ken McDonald Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

So here's a question for you: When was the last time you really, truly, rested?I don't mean just crashing on the couch scrolling through your phone—I mean soul-deep rest. The kind that fills you up and reconnects you with who you are… and whose you are.God made you in His image. You were literally handcrafted to reflect Him—His goodness, His creativity, and yes, even His rhythm of work and rest. And He didn't just suggest this rhythm to us—He modeled it. God worked for six days, creating everything, and then on the seventh day… He rested. Not because He was tired, but because He wanted to show us how to live in balance.That brings us to Exodus 20, where God says:“Remember the sabbath day, to keep it holy”It's not because God needs us to rest. It's because we need to rest. Jesus even said, “The sabbath was made for man, not man for the sabbath.” So it's a gift. A holy, weekly invitation to pause and breathe.Now, if you're Catholic, you know that this isn't just a day to nap. The Catechism of the Catholic Church reminds us that Sunday is now the fulfillment of the Sabbath—because Jesus rose from the dead on a Sunday. It's a day that symbolizes the new creation, the new beginning that Jesus gives us. This is why it's called the Lord's Day.Going to Mass on Sunday—or Saturday evening—is not optional. It's a holy day of obligation. That might sound strict, but think about it, God is giving you one day a week to rest, worship, and reconnect.CCC 2180 says: The faithful are bound to participate in the Mass. And choosing not to, without a serious reason, is actually a grave sin. That's how important it is.And Sunday isn't just about Mass—it's also about rest. True, sacred rest. The Catechism says we should refrain from unnecessary work, unless it's for our family's needs or essential services. So if you're a nurse or first responder or someone providing for your family—you're not being disobedient by working. But God still invites you to make space for rest, for worship, for renewal.And let's be honest—rest doesn't always come naturally in today's hustle culture. We pride ourselves on being busy. We wear exhaustion like a badge of honor. But God's not impressed by burnout. He's calling us into freedom.So, here's the real question:What does your Sunday look like?Do you make space for God? Do you give Him that hour at Mass?Do you trust Him enough to believe that your to-do list can wait? That He'll take care of the details if you put Him first?Because honestly, the Third Commandment isn't just a rule—it's a rescue. It's a holy reminder that you are not a machine. You're a beloved child of God, and He wants you to be whole, not just productive.So maybe this week, challenge yourself to truly live out the Sabbath. Go to Mass with your heart open. Turn off your email. Take a walk. Pray. Rest. Laugh. Breathe.Because when we keep the Sabbath holy… it keeps us whole.---------------------------------------------------------------------------------------------"music by audionautix.com"Adventures by A Himitsu https://soundcloud.com/a-himitsuMusic released by Argofox https://youtu.be/8BXNwnxaVQEMusic provided by Audio Library https://youtu.be/MkNeIUgNPQ8

A ton of awesome releases and advancements in this month's ModChat! First comes the release of the Lapse Kernel Exploit for both PS4 12.02 and PS5 10.05 firmwares. BadHTAB for the PS3 evolves into BadWDSD, a separate but better and more exciting development for PS3 owners allowing further access now on Super Slim variants! The original Xbox revision 1.6 gets a huge development as well, now with the ability to reflash the on-board BIOS for the first time. We touch up on some Switch news for the first time in a while, with a new Atmosphere CFW update for the latest Switch firmware, but not all good news when we discuss the EULA changes. However, some reverse engineering efforts towards the WaveBird receiver, Mario Party 4, Mario Kart 64, and even Dinosaur Planet have all released this month!

Luego ya os explico qué ha pasado. Vamos a ponernos al día con lo que ha ocurrido estos meses.

In this pre-event Brand Story On Location conversation recorded live from RSAC Conference 2025, Emily Long, Co-Founder and CEO of Edera, and Kaylin Trychon, Head of Communications, introduce a new approach to container security—one that doesn't just patch problems, but prevents them entirely.Edera, just over a year old, is focused on reimagining how containers are built and run by taking a hardware-up approach rather than layering security on from the top down. Their system eliminates lateral movement and living-off-the-land attacks from the outset by operating below the kernel, resulting in simplified, proactive protection across cloud and on-premises environments.What's notable is not just the technology, but the philosophy behind it. As Emily explains, organizations have grown accustomed to the limitations of containerization and the technical debt that comes with it. Edera challenges this assumption by revisiting foundational virtualization principles, drawing inspiration from technologies like Xen hypervisors, and applying them in modern ways to support today's use cases, including AI and GPU-driven environments.Kaylin adds that this design-first approach means security isn't bolted on later—it's embedded from the start. And yet, it's done without disruption. Teams don't need to scrap what they have or undertake complex rebuilds. The system works with existing environments to reduce complexity and ease compliance burdens like FedRAMP.For those grappling with infrastructure pain points—whether you're in product security, DevOps, or infrastructure—this conversation is worth a listen. Edera's vision is bold, but their delivery is practical. And yes, you'll find them roaming the show floor in bold pink—“mobile booth,” zero fluff.Listen to the episode to hear what it really means to be “secure by design” in the age of AI and container sprawl.Learn more about Edera: https://itspm.ag/edera-434868Note: This story contains promotional content. Learn more.Guests: Emily Long, Founder and CEO, Edera | https://www.linkedin.com/in/emily-long-7a194b4/Kaylin Trychon, Head of Communications, Edera | https://www.linkedin.com/in/kaylintrychon/ResourcesLearn more and catch more stories from Edera: https://www.itspmagazine.com/directory/ederaLearn more and catch more stories from RSA Conference 2025 coverage: https://www.itspmagazine.com/rsac25______________________Keywords:emily long, kaylin trychon, sean martin, marco ciappelli, containers, virtualization, cloud, infrastructure, security, fedramp, brand story, brand marketing, marketing podcast, brand story podcast______________________Catch all of our event coverage: https://www.itspmagazine.com/technology-and-cybersecurity-conference-coverageWant to tell your Brand Story Briefing as part of our event coverage? Learn More 

Cosmic is nearly Beta-worthy, The NVIDIA Beta driver is solid, and we look back on a Code of Conduct legacy at Gnome. Then a shiny new RISC gadget catches our eyes and wallets, there's plenty of controversy in the Kernel, and new things are coming for Linux Graphics. For tips we have mispipe for a slightly different take on piping commands, Bitwarden's Command Line interface, and a quick primer on quotation marks on the command line. The show notes are at https://bit.ly/4d0dxlh and happy 200th! Host: Jonathan Bennett Co-Hosts: Rob Campbell and Jeff Massie Guest: Leo Laporte Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Cosmic is nearly Beta-worthy, The NVIDIA Beta driver is solid, and we look back on a Code of Conduct legacy at Gnome. Then a shiny new RISC gadget catches our eyes and wallets, there's plenty of controversy in the Kernel, and new things are coming for Linux Graphics. For tips we have mispipe for a slightly different take on piping commands, Bitwarden's Command Line interface, and a quick primer on quotation marks on the command line. The show notes are at https://bit.ly/4d0dxlh and happy 200th! Host: Jonathan Bennett Co-Hosts: Rob Campbell and Jeff Massie Guest: Leo Laporte Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

Ubuntu and Fedora are out! And Git turns 20! Cosmic is showing up everywhere, Framework has an impressive AMD-powered 13-inch laptop, and Thunderbird is rolling out the Thundermail service! For tips we have vidir for renaming multiple files at once, pw-mon for monitoring pipewire, g as a go replacement for ls, and todist-rs for a TUI take on todoist. It's a great show, and the notes are at https://bit.ly/4lzTAWt thanks for coming! Host: Jonathan Bennett Co-Hosts: Jeff Massie, Ken McDonald, and Rob Campbell Download or subscribe to Untitled Linux Show at https://twit.tv/shows/untitled-linux-show Want access to the ad-free video and exclusive features? Become a member of Club TWiT today! https://twit.tv/clubtwit Club TWiT members can discuss this episode and leave feedback in the Club TWiT Discord.

No language is as inconsistent in spelling and pronunciation as English. Kernel and colonel rhyme, but read changes based on past or present tense. Ough has many pronunciations: ‘aw’ (thought), ‘ow’ (drought), ‘uff’ (tough), ‘off’ (cough), ‘oo’ (through). In response to this orthographic minefield, legions of rebel wordsmiths have died on the hill of spelling reform, risking their reputations to bring English into the realm of the rational: Mark Twain, Ben Franklin, Eliza Burnz, C. S. Lewis, George Bernard Shaw, Charles Darwin, and the innumerable others on both sides of the Atlantic who, for a time in their life, became fanatically occupied with writing thru instead of through, tho for though, laf for laugh (and tried futilely to get everyone around them to do it too). This began with the “simplified spelling movement” starting with medieval England and continuing to Revolutionary America, from the birth of standup comedy to contemporary pop music, and lasting influence can still be seen in words like color (without a U), plow (without -ugh), and the iconic ’90s ballad “Nothing Compares 2 U.” To explore this history is today’s guest, Gabe Henry, author of “Enough is Enuf, Our Failed Attempts to Make English Easier to Spell.” We look at the past and present of the digital age, where the swift pace of online exchanges (from emojis to social media) now pushes us all 2ward simplification. Simplified spelling may, at last, be having its day.See omnystudio.com/listener for privacy information.

If you've been on social media for more than 20 minutes in the past two years, chances are you know about Bryan Johnson, the tech millionaire in Silicon Valley intent on living forever. For most of his career, Bryan has been an unassuming CEO in the style of early Jeff Bezos. He has been documenting every moment of his process on social media, including the 100 pills he takes every day, constant red light therapies, experimental gene therapy, plasma swaps with his son, and nighttime boner monitoring. However, while a lot is known about his current obsession to live forever, less is known about his early life, time with the Mormon church, scandals with an ex-partner, ideologies, or even his motivations behind wanting to live forever. Support our Sponsors! Hiya Health: https://rocketmoney.com/milehigher Timestamps: Intro 0:00 An Extremely Brief 20 Minute Rant 0:53 The Early Life of Bryan Johnson 28:58 Bryan Finds his "Calling" 35:45 From "Rags" to Riches 39:48 Wanting to be Seen 45:14 The Founding of Kernel 47:35 Horrors at Neuralink 48:02 We Truly Hate AI 49:49 Silicon Valley Believes in the Absence of Choice 57:21 Taryn Southern's Controversy 1:01:29 $2M a Year to Live Forever 1:15:11 Would You Want to Live Forever? 1:17:55 Doctor Zolman's 3 Levels 1:24:18 Bryan's Unbelievable Routine 1:38:00 Trying Bryan's Supplements 1:45:24 Trying Bryan's Olive Oil 1:49:42 Trying Bryan's Cocoa Mix 1:54:48 We Were Very Disappointed 1:57:28 30 Minutes of Social Time, 7 Hours of Sleep 2:02:04 Not Beating Those 'Vampire' Allegations 2:07:03 Unofficial Trials and Risky Tests 2:14:01 Hiking With Bryan 2:23:43 Bryan's Inevitable Future(?) 2:27:12 Final Thoughts & Outro 2:32:14 Mile Higher Merch: HTTP://milehigher.shop Charity Merch for NCMEC:  https://kendallrae.shop Higher Hope Foundation: https://higherhope.org Check out our other podcasts! The Sesh https://bit.ly/3Mtoz4X Lights Out https://bit.ly/3n3Gaoe Planet Sleep https://linktr.ee/planetsleep Join our official FB group! https://bit.ly/3kQbAxg Join our Discord community, it's free! https://discord.gg/hZ356G9 MHP YouTube: http://bit.ly/2qaDWGf Are You Subscribed On Apple Podcast & Spotify?! Support MHP by leaving a rating or review on Apple Podcast :) https://apple.co/2H4kh58 MHP Topic Request Form: https://forms.gle/gUeTEzL9QEh4Hqz88 Merch designer application: https://forms.gle/ha2ErBnv1gK4rj2Y6 You can follow us on all the things: @milehigherpod Twitter: http://www.twitter.com/milehigherpod Instagram: http://www.instagram.com/milehigherpod YouTube: https://www.youtube.com/@MileHigher Hosts: Kendall: @kendallraeonyt IG: http://instagram.com/kendallraeonyt TW: https://www.twitter.com/kendallraeonyt YT: https://www.youtube.com/c/kendallsplace Josh: @milehigherjosh IG: http://www.instagram.com/milehigherjosh TW: https://www.twitter.com/milehigherjosh Producer: Janelle: @janelle_fields_ IG: https://www.instagram.com/janelle_fie... TW: https://www.twitter.com/janelle_fields_ Editor: Tom: @tomfoolery_photo IG: https://www.instagram.com/tomfoolery_photo/ Podcast sponsor inquires: joshthomas@night.co ✉ Send Us Mail & Fan Art ✉ Kendall Rae & Josh Thomas  8547 E Arapahoe Rd Ste J # 233 Greenwood Village, CO 80112 Music By: Mile Higher Boys YT: https://bit.ly/2Q7N5QO Spotify: https://open.spotify.com/artist/0F4ik... The creator hosts a documentary series for educational purposes (EDSA). These include authoritative sources such as interviews, newspaper articles, and TV news reporting meant to educate and memorialize notable cases in our history. Videos come with an editorial and artistic value. SOURCES CITED: https://pastebin.com/zjdgTvDL