Untitled Linux Show 246: Chasing the Sun

Summary

Untitled Linux Show 246: "Chasing the Sun"

Date: March 15, 2026
Host: Jonathan (with Ken and Jeff)
Theme: Latest updates in the Linux and open source ecosystem—software highlights, industry news, and community insights.

---

Episode Overview

This week's Untitled Linux Show dives deep into recent developments across the Linux and open source world. The team covers fresh releases and updates for key software (Calibre, GIMP, Handbrake, KeePassXC), delves into kernel, hardware, and file system benchmarks, unpacks Fedora’s issues with RISC-V, discusses the systemd project’s approach to AI contributions, and analyzes the business intrigue around SUSE and TrueNAS. Listener questions are addressed, and, as always, a set of practical Linux command-line tips close out the show.

---

Highlights & Key Discussion Points

1. Chasing the Sun: Embedded World & Jetlag Stories

• Jonathan opens with tales of his trip to Embedded World in Germany. Jetlag’s impact is real:

  “...you take off from Germany and it's morning time and you fly, but when you fly west, you're chasing the sun. So my day was long... I can't decide which one is better, driving at the beginning of a long trip or driving at the end of a long trip. They're both sort of terrible I think.” (01:30)

---

2. Calibre 9.5: Ebooks Get Smarter

[03:02]

• Ken summarizes the latest Calibre ebook manager update:
  • New "Edit Book" tool to remove unused images.
  • Option to display both paper book and current ebook page numbers.
  • Custom reading progress columns and annotation filtering by highlight style.
  • More intuitive menu tweaks and numerous bug fixes.
• Fun naming note: The 'libre' in 'Calibre' ("free" in Spanish/French) is intentional (03:00).
• Conversation shifts to sourcing DRM-free ebooks (Project Gutenberg, Humble Bundle).
• Panelists debate physical vs. digital reading and share stories of overflowing bookshelves.

---

3. GIMP 3.2 Released: Non-Destructive Editing Arrives

[09:20]

• Key Features:
  • Non-destructive layers for flexible editing.
  • Improved paintbrush tools and SVG export.
  • Faster development pace post-GIMP 3.0.
• Jonathan:

  "One of the big ones in 3.2 is non-destructive layers... I want to go try the SVG support. That sounds pretty cool." (09:34)

---

4. Linux Kernel 7.0 Filesystem Benchmarks

[11:42]
Jeff's rundown:

• File systems compared: XFS, EXT4, F2FS, Btrfs (CoW on/off).
• Benchmarks run on a beefy AMD EPYC 128-core server.
• XFS edges out EXT4; F2FS and Btrfs follow.
• Home users aren’t likely to notice much practical difference; stability/reliability should trump minor speed variances.
• Benchmarks reveal kernel version bumps (6.16, esp. for EXT4) offer substantial performance jumps in some tests.
• Quote:

  “For a home user, I would personally say… you’ll never really see it. I honestly would say stick with your default that your distribution recommends.” (16:52)

---

5. Kernel API Specification: A Move to Machine-Readability

[21:37]

• Draft spec aims to document kernel APIs in a structured, machine-readable way (parameter types, ranges, constraints).
• Facilitates robust user space compatibility and could enable smarter AI-driven kernel code interaction/generation.
• Jonathan:

  "It's the kernel, in some ways, growing up and becoming more of a standardized thing..." (21:54)

---

6. Handbrake 1.11: New Formats & Enhanced Audio

[23:29]
Ken’s quick take:

• Support for MOV containers, DNxHR, and ProRes encoding for pro video workflows.
• Enhanced AV1 support, new presets for latest AMD GPUs.
• Audio: PCM encoding/pass-through, custom channel ordering.
• GUI tweaks for Flatpak/sandboxed environments.
• Digression: Panelists nerd out about surround sound tracks and director’s commentary.

---

7. Fedora’s RISC-V Complaints & Embedded World Insights

[29:20]

• Performance headaches: Fedora engineer laments slow build times on RISC-V hardware - builds take ~143 min (vs. ARM 36 min, x86 29 min).
• Hardware bottleneck, not just software optimization.
• RISC-V's open nature means vendor fragmentation; difficult to standardize performance-enhancing instruction sets like AVX512.
• Jonathan:

  "RISC V is causing headaches for Fedora because the builds are slow... At least so far the various options that are out there for RISC V are kind of slow." (29:24)

• Jonathan previews an upcoming Floss Weekly episode possibly featuring RISC-V leadership.

---

8. systemd 260 RC3: AI Agents, File System Management & SystemV Script Retirement

[37:07]

• Deprecation: Old System V service script support is dropped.
• New feature ("mstack"): Simplifies overlay, bind mount management for containers.
• Dependencies raised: Requires newer OpenSSL, Python, and recent kernels.
• AI Documentation:
  • Adds dedicated guidance files (agents.md, claude.md) to help AI code generation/bots submit higher quality contributions, and to clearly flag AI involvement.
  • The panel discusses whether accommodating AI code contributions is a "middle ground" for projects.
  • Quote:

    “Why not lean into it and help the AI get better code output...” – Jeff (42:02)

---

9. SUSE for Sale? European Tech's Value and Strategic Suitors

[47:36]

• Swedish private equity owner EQT is seeking to sell SUSE, aiming to double its 2023 valuation—from ~$3B to ~$6B.
• Discussion: Who could/should buy SUSE?
  • Microsoft, Amazon, Intel, Walmart, Deutsche Bank, Siemens, SAP, AMD all mentioned.
  • Importance of European companies (and governments) seeking digital/software sovereignty.
  • Jeff:

    “I could see... Walmart being a little interested because then they get a complete Linux package that they can do whatever they want with...” (50:41)

  • Panel considers the larger context of US/European tech and government sensitivities.

---

10. TrueNAS Build Scripts Go Closed (for Now): Security vs. Openness

[65:37]

• iXsystems pulls TrueNAS build scripts from public repo—response to GPL violations by derivative commercial vendors (often in countries with weak recourse).
• Core code remains open, but the community can no longer build TrueNAS from scratch as before.
• Jonathan:

  “If you don’t have access to the build scripts, you really can’t build your own TrueNAS… the open-source part of me really kind of hates that, the business side of me understands...” (67:31)

• A necessary but regrettable move to protect commercial interests and the community.

---

11. KeePassXC 2.7.12: Password Import/Export and TOTP Upgrades

[61:17]

• Import: Full nested folder import support from Bitwarden.
• TOTP/OTP placeholder expansions for two-factor auth.
• Bug and security fixes, improved browser integration.
• The panel discusses the value of managing TOTP secrets in password vaults vs. on phones, and YubiKey/Titan-style hardware security keys.

---

12. Security Mitigations: 'Turning Off' No Longer Yields Big Gains

[74:21]

• Benchmarks (Phoronix): On recent Intel CPUs, security mitigation toggles show negligible performance impact.
• Only legacy CPUs show meaningful slowdowns when mitigations are enabled.
• “If performance is critical, upgrading hardware is the better solution than toggling mitigations.” (77:46)

---

Memorable Quotes

• Jonathan (on Calibre, 03:00):
  "It's not spelled like the word caliber is normally spelled, it's intentionally spelled with the word 'libre' at the end..."
• Ken (on physical books):
  "Maybe one day take a picture for us." (07:14)
• Jeff (on filesystems, 16:52):
  "The difference isn't going to be something that you'll really see... stick with your default that your distribution recommends."
• Jonathan (on systemd & AI, 43:38):
  "AI is going to disappear... the good parts of it are just going to get sort of absorbed into the fabric..."
