The Distro Everyone Should Copy
Oct 26, 2025
Fedora 43 arrives with polish, new spins, and a smarter installer; and one decision the rest of the Linux world should pay attention to.
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.
- CrowdHealth: This open enrollment, take your power back. Join CrowdHealth to get started today for $99 for your first three months using code UNPLUGGED.
- Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility.
Links:
- 💥 Gets Sats Quick and Easy with Strike
- 📻 LINUX Unplugged on Fountain.FM
- nebula-lighthouse-service
- nebula-lighthouse-service: init at 2.0.0 by bloominstrong · Pull Request #454855 · NixOS/nixpkgs — nebula-lighthouse-service is aimed to be run a a public nebula lighthouse for those who cannot host their own, or who want extra lighthouses without the burden of maintaining another lighthouse.
- Fedora Linux 43 Cleared For Release Next Week — While Fedora 43 wasn't ready for release this week due to outstanding blocker bugs, at today's Go/No-Go meeting it was decided that Fedora 43 is now in a position for shipping next week.
- Velocity Limitless / Projects / Slitherer · GitLab
- Fedora 43 Wallpaper Wrap-Up – Fedora Community Blog
- Fedora COSMIC Spin
- Plasma 6.5 - Reaching the Inflection Point
- [Fedora KDE] Early Plasma 6.5.0 - Fedora Discussion — With Fedora 43 being a go, we will be doing an update on repos towards the middle to end of next week that will bring Qt 6.10 and Plasma 6.5.1 to F43, and Plasma 6.5.1 (Most likely, plans are not 100% final in that regard) to F42. That will bring the update to the usual architectures, such as aarch64.
- Pick: Millisecond — Optimize your Linux system for low latency audio
- Millisecond on Flathub
- noblepayne/millisecond-flake
- rtcqs — rtcqs is a Python utility to analyze your system and detect possible bottlenecks that could have a negative impact on the performance of your system when working with Linux audio
- How do I get an out-of-the-box working Linux audio workstation? - LinuxAudio.org
- Pick: lemurs 🐒 — A customizable TUI display/login manager written in Rust
Transcript
WEBVTT
00:00:00.005 --> 00:00:04.125
It's crazy stormy in the Pacific Northwest this weekend. Wes and I have been
00:00:04.125 --> 00:00:06.505
sharing crazy weather notes back and forth.
00:00:07.065 --> 00:00:09.825
Yeah, you know, you got to keep up to date on where the latest power outage is.
00:00:09.965 --> 00:00:10.745
Did you ever lose power?
00:00:10.985 --> 00:00:11.945
No, thankfully not.
00:00:12.105 --> 00:00:15.945
The studio did not lose power either. And I thought I was doing pretty good
00:00:15.945 --> 00:00:19.165
because I'm out in the woods, kind of up against the mountains. The mountains.
00:00:19.465 --> 00:00:22.305
And the power didn't really seem like it was going to flicker.
00:00:22.385 --> 00:00:24.285
The wind didn't really seem like it was blowing too hard.
00:00:25.225 --> 00:00:30.545
9.50 p.m. I hear this chachunk. I'm like, uh-oh, that's not good.
00:00:30.805 --> 00:00:33.945
It sounds like a transformer or something like that.
00:00:34.165 --> 00:00:35.545
Large piece of electrical equipment.
00:00:36.105 --> 00:00:40.465
And I sit there for a second, and I said, okay, I need to pay attention to that.
00:00:40.565 --> 00:00:41.825
Yes, it's late, and I'm tired.
00:00:42.225 --> 00:00:45.165
And I had to have a couple of drinks because we went trick-or-treating,
00:00:45.245 --> 00:00:48.985
and they were giving out jello shots to the adults. I did not plan on that,
00:00:49.025 --> 00:00:50.005
so I'm like, okay, thanks.
00:00:50.325 --> 00:00:52.585
So I'm like, all right, fine. I go to check it. Sure enough,
00:00:53.025 --> 00:00:56.685
we've lost our power. I pull it up on the map, and oh, yeah, we're out, we're out.
00:00:57.005 --> 00:00:59.785
And I announced it to the kids. It's not really easy to tell because all the
00:00:59.785 --> 00:01:00.925
lights are on because we have a battery bank.
00:01:00.925 --> 00:01:01.905
The system just works, right.
00:01:02.185 --> 00:01:05.945
So I announced it to the kids. I'm like, hey, guess what? The power's out. They're like, it is?
00:01:06.345 --> 00:01:09.565
And the kids look around. They look out the window and they see the campground's
00:01:09.565 --> 00:01:13.405
dark. I go, can't we at least turn out the lights? LAUGHTER,
00:01:25.665 --> 00:01:30.345
Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.
00:01:30.585 --> 00:01:31.245
My name is Wes.
00:01:31.385 --> 00:01:32.105
And my name is Brent.
00:01:32.925 --> 00:01:36.645
Hello, gentlemen. Well, coming up on the show this week, we'll tell you what's
00:01:36.645 --> 00:01:41.265
interesting about the new Fedora 43 release and the thing that they're doing
00:01:41.265 --> 00:01:43.705
that we think every Linux distribution should copy.
00:01:43.845 --> 00:01:46.985
Then we'll round it out with some shout-outs, some boosts, some picks, and a lot more.
00:01:47.165 --> 00:01:51.285
So before we go any further, before we get into that show, we have to say time-appropriate
00:01:51.285 --> 00:01:54.185
greetings to our virtual lug. Hello, Mumble Room.
00:01:54.405 --> 00:01:54.765
Hello.
00:01:57.005 --> 00:01:57.885
Hello there.
00:01:58.345 --> 00:01:58.785
Hello.
00:01:59.745 --> 00:02:01.025
It's quite the group.
00:02:01.185 --> 00:02:01.685
It's on fire over there.
00:02:02.365 --> 00:02:05.405
I know. I know there's like some work going on in the background.
00:02:05.605 --> 00:02:06.945
Maybe I'm riding lawnmower. It's unclear.
00:02:07.065 --> 00:02:10.725
Things are happening and I love it. Yeah, our virtual lug gets together every
00:02:10.725 --> 00:02:12.305
Sunday and you're welcome to join us.
00:02:12.605 --> 00:02:16.225
That's at jupiterbroadcasting.com slash mumble. And of course you need the mumble
00:02:16.225 --> 00:02:18.425
app, which is like packaged everywhere.
00:02:18.985 --> 00:02:22.865
So you'll be able to find that. Also a big good morning to our friends over
00:02:22.865 --> 00:02:26.245
at Defined Networking. go check out Nebula.
00:02:26.405 --> 00:02:30.105
Defined.net slash unplugged is where you want to go to support the show and
00:02:30.105 --> 00:02:32.605
meet Managed Nebula from Defined Networking.
00:02:32.725 --> 00:02:37.245
It's a decentralized VPN built on an open source platform that we love called Nebula.
00:02:37.425 --> 00:02:39.285
Top to bottom, you're in complete control.
00:02:39.505 --> 00:02:43.625
They offer a managed product or something that you can completely self-host.
00:02:43.785 --> 00:02:48.185
It's optimized for speed, simplicity, and it uses industry-leading security.
00:02:48.365 --> 00:02:51.365
And Nebula's decentralized design, you know that's something I'm big into.
00:02:51.365 --> 00:02:52.725
It means your network is resilient.
00:02:53.265 --> 00:02:56.505
If you've got a home lab or a global enterprise, it will work for you.
00:02:56.585 --> 00:02:57.865
They developed it for Slack originally.
00:02:58.185 --> 00:03:02.045
Now, of course, it runs many networks. I can't tell you all of them,
00:03:02.145 --> 00:03:05.365
but it still manages all of the Slack infrastructure. They run all of their
00:03:05.365 --> 00:03:07.025
interconnectivity over that.
00:03:07.365 --> 00:03:10.785
Also, every Rivian vehicle going down the road is using Nebula to protect the
00:03:10.785 --> 00:03:11.865
data and the metrics there.
00:03:12.125 --> 00:03:15.345
And, you know, one of the things that can be tricky if you want to self-host
00:03:15.345 --> 00:03:17.605
would be setting up the lighthouse. That's kind of where you start.
00:03:17.785 --> 00:03:19.265
That's where a managed Nebula is really nice.
00:03:20.366 --> 00:03:23.666
There are easier ways to get going with a lighthouse these days,
00:03:23.686 --> 00:03:27.246
and that's the thing that you host that's responsible for keeping track of all
00:03:27.246 --> 00:03:30.306
your Nebula hosts and helping them find each other when they come online.
00:03:30.986 --> 00:03:34.826
And they don't actually transfer data themselves. It's more like node discovery.
00:03:35.146 --> 00:03:38.686
And Wes, one of the things that you and I have been watching is there's more
00:03:38.686 --> 00:03:44.646
public nodes coming online that you can use, and there's now a way to make it
00:03:44.646 --> 00:03:45.786
even easier to get set up.
00:03:46.006 --> 00:03:50.026
Yeah, right. So there's this public Nebula lighthouse service.
00:03:50.026 --> 00:03:53.506
One of the things that's neat is Nebula is so flexible that you can do this.
00:03:53.586 --> 00:03:56.686
So you can have someone run the lighthouse, and with a little automation,
00:03:56.686 --> 00:04:01.166
there's like a Python service that runs here around it, you can make it so you
00:04:01.166 --> 00:04:05.246
can submit your Nebula info to it so it can work as a lighthouse for you.
00:04:05.326 --> 00:04:08.086
There are a couple steps you want to take just for security so that you can
00:04:08.086 --> 00:04:11.946
do this safely, but they have good docs for that that we'll have linked.
00:04:12.266 --> 00:04:18.206
And listener Blumenstrong has taken it upon themselves to start a Nix package
00:04:18.206 --> 00:04:20.186
for that as well. So it's even easier.
00:04:20.346 --> 00:04:24.126
Ha ha. How cool is that? Is that something I should be looking at?
00:04:24.206 --> 00:04:26.066
Well, maybe we should run one. I don't know.
00:04:26.526 --> 00:04:28.846
Oh, a JB Lighthouse.
00:04:28.946 --> 00:04:29.166
Right?
00:04:29.486 --> 00:04:33.226
I'd be down for that. I'd be down for that. Well, thanks, Bloomin' Strong.
00:04:33.366 --> 00:04:36.606
Nice work on that. So go check out Nebula. It's awesome if you want to self-host it yourself.
00:04:36.766 --> 00:04:40.226
Or really, why not start with a managed product? Also could be a great option
00:04:40.226 --> 00:04:41.926
for friends, family, or your enterprise.
00:04:42.186 --> 00:04:45.646
It's a great way to support the show. Defined.net slash unplugged.
00:04:46.106 --> 00:04:48.546
Redefine your VPN experience with something you can actually control.
00:04:48.546 --> 00:04:51.446
Define.net slash unplugged.
00:04:54.246 --> 00:04:58.226
Well, Fedora Linux 43 has been officially cleared for release probably just
00:04:58.226 --> 00:05:01.446
about the time you're listening to this, October 28th.
00:05:01.506 --> 00:05:03.126
That's a Tuesday, 2025.
00:05:03.926 --> 00:05:07.846
And there's a lot to like in here. We weren't sure exactly what would land.
00:05:07.926 --> 00:05:10.906
You know, they kind of have these windows of time and then the team gets together.
00:05:11.046 --> 00:05:12.046
They have a go, no go meeting.
00:05:12.970 --> 00:05:14.470
And then they decide if it's ready or not.
00:05:14.670 --> 00:05:17.710
Yeah, it kind of keeps things interesting this time, anytime there's a release in progress.
00:05:17.950 --> 00:05:21.330
And one of the things they do is they have a blocker bug tracker where you can
00:05:21.330 --> 00:05:24.850
specifically see what's holding up the release. So if you're trying to kind
00:05:24.850 --> 00:05:27.870
of plan when Fedora might land, most of you probably aren't,
00:05:27.950 --> 00:05:32.050
but we do, it's really nice that they just publish a blocker tracker.
00:05:32.510 --> 00:05:34.530
And you can say, oh, okay, oh, this doesn't really apply to me.
00:05:34.590 --> 00:05:35.730
Well, then I'm going to go ahead and install it.
00:05:35.790 --> 00:05:38.450
And true, open source, transparent, yeah, just great.
00:05:38.670 --> 00:05:41.730
Yeah, and that's exactly what we did because the blockers that were there were
00:05:41.730 --> 00:05:45.190
no big deal for us at all. And the rest of the bits looked good.
00:05:46.190 --> 00:05:49.810
And this is the release where we finally get the new web UI installer.
00:05:50.310 --> 00:05:53.770
And Wes, you've kind of been the biggest Anaconda hater on the show.
00:05:54.070 --> 00:05:55.450
Ouch, you just had to say that.
00:05:55.450 --> 00:05:56.550
I just put it out there.
00:05:56.650 --> 00:05:57.090
Yeah, well.
00:05:57.230 --> 00:05:59.490
I mean, I know you warmed up to it a little bit as time went on.
00:06:00.090 --> 00:06:04.610
Yeah, hate's a strong word, but it's never been my favorite of the common installers. That's true.
00:06:04.830 --> 00:06:06.530
Yep, so it's now the default installer.
00:06:06.990 --> 00:06:11.170
It had been in use for Workstation, but it hadn't really rolled out wider. So now this time it is.
00:06:11.310 --> 00:06:14.490
Yeah. Let's start there, Wes. Did you like it?
00:06:14.810 --> 00:06:19.130
Oh, yeah. Actually, I am. I'm definitely a fan of the new web installer approach.
00:06:19.310 --> 00:06:22.090
I'm still kind of getting used to the flavor and the limitations.
00:06:22.090 --> 00:06:24.190
And, you know, I'm giving it early days and all that.
00:06:24.510 --> 00:06:28.570
I did notice as part of that, just kind of poking around while I was getting things installed.
00:06:29.090 --> 00:06:33.290
I wonder if our friend Neil could comment on this. Something called Slitherer.
00:06:34.530 --> 00:06:36.170
Yeah. What is Slitherer?
00:06:36.170 --> 00:06:36.570
Jesus.
00:06:37.210 --> 00:06:37.990
What is that?
00:06:37.990 --> 00:06:47.630
So Slitherer is a alternative, purposeful web engine runner built on QtWebEngine
00:06:47.630 --> 00:06:50.210
to run the Anaconda Web UI.
00:06:50.590 --> 00:06:57.510
And the reason it exists is because the quote-unquote default is to use Firefox,
00:06:57.750 --> 00:06:58.970
and that's what's used on Workstation.
00:06:59.810 --> 00:07:04.630
Almost every other spin experience, whatever...
00:07:05.400 --> 00:07:11.500
And using Firefox causes problems because then it confuses the window manager.
00:07:11.840 --> 00:07:15.800
And if you, for example, preload window rules for like how Anaconda is supposed
00:07:15.800 --> 00:07:20.240
to show up like on a tiling window manager, it will screw up because it will
00:07:20.240 --> 00:07:24.340
also affect Firefox, the web browser, and all these other things.
00:07:24.340 --> 00:07:29.400
So by having a dedicated web runner that has its own name that identifies as Anaconda.
00:07:30.640 --> 00:07:36.420
Things like window management rules or you want to de-confuse the desktop shell
00:07:36.420 --> 00:07:41.280
or whatever these things, if you have things that apply to Firefox,
00:07:41.500 --> 00:07:42.640
they won't apply to Anaconda.
00:07:42.840 --> 00:07:45.600
If you have things that only apply to Anaconda, they won't apply to Firefox.
00:07:45.980 --> 00:07:49.340
It's basically avoiding the – and also it won't cause things like,
00:07:49.400 --> 00:07:50.760
oh, hey, you have mixed up profiles.
00:07:50.760 --> 00:07:54.220
You have settings coming gearing over for one or the other. like weird
00:07:54.220 --> 00:07:59.360
stuff like that doesn't happen either and so slither is basically a very very
00:07:59.360 --> 00:08:07.380
simple wrapper that runs the Anaconda web UI through Qtweb engine and and that's
00:08:07.380 --> 00:08:13.360
that's used just to make it so that we don't have these weird complicated problems,
00:08:14.294 --> 00:08:18.974
result in things like oh hey i can't launch firefox randomly because firefox
00:08:18.974 --> 00:08:22.914
gets confused that anaconda is also running and anaconda is also firefox.
00:08:22.914 --> 00:08:25.534
Yeah well nicely done because i mean i think it's kind
00:08:25.534 --> 00:08:28.774
of the one of the things the flexibility you get and maybe problem you have
00:08:28.774 --> 00:08:32.294
to solve when you make a big switch like this so it's cool to see you know how
00:08:32.294 --> 00:08:35.734
do you actually make this possible to roll out wider and i do think you know
00:08:35.734 --> 00:08:38.814
it's a more direct it's a simpler experience it felt a little faster to me just
00:08:38.814 --> 00:08:42.254
going through the full install to get my system them down and I was trying the
00:08:42.254 --> 00:08:44.694
KDE spin this time around.
00:08:45.034 --> 00:08:45.514
Excellent.
00:08:45.854 --> 00:08:48.754
I also noticed this time when you boot into it, it even has a nice little thing
00:08:48.754 --> 00:08:52.534
that reminds you how much Fedora loves KDE and KDE loves Fedora.
00:08:52.714 --> 00:08:57.234
That's great. Yeah. Also under the hood, the installer switches from DNF4 to
00:08:57.234 --> 00:08:58.634
DNF5 for package management.
00:08:58.894 --> 00:08:59.254
Finally.
00:08:59.574 --> 00:09:00.234
That's pretty fun.
00:09:00.554 --> 00:09:04.574
Not that you'll experience any of that. No, you shouldn't. Because the only
00:09:04.574 --> 00:09:11.674
thing that actually uses that backend is Fedora server install DVD and the net install ISOs.
00:09:12.014 --> 00:09:15.354
Everything else is just, you know, it's an image-based install.
00:09:15.954 --> 00:09:19.494
Yeah. Also, I don't know what the impact of this is, but I read...
00:09:19.494 --> 00:09:21.114
And hey, some of us love a good net install.
00:09:21.254 --> 00:09:24.894
I read in the notes, too, that the RPM package format is actually still version
00:09:24.894 --> 00:09:27.494
4, which is going to be upgraded in the future.
00:09:28.194 --> 00:09:32.314
Yeah, so we have RPM 6, but it's set to the V4 format for backwards compatibility
00:09:32.314 --> 00:09:36.274
because, like, the build system infrastructure is still running older Fedora.
00:09:36.694 --> 00:09:38.954
You know, there's things that are still on RHEL in the infrastructure.
00:09:39.674 --> 00:09:43.834
Like, moving to the V6 format would just break everything right now.
00:09:43.854 --> 00:09:45.314
Yeah, that makes sense. Bite it off as its own thing.
00:09:45.614 --> 00:09:47.514
Yeah, so that's going to happen separately later.
00:09:48.456 --> 00:09:54.076
So let's talk a few details here. We got in Workstation, we have a version of
00:09:54.076 --> 00:09:57.056
GNOME now that is deprecating X11 support.
00:09:57.156 --> 00:10:01.236
So, of course, you'll still have X Wayland, but that's the only way you're going
00:10:01.236 --> 00:10:02.756
to be able to run legacy X applications.
00:10:03.016 --> 00:10:08.196
Other spins in desktop environments still support X11. This is an upstream GNOME change that lands.
00:10:09.236 --> 00:10:10.236
And the future is here.
00:10:10.416 --> 00:10:14.496
I guess so. The Wayland future, I guess, is here, right? I suppose so.
00:10:14.496 --> 00:10:19.016
So I don't have a lot of thoughts on that other than we knew this was coming.
00:10:19.136 --> 00:10:20.116
It was signaled for a while.
00:10:20.416 --> 00:10:26.096
And I think all of my systems have been whaling for years. So it kind of makes sense.
00:10:26.196 --> 00:10:29.716
I mean, there are other options, so I still have some remaining sympathy for
00:10:29.716 --> 00:10:30.876
folks where it doesn't work.
00:10:30.996 --> 00:10:35.336
But it really has progressed to a point of regular usability, which is great.
00:10:35.496 --> 00:10:41.036
I don't often comment on this. But what is striking is the new wallpaper.
00:10:41.036 --> 00:10:43.896
I love it. I really think it's great.
00:10:43.896 --> 00:10:46.656
Yeah, it's one of my favorites in the last few releases, I think.
00:10:46.756 --> 00:10:48.596
I think it's my favorite since the DNA wallpaper.
00:10:48.816 --> 00:10:49.716
Oh, wow.
00:10:49.956 --> 00:10:51.676
I feel like you're a little biased, Chris.
00:10:52.956 --> 00:10:54.396
Oh, yeah? Why is that? Because it's a rocket?
00:10:54.576 --> 00:10:57.876
Yeah, because it's a giant, like, JB rocket, pretty much.
00:10:58.556 --> 00:11:00.536
I think it's fantastic. I love it.
00:11:00.716 --> 00:11:02.756
It is really nice. The backstory is really nice, too.
00:11:03.096 --> 00:11:06.436
Do you have a TLDR version, an elevator version of the backstory?
00:11:06.656 --> 00:11:10.916
Well, it's basically inspired by Sally Ride and Sally Ride's legacy.
00:11:10.916 --> 00:11:12.916
She was the first American woman to go to space.
00:11:13.236 --> 00:11:15.236
I guess that was June 18th, 1983.
00:11:15.916 --> 00:11:20.156
So just a nice little chunk of history there. And I like that idea of doing
00:11:20.156 --> 00:11:22.716
wallpapers based on a little slice of history.
00:11:23.036 --> 00:11:26.276
Let's talk about some nitty gritty stuff, because I always love these kinds
00:11:26.276 --> 00:11:29.896
of like under the hood things. And I bet you were really excited to see this. And I'm not joking.
00:11:30.516 --> 00:11:34.616
Slash boot on a new install is going from one gigabyte to two gigabytes.
00:11:34.976 --> 00:11:36.336
Yeah, it's probably about time.
00:11:36.896 --> 00:11:39.816
If you're just upgrading, of course, that's not going to be the case.
00:11:39.816 --> 00:11:43.716
But yes, how big do you make your slash boot?
00:11:45.975 --> 00:11:49.875
Yep. I mean, at least a gig, probably two. I've gone up to five before.
00:11:49.975 --> 00:11:53.315
Yeah. Five is my max. Two is my minimum. Two is my minimum.
00:11:53.335 --> 00:11:54.855
I like having some excess space.
00:11:55.015 --> 00:11:58.375
Maybe you store like an emergency ISO on there or backups and stuff.
00:11:58.775 --> 00:12:01.035
Brent, do you have a minimum size for your Slash Boot?
00:12:01.495 --> 00:12:06.715
Yeah, I go at least two. I've certainly run into issues on encrypted systems
00:12:06.715 --> 00:12:08.915
where kind of everything gets stored there.
00:12:09.115 --> 00:12:12.595
And definitely Ubuntu is when my parents are using it, let's say.
00:12:12.595 --> 00:12:17.495
It's not great at expunging things in there. So they have way too many kernels and stuff.
00:12:17.615 --> 00:12:22.455
And that has brought down my mother's computer more times than I care to admit.
00:12:22.735 --> 00:12:27.075
So I now have like a task every six-ish months I had to go through and clear
00:12:27.075 --> 00:12:28.775
that because it's a tiny little boot.
00:12:29.495 --> 00:12:35.055
So I say, you know, disk is cheap. Make it as large as, I don't know, just go crazy. Five?
00:12:35.235 --> 00:12:39.015
Yeah, I'd be curious. I'd be curious. I say boost it and tell us how big your slash boot is.
00:12:39.095 --> 00:12:41.375
Why not just run the whole system off your boot, you know?
00:12:41.375 --> 00:12:42.595
Well, and I wondered...
00:12:42.595 --> 00:12:43.655
Fat32 is fine.
00:12:43.795 --> 00:12:48.375
This is crazy. My system was running 6.17.1.
00:12:48.675 --> 00:12:52.135
I believe 6.17.5 is the latest. It came out on October 23rd,
00:12:52.155 --> 00:12:53.815
so pretty fresh kernel in there.
00:12:53.995 --> 00:12:58.735
You get some new hardware feedback interfaces, which I think mostly is going
00:12:58.735 --> 00:13:02.595
to impact Ryzen processors. There's also some improvements for Intel multi-core
00:13:02.595 --> 00:13:05.515
scheduling in there, which could mean smoother multitasking.
00:13:05.875 --> 00:13:09.295
And then I think the one, for those of you that are trying to get higher res
00:13:09.295 --> 00:13:13.495
webcams these days, There's been an update to the IPU 7 driver in Linux 6.17.
00:13:13.835 --> 00:13:15.615
But speaking of...
00:13:16.850 --> 00:13:23.170
The immutable distributions, Fedora KinoNite decided to enable auto-updates by default.
00:13:23.630 --> 00:13:27.630
And this is done via Discover, which supports automatically updating the system
00:13:27.630 --> 00:13:32.930
in a rather safe, you know, RPM OS tree staged update. So it applies at the next boot.
00:13:33.130 --> 00:13:37.010
And, of course, you can roll back if you don't like it or something breaks or
00:13:37.010 --> 00:13:38.370
you can disable it altogether.
00:13:39.090 --> 00:13:42.350
But kind of an aggressive step. Do you have any thoughts on this one,
00:13:42.390 --> 00:13:45.470
Neil, about automatical updates on the KinoNite?
00:13:45.470 --> 00:13:51.930
Well, it's been a long-term goal of Timothy Reviere, who works on Kinoite specifically.
00:13:53.010 --> 00:14:00.170
And I think in general, for these systems, I personally am not a fan of automatic updates.
00:14:00.330 --> 00:14:05.650
I don't like them because I have been burned by them. But with these systems,
00:14:05.650 --> 00:14:11.030