• Ken (on SUSE's long list of owners, 52:49):
  "SUSE has got a history of being sold either all by itself or at... Along with whatever its parent company at the time was."
• Jonathan (on TrueNAS build controversy, 67:31):
  “If you don’t have access to the build scripts, you really can’t build your own TrueNAS… the open-source part of me really kind of hates that, the business side of me understands...”

---

Notable Timestamps

• Calibre update discussed: 03:02
• GIMP 3.2 release: 09:20
• Filesystem benchmarks: 11:42
• Kernel API spec: 21:37
• Handbrake 1.11: 23:29
• Fedora RISC-V gripes: 29:20
• Systemd 260 RC & AI docs: 37:07
• SUSE sale analysis: 47:36
• KeePassXC update: 61:17
• TrueNAS build controversy: 65:37
• Security mitigation benchmarks: 74:21

---

Command Line Tips

Ken:

• udevadm for querying device info, e.g., lookup all details about your NVMe/SATA drives (82:51+).

Jeff:

• Archdeckify: Turn your Arch-based system into a Steam Deck-like gaming platform for big-screen or HTPC setups (86:15+).

Jonathan:

• CTRL+R in Bash: Reverse-search your shell history for easy command recall (89:23+).

---

Closing & Reflections

• The episode ends with a discussion on the blurry borders of "AI" and its long presence in Linux kernel development—even predating current hype.
• The hosts express their appreciation for the community and look forward to upcoming events and conferences.
• Listener input and community sharing are encouraged—find more links and full details in the show notes.

---

This summary captures the core discussions, opinions, and notable moments for listeners who want a thorough yet digestible brief of this episode's content and tone.

Transcript

[Jonathan]

Hey, this week we have a bunch of updates to cover with things like Calibre, gimp, Handbrake and keypass. But there's also Fedora's RISC V complaint news in the kernel about an API specification that's perhaps going to get published. Systemd is adding some AI specific documentation and then SUSE may be for sale. We have thoughts about who we would like or not like to see purchase it. And then Truenas has made some serious waves by closing the source on their build scripts and a lot more. You don't want to miss it, so stay tuned. Podcasts you love from people you trust. This is Twit. This is the Untitled Linux Show, Episode 246 recorded Saturday, March 14. Chasing the sun hey folks, it is Saturday and it is time. It's time for the Untitled Linux Show. We're going to talk hardware, software, gaming. We're basically just going to nerd out over Linux and open source stuff. It's going to be a lot of fun. I've got Ken, I've got Jeff. I have half of Ken at least. There we go. Rob is flaked out. He said something about having family stuff. Bah. This is, this is the place to be. We've got some really cool stuff to talk about. If I'm a little weird today, if my voice is extra bassy. I just got back from Germany where I was at Embedded World, which was a lot of fun, but the jet lag is real. I got in last night at about 3:30 in the morning local time, which was also interesting. A very interesting sleepy drive because you know, you take off from Germany and it's morning time and you fly, but when you fly west you're chasing the sun. So my day was long, just put it that way. It was a very long day and they had to drive at the end of it. I, I can't decide which one is better, driving at the beginning of a long trip or driving at the end of a long trip. They're both sort of terrible I think. I think next time I'm going to try to either fly out of a closer a closer spot or maybe do a motel room in the morning in the evening. You know, the day before I fly out and the day after I fly out just because do not like I

[Ken]

found it better to have somebody else drive.

[Jonathan]

I suppose I could do that. My, my normal assistant also has four children to take care of, so that's kind a no go.

[Ken]

But yeah, who she got to blame for that?

[Jonathan]

No idea what you're talking about. All right, let's move into the show and Ken is actually going to kick us off and he's got an update for Caliber, or Calibre if you prefer. Because it's not spelled like the word caliber is normally spelled, it's intentionally spelled with the word libre at the end, which is why we sometimes call it calibre. There is a reason.

[Ken]

Well, even the Even though it says it should be caliber.

[Jonathan]

Yes. Well, it's the Internet. We could pronounce things however we want to. Ken, take it away later. Yeah, well, I suppose take it away. Tell us what's new in 9.5.

[Ken]

Well, I want to start off by reminding everybody it's been over a month since we last covered caliber 9.0's release. According to Bobby Borisov and Marcus Nestor Covid Goyal, who we just mentioned earlier, just released caliber 9.5. According to Marcus, the latest release introduces a new tool in the Edit Book component to remove unused images, an option to display the pages from the paper book page list while also showing the last page number, and a reset button for the Reading Stats panel in the Ebook Viewer. With the Reading Stats panel actually being added in version 9.4 now, according to Bobby, you can now create a custom column that displays reading progress and the Annotations browser now includes filtering by highlight style, making it easier to locate specific highlights, especially in large collections with extensive notes. We also see some new features added since 9.0, including improving the menu option preferences tweaks that allows you to get rid of the need for double applying it. To read about the numerous bug fixes since caliber 9.0. I do recommend reading Bobby and Marcus's articles as well as the release notes for all the versions since 9.0.

[Jonathan]

Yeah, interesting. There's some fun stuff in there. I still have not actually used Calibre. I continue to want to and I've just never sat down and done an install and imported any ebooks into it. Part of it is because I don't really have a great Linux machine for doing reading. I don't really want to sit at

[Ken]

one of my desks to read DRM free ebooks. Do you have.

[Jonathan]

I mean there are definitely places to get those. I have some where I've Humble Bundles

[Ken]

a great place for getting them.

[Jonathan]

I've got some from Humble Bundle. There's. There's also. Is it Project Gutenberg I think that has a bunch of DRM free classics.

[Ken]

Project Gutenberg Internet Archive and there's one I want to say eread.com I'd have to look at my history. Let's see here.

[Jeff]

So I don't have any ebooks.

[Jonathan]

No, I. If I was to do.

[Jeff]

I do have like Dungeons and Dragons and Pathfinder, but they're all in like a hierarchy org structure, you know.

[Jonathan]

Yeah, what's that?

[Ken]

It's a standard ebooks.org I'll go ahead and post the link in the. The discord.

[Jonathan]

Yeah. You know, my, my ebook reading at this point is going to be on one of the tablets, either the little Android tab or an iPad. And unfortunately Caliber doesn't actually run on those.

[Ken]

You just use. You can either hook up a USB cable between them and you can use

[Jonathan]

Calibre to manage your library. Yeah, that would be probably the thing that I need to do with it.

[Ken]

Or you can set up Calibre, act as a server where you connect it through it through a browser and download via from Calibre that way.

[Jonathan]

Yeah, absolutely. I like what Harold Finch points out here. My hard copies are all DRM free. And yes, as you can see, you can see it in the background of, of Jeff and Ken. You can't see in my background, but I promise it's there. My whole wall over here is bookshelves with books.

[Ken]

Maybe one day take a picture for us.

[Jonathan]

I could do that. Hold on. We'll do it live. We're doing it live. Just for fun.

[Jeff]

We'll do it live. Good on power. Shock proof. Recyclable. Cheap,

[Ken]

but not as easy to carry around.

[Jeff]

I mean, I think they are.

[Jonathan]

It depends upon how many.

[Ken]

One at a time.

[Jonathan]

One at a time is pretty easy.

[Jeff]

I don't read more than one at one book at a time. I put up one page and that's all I can handle.

[Ken]

Believe it or not, I'll find I jump between two or three different books.

[Jonathan]

Jeff just saw the picture. Yes. Yeah, it is very impressive.

[Jeff]

I. I thought I had a lot of books and I'm like, you got me beat. I.

[Ken]

Okay, what library did you just go to to get that?

[Jonathan]

No, that's literally my office. We. We have so many books that we actually need to go through them and, and purge. Because what, what we did is we've. My wife and I both. My wife and I both had a book collection. And then as our parents and grandparents were aging, they started downsizing theirs and we basically just every time someone said, hey, I have some books I'm getting rid of, we said, oh, we'll take them. Yes, yes please, we'll take your books. And so now we're at the point

[Ken]

where we need to see behind me is after doing some purging, I've still got a trunk of books that I haven't unpacked since I moved back to the States from England.

[Jonathan]

A truck or a trunk?

[Ken]

Trunk.

[Jonathan]

Okay. Those are two very different things. Yeah.

[Jeff]

For a second I thought you said truck. And I'm like, wait, what?

[Jonathan]

He's got a box truck in his backyard. Oh my goodness. All right.

[Jeff]

He's in the military. He's got a six by six.

[Ken]

Boy, would I be in trouble with my wife if that were the house.

[Jeff]

I probably have. My books are probably about four of those units. Maybe four and a half. That's. So you got me beat soundly on books.

[Jonathan]

Yeah. All right, so I've got a story here that we've talked about before and that is GIMP 3.2 is out. And we've covered this some as it's gone through the alpha and the beta process, but 3.2 is out and it's got some pretty cool stuff. One of the big ones in 3.2 is non destructive layers. It's moving GIMP into that non linear workflow, the non destructive workflow where you can, you can move things around and then unmove them. You can undo and redo. Move things on top of each other without permanently overriding. It's got some. Over some other interesting things with the paintbrush tooling, SVG export support. That's super interesting. I need to go play with that. Of course, the normal UX and UI improvements and polishing. You know, we had to wait for a long time for GIMP 3.0 to come out, but now that they've finally gotten that done, things are. Things are coming faster, quite a bit Speedier. So GIMP 3.2, and I've not downloaded it and played with it yet, but it definitely has some cool stuff. I want to go try the SVG support. That sounds pretty cool.

[Ken]

Hoping that when Ubuntu 26.04 comes out that that's part of it.

[Jonathan]

Yeah, well, you would hope.

[Jeff]

Yeah, you can, you can look at distrowatch too and it'll probably tell.

[Ken]

You have to do that during your story now.

[Jeff]

You should be riveted to the screen. During my story.

[Jonathan]

Indeed.

[Ken]

Of course, that's what I forget to look at it.

[Jonathan]

All right. Well, speaking of Jeff's story, he's GoT Some Linux 7.0 file system information and we're going to get to that right after this.

[Ad Host]

Want to see your brand on tv? Roku Ads Manager makes it easy to launch targeted ad campaigns in minutes, track results in real time, and drive on screen purchases with just a click of the Roku remote. Get a $500 match on your first $500 spent with code [e-mail] that's code R O K U500DS.roku.com Terms apply.

[Jeff]

I have two articles in the show Notes and both are about file system benchmarks. The first one's comparing several file systems using the latest 7.0 kernel code and it's file systems btrfs or butterfs betterfs, however you want to say it. Ext4, f2fs and xfs. Now all are in their default settings except for btrfs so it had a default setting and then they also Michael Erlebil turned on a mode where it runs, but the copy on write was turned off just to see what kind of performance difference that would make. Now these tests were all done with an AMD EPYC9745 which is 128 core CPU, so it's a beefy system with a lot of PCIe lanes available. Now the overall results showed that XFS came out on top with a close second for ext 4 with a moderate step down. F2FS had a mid pack ranking and better FS with no copy on write. And then at the which was a little step, it had a decent step down and then another step down was the stock BTRFs. Now it was noted by the author that of course there's a lot more to consider when selecting a file system beyond just raw performance, like the features and reliability. Most importantly, now most of us are not going to have a workload that's really going to make much of a difference, at least not in our home PCs. Now if you do notice, if you look at the results, bcachefs and openzfs were not included in the benchmarks. Now that's because they're not currently running with the 7.0 kernel, at least not at the time of this article. Now it did say as soon as everything was if as soon as they were working those results will be performed, those two file systems will be benchmarked, their results will be added into the results to fill out the table even more. Now the second article takes a look at the the two front rudders of the first article and then looks at their performance, how it's changed over the different kernel versions. So now the benchmarking didn't go back really far, but it did go back to the 6.12 LTS kernel and hit all the major releases, including 7.0. Now, when I say major releases, you know, 6.12, 6.13, 6.14, so on. Now, while the last article had a lot of file systems, this one is only XFS and ext4, which were the top two of the first article I talked about. They were the only ones that were benchmarked. Now, a lot of the benchmarks between the two look pretty overlaid on top of each other and some look like they're a little twisted where one's faster for a release or two and then the other one's on top for release or two. You know, kind of like you had a two wires and you twisted them. They just kind of keep changing, changing places. But, you know, overall they were really pretty close. The big difference in the two come to ext4 at the 6.16 kernel, where the flexible IO tester benchmarks the ext4 had a rather large speed increase. It was lagging quite a bit behind xfs. And you know, while it's even after the bump in speed, you know, it's still a little less performance, but it really closed the gap. I mean, and the 6.16 looks almost like a step function for speed. So it's 15 is at one level and then it just jumps up to Almost XFS for 6.16. Now, when you look at the overall results, XFS is slightly on top, but you know, it's narrow enough that it, it could be statistically insignificant. Now, the article doesn't go in to say if it is or isn't. And I didn't go through all the data to verify what the margin of error is and the statistical reliability of the benchmarking results. But it's pretty close. Now on both these benchmarks, I should say that people need to take them with a grain of salt. Now, these were all done on an SSD and like I said, a processor with 128 cores. So results for people running lesser hardware, like say you get a spinning rust disk or you've only got 16 cores or less, that's going to have an effect too. You know, what interface is your drive connecting to the rest of the system. You know, really for a home user, I would personally say that the difference isn't going to be something that you'll never, you'll never really see it, you know, and as stated in the last article, things like file system stability, error recovery, you know, other, other features that should factor More into your decision on which one to use. And if you, if you're going down the rabbit hole of which you should use and you're not sure what to do, you know, you're thinking, man, I better research all these. I honestly would say stick with your default that your distribution recommends. Personally, on my machines, I have a mix of ext4. Now that's on my Kubuntu machine, so Debian ubuntu machine and BetterFS, which is on my Casheos system, which is kind of the default file system for that. So, you know, I just stick with what I have because to me the difference isn't worth converting. So even though ext4 or betterfs is slower, you know, between the machines, I can't tell. And when I went from Kubuntu on my main machine to cache and change file systems, and the drives are all SSD, they're all connected to the PCIe interface, which would give me the greatest chance to see a difference, I couldn't see it. So I don't think the difference is worth converting unless, you know, you're adventurous and want to try something different.

[Jonathan]

But.

[Jeff]

Any thoughts from my illustrious co hosts?

[Ken]

Well, what I see Helix in a few of those graphs.

[Jeff]

Yeah, that's what I was talking about. The, the twisted, you know, where one wins and the other wins Helix.

[Jonathan]

Yeah, I thought he was talking about a Helix file system. Like, I've never heard of that. I don't know what that is.

[Jeff]

No, I can speak Canonese. Oh, yeah, that's why.

[Ken]

Don't ask me to speak Cantonese.

[Jeff]

That's why I said it's like a twisted, where 1, 1, 1 wins for one next release. They, you know.

[Jonathan]

Did you talk about the huge bump between 612 and 613? Do we know. Do we know what that was?

[Jeff]

No, I did not mention that one.

[Jonathan]

There's a six 12 to 13 or 15 to 16 and at least one of the. I guess there's been several of these. So ext 4 from 15 to 16 did much better in like flexible I O tester. But if you go and you look at the. Yes, there's quite a large increase. I don't know, maybe a 50% increase in performance between 612 and 613 in the Maria DB performance for both of them.

[Jeff]

So yeah, I didn't go into the real older ones. I just picked off like the 15 to 16. And

[Jonathan]

yeah, so if you look at the geometric mean, there's. You can see that there's a couple of noticeable bumps 12 to 13 must have fixed something and 15 to 16 also fixed something.

[Ken]

It's probably. Michael says that it was probably because of changing to using the amd p state in Linux 6.13.

[Jonathan]

Oh yes, performance stuff then Makes sense. It really does. All right, so there is something brewing that I find very interesting in the kernel moving on from file systems. Although this could be useful for file systems, there is a specification in the kernel that is now beyond the request for comments stage and patches are sent out for actual consideration for inclusion. From what I can tell, this isn't any actual kernel code, but no, we're talking about a specification framework for the kernel API, which is basically documentation for how user space programs call into the kernel and ask it to do things. So it's going to be, and actually it's going to be a machine readable API specification and it's going to include things like parameter types, the valid ranges for those variables, the constraints, alignment requirements, things like bit alignment and return value details like the success conditions and error codes and their meaning. And I will say that all of these things you can find already, but it would actually be really useful to have a single place where you can get to all of them and look up all of these bits of information about things in the kernel. The kernel has for the longest time said we don't break user space. I think this actually will help with that because it's going to distill all of that data down to a single place to check for changes. But it's going to be super useful for generating documentation, doing all sorts of things like that, and interesting to see. I don't know. I don't know when this is going to land. It probably will land. I don't know if it's going to be in 7.1 or 7.2, but it's pretty interesting to see that this is something that is being worked on. The series also includes a K unit test suite, so They've got like 38 tests and runtime verification of it, which is pretty interesting that they haven't tested that thoroughly for just being documentation changes. But still it's, it's, it's pretty cool to see that this is something being worked on. It's. It's the kernel. In some ways growing up and becoming more of a standardized thing make it easier for people to work with. No, I like it.

[Jeff]

I do too. I mean, I always pick up that.

[Jonathan]

Go ahead, Jeff.

[Jeff]

Oh, I was gonna say I almost picked up this story because I thought it was pretty cool where it was just, yeah, like you said, just standardizing it. Just helping people at want to interact with the kernel too. Just oh, here's my one resource rather than I had to dig through all these email lists and various documentation spread from hell to breakfast.

[Jonathan]

Now I have a thought with this, with it being machine readable, does that mean it's going to be easier to do AI coding of kernel stuff, kernel calls and all of that?

[Jeff]

We'll discuss that later at the end of the show.

[Jonathan]

I see. I'm not surprised.

[Jeff]

Not at the end, just a later

[Jonathan]

story towards the end. Closer to the end. Closer to the end than we are now. All right, well, moving away from kernel stuff, what about media management and conversion and well, transcoding? Yes, the sorts of things that Handbrake would let you do. I think we have an update for Handbrake and Ken has the scoop.

[Ken]

Yes Jonathan, I do. Now I just want to remind everybody the last version was released over five months ago, so we're that was version 1.10.2. Now according to Bobby Borisov, Handbrake version 1.11 has rolled out adding support for encoding video to the MOV or Move container format. It also introduces new digital nonlinear, extensionable high resolution. Now I'm going to abbreviate that, as I say it later, as DNXHR as well as Prores encoders, both widely used in professional video production. HandBrake 1.11 also improves AV1 support by adding a new AV1VCN 2160P 4K preset for AMD GPUs starting with the Radeon RX9000 series and introduces an AMD VCN AV1 10bit encoder. The audio subsystem receives updates as well. Now Handbrake 1.11 adds PCM encoding and pass through support, and introduces the ability to define custom channel ordering. I guess that'll be Handy if your 7.1 system that you've got in your home doesn't match the regular ordering. Linux users receive several interface and usability improvements and HandBrake 1.11 now uses Interface GTK file launcher when opening files in sandboxed environments, improving compatibility with Flatpak and other sandboxed distributions. It also adds buttons to the cycle through previews on the summary page, an option to change the user interface display language, and updated existing as well as already maintained locales. As always, I've just touched on the highlights, so I do recommend you get more details from Bobby's article.

[Jonathan]

Yeah, absolutely. I was super curious about that custom channel ordering and I'm now diving into it to discover if that is talking about surround sound stuff or if that's like when you've got more than one audio track.

[Ken]

I think it's a combination.

[Jonathan]

I'm looking, I'm looking now at the bug that it says it fixed. When I export a video with multi channel 5.1 audio from FCPX, resultant file contains a 5.1 channel 16 bit LPCM audio track which plays back just fine. But if I import this into HandBrake 1.8 for compression, HB reports some wildly inaccurate number of audio channels, usually 13 to 30, and only allows for a stereo mixdown. And in his screenshot he does indeed have multiple oh, so in this case they're both English, but it's two different encodings. So it's like the Dolby ProLogic and the AC3 Regular 5.1. So it's like two different encoding standards in the same. It sounds like you would also get into that with multiple audio tracks for different languages.

[Ken]

Languages or where you have one audio track with directors overdubbed?

[Jonathan]

Oh yeah, for sure. Same sort of thing.

[Jeff]

Cool.

[Jonathan]

Neat. To see better support for all of

[Ken]

that though my wife can't understand me while I'll sit down and watch the same movie again right after I've watched it just to hear the director's notes.

[Jonathan]

I usually don't have the patience to do a a second watch for the with the director's commentary. Once or twice I have, but if

[Ken]

I find the time I will try to do that. Yeah, usually I end up doing that. I'll watch the special behind the scenes stuff before I actually watch the movie.

[Jonathan]

Spoilers. All right, so I've got a news story about Risk five and I actually had some really interesting stuff happen while I was at Embedded World that we're going to talk about while we talk about this story. But first we're going to take a super quick break and we'll be right back after this.

[Ad Host]

Your favorite local grocery stores like Kroger, Ralph's, Fred Meyer and more are now delivering on uber eats. Get 40% off your order of fresh quality ingredients. Whether you just got home to an empty fridge or suddenly got a craving to whip up something new, you can get everything you need delivered in as little as 25 minutes. Get 40% off your order with code KROGER2026 plus members get $0 delivery fees. Order now on Uber Eats. Orders of $30 or more save up to $25 ends 4:30, 26 app for details.

[Jonathan]

Ryan Reynolds here from Mint Mobile. I don't know if you knew this, but anyone can get the same Premium Wireless for $15 a month plan that I've it's not just for celebrities. So do like I did and have one of your assistant's assistants switch you to Mint Mobile today. I'm told it's super easy to [e-mail]

[Ad Host]

Switch upfront payment of $45 for three month plan equivalent to $15 per month required intro rate first three months only, then full price plan options available, taxes and fees, extra fee full [e-mail] so

[Jonathan]

Fedora has a complaint about RISC V actually RISC V is causing headaches for Fedora because the builds are slow. And this is something that we've talked about that I've talked about with RISC V and that is that these are not super performant chips. At least so far the various options that are out there for RISC V are kind of slow. Now this is, this is specifically a Red Hat engineer, I believe it's Markin. Just, just a Kaiwich. Oh my goodness, I'm sure I just slaughtered that name. But anyway, he has a blog post on the subject that RISC V is slow and basically the fastest machine that they've got will build bin utils without link time optimization in about 143 minutes. Whereas they can do it on an ARM 64, an AR 64 board at 36 minutes and you can do it on their X8664 builds in like 29 minutes. So significantly slower. So RISC V, and this is really not terribly surprising, RISC V is not at this point designed to be a huge powerhouse. It's not for desktops, at least not yet. There's been a lot of dev boards that get embedded in a lot of things. In fact, people run a lot of RISC V soft cores on fp, but not super, super performant. Now there are there, there is at least one board that's coming. I was looking to see if he mentioned it in this article with the name of the board is the the Milk 5 Titan. That's the one because it's got an ultra risk URDP 1000 which is very impressive name. It can have up to 64 gigs of RAM and quite a few cores. So they're looking forward to that because they're going to get some more performance out of it. But for building packages and this is something that I've mentioned when I've done reviews on RISC V It is performant enough to build packages, but not necessarily performant enough that you'd want to use it. And they're seeing that performance difference even in doing these package builds now. I think I teased before I started this story that I met someone. Well, I did indeed. I went to Embedded World, like we talked about at the top of the show and one of the day. So they have. They have things broken out into different halls. And we were in Hall. I think it was Hall 3, which is like where the edge devices are. And so that's where meshtastic was at, because we're. We're at the edge. But no, machine to machine. That's what they call us. M2M. Machine to machine. But they had Hall 4 at Embedded World. That was all software stuff. And I started reading through the list of software things and started recognizing names like Ubuntu was there. Igalia was there. Canonical Buntu Canonical was there.

[Jeff]

There's also.

[Jonathan]

I think the Hall 4 was RISC v. The RISC V guys were there. They had a booth. And so I took one day and just sort of all of the names that I recognized, I went through and talked to them. Head into business cards. I'm like, hey, my business card says that I'm here for meshtastic Solutions, but I wear multiple hats. And I'm also the guy for podcasting. And turns out that when I walked up to the RISC V booth, the guy that I talked to was Andrea Gallo, who is their CEO. And so I've got his business card and a soft commitment to have him on as a show host on Floss Weekly. So super duper. Looking forward to that. Hopefully sometime soon. We'll let you guys know about it when that happens. But Anyway, over in Risk 5 World, things are. Well, let's just say that they are. They're looking very hard, but the vendors building RISC V chips so far have been concentrating on more performance per watt numbers than outright performance. And Fedora is sick of it. They're tired of it.

[Jeff]

Well, I was wondering when you said

[Jonathan]

it, was it Jeff.

[Jeff]

Oh, I was gonna say. I was. I was gonna. I was wondering when you were doing the article partway through, I'm like, is this an optimization thing or is this an actual. Just a hardware thing?

[Jonathan]

So I think it's a hardware thing. Yeah.

[Jeff]

Well, and there's room for. We need efficient processors. You know, it's got to run out of battery or something. And we can. We can wait a little bit longer as long as we keep that battery up.

[Jonathan]

Part of the problem with RISC V, and we talked about this in the past a little bit, is that when AMD or Intel or AMD and Intel actually they'll get together and they'll say, okay, we're going to implement this set of features and it's going to be called this in the X8664 spec. And that will allow for faster process like AVX512, let's just say. So here's the AVX512 extensions that we're going to add to X86,64. Both companies support it. And then you can go and you can use that in your, you know, your builds. You have those, you have those new instructions and suddenly things are faster because you have dedicated instructions. In RISC V there is a need for some of those instructions that will help. But it is difficult because there are so many players and it's an open spec, it is difficult to get those things standardized. And this is a complaint that distros like Fedoran and the like have had before is because it's so all over the place they can't turn on the equivalent of AVX512. You know, the SIMD instructions like over, over in ARM land you've got Neon and all those. There's just, there's not been at least so far, a kind of a step, an instruction stepping like that where okay, this is the name of it, here's the set of instructions. Everybody's going to implement it now it's being worked on and I think there is actually one of those sort of named instruction pools that is getting rolled out. But it, it takes time and again it's just not quite as efficient yet as the X86 64 or ARM guys are about it. But I know they're making progress. Ken, you were going to throw something in there.

[Ken]

I actually got distracted by what you were saying.

[Jonathan]

I forgot what you wanted to say. Well, that is all right.

[Jeff]

I was going to say it's really that double edged sword of hey, we've got all the flexibility we want. Well, but that flexibility also kind of slows down some adoptions of things and

[Jonathan]

it leads to, in this case, it's actually a form of fragmentation. Flexibility leads to a form of fragmentation in the actual instructions that each CPU will support. And so you get to this point to where distros to combat that fragmentation they sort of have to support the slowest common denominator of instruction sets.

[Jeff]

You could say a software analog would be just the Linux file, you know, The Linux distribution systems where you can change the versioning of stuff, how things work, where, you know,

[Ken]

sort of like when you still use the 32 bit

[Jonathan]

on some systems in some ways. Yeah, yeah, because everybody got a performance bump for going to 64 bits. All right, Jeff, let's talk about systemd. What is new now? We're covering an RC3 here, we're covering a release candidate. I feel like maybe there's a specific story in here that you found interesting, what's going on in this particular release.

[Jeff]

There is. So I'm going to first talk about kind of what's coming new in 260 and then we're going to hit something in release candidate three that came out even though. And I'll cover it later too. They just released RC4 like a couple days ago, so it's, it's churning fast. But to step back, you know, we talk about System D from time to time and you know, a lot of people, you know, well, some people don't like it while others are happy for it, happy with it, you know, for the initialization of a distribution. It's the equivalent kind of of the display of, you know, X11 versus Wayland. You know, there's people that argue back and forth though. I would say the systemd is probably more adopted roughly than the X11 versus Wayland. But there's still people that don't like systemd. That being said, I wanted to cover systemd version 260. That's release candidate 3. That's being really that, that got released just like the kernel. You know, there's release candidates. You know, systemd has the same method so they can keep putting these out, make sure everything's polished before it actually gets fully released. Now in this coming release in 260, they've removed the System System v service script support. Now this isn't as bad as it sounds because the support's been deprecated for a while and it's, it's been known for a long time that this was going away. So this should not take anybody by surprise. If it does, they have not been paying attention at all. A big feature that's being added on this is mstack and I'm not going to go into deep detail because systemd itself is a whole lot of deep detail. But overall it's a new feature for defining and managing structured overlay file systems and bind mounts using a self descriptive directory structure. Basically it simplifies complex containers and service root file system setups by organizing multiple mountain layers. So it'll just help with containers and a few other places too, but it just keeps your file system a little more organized. Now, there have been several dependencies which have been raised with this one, such as OpenSSL went from version 1.1.0 to 3.0.0, so you need to have a newer version of Open SSL to make 260 work. Same thing with Python, for example. Python went from 3.7 to 3.9. There's other ones in there, but just using those as examples. So when you if you make a switch to this, there's other libraries you're going to have to make sure you have newer versions of the kernel. Version was also raised from 5.4 to 5.10 for the baseline. That's just the baseline. The recommended baseline went from 5.7 to 5.14. But if you really want full functionality of systemd version 260, you're going to have to have kernel 6.6 or later. Now there's a lot of other additions and changes to the release and but this is the thing that really caught my eye and like I said, I went to GitHub to look at this and that's when I found they did release RC4. So these RCS are coming out pretty quickly. They're generating a lot of activity over there on systemd. So it's definitely being worked on by a lot of people. But what caught my eye in release candidate three is and I'm sorry some people are going to hate this, but they added AI agents documentation. Now I'm saying documentation so they're not adding AI to System D, it's documentation. So there's now an agents MD file in the git archive with the idea of helping and guiding AI scraper bots. So the the file will help the AI coding agents guide them on the systemd architecture, the development workflow, systemd's coding style and systemd's contribution guidelines plus help in running various systemd commands and integration testing plus noting that systemd contributions do require AI disclosures akin to the co developed by tag on the patches so it'll help AI know that it needs to make sure it says oh co developed by whatever AI it is. The agents MD also cited in a new claude MD file as a helper for claude code and also new for helping AI agents and systemd is adding the claude review YML file as the YAML file outputting of reviewing of systemd pull requests with claude code as the AI assistant. So now in the past and I thought this Was interesting because in the past we've covered how AI agent, you know, pull requests can overwhelm a project because, you know, so many times there's just too much garbage in those requests. Now we've talked about in the past about not letting AI requests in or only taking code from existing developers and you know, than other people saying, but the tools are out there, people are going to use them and what do you count as AI? And you know, I saw this and I thought this might be a good middle ground. So, you know, knowing that AI is here to stay, I don't see it going anywhere, at least not for a long time. Why not lean into it and help the AI get better code output and guided on what it should be doing and what it shouldn't be doing. So you're just giving it the parameter boundaries and a lot of help to make sure anything it does right is going to be more aligned with your project and actually be of more value to your project. Take a look at the article linked in the Show Notes for more details. And there's also links in the article to the GitHub page where you can get into all the technical details and you can get into the code and everything, you know. But Jonathan and Ken, do you think we might be on the way to other projects that can handle it the same way?

[Jonathan]

Yes, I do actually. And I'm curious, do you think this is part of again, at Embedded World and with various partners, we have their conversations about this and you know, I call myself an AI skeptic and was challenged on that and had some great conversations as a result. And one of the conclusions that the smart money had was that the current spending craze around AI is going to crash inevitably. But there is the places where AI makes sense, it's going to continue to be there. And I was thinking about this afterwards and I think essentially what's going to happen is AI is going to disappear. And by disappear I don't mean go away, but like the good parts of it are just going to get sort of absorbed into the fabric to where you it's not in front of your face anymore. And that's kind of happened, for example, with Google Search. I've gotten to the point now to where I search for something and you get the it's generated by AI, but the little blurb at the top, that's sort of trustworthy these days. Now obviously it's good to double check, but it's much better than it was. And it's gotten to the point to Where I don't see that, and go, oh, my goodness, it's AI. Get this out of here. It's now.

[Ken]

Oh, okay.

[Jonathan]

Well, that's. That's pretty okay. That, like, about half of the time it just flat out answers my question, and I can stop with that. So it's just I still like to

[Ken]

follow the links that it uses.

[Jonathan]

Well, yes. And it depends. And it depends upon what you're looking for. Right. So if you're just looking for, when does daylight savings time start in Europe? It's going to give you an answer, and it's probably going to be accurate. But if, if you say, you know, tell me about the history of the Rolling Stones. Well, sure, it'll give you some history blurbs, but you might also want to go to the Wikipedia page or the Rolling Stones website, you know, what have you. But I think we're sort of approaching this point where AI, I don't know this is quite the right way to put it yet, but we'll disappear just because the good parts get absorbed all that. To say things like this inside of projects where you have some AI documentation intended for the AI. I think maybe part of that it may help the AI sort of disappear in that it will just automatically do the right thing more often. Does that track, Jeff? Jeff? So I'm curious, and then I'll let Ken jump in.

[Jeff]

Yeah, I'm immersed in this stuff, and I agree, and you always do. To your point, Ken, you do have to kind of check. And if I'm searching, how high is Mount Everest? And it comes back and tells me it's 5,000ft, that doesn't seem like a reasonable answer to me. You know, and so there's some of that. And like Johnson said, the complexity of the question, oh, okay, I'm going to need a lot more detail than this. But, you know, but yeah, there's. There's a lot of this that I think we're going to be moving past the, oh, wow, look at the sparkly stuff to, oh, this is a darn good tool. You know, I, and I basically agree with what you're saying. It's going to fade back. Just like when the paradigm shift when computers first came into general use and people had them at their desk at businesses or the Internet became a big thing and it's like, yeah, it kind of disappears. It becomes almost a utility at that point.

[Ken]

A servant.

[Jeff]

Yeah, yeah, just a standard tool.

[Ken]

It blends into the wall when you're not using.

[Jonathan]

It just does its job. Absolutely. Any dad.

[Ken]

Ken, I think that's going to be a. I'm going to get go with a forecast of maybe a decade before we see that.

[Jonathan]

Oh wow, you think that long? I. Couple years, yeah.

[Jeff]

Jinx yo me a Coke.

[Jonathan]

All right. So there is some business stories in the Linux world this week too. This one caught me off guard. I was not expecting this. I was reminded that SUSE is actually owned by a private equity firm, EQT eqtab which is, I believe it's a German firm and they, excuse me, a Swedish firm. EQTAB is based in Sweden. So EQT is the name of an AB is probably the Swedish equivalent of LLC or something like that. It's limited liability of some sort. Anyway, EQT purchased it took SUSE private actually back in 2023 it was already a majority owner but it took the company private in 2023. The valuation then 2.72 billion euros or 2.96 billion US dollars. And so just about three years ago and they are now looking at trying to sell suse but not for less than they valued it at. No, EQT is trying to sell SUSE for around $6 billion. I don't know offhand what that is in euros. I'm sure the. I'm sure the story here has it somewhere. 5.1 billion. There it is. So 5.1 billion euros up almost 6 billion US dollars is what they consider it valued at now. That's a really good return on investment in three years. And I dare say that unlike sometimes when we cover stories like this, they have not run SUSE into the ground. Opensuse is still strong. If I ever have a company get bought out I would like it to go that well. Oh my goodness. A double evaluation in three years. Definitely successful. So it very interesting to see this now this is not set in stone. This is in fact you might consider this more like a rumor than even a news release but it sounds like this is a thing that is being explored. What's really interesting to think about though is who would come along and buy suse? Who would the. Who would the new owner of SUSE be? I could think of a couple of interesting ideas there. I'm curious, what do you guys think? Who in first off, in an ideal world who would you like to own suse? And secondly, what's some company names that come to mind that might be interested in it?

[Jeff]

Ah, boy hats.

[Ken]

I can't really think of who I would like to have on. I know I'm not sure I'd want IBM to Own it.

[Jeff]

I, well, IBM has already got one.

[Jonathan]

Yeah.

[Jeff]

Red Hat.

[Jonathan]

Yep.

[Ken]

And you'd probably see some pushback if they did try to buy it.

[Jonathan]

Yeah, probably regulatory pushback.

[Jeff]

I could see maybe Microsoft being a little interested because then they get a complete Linux package that they can do whatever they want with and just suck it right up.

[Ken]

Or even Amazon.

[Jonathan]

Amazon also came to mind. I could see Amazon buying it. There are three customers that this Reuter story mentions that actually I could see any of these three wanting to just outright own and that's Walmart, Deutsche bank and Intel. That's actually an interesting idea.

[Jeff]

But why would.

[Ken]

But does intel have the money right now?

[Jonathan]

No, it doesn't. That's the thing. Intel does not have that.

[Jeff]

They'd have to give them stock or something.

[Jonathan]

Right.

[Jeff]

But there's ways around that. You can do stock when you're a corporation.

[Jonathan]

You don't have to have money to buy things.

[Jeff]

Yeah, you really don't. There's all sorts of smoke and mirrors you can use.

[Jonathan]

Absolutely.

[Jeff]

But I don't see why would Walmart want it. They could, they could just grab whatever distro they want. Unless Walmart is trying to get into the cloud realm.

[Jonathan]

I've heard some, I'm heard, I've heard some mumblings. Walmart is trying to chase Amazon in almost everything that they do. So I, that would not terribly surprise me.

[Ken]

I think the only thing Walmart wouldn't want to get into is one hour delivery nationwide.

[Jonathan]

Aren't they, Aren't they? But they have delivery to the door. They are starting to move into that.

[Jeff]

They're, they're there for delivery stuff. I, but cloud, I could, you know Walmart does have the, the, the name recognition, the pocketbooks, the, you know, they wanted to. I could see them being a viable, or at least giving it a, a true competitive effort.

[Ad Host]

Yeah.

[Jonathan]

I will say though that when I first asked this question, Microsoft and Amazon were the two names that really came to mind as potential suitors and I know.

[Jeff]

Go ahead, Ken.

[Ken]

I was just going to say that SUSE has got a history of being sold either all by itself or at. Along with whatever its parent company at the time was.

[Jonathan]

Yeah, it's changed hands quite a few times now.

[Jeff]

I'm going to throw something out here a little bit. I could see when you mentioned Deutsche bank because okay, its value went up. But right now a lot of Europe is trying to get out from underneath American software and some of them have picked Red Hat. But suse, that's European, it's a German company. And as everybody tries to jump on or a lot of people are jumping on Linux in Europe and they want home based software, I could see the potential market for SUSE going up tremendously. So I could see where they, you know, the current holders are going. We see the potential here. There's a lot of upside on this market but we're just, we're just going to get out of it now and then because a lot of times those funds, they're not in it for super long term anyway. You know, they're hold, hold stuff for a while and then in general there's

[Jonathan]

exceptions but there's, there is yet another German company that comes to mind that is large and could have use for something in this space and that's Siemens. I could see somebody like Siemens, a dark horse, come in and say we'll take that, thank you very much. Siemens could do this without breaking a sweat. They are huge. And there's other, there's other European companies that sort of fit into that. I don't know if I technically need to make this disclosure but technically the parent company of the parent company that. Let me put it this way, Siemens is the parent company at the parent company of one of the places that write me a paycheck each month they are involved with Hackaday. I have no insider knowledge of anything going on at Siemens. I didn't even go by the Siemens booth at Embedded World. I went by the supply frame booth but not Siemens and they didn't know who I was at the supply frame booth anyway. So I'm not that big of a deal to Siemens.

[Jeff]

Yeah. For those who don't know Siemens, Siemens makes a lot of stuff that goes into things. They don't have as much consumer facing things as.

[Jonathan]

Yeah, very, very few consumer facing things but industrial. The factory that makes your consumer facing things almost certainly has something made by Siemens in it. Factory controllers. Oh yeah, that's a lot of what they do is like factory controllers, semiconductors.

[Ken]

Another company that we hadn't mentioned is SAP.

[Jonathan]

Yeah. Also a European, very large European company. I don't know that there's as much of a, of a business case for them to own a Linux supplier, but it's definitely not outside the roman box.

[Ken]

Strategic investment for.

[Jonathan]

Yeah, that is, that is an interesting thought. Again, we don't know anything. We don't know anything. We're just guessing. We're just talking.

[Jeff]

Yeah, we're thinking this is all speculation.

[Ken]

Like it was hallucinating by AIs.

[Jeff]

Yeah, exactly. No, it's, it's this is this is like a user group and we're all just throwing in our 2 cents while we drink our beer or 1 cent in some cases.

[Jonathan]

I get to do that. In Germany. We stopped at an Italian pizza place that made like actual authentic Italian pizza. And I teased the guys that Americans perfected pizza, but it was a very different sort of pizza than we get here in the U.S. now you're making

[Ken]

me want to take a break.

[Jeff]

Well, before anything, I do want to say so Wizardling had a comment and he said there is a significant concern overseas about the US tech having too much power. He said no offense, but maybe there isn't much awareness of the depth of the feeling about this issue outside the US and yeah, especially for people like us. I don't deal with Europe a lot. I do some, but not a ton. And everything I do is hardware. So we don't have a good barometer on how, how strong that feeling is.

[Jonathan]

Yeah, I, I have a little bit. I've got a couple of my partners that are in. Two partners that are in Europe and then one partner is a Frenchman living in Hong Kong, which is an interesting sentence to say. So I, I do get to hear a little bit about that from them. I have conversations with folks overseas quite a bit. But it, it is a thing. It is a. There is some common sentiment. But I will also tell you that it is something that European governments are at least thinking about in. In the same way that the US Is thinking about. And I hope Europe's thinking about this too, about diversifying its semiconductor sourcing so that not as much of it is made in China and Taiwan. Europe is thinking about diversifying its software stack so that not all of it comes from the U.S. one other thing to throw in here that Keith's 512 says is he says maybe a woman called sue will buy it. And then of course is Lisa sue at amd, which is another interesting thought. They definitely have the market cap to be able to do it right now. I don't know if that makes sense to their business model, but it's, it's definitely another, another player that could be mentioned in the same conversation, let's say.

[Jeff]

I could at least say it could be reasonable because they're trying so hard to get into the AI and all the enterprise which their CPUs are, but their GPUs are not near the player that Nvidia is. I could see them going here we're building you the operating system that you just load up and it will work.

[Jonathan]

It's more of a vertical stack. If they had the Linux OS as part of their portfolio, they can say, look, here's, here's our vertical slack. Our vertical slack. No, no, no, no. Our vertical software, vertical hardware and software stack. You know, buy our os, buy our hardware, we guarantee that it works together. You can get an AMD cpu, an AMD GPU and an AMD operating system. You put it all together and we guarantee it's going to work. That's actually, that's an interesting idea.

[Jeff]

And it will have AMD support so that you are not left without, you know, support to call. That's sometimes a lot of what hardware companies want because they don't want to try to figure all this stuff out. And they go, you know what? This, this ROI on this investment is going to do good for us.

[Ken]

So in fact, I think this week Michael Larabel wrote an article about AMD AI NPUs.

[Jonathan]

I mean it's definitely a thing that they are pushing. They're trying to get it continue to break into that market.

[Jeff]

The reason we're seeing.

[Ken]

Go ahead.

[Jeff]

Oh, I was gonna say the reason we're seeing so much on the consumer side on linux and for GPUs is because it how it ties into the enterprise AI compute market. It's very, very similar. So then they can leverage it for gaming and other things when it's like, oh well, we're 99% of the way there. Okay, we Dot and I cross a T and there we just opened up another little market for almost no effort.

[Jonathan]

Yeah, absolutely. All right.

[Ken]

They've got a great community to help support it.

[Jonathan]

We best move on. And Ken has a story about Keepass xc that's one of the open source password managers and we will get to that. But after a quick break, we'll be right back.

[Ad Host]

Refreshing Wild Cherry Cola meets Smooth Cream. The treat you deserve. Pepsi Wild Cherry and Cream. Treat yourself well.

[Ken]

Jonathan. It's been over four months since KeePass released an update. According to Marcus Nexter, KeePass is XC2. 7.12 was released this week, adding support for nested folders when importing passwords from Bitwarden. It also adds support for time, otp, an autotype and entry placeholder, and for setting the BE and BS flags to True for passkeys. Now KeePassX also prevents exploits through OpenSSL configurations, fixes showing correct checkbox value and entry, browser integration settings, and adds public key to register response. As always, you can get more details for Marcus article and plus, I don't want to be Tripping all over a lot of those anagrams or synonyms that they use.

[Jonathan]

Yeah, I wonder if time OTP is the same as taught P. Obviously they're both time based one time passwords. But there, there's the taught P is an actual implementation of it. I wonder if time OTP is.

[Ken]

It is. In fact, one of the things that I'm looking forward to using when I get the upgrade is the fact that it'll automatically. If you or setting up a new password for an account and you've set up two factor authentication, it'll automatically prompt you to create that.

[Jonathan]

The time OTP placeholder generates a time based one type password, a taught P according to RFC 6238. So yeah, it is the same thing. That is what Google Authenticator gives you as well. And so this allows you to put that top P secret into. Into your. Into both. Yeah, into both places.

[Ken]

Which I've done that with several two factor authentications I use once I figured out how to do it Keepass years ago.

[Jonathan]

Yeah, I, I always, that was always one of the things that concerned me. It's like if I put all of this stuff into say my cell phone, what happens when the cell phone dies or the screen breaks and I no longer have access to it? Now apparently people at Google have the same thought because you can sync all of that stuff up to your account, which is terrifying as well, but in a different way. But does make a lot of sense for being able to keep access to it. For sure. All right.

[Ken]

But I actually use Keepass on a daily basis or Keepass XE on a daily basis because that's my go to. I've just keep a copy a copy of it into the cloud for using with my phone from my Google Drive.

[Jonathan]

Speaking of which, I actually just received one of these guys in the mail. I've not even plugged it in yet, but I have it. I have it in hand. Thanks Robert, for sending it to me. This is a Google Titan security key. Fancy, fancy stuff. One of the things now what's that?

[Ken]

How much are those now?

[Jonathan]

I don't know. I got it for free. I bet it's. I bet it may not be cheap.

[Jeff]

What is the Titan key?

[Jonathan]

It's. It's. It hosts like your. Your password stuff and your pass keys. I am curious how much it costs but if you were to buy it,

[Jeff]

heard of it for.

[Ken]

Why am I saying thinking Fido.

[Jonathan]

That's only like $35. It's not that much. It's.

[Jeff]

It's gonna be you're going way back in time if you're thinking Fidonet.

[Ken]

No Fido 2 security keys.

[Jonathan]

I was gonna say there is Fido and security key.

[Jeff]

Yeah, I was teasing, Ken.

[Jonathan]

The security key is indeed built on FIDO Open standards. I don't remember what FIDO stands for, but it, it is one of the security key standards. Yeah, it's actually very, very similar to a Yubikey.

[Jeff]

Okay.

[Jonathan]

So yeah, I'll get that set up on some of my accounts and start using it.

[Ken]

Fido 2 basically is referring to Fido version 2.

[Jonathan]

Yes. All right, let's talk truenas. So this is the open source NAS open Source Network attached storage system. It's an enterprise Linux enterprise ready Linux based NAS solution and do a lot of stuff in the open on GitHub except now it no longer hosts its public build repository there. Which I saw this, I saw it on Twitter, actually the X, the social media network formerly known as Twitter, where Jeff Geerling actually posted about it and said is this true? Linked to this particular news report and there was a, there was actually a response there directly from truenas who said yes, you can read some deeper discussion at. And then a link to the forum. And then there's also a podcast by Chris and Chris on the T3 podcast, which I've not gotten a chance to go and listen, listen to that to see what they have to say about it. But the, the idea is that for security reasons and to be able to support Secure Boot better, they see the need to close the build scripts, pull them internal and not make them. Not make them open the way that they are. So I'll read to you, the CTO his statement here, or at least parts of it, why we did it. He says we had a growing problem with bad actors forking truenas, selling closed source commercial derivatives under their own brands and ignoring the GPL and other licensing obligations with no attribution, no contribution back to the project, no supporting the community or the engineering effort that built what they're reselling. And then here's the kicker. Unfortunately, many of these are in regions where we have little to no legal recourse. If you don't know where that is, that would be places like China where it's very, very difficult to, to go after someone for a license violation and other places, China's not the only one. But that's probably the probably where they're talking about. To address this challenge, we were already planning to take the build scripts internal with the upcoming refactor of the new Secure Boot feature along with myriad of the changes we wanted to make to the build infrastructure. Truenas 27 was a natural time to make this change. And what it does not mean we are not paywalling existing free features, period. If it's free today, it stays free. And then he also said what hasn't changed? We've always made decisions about which new features are fully open source, as in GPL or bsd, which are proprietary and which land in the free edition versus True NAS enterprise. He says that's how we fund the engineering that builds truenas for everyone. That model isn't new and it isn't changing. And he says he's happy to answer questions. I get all of that. But at the same time, if you don't have access to the build scripts, then you really can't build your own True nas. And so the whole thing is sort of inaccessible now. You could download their version of it, but not being able to do a build, I don't know. That does feel a little gross. Icky. The open source part of me really kind of hates that the business side of me understands that sometimes that is just the reality of a situation is that sometimes you have to do the difficult thing because you're otherwise just getting killed on the business side of it. It'll have. Obviously it has had and it will have fallout with users. I don't know. You hate to see it, right? You hate to see something like this, something that was developed out in the open. Now being said, okay, we're going to have to take this. This internal where you. You can't look at it anymore.

[Ken]

What's talking about compiling your own. They never. The link I just posted in Discord has where one of the Truenas staff says they've never had reproducible builds.

[Jonathan]

Not reproducible builds, but it. Well, let's go take a look at the link. Bottom line, the open source GPL v3 the build system is another matter. It's currently changing fairly radically internally for a variety of reasons. Blah, blah, blah blah blah. The repo is still there, folks can fork them into. Also okay, they're saying the stuff that is GPL is still out there, they're just not continuing to push to it. All the open source bits can be built if the community desires. 99% never done a build from source before. Mm yeah, 99 of the folks commenting on this thread have never done a build from source before. That's absolutely true. That's something that you, you know, why. Why would you want to this essentially running your Own Linux from scratch to run their build system, their build scripts. Yeah, so not, not fully reproducible builds, but yeah, they have had the ability for people to go through and build their own and now, now that is essentially going away. You can't do their, their newest builds completely, completely apart from using their stuff. So I think something is lost here. I think it's, I think it's wrong to suggest that nothing is lost here. But on the other hand, I think it's fair to say that it's not going to affect, you know, like he says, 99 of the people that would use true NAS. So it's kind of a, it's that

[Ken]

1% that could help improve it from the community that they're losing.

[Jonathan]

Yeah. Although they probably, the build scripts, they probably got very few pull requests into and oh, I hate to say this, but nowadays it's so easy to write AI pull requests. It's almost better to just turn them off and do it all internally.

[Ken]

Maybe that's why they're moving out of GitHub.

[Jonathan]

You know, it would not surprise me if that was actually a consideration with this. Let's just, you know, let's just not mess with it because of the AI pull requests. Keith512 says most people turn off secure boot as it is a pain. Most home users might turn off secure boot as it is a pain. But you get into commercial environments, you get into things that are underneath the. Oh, what's the new, what's the new European, the new European law, Security law, Cybersecurity Resilience act and all those things. Especially if you get into government work where you're under FAR and dfar Here in the us I'm sure countries around the world have their equivalents. You leave secure boot on because it's in the contract and you're not going

[Ken]

to be worrying about somebody dual booting on it.

[Jonathan]

Well, no, sometimes you dual boot. When you're doing this stuff, you just, you're going to be running something like Red Hat that has all the certifications and also has its secure boot stuff already. It's already sorted.

[Ken]

Well, but I wouldn't be able to just dual boot from it into opensuse or Tumbleweed.

[Jeff]

No, because a lot of, a lot of times in these where you're really trying to lock down information and ip, your USB ports are locked out, the firmware's password protected and encrypted.

[Jonathan]

It's.

[Jeff]

So even if you, you know, you're sitting at the machine, it takes some stuff. I mean, okay, you physically are at the machine. You can get around a lot of stuff, but it is not trivial to. You're not just, oh, I'm going to pop it open and throw this in, and no, it's. There's more to it.

[Jonathan]

And, you know, those. Those mitigations, they. One of the big things that they're trying to do is make it very difficult to do it either very rapidly or to do it accidentally. And so you see things like stuxnet, that was. Well, it was. It was intentional by the people that wrote the malware, but that was, you know, hey, I found a USB key. Let's plug it in and see what's on it. Well, the next thing you know, your machine's hosed and all the rest of the machines in the building. And then, of course, that one escaped out into the wild, because, of course it did. It was so viral because I plugged

[Ken]

into the wrong machine.

[Jonathan]

Yeah, somebody took a USB key out of the target building, and then it just went everywhere. Anyway, let's move on and let's talk about, well, more security stuff, but this time, the cost of security. Jeff has the scoop.

[Jeff]

So it's been a few years now since a lot of the hardware speculation issues for CPUs with hyper threading have come up. You know, when the first issues came out, turning on the hardware mitigation caused slowdowns on your cpu. Now, there were a lot of people who would disable those security features because they wanted the most speed they could get out of one of those chips, CPUs. And, you know, a lot of the security issues didn't really apply to home users. They were more of a concern for the cloud and enterprise markets. Not that somebody couldn't leverage them, but the average home user was not the primary target for a lot of that stuff. Well, fast forward a few years, and today, you know, chips have been designed from the ground up to take care of the issues. Now, we've talked about in the past, there's a silicon pipeline. So whenever someone says, oh, we got to make this design change, it might be three years before it actually hits a consumer market. Just from the design to testing, fabrication and so on. I won't go into that again here, but suffice to say, it takes a while. Now, there still is a switch to turn those security features on and off. And that's exactly what Michael Larable over at Phronix did to see if there was still a performance issue. Now, the article in the show notes is broken up into two sections. The first section, he just Benchmarks with a Panther Lake CPU, specifically a Core Ultra X7 358H, which can be found in current laptops. Side note, did everybody who can name a product reasonably, like retire or something?

[Jonathan]

Apparently, I don't know.

[Jeff]

Yeah. Anyway, so looking through there, the results showed no difference or very small differences between, you know, with security mitigation on and off. With the exception, a couple Exceptions, the Rocks DB Database 10.0.1 update random benchmark where the mitigations turned off, it was quite a bit faster, but other databases were just fine. And it was, I mean, it was just that one specific test and other Rocks DB benchmarks that did other things, they were fine as well. It was just that specific one. Now, there was one other standout and that was Raw Therapy, it's RAW photography software benchmarking. It also showed a big difference. I don't know why, I don't know what it was hitting that it didn't like, but it was slower as well. Everything else, other database tests, code compiles, other things, just if there was a difference, it was just noise. It was so small that you're never going to notice it. Now, the second part of the article, Michael did benchmarking across several Generations of laptop CPUs, define the performance differences with the mitigations on and off. So this one we had several generations. Now, you know, while some users swear by running their systems with mitigation turned off for better performance, you know, realistically looking at all the generations, there's little benefit in doing so for the Core Ultra Series 3, Panther Lake or even other recent Intel CPU generations for that matter. Only if going back several generations is there really a difference between, you know, anything to gain from having security mitigations on or off. So anything the last few generations doesn't really matter, you know, and realistically, if you got an older generation and you want to leave it off, you know, at that point, if performance is really that critical, you probably should start looking at a newer, some newer hardware because that would be a lot. You're going to have a lot greater jump in performance than just turning your mitigations on and off. But you can take a look at the article linked in the show notes for full details and the ability to dive deep into the results to see if your specific situation is going to be affected.

[Jonathan]

Yeah, very, very interesting stuff. I know that each of these have had, at least some of them have been big, but all of them have had some performance penalty. Some of those penalties they've been able to mitigate in hardware by fixing the actual problem.

[Jeff]

And that's why some of these you're not really seeing much is because it just took a few couple generations before. And going back to Silicon Pipeline we've talked about before, okay there, Panther Lake's out being sold right now. There's one that's being tested right now internally to intel. And all, all chip companies are like this. They're, they've got an internal one that's not going to be out for another year or something like that. And then they're designing the generation after that that's, you know, doing the circuit layouts right now and probably hasn't hit even test chip fabrication yet. So when they say you got to fix this in hardware, you got to go back a couple generations, you know, go in future generations before you can go, oh, we can change the, change the actual layout, fix this in hardware and then get it through the pipeline.

[Jonathan]

Yeah, yeah, absolutely. Interesting stuff. All right, well, that is the news for the week. We are about to move into some command line tips. But first we're going to take a real quick break. We'll be right back. An all new season of the Secret Lives of Mormon Wives is now streaming on Hulu and Hulu on Disney.

[Jeff]

Mom talk has just been blowing up.

[Ad Host]

Whitney and Jen are on Dancing with the Stars. Taylor is a bachelorette. Saying that out loud is crazy.

[Jonathan]

Like that is huge.

[Jeff]

But all the cool opportunities could pull us apart.

[Ad Host]

It's causing issues in everyone's marriage. My whole world is falling apart right now. It's chaos.

[Jonathan]

Watch the Hulu original series the Secret Lives of Mormon Wives now streaming on Hulu and Hulu on Disney for bundle subscribers terms apply. This episode is brought to you by Cologuard. Do you know what's really scary?

[Jeff]

Not screening for colon cancer when you turn 45.

[Jonathan]

The cologuard test is non invasive, requires

[Jeff]

no special prep or time off work and ships right to your door. In just three simple steps, Cologuard takes

[Jonathan]

the scare out of colon cancer screening.

[Jeff]

If you're 45 or older and at

[Jonathan]

average risk, ask your healthcare provider about the Cologuard test. Cologuard is available by prescription only. Learn more or request a prescription [e-mail]

[Jeff]

screen

[Ken]

Yep, Jonathan, this week I am introducing you to a command line tool for controlling the runtime behavior of systemd udevd, requesting kernel events, managing the event queue and providing simple debugging missions mechanisms. Now I'm going to show you how you can use UDEV ADM to query The UDEV database for device information. So let me go ahead and bring up my screen here and the basic command I'm going to demonstrate is UDEV with its active action verb of info. I'm going to tell it no pager. That means it doesn't automatically get paged into something where you can scroll up and down through it. And then I'm going to tell it to query all the information for my NVM NVME drive. And for those of you listening, I just hit Enter and it came back with the information about it. The devices/PCI00000://000000://NC colon 0120000://NVME 0. And that's just for the only NVME drive on this system.

[Jonathan]

And this is why we have UDEV so that it can get mapped to a simple dev NVMe 0 and 1.

[Ken]

And then what's interesting though is you've also got some symbolic links that are created for by ID or by path or by disk sequence. For those of you listening, those are broken out. I'm not going to read those that take too long. But the you can you use the output to grip for some of the information by piping it to grip and say searching for ID underscore serial, you can get the serial short or the long serial. And Jonathan, can you tell who the manufacturer of this particular NVME is?

[Jonathan]

It's a. It's a Kingston.

[Ken]

Yes, it is. Now you can also change the device you look at to say sda and that's going to give you a little bit more information. And by looking at the information that I get from for my drive that's mounted to sda, what would you say it is?

[Jonathan]

Well, so it's obviously something connected over SATA, which I believe what the S&SDA stands for. Yes, ST. It's an ST 4000

[Ken]

which is a Seagate model.

[Jonathan]

Yes, Seagate. Seagate technology. That's what ST stands for. Again, I've been off that embedded world. So ST there stands for like STMicro. Different company. Totally different.

[Ken]

Now I've actually got two devices with Rust on them in this system and this one's also in ST models.

[Jonathan]

That's cool. I like that you can use the short name and get all the long name info about something. I've not made use of this a whole lot in my Linux career and I will definitely have to. This is actually really useful.

[Ken]

I actually came across how to Use it. While I was looking into what was causing Dolphin to lock up for about 10 seconds to sometimes a minute.

[Jonathan]

Ew. Yeah, that's no fun. Did you figure it out?

[Ken]

But every it says that it could be that. I'm starting to see a lot of sector failures on one or both of these drives.

[Jonathan]

It's possible.

[Ken]

The first one I did was that the 4 terabyte one.

[Jonathan]

If you, if you run one of the top programs it'll tell you whether you're waiting on like input or if something is actually running the cpu. I forget the terms that it uses but like top and H top that I'll let you know.

[Ken]

Yeah,

[Jonathan]

yeah. It could very well be a drive given your problems. All right, very cool tip, Jeff. What do you have for us?

[Jeff]

Well, nothing that serious. I just figured I'd throw in something fun for the Steam deck fans. It's Archdecify. Basically it's a script to set up a SteamOS like gaming environment and you will need Arch or an Arch based distribution, the SDDM Display manager, a compatible gpu. They do make some notes that Nvidia hardware might have a few more issues to overcome because Steam Deck is normally amd. But it doesn't say you can't use Nvidia, it's just be aware there might be a couple little more hoops to jump through. A gamepad is best for UI experience because it again is Steam Deck and KDE Plasma is also recommended for the best experience you can use other desktops, but again optimize your experience. Go with KDE. Deckify lets you choose your desktop session and you can switch to a full screen gaming experience just like you'd find on SteamOS. Like on the Steam Deck you can get auto login through SDDM so it pop right in and it allows easy switching between game mode and desktop mode. There is to install it. There's one online command which I won't bore our readers going through it since it contains a longer URL and a few layers of directory. But basically it's pretty easy to install and run. Now they do add the typical warning that you know, okay, you're installing this, you could change some important system configurations and you could have some instability but you know, basically you're on a non distribution piece of software so be aware that you know in the off chance something goes off the rails, it's not their fault if it does, but people seem to have pretty good luck with it. So I won't go into all the details on usage but it basically turns your PC into like a Steam deck. And if you follow the link in the show notes to the GitHub page for the Archdeacify, you'll find the install link, the rest of the documentation, and you'll have your very own powerful Steam Deck ish system.

[Jonathan]

Yeah, Also useful for like a home theater PC setup, I would think. Doing a game on it. Yeah.

[Jeff]

Pretty cool.

[Ken]

Yeah, but you actually want to do this on bare metal or in a vm?

[Jonathan]

On bare metal, yeah. You're going to be gaming for sure.

[Jeff]

Yep, yep. Because then if you do it in a vm, then you're going to deal with all the GPU pass throughs and there's a whole lot of extra heavy lifting you'd have to do to make it work.

[Ken]

Right.

[Jeff]

And this is a script to set up the configuration. So it's not like it's totally redoing your system or loading a ton of things, it's just configuring things so that it mimics somewhat a Steam deck.

[Jonathan]

So I've got a tip for you today as well, and that is Control R of all things. And I didn't know about this until just recently, but this is a search function, it's the reverse search built into Bash and it will. Let's see if I can hide the logo. I don't know if I can easily hide the logo, but it will. You say, hey, I remember I did something with Pio, but I don't remember what the PIO command was. Well, so you can just start typing pio and it'll show you the most recent command that you ran that had PIO in it. If you want to find the next older one while you're right here, you just hold Control and hit R again. And it will take you back a step in history. So you can do that and look through all of them. And so in this case I was trying flags and eventually you get to the very, very end and it says that's it kiddo, I don't got any more to show you. And I believe Escape will drop you out of that and happens to put the most recent command on the screen. So let's see. Oh, interesting. Yeah, Control C then will drop you out without putting it there. And so essentially what this is doing is it's moving you back through history in exactly the same way that like hitting the up arrow does. It lets you search instead of stepping through them one at a time. This is not part of my Linux muscle memory, but it really should be.

[Jeff]

Yeah, how did we not talk about this before. I use this all the time.

[Jonathan]

I don't. And that's the thing. And I'm not sure how I didn't. No, it was a thing.

[Ken]

I just use a alias S A R a C H to search back to my history for something.

[Jonathan]

Yeah. And there are other ways that you can do it, but this is nice because it's so. Well, it's actually. It's live. You're. You're live interacting with it. And you can just continue hitting control R until you get to the one that you actually want to run. And then you hit enter and it's there.

[Ken]

So it's pretty cool what you start typing. Doesn't have to be at the beginning either.

[Jonathan]

It could be anywhere. It searches anywhere in the string. Yeah, that's a good call out for sure.

[Ken]

I started typing just help playing around with it when I had open my.

[Jonathan]

My tendency is I will. I will write, you know, history pipe symbol and then a grep. And so I'm. I'm grepping for a particular. Particular thing. This does the exact same thing. It's just. It's faster and you can just run it instead of have to copy and paste or whatever. Reese retype it out. So yeah, it's cool. And I'm with Jeff. How have we never covered this before? Standard. All right. That is. That is the show. I'm going to let each of the guys get the last word in. I know both of them have something. We'll let Jeff go first.

[Jeff]

Well, nothing, nothing too major.

[Jonathan]

Just.

[Jeff]

Just a little bit of poetry. A file that big, it might be very useful. But now it's gone. Have a great week, everybody.

[Jonathan]

All right. And same thing for Ken. Any last words for everybody?

[Ken]

Yes, I came across a quote by ted. Now I hope I say this last name right. So about what happens if we are sloppy about banning all code that has ever been used built using AI assisted technology. You want to read that quote? Just follow the links in the show notes to actually read the quote.

[Jonathan]

Is it. Is it not pithy enough to read out for us? Is it pretty long?

[Ken]

It's going to take a good minute or two. But if you want, I can try to read it without stumbling over words.

[Jonathan]

Yeah, you can read that. That's not too long.

[Ken]

Okay. According to Ted. So quoting him, I will again note that LTS kernels have been created using machine learning. Now here in quotes we have AI models composed of neural networks as early as 2018 to find kernel commits containing bug fixes that should be back ported to the Stable branch branches. Given that people seem to be throwing around AI slop without defining precisely what they mean by AI. If we are sloppy about banning all code that has ever been built using AI assisted tooling, you'd have to start shipping the Linux kernel back to the version used in Debian 8. Jesse,

[Jonathan]

there you go. AI has been, has been with us for quite a while. It's just now having its moment, it's moment in the sun.

[Jeff]

And we, we talked about that a little bit last week where it was like, well, what does AI actually mean? Where, where do you exactly draw that line? Because I remember at our programs on the Commodore 64. True, true, they weren't that great, but

[Jonathan]

yeah, I mean that's what the Lisp language was originally for and, and one of the big things that they were doing at the MIT labs is trying to get artificial intelligence working. So yeah, it's been around for a long time.

[Ken]

Then they changed to calling machine language.

[Jonathan]

Yeah, absolutely. All right, well that is the show and we sure appreciate the guys being here. Jeff and Ken, thank you both and we, we've had it, we had a lot of fun. I will, I will say that if you want to find me, there is of course Hackaday that is still where Floss Weekly lives. And also of course my shack and meshtastic Solutions that actually my day job these days. Having a lot of fun there. Getting to go to cool and fun places like Embedded World this past week, possibly going to make it to an Ubuntu conference in a couple of months. Getting invited there to do a workshop. Not a keynote speaker or anything like that, but invited to do a, like a 45 minute talk and looking forward to that as well. I'll get some more information about that as we get closer and it gets all finalized and settled. Yeah, we just, we appreciate everybody that's here, whether you watch or listen, if you get us live or on the download. We're glad you're here and we will see you next week on the Untitled Linux Show.