WEBVTT 00:00:11.459 --> 00:00:16.319 Hello friends and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.439 --> 00:00:17.239 My name is Wes. 00:00:17.559 --> 00:00:18.299 And my name is Brent. 00:00:18.459 --> 00:00:22.919 Hello, gentlemen. Well, coming up on the show today, we have had one wild week 00:00:22.919 --> 00:00:26.279 getting to and here at Texas Linux Fest. 00:00:26.419 --> 00:00:29.219 We'll tell you all about that. Then we're gonna round out the show with some 00:00:29.219 --> 00:00:32.319 great shout outs, some picks and a lot more. It's a packed episode. 00:00:32.519 --> 00:00:34.619 We've got a mumble room in listening right now. 00:00:34.859 --> 00:00:37.619 They're just in listening mode, but shout out to them for making it. 00:00:37.659 --> 00:00:43.379 And of course, everyone who tuned in over at jblive.tv as we are streaming live. from Austin Tejas. 00:00:45.279 --> 00:00:46.099 Pretty cool. 00:00:46.299 --> 00:00:48.899 It was a struggle for a few moments, but here we are. 00:00:49.079 --> 00:00:54.019 Also, a big shout out to Define.net slash Unplugged, our friends at Define Networking, 00:00:54.099 --> 00:00:57.659 a decentralized VPN built on the Nebula platform. 00:00:58.079 --> 00:01:01.659 It is really a great platform. It's optimized for speed, simplicity, 00:01:01.979 --> 00:01:02.979 industry-leading security. 00:01:02.979 --> 00:01:07.479 You can completely self-host all of the infrastructure yourself or take advantage 00:01:07.479 --> 00:01:10.799 of their excellent managed product at Define.net slash Unplugged. 00:01:10.799 --> 00:01:14.619 you go there, you can get 100 hosts absolutely free, no credit card required. 00:01:14.779 --> 00:01:18.659 I think I'm pretty stoked about Nebula because I must have talked to half a 00:01:18.659 --> 00:01:21.739 dozen people that were building things on top of Nebula. 00:01:22.319 --> 00:01:25.459 Listener TechDev told me about a really interesting platform he's been working 00:01:25.459 --> 00:01:26.779 on that's very close possibly. 00:01:26.899 --> 00:01:29.259 I don't want to say too much out of respect to our conversation, 00:01:29.439 --> 00:01:35.239 but it's people are building things on top of Nebula that is just extremely exciting. 00:01:35.379 --> 00:01:39.759 And Nebula has been built from the very beginning to be industrial grade. 00:01:39.939 --> 00:01:45.999 It was built to manage Slack's global empire of servers all around the world. 00:01:46.179 --> 00:01:50.359 But something that I don't know if most people know listening to this show is 00:01:50.359 --> 00:01:55.299 every Rivian vehicle on the road is using Nebula on the go. 00:01:55.559 --> 00:02:00.779 I mean, Nebula is in places you don't even realize just to make networking happen 00:02:00.779 --> 00:02:05.379 in a secure way that is reliable and low-impact on the host system. 00:02:05.679 --> 00:02:10.379 Nothing else offers Nebula's level of resilience, speed, and scalability. 00:02:10.579 --> 00:02:14.559 Go try it out. 100 hosts, absolutely free, no credit card required, 00:02:14.719 --> 00:02:18.279 at defined.net slash unplugged. 00:02:18.399 --> 00:02:20.839 Support the show at defined.net slash unplugged. 00:02:22.859 --> 00:02:25.719 Well, we don't have a lot of housekeeping since we are now down here in Texas 00:02:25.719 --> 00:02:28.919 LinuxFest. We will be returning home and we'll have more about that. 00:02:29.459 --> 00:02:32.599 The Texas tracker is still live for our return trip. 00:02:33.739 --> 00:02:36.579 And we still will also have the fake boost if you'd like to help us with the 00:02:36.579 --> 00:02:38.459 return effort on gas and food. 00:02:39.199 --> 00:02:43.699 And kind of along those lines, we got a note from the Darowich, 00:02:43.739 --> 00:02:45.179 or as we like to say, the Big D developer. 00:02:45.759 --> 00:02:49.579 Brent Lee, tell us about the note we got from the author of the very software 00:02:49.579 --> 00:02:50.719 we use to track our journey. 00:02:50.719 --> 00:02:53.839 Yeah, this is so sweet. Very, very, very cool for us to see. 00:02:54.099 --> 00:02:56.799 Here's the message. Hi, my name is Evgeny. 00:02:58.059 --> 00:03:02.719 Sorry, I got that wrong. Hi, my name is Evgeny, and I'm the Dvaric author. 00:03:02.979 --> 00:03:06.219 Love what you did with the Dvaric API. Awesome job. 00:03:06.859 --> 00:03:11.419 FYI, family location sharing is coming soon, although it might not be applicable 00:03:11.419 --> 00:03:15.379 to your use case, which admittedly is a very strange use case, 00:03:15.559 --> 00:03:21.179 where everyone has their own devarage instance but still i thought you might be interested cheers. 00:03:21.779 --> 00:03:24.619 I'm very interested in family service yeah i'm very interested in that. 00:03:24.619 --> 00:03:28.419 And also props to the great api i mean it was a super useful tool it was really 00:03:28.419 --> 00:03:29.719 easy to get the api key and start 00:03:29.719 --> 00:03:32.859 pulling down the data so you know it was kind of a great thing for us. 00:03:32.859 --> 00:03:37.659 Too it made for the perfect tracker for this use case it didn't didn't require 00:03:37.659 --> 00:03:41.699 a big lift on our end we just ran low-end simple clients on our mobile devices 00:03:41.699 --> 00:03:46.219 and it was so thank you so much for writing into it was really great to hear 00:03:46.219 --> 00:03:47.999 from you and for building such a cool project. 00:03:48.799 --> 00:03:53.199 So having that live tracker was really fun. I mean, it was fun for us. 00:03:53.299 --> 00:03:55.159 We heard from people at Texas Linux Fest. They enjoyed it. 00:03:55.559 --> 00:04:01.959 But it really put us into the zone, in the headspace of, oh, we are in a race here. 00:04:01.979 --> 00:04:03.139 What? We were racing? 00:04:04.259 --> 00:04:08.159 Yeah. Well, yeah, because, you know, when we recorded last week, 00:04:08.739 --> 00:04:13.119 Chris and I, we were still at home. But Brent, you and your cats, a.k.a. 00:04:13.299 --> 00:04:17.939 Team Moose, Cosmo, Emmett, and Brent, well, you were already on the road, 00:04:17.959 --> 00:04:20.419 and you'd actually made pretty significant progress. 00:04:20.739 --> 00:04:26.379 And our team, Team Bigfoot, we hadn't even started. I mean, I wasn't even fully packed yet. 00:04:26.839 --> 00:04:31.379 I mean, we got on the road. I woke up. I did one last load of laundry. I met Chris in Olympia. 00:04:31.919 --> 00:04:35.639 And that was mid-morning on Monday, so we were already feeling the heat. 00:04:36.159 --> 00:04:40.739 After almost eight hours of driving right on the nose, we have stopped for our 00:04:40.739 --> 00:04:46.399 first meal of the day in Pendleton, Oregon, and we're just trying to debate how far we want to get. 00:04:47.139 --> 00:04:51.299 We're kind of thinking Boise now, but we'd like to put the fear into Brent. 00:04:51.679 --> 00:04:55.179 Yeah, we were thinking maybe as far into Utah as we could possibly get. 00:04:55.499 --> 00:04:58.319 But then we remembered we actually do have to sleep. Yeah. 00:04:58.719 --> 00:05:01.139 Yeah, we don't want to kill ourselves before we get there, so... 00:05:01.943 --> 00:05:06.183 Probably Boise. We'll see. It's just the desire to put the fear into Brent is strong. 00:05:06.483 --> 00:05:10.483 The motivation, even on the first day, because, you know, you set the tone, 00:05:10.643 --> 00:05:15.483 Brent, with that almost 600-mile journey you did on your first day. 00:05:15.963 --> 00:05:16.763 Oh, yeah. 00:05:16.863 --> 00:05:21.543 And we're like, so not only are we two days behind, we have an additional 600 00:05:21.543 --> 00:05:26.063 miles on Brent that we have to travel, and he's gotten this incredible head start. 00:05:26.483 --> 00:05:31.883 So it was hard, but we did stop for the night in the Idaho area and rested. 00:05:32.423 --> 00:05:35.723 But it was one of those, you know, hit your head on the pillow and then wake 00:05:35.723 --> 00:05:37.423 up in the morning and get right back on the road. 00:05:37.583 --> 00:05:42.823 Because the entire time, we know Brent has a key tactical advantage over us. 00:05:42.983 --> 00:05:45.323 And that is, once you get tired. 00:05:45.483 --> 00:05:47.163 I just sleep wherever I want to, really. 00:05:47.423 --> 00:05:50.463 You pull over, you cuddle up with the kitties, and there you go. 00:05:50.563 --> 00:05:53.503 Rest stop, middle of a parking lot somewhere. 00:05:53.503 --> 00:05:57.223 And then additionally, like when you want to leave, you don't have to pack anything up. 00:05:57.303 --> 00:05:59.583 I mean, like you may maybe have some things out, but like you don't have to 00:05:59.583 --> 00:06:03.003 like get your luggage and get that back down into the car and check out. 00:06:03.463 --> 00:06:08.403 Like you just tidy up and start the engine and drive and you're generally pretty close to the highway. 00:06:08.583 --> 00:06:09.643 I don't have to talk to anybody. 00:06:09.883 --> 00:06:09.963 Right. 00:06:10.083 --> 00:06:12.383 Well, that does mean his engine has to start, but that's a separate matter. 00:06:12.383 --> 00:06:16.343 That's a separate issue. But for Wes and I, it meant at some point we had to 00:06:16.343 --> 00:06:17.943 decide, are we going to keep going or not? 00:06:18.243 --> 00:06:21.383 Okay. If we're not, where are we going to stop? Can we find a place? 00:06:21.463 --> 00:06:24.383 Can we book it? Is it too expensive? because we're trying to do this on a shoestring budget. 00:06:24.983 --> 00:06:28.583 And then it's generally off the beaten path a bit to get there. 00:06:28.623 --> 00:06:30.823 So you're killing 20 minutes driving there. 00:06:31.023 --> 00:06:31.983 I didn't consider that. 00:06:32.043 --> 00:06:34.103 Yeah, we weren't staying in downtown Boise, right? 00:06:34.403 --> 00:06:35.883 Right, right, because we're going for budget. 00:06:36.223 --> 00:06:39.083 Yeah, I was like always 100 feet off of my route. 00:06:39.223 --> 00:06:42.943 So that was something we had to constantly do the math on and try to decide 00:06:42.943 --> 00:06:44.763 if it was worth it to stop or not. But we did. 00:06:44.923 --> 00:06:48.223 We took it easy the first night. Day two, we made some progress. 00:06:48.983 --> 00:06:54.243 It's day two. We just stopped for lunch in the fairly cute town of Helper, 00:06:54.383 --> 00:06:57.043 Utah, taking a little stroll by the water. 00:06:57.243 --> 00:07:00.383 Yeah, they've got a nice little park. They've got an old train on display. 00:07:01.536 --> 00:07:05.296 What do you think, though? Like, are we having some of the worst driving luck 00:07:05.296 --> 00:07:09.496 just with the storms? We seem to be chasing. 00:07:10.096 --> 00:07:12.456 We're storm chasers on this trip. We're chasing the storm. 00:07:13.296 --> 00:07:16.676 Yeah, I mean, I think we've seen more lightning just in the past two days than 00:07:16.676 --> 00:07:19.216 I've seen in, like, the past year to date. 00:07:20.096 --> 00:07:23.416 And it's been mostly just sloppy, wet driving. 00:07:23.996 --> 00:07:27.756 Oh, man. It's like one half of the car is in a creek, you know. 00:07:28.076 --> 00:07:31.416 And then, like, only one half of the car actually has traction on the ground. 00:07:31.536 --> 00:07:34.176 So it was another reason we got off and decided to stop here. 00:07:34.576 --> 00:07:37.416 But now the storm approaches because we got ahead of it sufficiently, 00:07:37.416 --> 00:07:39.996 but now it's catching up again, so we can't stop for too long. 00:07:40.276 --> 00:07:44.276 Plus, we don't want the moose to get that far ahead. He's on the road right now. 00:07:44.576 --> 00:07:47.436 Yeah, we're always checking the tracker. When we stop for lunch, 00:07:47.456 --> 00:07:49.256 we're checking the tracker, and you can hear in the background, 00:07:49.436 --> 00:07:51.916 the storm was catching up to us. 00:07:52.096 --> 00:07:55.976 So day two for us was day four for Brent. 00:07:56.076 --> 00:07:57.196 I hate that still. 00:07:57.396 --> 00:08:00.836 So day two for you, because I couldn't keep track of where you guys. 00:08:00.836 --> 00:08:01.316 Were during. 00:08:01.316 --> 00:08:03.296 All this so was that monday or was that tuesday. 00:08:03.296 --> 00:08:07.396 That would have been tuesday wow yeah okay all right and so you you know at 00:08:07.396 --> 00:08:09.916 this point you're doing pretty good not that you didn't do great but you're 00:08:09.916 --> 00:08:13.076 doing pretty good and it's day four and it kicks off for brent he's outside 00:08:13.076 --> 00:08:18.616 of a hilton um with maybe a little extra time on his hands ah. 00:08:18.616 --> 00:08:25.136 Well just as i was getting the top cover off of the generator i got that old 00:08:25.136 --> 00:08:30.816 knock uh i guess they weren't too happy with a post-apocalyptic elliptic looking 00:08:30.816 --> 00:08:32.396 van parked at the Hilton. 00:08:34.635 --> 00:08:42.015 but that's okay so i packed up through the sneaky solar panel back in the van, 00:08:43.035 --> 00:08:50.655 and uh i guess we're just gonna drive for a bit there's no there's like no shade 00:08:50.655 --> 00:08:58.335 around here just i'm dying so chris and wes i damn you. 00:08:58.335 --> 00:09:02.235 Tuesday was not a good first day or good start of the day for rent. 00:09:02.235 --> 00:09:05.555 Like in that moment i realized i 00:09:05.555 --> 00:09:08.375 chose a vehicle to drive to texas that didn't have 00:09:08.375 --> 00:09:12.215 any functioning air conditioning while going down the road you were very generous 00:09:12.215 --> 00:09:16.035 to say hey brent um hey you do have like an air conditioner on there i know 00:09:16.035 --> 00:09:20.535 it runs like off ac power but you also have a generator yeah the generator you 00:09:20.535 --> 00:09:23.575 know you haven't spent any time trying to fix it and making sure it works before 00:09:23.575 --> 00:09:26.615 the trip but maybe you could at this point yeah you. 00:09:26.615 --> 00:09:27.795 Were at a good spot but you got the knock. 00:09:27.795 --> 00:09:33.335 Oh man i thought it was perfect because it was like 11 a.m something like that. 00:09:33.335 --> 00:09:34.175 And i had slept. 00:09:34.175 --> 00:09:35.535 There overnight and nobody knocked. 00:09:35.535 --> 00:09:38.715 You're actually you're lucky you made it that far you're lucky you made it to 11 a.m. 00:09:38.715 --> 00:09:41.615 To tell you the truth that's a very good point but when i parked there overnight 00:09:41.615 --> 00:09:46.595 it was the parking lot was filled with rvs and campers like a bunch of cars and stuff but, 00:09:47.055 --> 00:09:50.315 i might have slept in a little because i had this yeah you were real lead on 00:09:50.315 --> 00:09:55.055 the race and when i woke up i was one of two cars in the whole parking lot so 00:09:55.055 --> 00:09:56.215 i don't think that was good for me Yeah. 00:09:56.355 --> 00:09:57.035 You lost your cover. 00:09:57.315 --> 00:10:01.095 I mean, I don't think it would have been so bad if that was the worst that Tuesday 00:10:01.095 --> 00:10:04.215 got for you, but it actually got worse. 00:10:04.335 --> 00:10:04.755 That's true. 00:10:20.889 --> 00:10:22.169 So what are we hearing here. 00:10:22.169 --> 00:10:25.409 Well this is me driving on 00:10:25.409 --> 00:10:28.469 the interstate for about the last 40 seconds 00:10:28.469 --> 00:10:31.509 and something breaking on the van as 00:10:31.509 --> 00:10:34.649 i just accelerate to try to get on the interstate and make some miles finally 00:10:34.649 --> 00:10:40.089 and i realize something's very wrong and that is the sound of something being 00:10:40.089 --> 00:10:43.969 caught in the cooling fan and it's just whipping around hitting everything in 00:10:43.969 --> 00:10:48.889 the engine bay and causing havoc and i realized something's very wrong this 00:10:48.889 --> 00:10:50.509 is the very first van breakdown. 00:10:50.509 --> 00:10:52.569 Oh man we. 00:10:52.569 --> 00:10:53.549 Knew it would happen. 00:10:53.549 --> 00:10:54.569 Well but we didn't. 00:10:54.569 --> 00:10:55.729 Know where or when. 00:10:55.729 --> 00:10:59.249 We didn't want it to happen no we didn't we didn't want it to. 00:10:59.249 --> 00:11:00.409 Happen sure sure sure we. 00:11:00.409 --> 00:11:03.709 Knew it would help us we knew it would help us in the race but we weren't sure 00:11:03.709 --> 00:11:06.149 uh how bad it was and brett you got right to work. 00:11:06.149 --> 00:11:08.369 Well i knew the van would break at some point. 00:11:08.369 --> 00:11:09.169 So you got. 00:11:09.169 --> 00:11:12.269 I brought some tools you brought your tools i brought coveralls i 00:11:12.269 --> 00:11:15.149 brought i don't know a sense of i can fix it 00:11:15.149 --> 00:11:17.849 i got really lucky though 00:11:17.849 --> 00:11:21.609 because i was at a rest stop and i took my time uh and 00:11:21.609 --> 00:11:24.529 i thought okay i gotta get back on the road and i you know 00:11:24.529 --> 00:11:28.369 looked at one of my belts and it 00:11:28.369 --> 00:11:31.249 seemed like it was a little looser than when i started this trip and 00:11:31.249 --> 00:11:33.969 i was like ah maybe on the next rest stop i'll have a look and maybe i can 00:11:33.969 --> 00:11:37.089 do something about it and so i got just on the freeway as i was accelerating 00:11:37.089 --> 00:11:41.749 boom that sound started happening i was like oh i made the wrong decision here 00:11:41.749 --> 00:11:45.929 and uh i was super lucky because there was an off-ramp right there oh it could 00:11:45.929 --> 00:11:49.609 have been miles of trying to drive or having to stop on the side of the interstate 00:11:49.609 --> 00:11:51.389 which is never what you want to be and you. 00:11:51.389 --> 00:11:52.989 Weren't even sure what the extent of the damage was. 00:11:52.989 --> 00:11:54.389 No not at all could be breaking. 00:11:54.389 --> 00:11:55.969 Things in there the alternator could be gone. 00:11:55.969 --> 00:11:59.449 Your fan could get cracked i knew at least i still had steering, 00:12:00.656 --> 00:12:03.456 and brakes which i guess is all i need to get off the road 00:12:03.456 --> 00:12:06.276 but i was very lucky because i was able to take this off 00:12:06.276 --> 00:12:11.536 ramp and judged like i could drive a couple more hundred feet and i was able 00:12:11.536 --> 00:12:17.016 to stop at a fuel station that also just happened to have like a big truck garage 00:12:17.016 --> 00:12:21.056 tied to it so i thought okay i can i can park here and try to fix it myself 00:12:21.056 --> 00:12:24.576 if it's really bad i can try to you know, 00:12:25.076 --> 00:12:27.676 guilt these guys into helping me basically help. 00:12:27.676 --> 00:12:28.436 A guy out please. 00:12:28.436 --> 00:12:30.356 That was just an old van But. 00:12:30.356 --> 00:12:32.176 You pop the hood, you got to work. 00:12:34.216 --> 00:12:37.796 Okay. Everything seems okay. 00:12:38.096 --> 00:12:46.776 I'm just tightening the alternator into place, getting the belts tight. 00:12:49.676 --> 00:13:00.976 And then we'll see if it runs okay. Okay, the AC fan, the AC belt did run around 00:13:00.976 --> 00:13:04.076 the fan as a backup belt or a secondary belt. 00:13:04.776 --> 00:13:12.956 If that's missing, then only the power steering belt goes around the cooling fan. 00:13:13.236 --> 00:13:17.316 I do not want the cooling fan to stop working. That would be very, 00:13:17.316 --> 00:13:19.836 very bad for a Texas trip. 00:13:20.616 --> 00:13:22.076 So we'll see how it goes. 00:13:23.056 --> 00:13:26.036 Roadside repair brent and you 00:13:26.036 --> 00:13:30.116 know he did it he got it fixed and he tried to give her the first start. 00:13:30.116 --> 00:13:36.196 Okay here we go i'm gonna start the van for the first time since pulling over, 00:13:42.036 --> 00:13:51.456 oh doesn't want to start oh it's in second gear there we go put in park Sounds okay. Will it start? 00:13:53.416 --> 00:13:54.516 Oh, come on. 00:13:56.656 --> 00:13:58.216 Oh, there we go. 00:14:00.584 --> 00:14:07.124 And it sounds good in here. No more slapping around of belts and such. 00:14:07.884 --> 00:14:09.964 Okay. Okay. 00:14:11.704 --> 00:14:14.844 I think we can carry on. I'm hungry. 00:14:16.644 --> 00:14:19.304 That was a big win. Big win for you. 00:14:19.444 --> 00:14:24.244 I was really lucky because what ended up happening was one of the belts definitely snapped. 00:14:24.784 --> 00:14:28.144 And I tried before going on the strip to replace them all, and the mechanic 00:14:28.144 --> 00:14:28.904 just couldn't find them. 00:14:29.284 --> 00:14:29.504 Wow. 00:14:30.324 --> 00:14:33.704 Huh so of course one of them has to break and 00:14:33.704 --> 00:14:36.424 it ended up being the air conditioning belt which as you know 00:14:36.424 --> 00:14:39.484 the van has no it has no working air conditioning which 00:14:39.484 --> 00:14:42.204 uh makes me suffer uh so it 00:14:42.204 --> 00:14:45.104 wasn't working anyways you may as well just delete on that yeah and uh 00:14:45.104 --> 00:14:48.064 but when it snapped it took out one of the alternator belts too 00:14:48.064 --> 00:14:51.524 and so i had to kind of learn how 00:14:51.524 --> 00:14:54.744 to put that back on i'd never done that before um but 00:14:54.744 --> 00:14:57.424 it only took me about 90 minutes so i was feeling good i was like 00:14:57.424 --> 00:15:00.504 okay first breakdown yep so i get that out of the way because i knew it was 00:15:00.504 --> 00:15:04.124 gonna happen at some point and it only took me 90 minutes that is impressive 00:15:04.124 --> 00:15:08.204 i was hungry at that point but there was this little roadside stop and they 00:15:08.204 --> 00:15:13.124 had fries and they had 32 ounces of sweet tea for really super cheap so i figured 00:15:13.124 --> 00:15:15.084 well i needed a break anyway and. 00:15:15.084 --> 00:15:18.044 Then you hit the road with some gusto and i have 00:15:18.044 --> 00:15:21.284 to say as your luck improved our luck 00:15:21.284 --> 00:15:26.524 took a turn for the worse and we were you know driving for i don't know at this 00:15:26.524 --> 00:15:30.764 point 13 hours trying to find some place to stop we finally booked an airbnb 00:15:30.764 --> 00:15:36.424 that would let us in that night only to arrive open the open the door and discover 00:15:36.424 --> 00:15:39.784 someone had stolen it right out from underneath us it's. 00:15:39.784 --> 00:15:45.444 The second night and we've arrived at an airbnb but something's a bit off and 00:15:45.444 --> 00:15:53.464 we don't really know if if it's okay we walked in and somebody else's luggage and bags are here. 00:15:53.564 --> 00:15:56.084 The bedroom's got luggage in it. There's bags in the living room. 00:15:57.305 --> 00:15:59.825 But there doesn't seem to be anybody else here? No, totally empty. 00:16:00.205 --> 00:16:03.485 I mean, not a ton of lights on or anything. No one else parked here. 00:16:04.585 --> 00:16:08.825 And, you know, the code we got through the app, I mean, it worked. We opened the door. 00:16:09.665 --> 00:16:12.025 And I've messaged the host, but I haven't heard anything yet. 00:16:12.045 --> 00:16:13.485 I'm not sure if we can stay here tonight. 00:16:13.725 --> 00:16:17.725 But, you know, we spent a good, we got a good amount of miles in today. 00:16:17.845 --> 00:16:19.725 It wasn't our biggest day, but it was a good day. 00:16:19.945 --> 00:16:23.025 So this is a good time to stop, if we can. 00:16:23.605 --> 00:16:27.225 So we're in New Mexico, and we're kind of in the outskirts of New Mexico. 00:16:27.305 --> 00:16:30.365 So there's like five options to pick from to begin with. 00:16:30.865 --> 00:16:35.505 And what we discover is that somebody else had shown up, quickly dropped off 00:16:35.505 --> 00:16:39.865 all their stuff, took a shower, and then they headed out for the evening or something like that. 00:16:39.945 --> 00:16:44.805 And then we show up a half hour later and they've showered and the place has been taken over. 00:16:45.365 --> 00:16:50.005 And we're exhausted and it's dark and there's like no lights in this area of New Mexico at all. 00:16:50.085 --> 00:16:51.685 No street lights, no signs. 00:16:52.065 --> 00:16:57.085 The roads are horrible, horrible, horrible roads. and we're trying to communicate 00:16:57.085 --> 00:16:59.605 with this Airbnb owner on what the F we can do. 00:16:59.785 --> 00:17:03.025 I mean, we have nowhere to go. There's pretty much no other options to stay 00:17:03.025 --> 00:17:05.405 and we're looking at the next town would be like Albuquerque, 00:17:05.625 --> 00:17:08.725 which was hours away at that point and we were tired. 00:17:09.285 --> 00:17:11.025 Meanwhile, you're having a great time. 00:17:11.165 --> 00:17:11.405 Oh, yeah. 00:17:15.905 --> 00:17:21.905 Well, it is end of day four, 125 a.m. 00:17:23.625 --> 00:17:26.365 I think it did okay. today it was 00:17:26.365 --> 00:17:31.985 an adventurous day oh the belt's coming off and everything actually with the 00:17:31.985 --> 00:17:40.045 belt off the van sounds really nice i have to say it sounds smoother ride smoother 00:17:40.045 --> 00:17:45.805 i might have a little bit more power although i might just be imagining that, 00:17:47.945 --> 00:17:56.085 i got a little tired of sleeping in the van near other people so i went off 00:17:56.085 --> 00:18:03.325 a small side road off the interstate and found this sweet boondocking spot chris 00:18:03.325 --> 00:18:04.005 you're going to be jealous, 00:18:05.325 --> 00:18:06.625 as you can hear, 00:18:09.925 --> 00:18:13.345 it's like in the middle of the wilderness on 00:18:13.345 --> 00:18:21.725 the tiny little side road and there's perfect so a nice reward for the end of 00:18:21.725 --> 00:18:31.105 a good day I hope tomorrow is a little less exciting the van's doing great other 00:18:31.105 --> 00:18:32.305 than losing a little bit of rubber, 00:18:35.871 --> 00:18:38.191 well adventure continues yeah. 00:18:38.191 --> 00:18:43.251 And meanwhile we were back on the road but now we were headed in the wrong direction. 00:18:43.251 --> 00:18:46.211 And back on the road again we go they don't 00:18:46.211 --> 00:18:49.471 know who is here they've got another airbnb 00:18:49.471 --> 00:18:54.471 further away more out of our way further away from country further away from 00:18:54.471 --> 00:18:59.511 austin that we can go to for the night we've been given the um the name kevin 00:18:59.511 --> 00:19:04.091 and a phone number in case Because we have to go onto a ranch where we're going 00:19:04.091 --> 00:19:07.071 to get lost because it's pitch black out and dark. 00:19:07.671 --> 00:19:11.791 And we're going to find Kevin and his Airbnb, and we're going to try to stay 00:19:11.791 --> 00:19:15.291 in there. And hopefully that doesn't have somebody's luggage in it. Jeez. 00:19:17.691 --> 00:19:23.871 The darkness, I cannot describe the darkness in this place. And so the owner gives us a tip. 00:19:25.051 --> 00:19:28.491 When you route, don't use Google Maps. Use Apple Maps. 00:19:28.491 --> 00:19:31.631 Yeah, it's going to take you all the long way through the ranch. 00:19:31.851 --> 00:19:36.111 Through the ranch. So Apple Maps did get us to the driveway, 00:19:36.151 --> 00:19:40.091 but the driveway we drove past twice because it was so dark and you couldn't see it. 00:19:40.271 --> 00:19:42.691 And then once we pulled down, and I have pretty bright headlights, 00:19:42.791 --> 00:19:45.451 and once you pull down, we were off-roading. 00:19:45.591 --> 00:19:48.911 We were in Jeep territory or like raised truck territory. 00:19:49.071 --> 00:19:50.311 I don't think your car was meant for that. 00:19:50.311 --> 00:19:50.431 No. 00:19:50.591 --> 00:19:51.871 Yeah, think Forest Service road. 00:19:51.991 --> 00:19:56.451 And so we were bump, bump, bump, and we're going through washouts. And I'm not kidding. 00:19:56.871 --> 00:20:02.231 I'm driving up along the side of a washout, so we're at an angle because I'm driving around. 00:20:02.371 --> 00:20:05.811 I think that was the one we were like, do we just abandon this? 00:20:05.871 --> 00:20:07.211 We were asking, should we just turn around? 00:20:07.491 --> 00:20:08.491 But you've got a bed in the back. 00:20:08.951 --> 00:20:12.931 No, no. We finally roll up, and the owner, the guy that owns the Airbnb, 00:20:13.011 --> 00:20:16.391 he's got a big smile on his face. And he says, guys, I'm so sorry. 00:20:16.911 --> 00:20:21.471 I sent you to the wrong address. You need to go somewhere else on the ranch. 00:20:22.071 --> 00:20:24.351 Yeah, he sent us his address. 00:20:24.571 --> 00:20:28.131 His home address. Not the Airbnb address If. 00:20:28.131 --> 00:20:34.051 I hadn't just experienced this story I don't know if I would believe it So six, 00:20:34.171 --> 00:20:37.671 seven miles down the road Most of it out of the direction we actually need to go, 00:20:38.691 --> 00:20:41.711 We get to the ranch, which is almost impossible to see in the dark, 00:20:41.731 --> 00:20:43.491 so we had to turn around twice to even pull into the ranch. 00:20:44.151 --> 00:20:47.291 And the address they gave us was to the wrong house on the ranch. 00:20:47.691 --> 00:20:48.931 It was the guy that owns the ranch. 00:20:49.511 --> 00:20:53.531 So then we went up to talk to him for a bit and then turned around and very 00:20:53.531 --> 00:20:57.771 slowly crawled down the road because not only is it not paved, 00:20:59.991 --> 00:21:04.591 it's significantly not paved, right? It's pretty sizable potholes. 00:21:04.711 --> 00:21:06.251 What do you think of the Airbnb? It's okay, right? 00:21:06.491 --> 00:21:08.631 Yeah. It's a little musty, but it's all right. It's a little musty. 00:21:08.691 --> 00:21:12.351 The floors are a little soft, but there's a TV, there's a fridge, 00:21:12.431 --> 00:21:13.691 there's definitely two beds, I think. 00:21:13.811 --> 00:21:16.231 Okay, good. So we will make it work. 00:21:17.971 --> 00:21:23.191 Honestly, the mood was a bit low because we were still way, way behind, 00:21:23.191 --> 00:21:29.971 and we'd had now gone off course, and Brent, which really killed us, was on the move. 00:21:30.091 --> 00:21:33.931 As we're going the wrong direction, as we're finding this Airbnb on the ranch, 00:21:34.751 --> 00:21:39.371 Brent was making really good progress after he had stacked his W fix in his bells. 00:21:40.091 --> 00:21:42.791 And Wes and I had to do some hard math. 00:21:43.171 --> 00:21:46.051 So we're looking at the maps now that we've settled into our Airbnb. 00:21:47.431 --> 00:21:50.451 And to get to Austin, I just saw a shooting star. 00:21:51.071 --> 00:21:54.351 To get to Austin by, say, 4.30 p.m. 00:21:54.471 --> 00:21:59.231 tomorrow, which I think would beat Brent, we would have to leave our Airbnb at 1.30 a.m. 00:21:59.491 --> 00:22:01.851 in the morning. It's 9 p.m.-ish right now. 00:22:03.011 --> 00:22:07.031 well then what are we doing recording we should be in bed yeah we this is well 00:22:07.031 --> 00:22:12.451 this is the thing is do we want to get up at 1 a.m and beat him and show up 00:22:12.451 --> 00:22:14.391 a day early with no place to stay, 00:22:14.931 --> 00:22:21.711 or do we let our buddy win and we sleep in i just i'm torn so uh as as we check the tracker right now, 00:22:22.571 --> 00:22:26.271 he's about a solid day of driving tomorrow and he'll be in austin he's making 00:22:26.271 --> 00:22:31.511 really good time today we made really good time today too we put down almost 00:22:31.511 --> 00:22:37.451 800 miles more than 800 miles yesterday we put down over 600 miles today 10 00:22:37.451 --> 00:22:40.591 hours of driving today 14 hours of driving yesterday, 00:22:41.471 --> 00:22:45.311 uh and now we just have to decide if we if we want to kill ourselves and show 00:22:45.311 --> 00:22:51.071 up exhausted in but winners which would be invigorating or we could tell them 00:22:51.071 --> 00:22:52.991 just to meet us at terry blacks Yeah. 00:22:53.571 --> 00:22:56.691 Hey, are you here yet, Brent? Are you here yet? We have a table. 00:22:59.406 --> 00:22:59.826 Satisfying. 00:23:02.426 --> 00:23:07.466 But I didn't sleep last night. And I feel like it would be pretty dumb to get 00:23:07.466 --> 00:23:11.246 only like three or four hours of sleep tonight after not sleeping and driving so much. 00:23:11.846 --> 00:23:14.266 You don't want this Texas Linux Fest to be your last. 00:23:16.126 --> 00:23:18.286 I still haven't made it in my mind yet. I don't know what we're going to do. 00:23:18.726 --> 00:23:22.666 So we knew that in order for us to win this thing, our buddy Brent was probably 00:23:22.666 --> 00:23:25.606 going to need to suffer a breakdown. And we didn't want to wish that on him. 00:23:26.006 --> 00:23:31.046 And we're racking our brains. I mean, we were big-picture ideating, 00:23:31.066 --> 00:23:33.106 as they say, using our imaginary. 00:23:33.806 --> 00:23:37.626 Like, we thought, could we contact a listener that could go track Brent down 00:23:37.626 --> 00:23:38.926 and distract him for a while? 00:23:38.926 --> 00:23:40.566 That worked a couple days earlier. 00:23:40.646 --> 00:23:45.486 We thought, could we, like, sick PJ on Brent for a bit, and maybe PJ could distract Brent for a while? 00:23:45.546 --> 00:23:46.026 Come on, guys. 00:23:46.166 --> 00:23:46.886 Yeah, I know, right? 00:23:47.006 --> 00:23:48.666 There's a lot of solar stuff to talk about. 00:23:48.726 --> 00:23:52.866 Wes, you were sending me a strange number of delicious restaurants in Memphis. 00:23:52.866 --> 00:23:55.046 I wanted you to have a good foodie journey. 00:23:55.046 --> 00:23:58.106 We just knew, like, okay, so we thought, okay, well, we don't want him to break 00:23:58.106 --> 00:24:00.006 down, but we would like to beat him. 00:24:00.086 --> 00:24:04.906 And there's just physically no way we can do it unless we can get you properly distracted. 00:24:05.906 --> 00:24:06.966 How dare you? 00:24:07.766 --> 00:24:12.426 So we sent you a message the next morning suggesting, since you had such a brilliant 00:24:12.426 --> 00:24:16.046 lead, that perhaps it was a good time to invest in a little bit of generator repair. 00:24:16.146 --> 00:24:18.786 Well, and we did. You know, we were concerned about his poor kiddies, too. 00:24:19.826 --> 00:24:25.526 So brent on what would be day five for him i guess that would be wednesday morning for us you. 00:24:25.526 --> 00:24:27.686 Guys were in new mexico i was in arkansas. 00:24:27.686 --> 00:24:31.846 Yeah yeah we're in new mexico sweet boondocking spot you did it was it actually 00:24:31.846 --> 00:24:33.446 was a really great spot really good yeah. 00:24:34.426 --> 00:24:40.546 I woke up in my little boondocking spot here in hot springs arkansas, 00:24:42.600 --> 00:24:46.100 I did better than I even thought last night. This spot is great. 00:24:46.320 --> 00:24:47.780 I parked under the shade of a tree. 00:24:48.380 --> 00:24:54.260 It is beautiful as a river with fish. Just like, I don't know, 100 meters that way. 00:24:55.020 --> 00:24:59.180 I got the solar panel out. Getting a little bit of solar charging going. 00:25:02.000 --> 00:25:05.420 The boys escaped for a little bit, but I don't blame them. 00:25:05.600 --> 00:25:10.320 They just ate some grass and scurried back into the van. 00:25:11.360 --> 00:25:14.400 um chris and wes are trying to 00:25:14.400 --> 00:25:23.500 encourage me to delay my departure to fix the generator that way i can get air 00:25:23.500 --> 00:25:31.760 conditioning in the van when we're parked in austin and even though i believe this is a delay tactic, 00:25:33.500 --> 00:25:39.000 because i'm still a couple hundred miles ahead of them in the race And I think 00:25:39.000 --> 00:25:39.740 they're probably right. 00:25:40.420 --> 00:25:42.500 I have a little bit of shade, a good setup. 00:25:43.660 --> 00:25:47.720 No one around to really kick me out of a hotel parking lot. 00:25:49.120 --> 00:25:54.440 So I think I might spend maybe an hour, hopefully not two, but maybe two, 00:25:55.100 --> 00:26:00.880 just taking the carburetor out of the generator, cleaning it up and seeing if 00:26:00.880 --> 00:26:02.920 I can get the generator to run a little more smoothly. 00:26:06.192 --> 00:26:07.172 Maybe I'll jump in the river. 00:26:07.732 --> 00:26:11.972 You see, what you have to understand is Brent's kind of a galaxy brain, 00:26:12.212 --> 00:26:14.712 and time is relative to perception. 00:26:15.532 --> 00:26:16.172 Isn't it for you? 00:26:16.252 --> 00:26:18.972 It was kind of an hour you spent. You kind of spent an hour on it. 00:26:18.972 --> 00:26:19.372 It felt like it. 00:26:20.412 --> 00:26:23.552 Okay, it is 3.40, much later than I was hoping. 00:26:25.852 --> 00:26:30.212 But the car was back together. It definitely needed a great cleaning. 00:26:30.632 --> 00:26:36.032 That is clearly the issue. I had to sacrifice my toothbrush to clean some of 00:26:36.032 --> 00:26:41.612 the components, so I should make a note to get a new toothbrush in Austin. 00:26:44.092 --> 00:26:53.652 But everything's back together. I did find two O-rings that were completely damaged and fell off. 00:26:54.772 --> 00:27:01.272 and I had to construct my own out of, well I found, I looked around trying to 00:27:01.272 --> 00:27:03.932 find what I could use and I found 00:27:03.932 --> 00:27:07.232 an air freshener which was the perfect thickness and I could modify it. 00:27:07.392 --> 00:27:14.752 So I've used that in place of a rubber o-ring, hoping that lasts a few days. 00:27:15.672 --> 00:27:22.492 But anyhow, I just need to put some of the glass fuses back in for the starter. 00:27:23.052 --> 00:27:28.332 so let me just do that here and then we could give it a shot and see if it actually 00:27:28.332 --> 00:27:33.852 will start so i need a screwdriver there we go, 00:27:36.092 --> 00:27:44.712 one in two in okay are you ready oh i did check the oil it's slightly overfilled, 00:27:58.507 --> 00:28:04.187 well i mean let's tinker a little bit more. 00:28:04.187 --> 00:28:11.067 Oh that's hard to hear too because brent and so team bigfoot our team and team 00:28:11.067 --> 00:28:16.807 moose uh we had a time difference between us so we could get up a little bit 00:28:16.807 --> 00:28:19.407 earlier and hit the road before you would even be awake. 00:28:20.027 --> 00:28:25.087 So while you were fiddling with the generator, we were laying down miles like madmen. 00:28:26.567 --> 00:28:32.687 We are 521 miles into day three. We just crossed the border into Texas. 00:28:32.927 --> 00:28:39.687 We've been driving for seven hours and 40 minutes, and we are just about tied 00:28:39.687 --> 00:28:42.107 right now with our buddy Brent. 00:28:42.267 --> 00:28:45.507 Maybe he's making a tactical mistake, west bay he very 00:28:45.507 --> 00:28:48.247 well may be i mean we're neck and neck at this point we're 00:28:48.247 --> 00:28:51.427 both still like six and a half hours outside austin but 00:28:51.427 --> 00:28:54.527 we're each six and a half hours outside i 00:28:54.527 --> 00:28:58.967 cannot believe we have closed this gap it's incredible last we heard from brent 00:28:58.967 --> 00:29:02.747 because we're kind of slow on updates right now he was taking time to fix on 00:29:02.747 --> 00:29:08.027 his generator specifically the car on that thing yeah we don't know if it went 00:29:08.027 --> 00:29:11.527 well if it went terribly uh he hasn't said anything but we've, 00:29:12.367 --> 00:29:15.087 I mean, the tracker's updating, but he's at the same location. 00:29:15.187 --> 00:29:15.907 He seems to have not moved. 00:29:16.067 --> 00:29:19.947 Yeah. Is he tricking us? Is he slow playing us? Does he just not take us seriously? 00:29:20.707 --> 00:29:25.027 Either way, it may have been a fatal mistake because we're catching up right now. 00:29:25.607 --> 00:29:29.607 Or he may be tricking us. I don't know. I'm bracing myself for either thing. 00:29:29.947 --> 00:29:34.027 So as Brent wrapped up the work on the generator, he took a moment to check 00:29:34.027 --> 00:29:36.007 how we were doing on the tracker. 00:29:36.627 --> 00:29:38.247 I don't think it was looking too good. 00:29:38.387 --> 00:29:39.287 I am now all powering. 00:29:40.469 --> 00:29:48.409 van started boys tucked in and i'm about to hit the road for the first time today it is 4 44. 00:29:49.789 --> 00:29:56.649 uh my map claims i have 466 miles the texas tracker claims i have 389, 00:29:57.509 --> 00:30:03.549 and the boys have 298 so they're 100 miles ahead of me i am losing the race 00:30:03.549 --> 00:30:08.189 because i I got distracted by generators. 00:30:09.289 --> 00:30:11.449 Okay. Carrying on. 00:30:11.549 --> 00:30:16.489 I cannot believe that worked. I cannot believe that actually worked as a strategy. 00:30:17.629 --> 00:30:23.049 And so, I mean, and to be fair, we were in an area of West Texas where we could 00:30:23.049 --> 00:30:25.589 just lay down miles like crazy. 00:30:25.909 --> 00:30:28.049 The speed limit was like 85 miles per hour. 00:30:28.849 --> 00:30:32.689 We were also deploying other tactics. You know, we were trying to convince Brent 00:30:32.689 --> 00:30:35.069 that we were not moving as much as we were. 00:30:35.069 --> 00:30:38.249 Yes, that was a bit of a psychological warfare play. You were really good at that. 00:30:38.389 --> 00:30:41.589 Yeah, you know, like we tried to convince him we were going to a museum, 00:30:41.609 --> 00:30:45.489 but we also, I managed to get Gemini to Photoshop you. 00:30:45.809 --> 00:30:48.569 Like you were filling gas, but it kind of looks like you're at a food truck. 00:30:48.709 --> 00:30:51.109 So I was hoping maybe Brent thought we were stopping for lunch. 00:30:51.169 --> 00:30:55.809 I thought that was real. I was like, I'm under a van and you guys are getting 00:30:55.809 --> 00:30:57.289 tacos. He looked effort. 00:30:57.369 --> 00:31:00.529 He swapped out because we only did two stops that Texas day. 00:31:00.849 --> 00:31:03.409 And so there was no time to stop for food trucks. We were in a race. 00:31:03.409 --> 00:31:07.769 We stopped twice And we stopped for less than 15 minutes And so then what Wes 00:31:07.769 --> 00:31:10.749 did He took a picture of me at the gas pump And then while we're on the road 00:31:10.749 --> 00:31:13.689 He throws that through the LLM To make it look like we're at a taco stop To 00:31:13.689 --> 00:31:14.889 make you think we're taking our time 00:31:15.289 --> 00:31:17.989 It was strategic And it worked. 00:31:18.869 --> 00:31:20.189 He's never gonna trust me again. 00:31:22.101 --> 00:31:27.101 Welcome to Austin. We did it. We did it. Over 13 hours of driving today. 00:31:28.421 --> 00:31:33.401 I think almost 900 miles. I can't believe it. We made some good time today, 00:31:33.401 --> 00:31:35.961 and we actually beat Brent by about two hours. 00:31:36.261 --> 00:31:40.661 So we're going to set up some Star Trek on the TV, and we're going to order some tacos. 00:31:41.121 --> 00:31:44.121 And when Brent gets here, we'll have some gluten-free tacos for him, 00:31:44.201 --> 00:31:45.641 and we'll be nice and fed. 00:31:46.061 --> 00:31:49.401 It feels pretty good. I can't believe we pulled that out. I mean, 00:31:49.501 --> 00:31:51.061 we started so far behind. 00:31:51.621 --> 00:31:55.701 There was no way. I mean, we kept doing every possible piece of math. 00:31:55.861 --> 00:31:57.841 We looked at every possible alternative route. 00:31:58.021 --> 00:32:01.641 We even pulled up the, like, maintenance database for the various states we 00:32:01.641 --> 00:32:05.441 were driving through trying to optimize if we could catch any extra advantage. 00:32:06.041 --> 00:32:12.221 In over 13 hours of driving today, we only made two stops, and each stop was 00:32:12.221 --> 00:32:16.101 under 15 minutes because we knew we had very little margin of error. 00:32:16.401 --> 00:32:20.201 And so we hustled. We grabbed, like, food we knew we could eat. 00:32:20.201 --> 00:32:22.481 So we had gas station food today, 00:32:22.721 --> 00:32:26.201 so that's why we're having nice tacos tonight, because we earned it. 00:32:26.801 --> 00:32:30.841 We did, and then all there was to do was to wait for our buddy Brent to arrive. 00:32:31.561 --> 00:32:38.361 Okay, just about two hours later, and Brent just pulled up to the Airbnb. 00:32:39.381 --> 00:32:44.181 We're a day ahead of schedule. We all hauled today. 00:32:45.141 --> 00:32:48.421 Someone's at the door, Wes. Who is it? 00:32:49.001 --> 00:33:01.041 Hello? brantley hi buddy let's come here oh yeah good job you stayed up for 00:33:01.041 --> 00:33:02.921 me you hauled i did i stayed up, 00:33:03.501 --> 00:33:05.321 are you recording i'm recording, 00:33:07.861 --> 00:33:11.981 how's the kitties doing are they okay okay they're probably hungry or whatever. 00:33:13.801 --> 00:33:19.621 You know what's funny, too, is we didn't really talk ahead of time about recording 00:33:19.621 --> 00:33:21.041 clips. We just both did it. 00:33:21.121 --> 00:33:22.281 I know. You've trained me well. 00:33:23.961 --> 00:33:28.981 So we talked for way too long about the race and, oh, this moment, oh, that moment. 00:33:29.141 --> 00:33:32.421 I couldn't believe how much rain you both got. Had I got that rain, 00:33:32.481 --> 00:33:35.861 I would have been flooded. The van still rains inside. 00:33:36.041 --> 00:33:39.861 Right. Monsoon levels of rain we went through all the way until we got to Salt Lake City. 00:33:40.341 --> 00:33:44.101 but it was fun to like you know trade trade like moments or you know what were 00:33:44.101 --> 00:33:46.901 you thinking at this time because we were thinking this yeah we. 00:33:46.901 --> 00:33:49.521 Only got a few updates right we were both kind of being a little secretive. 00:33:49.521 --> 00:33:50.181 Mostly just. 00:33:50.181 --> 00:33:51.121 Watching each other on the track. 00:33:51.121 --> 00:33:54.561 Yeah yeah so once we had that all the way it was time to go out there and do 00:33:54.561 --> 00:33:58.861 a good peeper scan because i wanted to see brent's repair job that he had done on the road nice. 00:33:58.861 --> 00:34:03.981 Fix but i'm very lucky because yeah nothing else got destroyed Yes, 00:34:05.581 --> 00:34:08.201 and also it could have taken out my power steering belt. 00:34:08.861 --> 00:34:11.361 Probably all these extra zip ties you put in to really hold things together. 00:34:11.481 --> 00:34:13.921 I didn't do that, my mechanic did that. Oh really? I know. 00:34:45.249 --> 00:34:49.629 One password dot com slash unplug. Take the first steps to better security for 00:34:49.629 --> 00:34:53.569 your team by securing your credentials and protecting every application, 00:34:53.829 --> 00:34:57.369 even unmanaged shadow ID applications that you didn't even know about. 00:34:57.509 --> 00:35:01.529 If you're in security or if you're an IT professional, you need to go to one 00:35:01.529 --> 00:35:03.249 password dot com slash unplug. 00:35:03.389 --> 00:35:05.509 That's the number one password dot com. 00:35:05.829 --> 00:35:10.209 And then unplugged is all lowercase. Like, I understand it. You've got a mountain 00:35:10.209 --> 00:35:12.569 of assets. You've got devices. You've got your identities. 00:35:12.769 --> 00:35:15.769 You've got the applications. There's new applications coming online all the time. 00:35:16.249 --> 00:35:20.429 It's a lot, and it creates a mountain of security risk that's constantly dynamically changing. 00:35:20.569 --> 00:35:26.589 But you can conquer that mountain of security risk with 1Password Extended Access Management. 00:35:26.809 --> 00:35:30.789 Did you know that over half of IT pros that were surveyed said that SaaS brawl 00:35:30.789 --> 00:35:34.409 is an actual challenge? Because you just have applications your users are signing 00:35:34.409 --> 00:35:36.569 up for that you didn't even know about. They're creating credentials. 00:35:36.569 --> 00:35:37.949 They're putting company data in there. 00:35:38.229 --> 00:35:41.989 There's often redundancy. And then how do you properly manage that when it's 00:35:41.989 --> 00:35:45.789 time for somebody to move on and make sure you're actually meeting your compliance goals? 00:35:45.949 --> 00:35:51.129 Well, that's where Trelica by 1Password comes in. It inventories every app in use at your company. 00:35:51.269 --> 00:35:55.049 And then it has pre-populated app profiles. They can assess your SaaS security 00:35:55.049 --> 00:35:56.729 risk. It'll let you manage the resources. 00:35:56.989 --> 00:35:59.709 You can optimize the spend to see if there is a redundancy in there. 00:35:59.809 --> 00:36:03.009 But I think my favorite part is you can make sure that you're enforcing your 00:36:03.009 --> 00:36:06.289 company's best practices across every application you use. 00:36:06.289 --> 00:36:12.729 and you've got a process to securely onboard and off-board employees and you've 00:36:12.729 --> 00:36:16.089 got a system to manage that shadow IT like the contractors and the applications 00:36:16.089 --> 00:36:19.029 you didn't know about because Trellica by 1Password provides you a complete 00:36:19.029 --> 00:36:21.029 solution for SaaS access governance. 00:36:21.269 --> 00:36:24.189 It's just one of the ways extended access management helps a team strengthen 00:36:24.189 --> 00:36:27.249 compliance and make sure they're meeting their security goals as well. 00:36:27.409 --> 00:36:29.929 They have a beautiful dashboard to help you manage all of this. 00:36:30.029 --> 00:36:32.789 I mean, you know about 1Password, the excellent password manager. 00:36:32.969 --> 00:36:36.909 Well, you need to check out their new offerings. They're just really powerful, 00:36:36.929 --> 00:36:40.589 and they're, for the next generation of security concerns, the real IT pros face. 00:36:40.769 --> 00:36:44.629 Go take the first step to better security for your team by securing your credentials 00:36:44.629 --> 00:36:48.969 and protecting every application your users use, even the unmanaged ones. 00:36:49.029 --> 00:36:53.569 So you need to go learn more. You can support the show. You can go to 1password.com slash unplugged. 00:36:53.649 --> 00:36:58.069 You go there. You find out the deets you learn, and you support us. It's real easy. 00:36:58.209 --> 00:37:04.849 It's 1password.com slash unplugged, all lowercase, 1password.com slash unplugged. 00:37:07.784 --> 00:37:14.024 So after the long trek down, we actually got here to do what we were intending 00:37:14.024 --> 00:37:16.324 the entire trip to be about. It wasn't just the race. 00:37:16.764 --> 00:37:19.084 It was actually Texas Linux Fest. Remember that, boys? 00:37:19.204 --> 00:37:20.564 Oh, that little thing. Right. 00:37:21.804 --> 00:37:23.684 That's why we're here. Oh, yeah, right. 00:37:23.844 --> 00:37:29.684 It's a good thing we got here a day early, I think, because we clearly all needed a day off in between. 00:37:29.944 --> 00:37:33.584 Oh, yeah. We pushed it hard. We pushed it hard. You collected some stats for us. 00:37:33.704 --> 00:37:34.944 Oh, yes, I did. 00:37:35.304 --> 00:37:38.344 Why don't we? Let's cover those before we get to the fest. Just because it's fun. 00:37:38.484 --> 00:37:41.044 The numbers are fun. Okay, so our boy Team Moose over there. 00:37:41.044 --> 00:37:41.384 Uh-huh. 00:37:42.504 --> 00:37:47.424 Well, he did pretty good because he had an average velocity of 94.2 kilometers 00:37:47.424 --> 00:37:50.924 per hour, which he can maybe translate into freedom units. 00:37:50.944 --> 00:37:53.264 That's over 60 miles per hour, right? 00:37:53.444 --> 00:37:57.404 Yeah. I had no idea because my speedometer doesn't work, but that feels good. 00:37:57.524 --> 00:37:58.464 That's really impressive. 00:37:58.844 --> 00:38:01.724 And he managed to drive for almost 31 hours. 00:38:01.964 --> 00:38:02.864 Well done, sir. 00:38:02.864 --> 00:38:07.084 And this is not, you know, this is like actual time measured when he was in motion from the stats. 00:38:07.284 --> 00:38:08.484 Right, right. Just in motion time. 00:38:08.584 --> 00:38:13.884 It is when you can see the day breakdown here. So he started off really well. Day one, 10.44 hours. 00:38:14.624 --> 00:38:19.384 But then you kind of see where there was maybe some easier going in the middle. Next day was one hour. 00:38:19.664 --> 00:38:19.984 Oh. 00:38:20.324 --> 00:38:22.364 Hey, hey, hey. That was Sunday of Linux unplugged. 00:38:22.364 --> 00:38:23.664 Okay, all right. Okay, okay, fair, fair. 00:38:23.724 --> 00:38:25.224 Okay, then four hours after that. 00:38:25.404 --> 00:38:25.524 Yeah. 00:38:25.604 --> 00:38:27.484 And then the last two days you finished pretty strong. I mean, 00:38:27.624 --> 00:38:29.544 you know, seven plus on each of us. 00:38:29.564 --> 00:38:31.144 A seven hour drive day is no joke. 00:38:31.144 --> 00:38:31.464 No joke. 00:38:32.064 --> 00:38:33.644 You guys did like double that. 00:38:33.764 --> 00:38:34.464 Well, what did we do. 00:38:34.584 --> 00:38:37.824 Wes? Yeah, okay. Well, so we had an average velocity not too much higher than 00:38:37.824 --> 00:38:40.044 Brent's, 102.5 kilometers per hour. 00:38:40.064 --> 00:38:41.544 Oh, okay. So we were slightly faster. 00:38:42.124 --> 00:38:46.344 And which was good because we had to do a total driving of 36.1 hours. 00:38:46.484 --> 00:38:47.524 Oh, my gosh. 00:38:47.724 --> 00:38:48.084 Wow. 00:38:49.064 --> 00:38:50.984 That's almost an entire work week of driving. 00:38:51.104 --> 00:38:55.044 And there was only three days to do it. So day one, we put in 13.02. 00:38:55.364 --> 00:38:55.604 That's impressive. 00:38:55.804 --> 00:38:55.924 Yeah. 00:38:56.304 --> 00:39:00.624 Day two, we took it a little easier. We did 9.95, just about 10 hours of driving. 00:39:00.624 --> 00:39:05.284 And then on that killer critical last day, 13.14. 00:39:05.724 --> 00:39:06.124 What? 00:39:06.544 --> 00:39:06.924 Wow. 00:39:06.924 --> 00:39:09.944 It's a good thing you don't sleep. You just drive the whole time. 00:39:09.964 --> 00:39:13.204 It's a good thing I like to drive. It's a good thing. Wow. Yeah, it is. 00:39:14.064 --> 00:39:19.584 So we definitely rested. We just, the first, the next day, before the fest started, 00:39:19.604 --> 00:39:20.944 we didn't even leave the Airbnb. 00:39:21.364 --> 00:39:21.644 No. 00:39:21.784 --> 00:39:22.904 We did not get in the car. 00:39:23.264 --> 00:39:23.324 We didn't drive. 00:39:23.484 --> 00:39:24.724 We didn't go. We just crashed. 00:39:24.724 --> 00:39:25.764 We ordered some food in. 00:39:25.904 --> 00:39:27.044 We ordered food and rested. 00:39:27.784 --> 00:39:28.704 Watch some Star Trek. 00:39:28.704 --> 00:39:33.484 And kind of planned our Fest coverage, too, so there were some of that as well, but oh, my gosh. 00:39:33.604 --> 00:39:39.004 And I think that was the good move, because we were recharged for Texas Linux 00:39:39.004 --> 00:39:42.924 Fest day one, and one of the things we always like to go do once we show up, 00:39:42.944 --> 00:39:47.644 you get registered, and you go find our buddy Carl, and you get some pocket meat. 00:39:48.324 --> 00:39:52.404 That looks good. That looks really good. Hey, buddy. How are you? 00:39:55.732 --> 00:39:56.592 How's Carl? 00:39:59.032 --> 00:39:59.472 Yeah, 00:40:01.652 --> 00:40:08.852 Yeah, hello Yeah, we did it drove right we sure did how was it right pretty 00:40:08.852 --> 00:40:11.572 good So pretty good. It was a hell of a race. I was following the tracker. 00:40:11.912 --> 00:40:16.932 Yeah, I thought for sure he had I really I did Yeah, until the last day. 00:40:19.112 --> 00:40:24.932 Speaking of, gotta keep it... Oh, there it is! The pocket meat's out. The pocket meat is out. 00:40:25.732 --> 00:40:27.672 It's almost all worth it just for the pocket meat. 00:40:27.752 --> 00:40:28.692 That's the only reason I came. 00:40:28.792 --> 00:40:30.192 He even has a variety. 00:40:30.392 --> 00:40:33.852 Yeah, he does. He does. So we were in the zone once we got our pocket meat. 00:40:34.392 --> 00:40:37.972 Would you believe it, we all managed to get up on time and get out the door. 00:40:38.832 --> 00:40:41.852 Barely. Barely. I mean, there was some edge cases there, maybe. 00:40:41.852 --> 00:40:45.172 I won't suggest who might have been a little bit late. But we're here. 00:40:45.992 --> 00:40:50.232 and we've gotten some of our initial pocket meat. That's been nice. We've been registered. 00:40:50.892 --> 00:40:58.112 We got to walk the floor a bit, and we popped our head into the Bootsy room. That was a little busy. 00:40:58.712 --> 00:41:02.012 Oh, yeah, packed. I mean, I don't think we couldn't really stay for more than 00:41:02.012 --> 00:41:05.112 a few minutes just to get a taste because anywhere we stood, 00:41:05.292 --> 00:41:06.592 we were blocking somebody's view. 00:41:06.832 --> 00:41:09.112 I think people are here for the Atomic Distros. 00:41:09.512 --> 00:41:11.272 Yeah, they want their containers booting. 00:41:12.132 --> 00:41:18.732 But Brent came with no intention of seeking tech support, but ended up having 00:41:18.732 --> 00:41:21.092 an opportunity to get a little direct support from Framework. 00:41:21.212 --> 00:41:22.212 Tell me about that, Brentley. 00:41:22.812 --> 00:41:26.472 Well, I decided I probably would like the right side of my ports to work again, 00:41:26.472 --> 00:41:29.512 so I thought I could chat with the Framework folks. And they were helpful. 00:41:29.652 --> 00:41:30.452 They had some suggestions. 00:41:30.752 --> 00:41:33.932 Of course, you can just swap out the entire motherboard and go that way. 00:41:34.072 --> 00:41:39.432 But I don't know. I'm going to keep tinkering, see if we can fix it. 00:41:39.992 --> 00:41:44.132 It did suggest a USB-C hub too, which could potentially at least be a temporary patch. 00:41:46.527 --> 00:41:50.827 And, of course, already we've seen, I don't know, 10, 12 different listeners, 00:41:51.087 --> 00:41:55.587 including listener Lee, who set us up with some 3D-printed rocket ships. 00:41:56.187 --> 00:41:59.767 That's true. Yeah, basically, we keep bumping into listeners. It's pretty great. 00:41:59.987 --> 00:42:04.347 I think Friday will probably be the smaller of the days, and then I think Saturday 00:42:04.347 --> 00:42:05.707 is probably going to be the big main day. 00:42:07.027 --> 00:42:11.327 And mostly, I just have to make sure we get into that Vim mastering room because 00:42:11.327 --> 00:42:13.387 I want us all to leave this as Vim masters. 00:42:13.607 --> 00:42:15.587 It's not too late, right? We still have time for the Vim workshop? 00:42:16.127 --> 00:42:20.587 Yeah, it's high time you kick that disgusting nano habit of yours anyway. 00:42:22.067 --> 00:42:25.307 Hey now, hey now. I just want to foster a collaborative environment, 00:42:25.307 --> 00:42:27.447 so I was willing to go to the VIM workshop. 00:42:27.727 --> 00:42:31.607 I was willing to sit through a long VIM workshop. 00:42:31.627 --> 00:42:31.867 Really. 00:42:31.947 --> 00:42:36.187 So the VIM workshop didn't work out, and I couldn't find the nano workshop. 00:42:36.187 --> 00:42:37.827 I'm not sure what that was about. 00:42:38.967 --> 00:42:42.787 So I think the next best thing to do would be to go get some barbecue, obviously. 00:42:43.547 --> 00:42:46.407 We've got a little crew assembled here, so we've been organizing over bit 00:42:46.407 --> 00:42:49.647 chat um and we're going to styles barbecue 00:42:49.647 --> 00:42:52.487 styles switch barbecue which is about 10 minutes 00:42:52.487 --> 00:42:55.207 from the event center now of course we have 00:42:55.207 --> 00:42:58.067 to go back to the airbnb first yeah 10 minutes the other 00:42:58.067 --> 00:43:01.287 direction yeah yeah we gotta get our car gotta get 00:43:01.287 --> 00:43:03.887 that but then we'll have it and we can transport and a lot 00:43:03.887 --> 00:43:06.927 of folks don't have vehicles they are like 00:43:06.927 --> 00:43:09.887 traveling for the event and so we may 00:43:09.887 --> 00:43:13.407 be a little short on cars so we're gonna have one to add to the carpool that'll 00:43:13.407 --> 00:43:17.167 be good and we'll get our barbecue fixed while we're in town i blame carl you 00:43:17.167 --> 00:43:20.647 know after he gave us the generous help into pocket meat you know then we saw 00:43:20.647 --> 00:43:23.347 him wandering around with just like i don't know if it was a turkey leg or a 00:43:23.347 --> 00:43:26.367 stick it was just a big stick of meat just a big stick of meat so what were 00:43:26.367 --> 00:43:29.147 we supposed to do we were not going to be satisfied with burgers or. 00:43:30.100 --> 00:43:33.840 So we run back, and we get my car, and we head towards lunch, 00:43:33.840 --> 00:43:38.000 where the listeners are waiting for us, and I get a flat tire along the way. 00:43:39.220 --> 00:43:40.480 Finally, you break down. 00:43:40.680 --> 00:43:42.260 I know. After the race. 00:43:42.400 --> 00:43:43.080 At least we were in Austin. 00:43:43.280 --> 00:43:46.980 And I did have a tire air pump with me, so I could put some air in it and get 00:43:46.980 --> 00:43:48.940 us to lunch, but it was just go figure. 00:43:49.060 --> 00:43:53.100 So we showed up a little late to lunch, but very much liked that Stiles barbecue. 00:43:54.220 --> 00:43:58.700 And we spent the rest of the afternoon kind of doing the networking track. 00:43:58.700 --> 00:44:02.920 went back for a bit did a lot of chatting and uh settled in for the evening 00:44:02.920 --> 00:44:07.040 with some star trek and got ourselves prepared for day two which was when the 00:44:07.040 --> 00:44:10.560 keynote was going to be and like the real big day of the texas linux fest. 00:44:10.560 --> 00:44:14.860 It's saturday and uh we're maybe a little late we're rushing right now to make 00:44:14.860 --> 00:44:18.600 it to the keynote we're here can we blame brent for this a little bit oh yeah 00:44:18.600 --> 00:44:22.680 yeah oh definitely i had a giant breakfast at about three minutes before we 00:44:22.680 --> 00:44:27.340 had to leave so that's on me All right. Okay, good. Well, that's settled then. 00:44:27.920 --> 00:44:29.720 Let's get to it. Walk faster. 00:44:30.140 --> 00:44:32.360 And we did make it to the keynote indeed. 00:44:32.580 --> 00:44:35.660 We made it just in time. They have cool space chairs in the auditorium, 00:44:35.700 --> 00:44:39.080 and it is Dustin Kirkland giving the keynote. 00:44:39.280 --> 00:44:43.560 He's the SVP of engineering at Chain Guard now. His name might sound familiar 00:44:43.560 --> 00:44:46.460 to you because he also used to work at Canonical. 00:44:46.620 --> 00:44:49.380 And I enjoyed his keynote. I hadn't heard much about Chain Guard, 00:44:49.420 --> 00:44:52.080 and it's always good to kind of catch up on what Dustin's been doing because 00:44:52.080 --> 00:44:54.620 he's been in the industry for quite a long time, doing good stuff. 00:44:54.720 --> 00:45:00.620 So, it also, I get to introduce the keynote speaker for this conference, 00:45:00.680 --> 00:45:01.680 which I'm very excited about. 00:45:01.900 --> 00:45:05.620 I've known Dustin for longer than probably either of us will want to admit. 00:45:06.000 --> 00:45:11.560 And now he's working at ChainGuard on securing Linux. And I think that that's 00:45:11.560 --> 00:45:13.400 something that everyone needs. 00:45:13.980 --> 00:45:17.040 Thank you, Justin. Ted, thank you so much. 00:45:21.720 --> 00:45:26.700 All right. Good morning, Texas Linux Fest. What an absolute thrill and honor 00:45:26.700 --> 00:45:32.320 it is to be your speaker here this morning in my hometown of Austin, Texas. 00:45:32.840 --> 00:45:39.400 I've been attending this conference since 2010, and to be on this stage is an 00:45:39.400 --> 00:45:42.140 honor and a privilege. So thank you to the organizers for the invitation. 00:45:42.320 --> 00:45:46.480 Very much appreciate the opportunity to spend a few minutes with you here today 00:45:46.480 --> 00:45:48.900 and talk about software security. 00:45:51.264 --> 00:45:54.844 This is definitely not my first Texas LinuxFest rodeo. 00:45:55.444 --> 00:45:59.424 In 2010 was the original Texas LinuxFest. 00:45:59.644 --> 00:46:03.324 And as I remember, it was a couple of tables set up in a strip mall, 00:46:03.704 --> 00:46:05.664 the way I remember it anyway. 00:46:06.164 --> 00:46:10.084 But it had an incredible spark of energy. 00:46:11.124 --> 00:46:16.424 The people were passionate. The hallway conversations were all about the early 00:46:16.424 --> 00:46:21.144 days of cloud and cloud computing. I remember quite a bit of talk about cloud 00:46:21.144 --> 00:46:25.864 computing and whether it was real or not, or an industry shift or not. 00:46:26.544 --> 00:46:31.884 In any case, it certainly felt like something big. And here we are 15 years 00:46:31.884 --> 00:46:36.584 later, and this conference is still going and thriving and super proud to see this. 00:46:36.784 --> 00:46:41.644 I really felt like Dustin had a good tone there. And he brings some historical 00:46:41.644 --> 00:46:44.764 context to the area. He's familiar with the Linux scene in the area. 00:46:44.984 --> 00:46:48.024 So after the keynote, we wanted to just grab his ear real quick. 00:46:48.024 --> 00:46:54.524 and kind of get a sense of what is the Linux industry scene if you want to live in Texas? 00:46:54.704 --> 00:46:57.524 What do you expect? And then obviously we just chatted more from there. 00:46:58.024 --> 00:46:59.504 The keynote just wrapped up. It 00:46:59.504 --> 00:47:02.844 was great. And so we had to grab Dustin to chat with him a bit about it. 00:47:03.004 --> 00:47:07.264 And I think I wanted to start, Dustin, with, could you describe what the Linux 00:47:07.264 --> 00:47:09.544 scene in general is like, kind of in the Austin and Texas area? 00:47:09.604 --> 00:47:10.764 Because I know you've been here for a long time. 00:47:11.164 --> 00:47:16.084 Yeah, I've been in Austin, Texas for 25 years, since 2000. I started my career 00:47:16.084 --> 00:47:20.664 at the IBM Linux Technology Center, which is just across the street from where the conference is here. 00:47:20.864 --> 00:47:27.184 What's cool about that is that brought about 1,000 engineers to Austin in the 00:47:27.184 --> 00:47:30.124 early 2000s, Linux engineers specifically. 00:47:30.124 --> 00:47:34.964 A lot of open source passion has flown through here over those years. 00:47:35.124 --> 00:47:37.044 Of course, I've stayed. Others have moved around. 00:47:37.744 --> 00:47:40.604 But, yeah, there's a lot of passion for open source in general. 00:47:40.604 --> 00:47:44.324 the Austin, just the Austin mindset, the keep it weird, the, 00:47:44.324 --> 00:47:46.404 just the Austin mindset, the tech mindset. 00:47:48.160 --> 00:47:51.720 Aligns well with open source, the open source ethos. So I love it. 00:47:51.780 --> 00:47:55.100 There's a bunch of tech companies here, many of which have their security centers 00:47:55.100 --> 00:47:59.920 or their network centers based around Austin. So, you know, it's a, it's a great scene. 00:48:00.980 --> 00:48:04.000 Okay. So you said something during the keynote that we all went, 00:48:04.200 --> 00:48:08.420 Oh, and you were, you took a pretty strong stand and said that the best solution 00:48:08.420 --> 00:48:11.340 really for security in the enterprise, especially for infrastructure, 00:48:11.340 --> 00:48:14.840 like Linux boxes is maybe a rolling distro. 00:48:15.000 --> 00:48:18.120 Can you expand on that a little bit? Because I think some people listening to 00:48:18.120 --> 00:48:20.040 that think the opposite when it comes to enterprise. 00:48:20.660 --> 00:48:24.780 Yeah, I think that's largely been the case. You know, the concept of a rolling distro is not new. 00:48:25.020 --> 00:48:32.080 You can go back to the mid-90s with Debian, Red Hat, SUSE, Ubuntu. 00:48:32.820 --> 00:48:39.920 Everyone has had a rolling distro. But it's never really been able to or fitted 00:48:39.920 --> 00:48:43.660 to run in an enterprise environment. The stability was just not there. 00:48:43.820 --> 00:48:46.520 And so at ChainGuard, we've kind of taken the opposite approach we've said 00:48:46.520 --> 00:48:49.960 the time is now for rolling distros maybe it wasn't possible when 00:48:49.960 --> 00:48:52.900 every build had to be done on a manually booted and 00:48:52.900 --> 00:48:55.620 installed physical machine but just with the 00:48:55.620 --> 00:49:01.540 dawn of cloud native with containers uh with serverless jobs it's just it's 00:49:01.540 --> 00:49:05.700 so much possible more possible now to build and test and run everything everywhere 00:49:05.700 --> 00:49:10.560 uh and crank through those builds and do so in a way that you can maintain the 00:49:10.560 --> 00:49:14.000 the security and the quality of are there going to be problems yeah Yeah, absolutely. 00:49:14.600 --> 00:49:17.540 But the problems I would posit with a rolling distro are small. 00:49:17.720 --> 00:49:21.000 When you're trying to bisect what changed between yesterday and today, 00:49:21.220 --> 00:49:23.920 that's a problem you can solve in a few minutes to hours. 00:49:24.040 --> 00:49:29.160 When you're trying to bisect what went wrong between the 2017 release of some 00:49:29.160 --> 00:49:33.060 enterprise Linux and the 2025 release, and you're trying to upgrade in between, 00:49:33.180 --> 00:49:34.700 I mean, everything changed, you know. 00:49:34.840 --> 00:49:37.940 So, yeah, I'm a huge proponent of rolling distros. 00:49:38.120 --> 00:49:43.480 I've suffered through the, you know, two decades of that not being ready. I think we're ready now. 00:49:43.880 --> 00:49:46.600 I love to hear that. So did Chaingard. 00:49:47.409 --> 00:49:51.909 Create their own distribution to accomplish that? And are there like special 00:49:51.909 --> 00:49:54.549 tools in there to make that a safe experience? 00:49:54.969 --> 00:49:59.309 Yeah, we did actually. So I didn't mention this in the keynote, but I probably should. 00:49:59.529 --> 00:50:03.989 Every single bit of Chain Guard is built entirely and bootstrapped entirely from source. 00:50:04.249 --> 00:50:11.509 We are not a derivative of Alpine, Ubuntu, Debian, Fedora, Gentoo, Arch, we're Nix. 00:50:11.669 --> 00:50:14.449 We're not a derivative of anything. We've built the compilers, 00:50:14.649 --> 00:50:18.389 the libraries, every single package, every project from source. 00:50:18.649 --> 00:50:22.389 We also have built automation that does all of that automatically. 00:50:22.809 --> 00:50:26.589 So unlike, and I'm the Debian maintainer for a couple of dozen Debian packages 00:50:26.589 --> 00:50:31.849 or have been over the years, every Debian package has one or more human name 00:50:31.849 --> 00:50:34.629 email addresses who are responsible for that package. 00:50:34.749 --> 00:50:38.569 And that's true for pretty much every other distro. We've taken a different approach. 00:50:38.729 --> 00:50:44.409 We have build rules checked in in a YAML format, but it's the machine that builds 00:50:44.409 --> 00:50:48.129 these and does that over and over and determines when there's a regression, 00:50:48.129 --> 00:50:52.249 even tries to automatically address problems and fix them when possible. 00:50:52.409 --> 00:50:55.669 So yes, we've bootstrapped this entirely from source. 00:50:57.209 --> 00:51:02.249 Wow. And so if I have a problem, I assume there's mechanisms to roll back? 00:51:02.889 --> 00:51:08.869 Yeah. So rollback is, maybe this is part of why a rolling distro is possible now. 00:51:09.009 --> 00:51:15.569 Rollback means stop the container that's not working and start the container that is working. 00:51:16.149 --> 00:51:19.669 So rollback is just go back to the previous version, the previous digest of 00:51:19.669 --> 00:51:21.669 the best-known working version. 00:51:21.889 --> 00:51:26.009 And so, you know, much of that didn't exist 15, 20 years ago, 00:51:26.089 --> 00:51:27.269 and so this wasn't possible. 00:51:27.589 --> 00:51:32.009 Now, when we're talking about VMs and potentially even hardware, 00:51:32.629 --> 00:51:36.729 we're leaning into some of the containerized mechanisms for doing that. 00:51:36.729 --> 00:51:42.409 So FS Verity, you know, read-only overlay file systems boot C is actually, 00:51:42.649 --> 00:51:44.409 you know, really interesting here. 00:51:44.569 --> 00:51:49.709 So treat a container, treat a VM like a container, have that container effectively 00:51:49.709 --> 00:51:54.269 boot as a read-only immutable mount point for the root file system. 00:51:54.269 --> 00:51:58.929 And when you update, just download a new container image and reboot and remount. 00:51:59.229 --> 00:52:02.109 And, you know, there you go. Oh, you need to roll back. Okay, 00:52:02.269 --> 00:52:06.609 we'll just go to the previous digest of that container and you're back to the 00:52:06.609 --> 00:52:08.109 last known good working version. 00:52:09.968 --> 00:52:13.868 It does seem like the technologies are finally there to make it all work. 00:52:13.968 --> 00:52:18.808 So am I picking up, it's a real kind of minimal base OS and then the applications 00:52:18.808 --> 00:52:21.568 are all containerized? Yeah, that's right. Minimal base OS. 00:52:21.808 --> 00:52:26.328 The applications, we do package them and we render. 00:52:26.628 --> 00:52:32.008 Think about it as like rendering an image is the minimum set you need plus whatever 00:52:32.008 --> 00:52:35.068 application is you need to run. And if you want to run that as a container, great. 00:52:35.328 --> 00:52:39.468 If you want to run that as a VM and there are actually some workloads that just 00:52:39.468 --> 00:52:40.688 don't containerize well. 00:52:40.928 --> 00:52:43.328 There's workloads where performance is key. 00:52:43.768 --> 00:52:49.828 You know, applications that want full access to the CPU, memory, disk, network, IO, GPU. 00:52:50.508 --> 00:52:54.948 We can render any of those containers as a VM image, you know, 00:52:55.048 --> 00:53:01.308 and we can also, there are some workloads that for security reasons need to be in its own VM. 00:53:01.508 --> 00:53:04.688 You know, you run a privileged container, your pod is kind of compromised, 00:53:04.708 --> 00:53:08.768 or I would treat it as basically compromised once you're running a privileged 00:53:08.768 --> 00:53:10.588 container inside of that pod. 00:53:11.488 --> 00:53:14.448 So all of these are important mechanisms there. 00:53:14.968 --> 00:53:17.748 But yeah, you run the applications themselves as containers, 00:53:17.948 --> 00:53:21.488 containerize it, drag along all the bits and pieces you need for that application 00:53:21.488 --> 00:53:24.488 to run and run well, and keep it separate from the rest of the system. 00:53:25.108 --> 00:53:28.648 Okay, last question. We've been talking Enterprise today, but you announced 00:53:28.648 --> 00:53:32.108 the release of a Raspberry Pi image. Tell me a little bit about what's that about. 00:53:32.488 --> 00:53:36.228 Yeah, it's a bit of a fun experiment. So, you know, at ChainGuard, 00:53:36.348 --> 00:53:41.148 we get to hack on some things in our spare time sometimes. And this was a pet 00:53:41.148 --> 00:53:43.128 project of mine and a couple of other engineers. 00:53:43.168 --> 00:53:47.188 We, you know, are running home assistants or other things on our Raspberry Pis. 00:53:47.248 --> 00:53:51.208 My solar array monitor is running on a Raspberry Pi. 00:53:51.628 --> 00:53:56.888 And I've run Debian and Ubuntu on those machines very well and successfully for many years. 00:53:57.448 --> 00:54:01.828 But we, as a, this was kind of a Christmas project. So way back in December, 00:54:02.088 --> 00:54:07.288 I started working on, could I actually get a Chainguard OS to boot and run on Raspberry Pi? 00:54:07.408 --> 00:54:11.848 And I did, and not unexpectedly, because it's all the same bits that we put 00:54:11.848 --> 00:54:17.088 into our production-grade enterprise rolling distro images. I scanned it for 00:54:17.088 --> 00:54:19.228 vulnerabilities, and there were zero. 00:54:19.408 --> 00:54:22.588 Not unexpected. I mean, it's unexpected as someone who's never done this before, 00:54:22.728 --> 00:54:27.148 but this is literally the exact same bits as we're putting into our container images. 00:54:27.328 --> 00:54:31.148 So, yeah, that's pretty remarkable, frankly. So it took us a little while to 00:54:31.148 --> 00:54:34.308 get it to a point where we were ready to talk about it and then saved it for 00:54:34.308 --> 00:54:39.168 a few months for this conference Which seems like the right audience to talk about this way. 00:54:40.003 --> 00:54:42.283 Well, Dustin, great keynote. Thanks for answering the questions. 00:54:42.523 --> 00:54:44.543 It's good to chat with you. Yeah, thanks, Chris. Appreciate it. 00:54:44.903 --> 00:54:48.643 It was nice to catch up with Dustin again. He had a great keynote, 00:54:48.683 --> 00:54:50.563 and that will be linked in the show notes. 00:54:50.703 --> 00:54:55.403 In fact, we've kind of gone through and put the favorite talks of ours that 00:54:55.403 --> 00:54:58.083 are online on the Texas Linux Fest YouTube channel. 00:54:58.503 --> 00:55:02.603 And I believe as we are speaking right now, they're probably uploading more. 00:55:02.703 --> 00:55:06.063 So we'll link to the favorites that are up there so far, plus the channel in 00:55:06.063 --> 00:55:09.943 general, including Dustin's talk, if you want to go watch. There's some good ones. 00:55:10.583 --> 00:55:14.443 But we did the talk thing, and then at lunch on Saturday, it was time to celebrate 00:55:14.443 --> 00:55:16.863 the 12th birthday for Linux Unplugged. 00:55:17.243 --> 00:55:21.483 Lunchtime on Saturday, and that means it's birthday party time. 00:55:21.763 --> 00:55:23.723 Happy birthday, boys. Happy birthday. 00:55:24.123 --> 00:55:29.163 And I knew we might have trouble because when we arrived, and we arrived early, 00:55:29.243 --> 00:55:31.743 we usually arrive late, but this time we arrived early so we could actually 00:55:31.743 --> 00:55:33.743 get a bite to eat before the crowd showed up. 00:55:34.223 --> 00:55:39.263 And so it was just us. It was just the three of us, and we overwhelmed the guy. 00:55:39.943 --> 00:55:43.443 He told us that he was the only guy there, and that because of that, 00:55:43.503 --> 00:55:46.723 they only had one thing on the menu. They were doing a reduced menu. 00:55:47.183 --> 00:55:51.843 I knew we were in trouble, and then everybody started showing up. 00:55:52.443 --> 00:55:57.023 This is a little embarrassing. We have completely overrun this poor little facility. 00:55:57.323 --> 00:56:00.363 They're understaffed today. They're so understaffed, they're doing only one 00:56:00.363 --> 00:56:02.583 menu item. They have two people working here. 00:56:03.503 --> 00:56:04.923 And I don't know. 00:56:07.303 --> 00:56:10.903 There's 50 of us? I'm not sure. There's a lot. There's too many of us. Oh, okay. 00:56:12.183 --> 00:56:15.023 Line out the door. Line out the door. 00:56:15.243 --> 00:56:15.983 Multiple times. 00:56:16.243 --> 00:56:19.983 Yeah. But we have such a great audience. Everybody was chill. 00:56:20.483 --> 00:56:22.983 Everybody was cool. And by the end of it, the guy was at ease. 00:56:23.203 --> 00:56:25.103 Yeah. The staff handled it super well. 00:56:25.303 --> 00:56:25.483 Yeah. 00:56:25.623 --> 00:56:28.183 They did a good job of letting people know ahead of time. We tried to share 00:56:28.183 --> 00:56:31.543 that info, too. You don't have much choice here, but you can come. 00:56:31.743 --> 00:56:32.283 Yeah, yeah. 00:56:32.383 --> 00:56:33.763 And it turned into a great little party. 00:56:33.983 --> 00:56:37.883 And Brent had a chance to chat with some of the attendees. and we just wanted 00:56:37.883 --> 00:56:39.283 to know a couple of questions. 00:56:39.783 --> 00:56:43.363 All right, we're here at Texas Linux Fest. Let me know what's your name, 00:56:43.483 --> 00:56:47.423 which desktop you're using, and which distro. My name's Tyler, Hyperland Nixos. 00:56:47.903 --> 00:56:51.443 My name is Justin. I got KDE Plasma on a Steam Deck. Hey there, 00:56:51.523 --> 00:56:53.943 I'm Willard Nilgis. I use KDE on Arch Linux. 00:56:54.623 --> 00:56:57.163 David Fretz, I run Gnome on Red Hat. 00:56:57.863 --> 00:56:59.943 Carl George, Gnome on Fedora. 00:57:01.083 --> 00:57:06.323 And Derek, Gnome on Ubuntu. All right, and how long have you been Linuxing? Around four years. 00:57:06.983 --> 00:57:11.303 My first was around 2010 with like Zorin OS and whatnot, but it's back and forth. 00:57:11.483 --> 00:57:13.163 These days it's primarily on the Steam OS. 00:57:13.783 --> 00:57:19.143 A little over 10 years since about 2014. Late 90s? I don't remember when. 00:57:20.443 --> 00:57:25.623 16 years? I just did the math. Almost 10. Nice. Thank you, gentlemen. 00:57:25.903 --> 00:57:28.323 Wow. Wow. And they weren't the only ones. 00:57:28.403 --> 00:57:31.083 My name is Matthew Brahms. I'm using Debian and using GNOME. 00:57:32.175 --> 00:57:36.395 My name is Prasad. I'm currently using Garuda on my main desktop with KDE and 00:57:36.395 --> 00:57:39.355 on my new one, CacheOS on Framework. 00:57:39.895 --> 00:57:42.455 My name is George. I'm using Fedora and GNOME. 00:57:43.195 --> 00:57:46.795 Chris, and I'm currently on Fedora. The KDE spin. 00:57:47.555 --> 00:57:51.735 Hey, I'm Reza. I've been using GNOME on Fedora and i3 on RHEL. 00:57:53.075 --> 00:57:58.355 Dave, Sway and Fedora all the way. Very nice. And how long have you been Linuxing? 00:57:59.195 --> 00:58:02.715 15 years. 13 years. 20? 00:58:04.195 --> 00:58:07.915 I'll have to kind of see, but I guess I can date myself. My first Linux distro 00:58:07.915 --> 00:58:11.195 was Yagrasil Plug-and-Play Linux, so that tells you something. 00:58:12.395 --> 00:58:14.035 It's got to be at least 25 years. 00:58:15.275 --> 00:58:16.895 Not really sure. Maybe 15? 00:58:17.455 --> 00:58:20.275 Wow, wow. And one more batch. I love this. One more batch. 00:58:20.355 --> 00:58:25.995 My name is Robbie Calicott. I use Fedora KDE, the best desktop. 00:58:25.995 --> 00:58:36.275 up uh jodo bannon um fedora gnome i couldn't tell you 20-ish years not quite 00:58:36.275 --> 00:58:42.975 30 uh jonathan wright uh kde on fedora and almost 20 years a. 00:58:42.975 --> 00:58:46.195 Lot of long timers a lot of long timers but it was good i. 00:58:46.195 --> 00:58:47.195 Like hearing the mix too. 00:58:47.195 --> 00:58:49.955 I was asked after you know because 00:58:49.955 --> 00:58:52.775 people are like brent's asking all these questions uh i was asked 00:58:52.775 --> 00:58:58.475 if i saw any themes like is there a main desktop or something that's standing 00:58:58.475 --> 00:59:02.495 out or a distro that most people are running and as you heard there there's 00:59:02.495 --> 00:59:06.715 there's zero consensus zero there's only a consensus on how long people have 00:59:06.715 --> 00:59:10.195 been running linux that attend uh texas linux fest like a. 00:59:10.195 --> 00:59:10.875 Lot of long timers. 00:59:10.875 --> 00:59:11.735 Really impressive. 00:59:11.735 --> 00:59:15.435 Not all of them but a long of them you know about herding cats but i think i 00:59:15.435 --> 00:59:16.455 think that might be the case here. 00:59:16.455 --> 00:59:19.895 Lunch was great We had a really good meetup, great birthday party. 00:59:20.135 --> 00:59:24.995 But then after that, it was time to get back to work because Wes Payne had to 00:59:24.995 --> 00:59:29.515 bring that Nick's energy for his talk that was coming up in just a couple of hours. 00:59:29.695 --> 00:59:33.555 You could argue the meetup's not really over because Brent's currently giving a tour. 00:59:34.515 --> 00:59:38.795 Brought a few folks back to the Airbnb that really wanted to see the moose. 00:59:39.195 --> 00:59:43.975 And so Brent's currently giving a tour of the van. And while he's giving tours of the van, Mr. 00:59:44.055 --> 00:59:47.215 Wes Payne is preparing for his talk, which comes up very soon. 00:59:47.215 --> 00:59:47.995 How are you feeling, Wes? 00:59:48.815 --> 00:59:52.395 I'm feeling good. You know, there's been a lot of good talks here at Texas Linux Fest. 00:59:54.067 --> 00:59:59.687 No other Knicks talks. So I'm trying to charge myself up to fit the Knicks evangelist 00:59:59.687 --> 01:00:03.587 role I have inside myself and really try to embody that for everybody. 01:00:03.807 --> 01:00:06.687 Because, you know, we need some Knicks at Texas Linux Fest. 01:00:06.887 --> 01:00:10.007 We did. And I think it was a good talk. I may be a bit biased, 01:00:10.107 --> 01:00:12.607 but I thought it was a good, clean presentation, Wes. 01:00:12.687 --> 01:00:16.427 He had a good mix of practical code on the screen and also lean, 01:00:16.547 --> 01:00:18.287 mean bullet points when needed. 01:00:18.307 --> 01:00:21.567 And then some video examples mixed with some live examples. 01:00:22.327 --> 01:00:25.147 And it flowed. the whole thing flowed. It was a good presentation. 01:00:25.467 --> 01:00:28.007 And the other thing that I think was a good sign is when we talked to people 01:00:28.007 --> 01:00:32.787 after your presentation, they said that your demonstrations made a few more 01:00:32.787 --> 01:00:35.607 things click for them that they hadn't got just by listening to the podcast. 01:00:35.807 --> 01:00:39.547 Hey, that is what I was aiming for. If it could stoke anyone's curiosity, 01:00:40.147 --> 01:00:43.947 maybe demystify things, maybe make NixOS seem a little more approachable, 01:00:44.127 --> 01:00:45.147 then I think I've succeeded. 01:00:45.307 --> 01:00:48.847 And I think there's some interest in that whole sidecar module concept, 01:00:49.187 --> 01:00:51.727 the Nix sidecar. I think there's interest in that. 01:00:51.727 --> 01:00:55.247 You know, it's a very useful pattern, especially if you're already kind of all 01:00:55.247 --> 01:00:57.707 in on Mesh Networks, as I think three of us are. 01:00:58.247 --> 01:01:02.067 And then you got the combo, right, of, okay, I can have this directly on my 01:01:02.067 --> 01:01:07.507 network as a first-class entity with the whole curated catalog of NixOS services 01:01:07.507 --> 01:01:10.007 and modules at your fingertips. At least that's the idea. 01:01:10.147 --> 01:01:14.207 It's pretty powerful. It's pretty powerful. So good fest for you boys? 01:01:14.427 --> 01:01:14.687 Oh, yeah. 01:01:14.807 --> 01:01:15.167 Good fest? 01:01:15.227 --> 01:01:15.847 Excellent fest. 01:01:15.967 --> 01:01:16.607 Great fest, right? 01:01:16.727 --> 01:01:20.807 Yes, great fest. I liked the new venue. Something about a university kind of 01:01:20.807 --> 01:01:25.267 made it feel a little more community-minded than like a corporate conference center. 01:01:25.667 --> 01:01:27.507 And then at least for me as a speaker, it was a great experience. 01:01:27.667 --> 01:01:29.907 I mean, they had a video set up. They had professional audio stuff. 01:01:30.027 --> 01:01:33.647 There was a mic ready. They had all kinds of dongles and ports ready to plug your laptop in. 01:01:33.787 --> 01:01:37.187 And they had like a nice little screen for the speaker so I could see the talk too. 01:01:37.407 --> 01:01:40.187 Yeah, that is a good setup. And the venue, I think, did work. 01:01:40.387 --> 01:01:42.727 It wasn't, you know, we're not quite in the heart of Austin. 01:01:42.887 --> 01:01:45.587 But you're in an area that's still got a lot of Austin flavor. 01:01:45.587 --> 01:01:49.987 And there's tons of places to go out to and eat and all the things you want 01:01:49.987 --> 01:01:52.527 from Austin are in this area. And you're probably, you know, 01:01:52.647 --> 01:01:53.427 20 minutes from downtown. 01:01:54.278 --> 01:01:55.258 depending on traffic. 01:01:55.658 --> 01:01:59.218 And you know, it is a community run event. So it was neat to see just all the 01:01:59.218 --> 01:02:03.338 hard work that had gone into it and just the hard work that continues going into there. 01:02:03.478 --> 01:02:06.378 You know, I heard a lot of folks reflecting on, you know, what went right this 01:02:06.378 --> 01:02:09.438 year and what didn't and kind of thoughts for the future and what might change. 01:02:09.558 --> 01:02:12.278 So I'm really grateful the audience made this trip possible. 01:02:12.458 --> 01:02:14.978 I think we were able to have a little bit more fun with it because it was an 01:02:14.978 --> 01:02:18.818 audience funded trip and that added a whole new element that we would love to do again. 01:02:18.818 --> 01:02:25.918 In fact, keep your eyes on the Texas Tracker, texastracker.jupiterbroadcasting.com, 01:02:26.038 --> 01:02:27.598 because the race begins. 01:02:27.818 --> 01:02:31.158 Where last time it was a race against Team Bigfoot and Team Moose, 01:02:31.278 --> 01:02:33.978 this time it's a race against time. 01:02:34.178 --> 01:02:39.658 We're working together to, as fast as possible, get up to System76 in Colorado, 01:02:39.658 --> 01:02:43.818 in Denver, so that way they can give us an in-person, hands-on tour of the new 01:02:43.818 --> 01:02:46.558 Cosmic desktop and its current release status. 01:02:46.558 --> 01:02:51.758 and then we also have to obviously meet up with editor drew maybe treat him 01:02:51.758 --> 01:02:55.278 to a dinner or something like that while we're in the area and brent has some 01:02:55.278 --> 01:02:59.418 van parts coming in so we might have to do some quick van fixing on then we 01:02:59.418 --> 01:03:01.698 have to hit the road to make it back to the studio, 01:03:02.638 --> 01:03:06.278 because canonical's vp of engineering is going to be joining us for a chat and 01:03:06.278 --> 01:03:09.878 we want to get to the studio in time to make it for that conversation so the 01:03:09.878 --> 01:03:13.498 trip back to the studio is going to be a real race against time we'll have the 01:03:13.498 --> 01:03:18.338 tracker going once we reach denver too we're going to be splitting and going our separate ways. 01:03:18.578 --> 01:03:21.798 The Moose and Team Bigfoot will be going in opposite directions, 01:03:21.818 --> 01:03:23.338 and you can keep an eye on us there as well. 01:03:23.558 --> 01:03:27.818 It should be just as hardcore of a drive as we had on the way down. 01:03:27.898 --> 01:03:31.238 Hopefully maybe not quite as hardcore because we're not racing against each other. 01:03:31.378 --> 01:03:34.198 I think we're supposed to tell Brent that we're leaving tonight, right? 01:03:34.298 --> 01:03:34.478 Right. 01:03:35.058 --> 01:03:40.978 I was about to say I hope there's less finagling of, I don't know, my timeline, let's say. 01:03:41.058 --> 01:03:44.678 Well, let's just say there was a brief conversation last night when someone 01:03:44.678 --> 01:03:47.838 disappeared. we thought, wouldn't it be hilarious if we loaded up in the car 01:03:47.838 --> 01:03:50.918 and hit the road to Denver right now? Yeah, you came back and we were gone. 01:03:50.998 --> 01:03:51.758 I would have been like, sweet! 01:03:52.198 --> 01:03:56.798 I placed it myself. Right? That's true. But no, we're going to caravan together to Denver. 01:03:56.978 --> 01:04:00.018 We're looking forward to seeing our friends at System76 and then, 01:04:00.218 --> 01:04:01.958 of course, making it back home. 01:04:02.138 --> 01:04:05.418 We're hoping that it goes pretty smooth, there's no major incidents, 01:04:05.578 --> 01:04:08.818 and we can make this tight timeline work because if it works out, 01:04:08.878 --> 01:04:12.058 we're going to have some great content for you when we get back next week. 01:04:12.458 --> 01:04:15.898 Big shout out to everybody who made it to Texas Linux Fest. All of you who said 01:04:15.898 --> 01:04:19.698 hi or those of you that didn't get a chance to say hi, it's one of our favorite fests. 01:04:19.938 --> 01:04:23.938 And we always really enjoy, too, just the whole scenery and all of it. 01:04:24.118 --> 01:04:25.378 Just eternally grateful that 01:04:25.378 --> 01:04:29.378 you showed up and extremely grateful that the audience made it possible. 01:04:29.558 --> 01:04:33.078 And don't forget, there are some goodies on that Texas Linux Fest YouTube channel. 01:04:36.042 --> 01:04:41.642 Unraid.net slash unplugged. Unleash your hardware right now with Unraid. 01:04:41.842 --> 01:04:46.342 I think the secret is that you can use what you have in your closet right now to get started. 01:04:46.522 --> 01:04:51.622 You can use the drives you've got. You can use the interest and the passion from a topic we covered. 01:04:51.882 --> 01:04:53.502 You know, when we talk about things 01:04:53.502 --> 01:04:57.642 like ersatz TV, the community makes applications available for Unraid. 01:04:57.762 --> 01:05:01.762 Because Unraid is a powerful operating system you load on the existing hardware 01:05:01.762 --> 01:05:06.922 you have. They've been around for over 20 years, and they have proven year after 01:05:06.922 --> 01:05:09.762 year they know how to make a great product and maintain it. 01:05:09.862 --> 01:05:13.462 So if you go to unraid.net slash unplugged, you support the show, 01:05:13.522 --> 01:05:16.742 but you can also get Unraid, and you can use it 30 days totes free. 01:05:17.002 --> 01:05:20.842 Just get a sense of the architecture of how the system works and kind of the 01:05:20.842 --> 01:05:23.662 robust and, I'd say, bulletproofness of it. 01:05:23.782 --> 01:05:26.922 And they're always improving Unraid, too. There's a new version just around 01:05:26.922 --> 01:05:31.582 the corner, and the UI continues to get nicer and nicer with each release. 01:05:31.582 --> 01:05:33.062 that's an area of focus of theirs. 01:05:33.302 --> 01:05:37.502 They've also recently introduced an API with applications already getting built 01:05:37.502 --> 01:05:41.542 around it, and there's easy integration with mesh networking like TailScale. 01:05:41.602 --> 01:05:44.362 So you can install an application, click a box, it's on your TailNet. 01:05:44.682 --> 01:05:46.422 Hardware pass-through, crazy easy. 01:05:47.062 --> 01:05:50.782 Unraid has always been the leader in making it super easy to take hardware and 01:05:50.782 --> 01:05:55.722 pass it through to a VM, but now they've got options like share your GPUs and all kinds of stuff. 01:05:55.962 --> 01:05:58.482 And also, this has been out for a minute now, but I love this, 01:05:58.622 --> 01:06:01.502 Unraid also at the OS level supports Wi-Fi. 01:06:01.582 --> 01:06:04.982 So if you don't have Ethernet in your place, I know it sucks. I'm there with you. 01:06:05.622 --> 01:06:10.662 They just support that right out of the box now. So you've got things like QXL virtual GPU support. 01:06:11.002 --> 01:06:15.222 You've got the newer, faster Linux kernels. You've got an awesome file system stack. 01:06:15.382 --> 01:06:17.962 I mean, I'm talking to one of the best ZFS implementations you've ever seen 01:06:17.962 --> 01:06:22.602 because it can also integrate with or implement and transition from other ZFS 01:06:22.602 --> 01:06:26.962 systems like Ubuntu or TrueNAS or Proxmox and just move it right over to Unraid so it works real good. 01:06:27.462 --> 01:06:30.702 And you don't have to fuss with it. You know, you got what? 01:06:30.702 --> 01:06:34.222 you got a Saturday to get this working that's going to do and then you're going 01:06:34.222 --> 01:06:37.322 to have access to all the cool stuff we talk about all the time and be in control 01:06:37.322 --> 01:06:40.802 of your data and you can use the existing hardware if you're a tinker or a power 01:06:40.802 --> 01:06:44.722 user or you just want a better way to run your apps your VMs whatever it might be applications 01:06:45.142 --> 01:06:48.002 Unraid is going to give it to you it's really the freedom to build your perfect 01:06:48.002 --> 01:06:52.802 server check it out support the show go to Unraid.net slash unplugged. 01:06:56.384 --> 01:06:59.244 Well, we got ourselves, what are we calling these? Fake boos. 01:06:59.304 --> 01:07:00.744 With love. Fake boos with love. 01:07:01.024 --> 01:07:01.884 Very real fake boos. 01:07:02.024 --> 01:07:03.084 Yeah, the fake boos with love. 01:07:03.244 --> 01:07:09.484 We got the first one here from Tiny. A little Tiny 20 USDs, but everything helps. Thank you so much. 01:07:10.624 --> 01:07:11.364 Thank you, Tiny. 01:07:11.624 --> 01:07:15.344 Thank you for all the amazing shows over the years. I found you all during the 01:07:15.344 --> 01:07:19.904 Linux Action Show days, and it's part of the reason I have my dream job today. 01:07:20.644 --> 01:07:22.744 I'd like to show my Ansible roles as well. 01:07:22.784 --> 01:07:25.704 If you don't mind. Yeah, let's take a little look. All right. 01:07:25.704 --> 01:07:28.864 Yeah, there's some nice stuff in here. I got a little sneak peek, 01:07:28.904 --> 01:07:33.264 and there are a lot of nice roles. I'm looking at the NextCloud one right now. 01:07:33.364 --> 01:07:34.384 I'm looking at the AgGuard one. 01:07:34.744 --> 01:07:35.904 Clearly very well organized. 01:07:36.524 --> 01:07:41.344 Tiny says, includes roles for deploying various Homelab services and my desktop setup. 01:07:41.344 --> 01:07:46.204 The most unique thing about it is that it uses Ansible pull and a systemd timer 01:07:46.204 --> 01:07:49.604 to make sure that the latest configuration gets pulled down every night, 01:07:49.604 --> 01:07:53.844 so when I add a new app or change my shell it just magically appears in all 01:07:53.844 --> 01:07:56.384 my boxes in 24 hours or less that's great. 01:07:56.384 --> 01:08:00.484 That's big brain right there system d to pull down the changes in the background 01:08:00.484 --> 01:08:03.144 overnight so the next time you just go to use the box it's got all your new 01:08:03.144 --> 01:08:06.224 settings that you changed on the other machines awesome tiny maybe. 01:08:06.224 --> 01:08:07.604 Tiny should be admin in your boxes. 01:08:07.604 --> 01:08:11.524 Yeah at least the studio boxes thank you for the uh fake boost too tiny appreciate 01:08:11.524 --> 01:08:16.764 it well mr adversary 17 came in with 100 000 sats, 01:08:21.130 --> 01:08:24.090 Adversaries writes, here's some fake sats for the trip back. 01:08:24.290 --> 01:08:27.630 Yeah, that is true. It does take gas to get back, too. So thank you for thinking of us. 01:08:27.870 --> 01:08:31.750 I have to say two adversaries helped me fix my framework. 01:08:32.490 --> 01:08:37.350 Oh, so the... Okay, wait. So let me recap. Last week, we found out that on the 01:08:37.350 --> 01:08:40.110 initial drive down, you burned out one of the sides of your framework. 01:08:40.210 --> 01:08:42.890 And did the entire Linux unplugged that week. 01:08:42.950 --> 01:08:43.790 With a burned outside. 01:08:44.090 --> 01:08:44.530 Uh-huh. 01:08:44.970 --> 01:08:45.850 So what was it? 01:08:45.850 --> 01:08:53.290 Well i think the charger in the van that i've plugged into this laptop a couple times before um you. 01:08:53.290 --> 01:08:54.910 Mean that really sweet anchor charger i gave. 01:08:54.910 --> 01:08:57.630 You you got me that that thing's awesome and. 01:08:57.630 --> 01:08:58.530 Maybe not so awesome. 01:08:58.530 --> 01:09:01.630 Well i don't know i gotta do some testing on it but uh 01:09:01.630 --> 01:09:04.330 it must have misbehaved overnight because i plugged the 01:09:04.330 --> 01:09:07.150 laptop in overnight to just charge it up for the show as 01:09:07.150 --> 01:09:10.290 a responsible co-host does uh but 01:09:10.290 --> 01:09:13.510 it was the computer was dead in the morning and uh 01:09:13.510 --> 01:09:16.750 none of the ports on the right side which is where it was plugged in uh were 01:09:16.750 --> 01:09:20.550 working anymore um but i did the show it somehow 01:09:20.550 --> 01:09:26.930 survived and uh after the show late at night we took the whole thing apart because 01:09:26.930 --> 01:09:31.150 you know framework you can and uh we were looking we took the motherboard right 01:09:31.150 --> 01:09:35.630 out and we're looking for like okay did this like something burn on it or like 01:09:35.630 --> 01:09:37.670 a capacitor yeah could you see like a dark. 01:09:37.670 --> 01:09:38.390 Spot or something. 01:09:38.390 --> 01:09:41.870 Anything that might give little hints of what the next step might be because 01:09:41.870 --> 01:09:46.630 I you know you can replace the motherboards but I didn't really want to and 01:09:46.630 --> 01:09:50.210 the folks here at Texas Linux Fest the framework folks were like well at least 01:09:50.210 --> 01:09:52.310 it's possible and easy to replace the motherboard. 01:09:52.310 --> 01:09:57.070 And to their credit they're like since your other side does work what you could 01:09:57.070 --> 01:10:02.750 do is take your 11th gen mobo out put it in a case uses a media server and you 01:10:02.750 --> 01:10:04.110 still get a useful machine out of it. 01:10:04.110 --> 01:10:05.290 Which is a great idea yeah. 01:10:05.290 --> 01:10:07.190 Especially if you threw in something like a usbc dock. 01:10:07.190 --> 01:10:10.230 Yeah yeah so i mean it wasn't the worst 01:10:10.230 --> 01:10:15.330 case isn't that bad i suppose but it turns out that we were able to in in the 01:10:15.330 --> 01:10:19.370 investigation you know as responsible uh you know tinkerers we unplugged the 01:10:19.370 --> 01:10:25.270 battery before started taking everything else apart good and we plugged the 01:10:25.270 --> 01:10:27.950 battery back in and all the ports started working again it did it. 01:10:27.950 --> 01:10:29.630 Just you didn't do anything else but unplug the battery. 01:10:29.630 --> 01:10:32.670 Yeah well no that's not true we unplugged the battery took 01:10:32.670 --> 01:10:35.390 everything out looking you know had the had the 01:10:35.390 --> 01:10:40.590 motherboard in our hands looking for like some kind of anything that might suggest 01:10:40.590 --> 01:10:45.250 what we might fix uh because at that point i was like well i i want to learn 01:10:45.250 --> 01:10:48.330 micro soldering i could change this thing which is probably not going to go 01:10:48.330 --> 01:10:51.850 good but it turned out we were like well okay well i got to use this thing so 01:10:51.850 --> 01:10:54.190 i just put it back together and we plugged the battery in, 01:10:54.872 --> 01:10:59.632 And the framework does like a little pause to do a bunch of hardware diagnostics 01:10:59.632 --> 01:11:00.832 if the battery's unplugged. 01:11:01.012 --> 01:11:04.352 And then with a little bit of testing, everything started working again. 01:11:05.892 --> 01:11:08.092 So you literally unplugged it and plugged it back in again. 01:11:08.212 --> 01:11:09.472 You just needed a hard reset. 01:11:09.752 --> 01:11:12.892 To be fair, in person, it was much more involved, more strategic, 01:11:13.192 --> 01:11:15.652 much more like we sequenced our testing. 01:11:15.652 --> 01:11:18.752 But if it ever happened again, you would just go right to plug and unplug the battery, I suppose. 01:11:19.272 --> 01:11:22.712 The bad thing is that makes me not want to investigate the charger and just 01:11:22.712 --> 01:11:25.112 kind of like, oh, yeah, next time I just unplug and plug the battery in. 01:11:25.132 --> 01:11:26.412 That's not probably a good thing. 01:11:26.432 --> 01:11:27.452 You'd still like to know why it happened. 01:11:27.672 --> 01:11:29.212 Yeah, what if it happens right before a show? 01:11:29.312 --> 01:11:31.492 The conversation we had with the Framework folks is like, yeah, 01:11:31.612 --> 01:11:38.832 we're actively investigating various USB-C charger and USB-C cable combos, 01:11:38.832 --> 01:11:44.172 and they're discovering this Anker one is totally fine, while maybe this Anker one isn't finer. 01:11:44.572 --> 01:11:47.012 E-Green was the other. There was another brand they mentioned. 01:11:47.752 --> 01:11:49.932 Mom, not Monster Cables, Master? 01:11:50.292 --> 01:11:50.992 I don't know. 01:11:51.112 --> 01:11:51.972 I should have took notes. 01:11:51.972 --> 01:11:54.512 Yeah, we probably actually, maybe we have it on audio somewhere. 01:11:55.612 --> 01:12:01.052 I did also hear at our meetup that one listener was working actively with the 01:12:01.052 --> 01:12:06.092 framework folks and a kernel developer to work out some of the framework 16 01:12:06.092 --> 01:12:09.292 driver issues on, I think it was AMD specifically. 01:12:09.572 --> 01:12:13.412 And so they're very active in trying to just figure out, hey, 01:12:13.512 --> 01:12:17.072 is this a framework issue? Is this a Linux driver issue? 01:12:17.312 --> 01:12:20.132 How do we get things upstream and make everything work? 01:12:20.252 --> 01:12:24.712 Yeah. So thank you for the fake boost. We are absolutely still accepting some 01:12:24.712 --> 01:12:25.812 contributions to get us home. 01:12:25.932 --> 01:12:29.612 We'll put a link to that in the show notes if you'd like to send us a Fiat fake boost. 01:12:29.672 --> 01:12:32.712 Or you can actually send sats like adversaries did through the forum as well. 01:12:32.992 --> 01:12:34.552 Thank you to everybody who did that. 01:12:39.152 --> 01:12:48.212 And our first boost comes in from Kangaroo Paradox with 153,084 sataroonies. 01:13:03.028 --> 01:13:07.768 Now, this came in a little late last week, but he says, here's a last-minute Nix config submission. 01:13:08.368 --> 01:13:11.448 I'm looking forward to my roast. All right, we've got to look at that. 01:13:12.108 --> 01:13:15.868 Well, first off, just check out this nice little grid of hosts with cool names, 01:13:15.908 --> 01:13:20.908 but then there's an AMD laptop, an M2 MacBook Air laptop, a Mac Mini M1 server, 01:13:21.408 --> 01:13:25.348 DNS for the main site, main NAS, backup NAS, DNS for the secondary site, 01:13:25.448 --> 01:13:28.768 and a VM template using cloud in it. This is cool. 01:13:29.008 --> 01:13:32.208 All right, that is really awesome, actually. This is really well done. 01:13:32.208 --> 01:13:37.528 Also, he said, here's some stats for a few drinks while you're down in Texas. That's really great. 01:13:37.768 --> 01:13:38.808 Thanks for the mead. 01:13:39.408 --> 01:13:40.088 Oh, really? 01:13:40.368 --> 01:13:40.608 Yeah. 01:13:40.988 --> 01:13:41.868 Mead, tell us about this. 01:13:41.968 --> 01:13:44.908 A little half pint of mead at the mead. We chose a good spot. 01:13:44.988 --> 01:13:46.568 I had some amazing drinks. 01:13:46.808 --> 01:13:52.028 Yeah, yeah. So Brent got mead. I had a Diet Pepsi. And Wes had probably something fancy. I don't know. 01:13:52.148 --> 01:13:55.288 I know you, Wes, though. You do like yourself a little fancy every now and then. 01:13:55.648 --> 01:13:58.708 But really appreciate it, Conger. Thank you for being our a baller, 01:13:58.948 --> 01:14:01.448 a booster this week. You're the best around. 01:14:02.988 --> 01:14:05.688 Blackhost boots in with 100,000 cents. 01:14:05.768 --> 01:14:09.768 All right. That's pretty much baller, too, I say. 01:14:13.568 --> 01:14:14.628 Thank you, Blackhost. 01:14:14.848 --> 01:14:16.688 No message, though, just the cents. 01:14:16.928 --> 01:14:17.988 Always appreciate the value. 01:14:18.668 --> 01:14:24.308 Well, Magnolia Mayhem sent in a message with 27,468 cents. 01:14:24.448 --> 01:14:25.168 Mayhem, you say? 01:14:27.408 --> 01:14:29.808 He's a great guy, but I think his drawer is full of Froot Loops. 01:14:32.208 --> 01:14:36.448 Hey, do y'all need some gas sats? Better late than never, I guess. 01:14:36.628 --> 01:14:40.048 Anyway, it's awesome seeing this community come together to help our little 01:14:40.048 --> 01:14:43.268 literate hosts. Iterate hosts here? 01:14:43.388 --> 01:14:47.148 Wait a second. I'm not sure that's a compliment, so maybe we just skip that. 01:14:48.128 --> 01:14:49.768 Hey, but they did help. 01:14:50.008 --> 01:14:54.608 Yeah, that's true. I'm too many states to the east, they say, 01:14:54.708 --> 01:14:56.048 to help. No, you're helping right now. 01:14:56.208 --> 01:15:00.128 Oh, yeah, you can help from anywhere. That's the best part. But if any of you 01:15:00.128 --> 01:15:04.128 screw up bad enough to find your way to Mississippi, my doors are open. 01:15:04.708 --> 01:15:09.228 Not sure what you'd be doing here, of course, but I do know some good hiding 01:15:09.228 --> 01:15:12.388 spots if you're on the run. Pretty much the only reason I can think of. 01:15:12.508 --> 01:15:13.348 That could come in handy. 01:15:13.468 --> 01:15:14.988 You never know. You never know. 01:15:15.068 --> 01:15:18.228 I did cross the Mississippi, but I don't think I was anywhere near Mississippi. 01:15:19.468 --> 01:15:23.528 He also says, you do not, you do not want to see my next config. 01:15:23.868 --> 01:15:24.928 We might still, though. 01:15:25.468 --> 01:15:29.948 He's also back on Albie again. Hey, back on the self-hosted train. Well done, buddy. 01:15:30.108 --> 01:15:32.008 Oh, yeah, boosting via that podcast index. 01:15:32.648 --> 01:15:37.168 Very cool. All right, well, Night 62 is here with a nice boost. 01:15:41.240 --> 01:15:44.040 24,203 sats. Hello, gents. 01:15:44.320 --> 01:15:47.640 I meant to send this earlier. This is for Texas Linux Fest. I know that for 01:15:47.640 --> 01:15:50.400 me, the highlight of my trip to scale here this year was hanging out with the 01:15:50.400 --> 01:15:53.620 three of you and talking open source tech over some good food. 01:15:53.740 --> 01:15:55.300 Yeah, that tends to be the way we do it. 01:15:55.500 --> 01:15:59.440 I won't be able to make it to Texas, unfortunately, but I hope this modest amount 01:15:59.440 --> 01:16:03.460 of sats is added to everything the community has given to help make sure the 01:16:03.460 --> 01:16:06.100 others have similar experience in the community. Oh, that's really cool. 01:16:06.180 --> 01:16:06.680 So sweet. 01:16:06.960 --> 01:16:09.500 Thank you for cultivating one of the greatest podcasting communities out there. 01:16:09.500 --> 01:16:11.800 I enjoy getting to know many of the community members like PJ, 01:16:12.420 --> 01:16:16.740 Carl the Pocket Meat Man, and TechDev and others. Have a great time at Texas 01:16:16.740 --> 01:16:19.680 Linux Fest, and I hope to see you all at scale next year. 01:16:20.080 --> 01:16:20.960 So sweet. 01:16:20.960 --> 01:16:24.180 That's great. That is really great. It is really something. 01:16:24.480 --> 01:16:28.900 I mean, we bump into so many people down here, you know, so you really are giving 01:16:28.900 --> 01:16:31.640 us a chance to reconnect with the audience, and that really is something special. 01:16:31.680 --> 01:16:36.360 It always energizes us like never before, and so to have Texas Linux Fest happen 01:16:36.360 --> 01:16:39.280 in the fall when most of the other things happen in the spring. 01:16:39.280 --> 01:16:41.860 We've kind of been on a lull for a bit. Thank you. 01:16:42.180 --> 01:16:42.840 We needed the recharge. 01:16:43.060 --> 01:16:43.160 We did. 01:16:43.400 --> 01:16:43.780 Yeah. 01:16:44.360 --> 01:16:45.900 So we drove ourselves exhausted. 01:16:47.800 --> 01:16:51.040 Well, Kiwi Bitcoin guide comes in with 20,000 cents. 01:16:51.160 --> 01:16:53.420 All right. I think so. 01:16:53.600 --> 01:16:55.960 Oh, it's a time traveler boost for Texas. 01:16:56.480 --> 01:16:58.800 Somebody make us a time traveler clip. We need that. 01:16:59.160 --> 01:17:03.100 I'm randomly working through the back catalog to learn things as they come up 01:17:03.100 --> 01:17:06.920 in my setup. So we're like sort of a, you know, go look it up in Linux Unplugged as you do it. 01:17:07.060 --> 01:17:08.000 That's fun. Sure. 01:17:08.000 --> 01:17:14.840 I just learned the difference between Snap and Flatpacks in episodes 532, 501, and 499. 01:17:15.980 --> 01:17:19.760 It's evergreen content. So thanks for the work you put into creating these and 01:17:19.760 --> 01:17:20.860 the passion and the delivery. 01:17:21.000 --> 01:17:25.540 That's great. I'm so glad. I'm so glad that was useful for you. 01:17:25.660 --> 01:17:28.360 Thank you very much for the boost. Appreciate the value coming back our way. 01:17:28.500 --> 01:17:28.980 We sure do. 01:17:29.100 --> 01:17:32.080 It does mean a lot to us. All right, Brentley, I think you're up. 01:17:32.260 --> 01:17:38.680 We got ourselves a bite bitten. Boosting in here. One, two, three, four, five sets Oh, 01:17:43.152 --> 01:17:48.552 One boost for two people talking. I'm three drinks in while boosting four of 01:17:48.552 --> 01:17:50.152 these five NextCloud fans. 01:17:50.572 --> 01:17:55.472 That is hilarious. One boost for two people. I'm three drinks in while boosting 01:17:55.472 --> 01:17:57.492 four of these five NextCloud fans. 01:17:57.712 --> 01:18:01.312 Byte Bitten was at, I guess, the NextCloud conference, as they do, 01:18:01.452 --> 01:18:03.452 and was listening to the live show last week. 01:18:04.152 --> 01:18:07.632 Byte, it's good to hear from you. Thank you for the boost. Oh, 01:18:07.692 --> 01:18:13.712 I like this name. Tetra Pulse comes in with 16,500 sats. 01:18:16.212 --> 01:18:20.452 It's true. I like that name for some reason. You know, Tetra Pulse. 01:18:20.712 --> 01:18:22.672 Emptying my fountain wallet. Enjoy. 01:18:23.092 --> 01:18:26.132 Mwah. Thank you. Appreciate the sats. 01:18:26.772 --> 01:18:30.872 Our pal Suderman comes in with 5,555 sats. 01:18:30.892 --> 01:18:31.592 Hey, there he is. 01:18:35.372 --> 01:18:38.312 First time I've listened live, totally because i thought you 01:18:38.312 --> 01:18:43.552 might look at my nix config but your lm it must have been drinking yeah i've 01:18:43.552 --> 01:18:49.292 never even tried sops before but anyway thanks for the super kind review i listen 01:18:49.292 --> 01:18:54.172 to y'all all the time oh and the name is pronounced suderman rhymes with superman 01:18:54.172 --> 01:18:58.252 superman i see okay so suderman is that uh you. 01:18:58.252 --> 01:19:01.672 Know what happens with those lms right like you ask them for something they're 01:19:01.672 --> 01:19:05.032 gonna try to give it to you so we're like we were like we're being way too nice 01:19:05.032 --> 01:19:09.872 to this guy's repo, give us something to be critical about. And Wes is like, that's not legit. 01:19:10.032 --> 01:19:12.912 So that's why we're like, we'll put this in the LLM criticism section. 01:19:13.352 --> 01:19:15.032 Because it was too damn good. 01:19:15.212 --> 01:19:15.552 That's right. 01:19:15.672 --> 01:19:19.352 That was the problem. It was too damn good. Thank you very much for the boost. Appreciate it. 01:19:19.752 --> 01:19:22.352 Well, Jordan Bravo came in with a Rodex. 01:19:23.762 --> 01:19:28.502 I'm late to the party, but here is the unified Nix config for all of my machines. 01:19:28.742 --> 01:19:28.902 Oh, boy. 01:19:29.222 --> 01:19:33.842 Three servers and four workstations. They all use Nix OS, except one workstation, 01:19:34.042 --> 01:19:35.782 which has Ubuntu with Nix. 01:19:35.942 --> 01:19:40.382 Oh, man. Jordan Bravo, you madman. 01:19:40.742 --> 01:19:43.042 There's a lot of interesting stuff. Just looking at the imports, 01:19:43.182 --> 01:19:47.242 I'm seeing Nix Bitcoin, I'm seeing SOPs, System Manager, too. 01:19:47.322 --> 01:19:50.302 I wonder if you're using the Ubuntu box. I was only just recently learning about 01:19:50.302 --> 01:19:54.802 System Manager. And you know, Jordan's a regular in our NixNerds Matrix room, 01:19:54.802 --> 01:19:56.422 too, so maybe see him there. 01:19:56.562 --> 01:20:01.702 I'm just kind of noticing the structure here. He's got a host directory, 01:20:01.722 --> 01:20:05.142 and then he's got a folder for each one of his hosts, like Tux is his laptop in here. 01:20:05.222 --> 01:20:07.762 And then in there, he's got his configuration.nix, his hardware configuration, 01:20:07.802 --> 01:20:09.202 and his home.nix, of course. 01:20:09.822 --> 01:20:14.162 Yeah, this is a really solid layout. I'd say this is the top-notch layout. 01:20:14.322 --> 01:20:15.922 This is one of the top-notch ones, I'd say. 01:20:16.002 --> 01:20:17.462 You know, you could maybe copy some of that. 01:20:17.542 --> 01:20:22.122 I don't just toss around top-notch willy-nilly. That's a top-notch config right 01:20:22.122 --> 01:20:24.802 there, bravo. Well done. I like it a lot. 01:20:25.442 --> 01:20:27.402 Goofy Ambitions is also here with a row of decks. 01:20:28.342 --> 01:20:31.402 That's 2,222 sats. This is a great segment. 01:20:31.702 --> 01:20:34.662 Keep them coming. And it was the config. Oh, that's our first. 01:20:34.782 --> 01:20:37.882 That's our one and only vote so far for doing another config confession. 01:20:37.902 --> 01:20:38.482 All right. 01:20:38.822 --> 01:20:42.182 All right. We have one. Thank you, Goofy. That's one. We need more, though. 01:20:42.582 --> 01:20:46.802 Tech Dev 5521 comes in with 5,000 sats. 01:20:48.722 --> 01:20:51.502 been listening to the show since mike fell in love with 01:20:51.502 --> 01:20:56.502 swift on coder and matt was the co-host of last first time boost though hey 01:20:56.502 --> 01:20:59.862 the boost about the show being international with a listener in china and wanted 01:20:59.862 --> 01:21:04.162 to flip the role i've listened to the show from the u.s canada columbia england 01:21:04.162 --> 01:21:09.902 spain the uae holland georgia and russia see y'all at texas linux. 01:21:09.902 --> 01:21:10.802 Fest yes and. 01:21:10.802 --> 01:21:13.182 See tech dev we did indeed and that was great. 01:21:13.182 --> 01:21:17.622 It was it was really great thank you uh tech dev for the boost and uh thank 01:21:17.622 --> 01:21:20.822 you for the great conversation looking forward to uh your project keep us in 01:21:20.822 --> 01:21:24.422 the loop on how that goes he knows what i'm talking about oh. 01:21:24.422 --> 01:21:28.702 Yeah well gene bean did boost in two boosts and they're both rows of ducks, 01:21:31.443 --> 01:21:35.743 Boost number one, Chris, you got to use the branch and pull request model for 01:21:35.743 --> 01:21:38.043 working on your next configs. 01:21:38.283 --> 01:21:42.903 It's so much easier to do than one big commit after lots and lots of work. 01:21:43.043 --> 01:21:46.263 See, this is great because Gene can say it and then I don't have to harp on it. 01:21:46.343 --> 01:21:49.103 I know, now you're all giving it to me. All right, thank you, Gene. 01:21:49.283 --> 01:21:49.703 Thanks, Gene. 01:21:50.463 --> 01:21:55.263 Regarding keeping those fake boosts around, I see ZapRite has an API and can 01:21:55.263 --> 01:22:01.363 send webhooks. What if you fire a webhook on payment that triggers a boost CLI 01:22:01.363 --> 01:22:02.903 or similar for the same amount? 01:22:03.123 --> 01:22:07.883 That would get the funds from ZapRite into the splits and the regular boosting ecosystem. 01:22:08.383 --> 01:22:11.723 That is, assuming that some kind of Nostra hub. 01:22:11.723 --> 01:22:16.343 He linked us, yeah. He linked us to that. There isn't another API we could use instead. Yeah. 01:22:16.523 --> 01:22:18.563 A certain API doesn't have... 01:22:18.563 --> 01:22:20.503 I bet that's an Albi hub. Does Albi have a Nostra ID? 01:22:20.683 --> 01:22:24.323 That's what I'm thinking it is. Jeez. Yeah. That's a great idea in a way. 01:22:24.323 --> 01:22:27.883 I mean, it's kind of a hacky solution, Gene, but it's also kind of a brilliant solution. 01:22:28.063 --> 01:22:30.203 You know what I mean? Because if you just call him Boosie a lion and then distributing 01:22:30.203 --> 01:22:36.243 the sets, you may find that there is even a possible better solution on the horizon. 01:22:36.403 --> 01:22:38.543 You never know, Gene. Maybe we know something. 01:22:38.703 --> 01:22:39.103 Bum, bum, bum. 01:22:39.303 --> 01:22:40.803 Gene's an idea, man, and I appreciate that. 01:22:40.803 --> 01:22:44.423 I do. I do. I love hearing from Gene. It doesn't feel like it's a complete episode 01:22:44.423 --> 01:22:45.263 if we haven't heard from Gene. 01:22:45.463 --> 01:22:46.883 I hope we get to see him again next year. 01:22:47.163 --> 01:22:51.503 Yeah. A Dude Trying Stuff came in with 2,222 sets. The road decks. 01:22:52.583 --> 01:22:56.763 Live boosting from Bucky's on the road trip home Jealous We haven't even seen. 01:22:56.763 --> 01:22:57.503 A Bucky's yet. 01:22:57.503 --> 01:23:02.363 Oh, glad your map led you faithfully south It was great to meet you all Drive safe. 01:23:02.363 --> 01:23:03.403 That's so sweet Oh. 01:23:03.403 --> 01:23:03.963 Thank you That's. 01:23:03.963 --> 01:23:05.663 Awesome I had a Bucky's check-in. 01:23:07.363 --> 01:23:13.443 Bobby comes in with a row of ducks Boost Nice to catch you live for a change 01:23:13.443 --> 01:23:17.503 Doesn't happen often from the EU Even with my sleep schedule Ah. 01:23:17.563 --> 01:23:18.443 Thank you, Bobby Yeah. 01:23:18.503 --> 01:23:21.503 That was live from today this morning Awesome We appreciate it yeah we do. 01:23:21.503 --> 01:23:27.103 We got one last boost here Dougie fresh 3023 sets so you coming. 01:23:27.103 --> 01:23:27.863 In fresh huh. 01:23:27.863 --> 01:23:28.303 Oh yeah, 01:23:32.075 --> 01:23:36.955 I enjoy listening to the show. It's a statement. It's a really nice statement. 01:23:37.155 --> 01:23:37.395 I like it. 01:23:37.495 --> 01:23:39.675 Doug, you might have been listening live because that came in this morning too. 01:23:39.715 --> 01:23:43.555 Awesome. Thank you, Doug. You're fresh. I love the name and I appreciate the boost too. 01:23:44.055 --> 01:23:46.815 Thank you, everybody who supported the show with the boost. We do have the 2000SAT 01:23:46.815 --> 01:23:48.095 cutoff just for time on air. 01:23:48.375 --> 01:23:51.555 And of course, we also have the membership program. You can become a core contributor 01:23:51.555 --> 01:23:53.055 or a Jupiter Party member. 01:23:53.355 --> 01:23:56.555 We really appreciate that. You also, you can just stream them SATs. 01:23:56.635 --> 01:23:59.435 It's one of the really cool things about the SAT streaming technology platform 01:23:59.435 --> 01:24:02.735 in general is you can do a boost message Or you can set an amount and say, 01:24:02.835 --> 01:24:05.675 this is my budget, and just when I play the podcast, we send the sats. 01:24:05.855 --> 01:24:12.935 We had 27 of you actually do that, and collectively, you stacked 69,437 sats. 01:24:13.195 --> 01:24:15.535 Not bad, right? Just listening to the show, getting some value, 01:24:15.635 --> 01:24:18.135 sending some sats our way, going to go right into our gas tank. 01:24:18.275 --> 01:24:23.375 When you combine that with all of our boosters, oh, this is a cool number, actually. 01:24:23.575 --> 01:24:25.775 It's got like a double meaning almost to it, I think. 01:24:26.055 --> 01:24:28.955 This is really cool. When you combine this with all of our boosters, 01:24:29.195 --> 01:24:36.015 we stacked a really respectable 451,000 and elite 337 sats. 01:24:38.435 --> 01:24:41.355 Thank you, everybody. I'm assuming those were the Canadian supporters helping 01:24:41.355 --> 01:24:43.375 Brent make it down the road, right? 01:24:43.555 --> 01:24:45.475 Gotta get home. Gotta get home. 01:24:45.495 --> 01:24:48.195 It wouldn't have been, you know, it wouldn't have been Texas Linux Fest without 01:24:48.195 --> 01:24:49.655 Brent, so we really appreciate that. 01:24:49.715 --> 01:24:53.175 That's right. Thank you, everybody, who helped us out. If you'd like to support 01:24:53.175 --> 01:24:56.255 the show and get in on the boosting fun, you can do it a couple of different ways. 01:24:56.255 --> 01:24:59.055 fountain.fm is the easiest one because they host 01:24:59.055 --> 01:25:01.995 all the stuff for you that's like you know they take care 01:25:01.995 --> 01:25:05.835 of it it's pre-packaged ready to go you just got to get connected to 01:25:05.835 --> 01:25:08.495 a debit card or get some sats in there but if you 01:25:08.495 --> 01:25:11.235 want to go the ultimate champion route you can 01:25:11.235 --> 01:25:15.215 do an albi hub it's a self-hosted setup from top to bottom that plugs into the 01:25:15.215 --> 01:25:19.655 back end of a lot of different apps so flexible open infrastructure and it's 01:25:19.655 --> 01:25:24.255 a lot of fun albi hub or if you just want to get started fountain.fm and thank 01:25:24.255 --> 01:25:25.335 you everyone who supports with the 01:25:25.335 --> 01:25:28.735 membership over at jupyter.party or linuxunplugged.com slash membership. 01:25:48.259 --> 01:25:53.039 So let's talk about our pick this week. Michael Arbel found this one over at 01:25:53.039 --> 01:25:57.519 Pharonix, but we had to include it because we still have such a soft spot for the TUI. 01:25:57.679 --> 01:26:03.339 It's called ISD, Interactive System D, a better way to work with System D units. 01:26:03.499 --> 01:26:05.399 Yes, ISD is a better deal. 01:26:05.579 --> 01:26:10.239 And it's a keyboard-focused, highly customizable TUI with some really fun features. 01:26:10.419 --> 01:26:13.719 You can quickly switch between system and user units, which is nice. 01:26:13.939 --> 01:26:17.359 The graphical interface is sort of split into two segments. 01:26:17.959 --> 01:26:22.699 making it really easy to read the list but then also read the individual unit and what it does. 01:26:22.879 --> 01:26:25.739 You installed it on your machine. I see you got access to the journal in there. 01:26:25.859 --> 01:26:27.859 You can see dependencies of different unit files. 01:26:28.159 --> 01:26:31.179 Yes. So not only do you get the status by default but it's really easy to then 01:26:31.179 --> 01:26:34.899 go see okay what are the latest logs for that unit and then also there's a cat 01:26:34.899 --> 01:26:37.959 tab so you can just see what is the actual unit file itself. 01:26:38.739 --> 01:26:45.099 Yeah you can do user or system wide and so actually it turns out we had this in a previous episode. 01:26:45.279 --> 01:26:45.879 No we did? 01:26:45.879 --> 01:26:50.039 It was literally the same month it first came out. So I think it might have been like a bonus pick. 01:26:50.219 --> 01:26:52.779 As a look, we've just seen this kind of being floated out there. 01:26:52.859 --> 01:26:56.679 But since then, it's been continued to be developed. They just had released 060. 01:26:57.219 --> 01:27:00.759 And since then, it's also been packaged in Nix. So it seemed like an appropriate 01:27:00.759 --> 01:27:03.499 sort of re-pick to now that's, I think, really usable. 01:27:03.779 --> 01:27:06.819 All right. You got a Nix angle in there. Well done, sir. Yeah, 01:27:06.879 --> 01:27:09.739 it looks good. And seemingly pretty simple to get going. 01:27:10.339 --> 01:27:13.519 And did we catch the license? We always try to... Yes. 01:27:14.359 --> 01:27:19.739 the license is, survey says GPL, I think 2? Why didn't they list it on the thing? 01:27:20.522 --> 01:27:25.262 But it's a GNU public license. And it is also mostly written in Python. 01:27:25.982 --> 01:27:28.882 83% Python. That'll get the job done for you. 01:27:29.002 --> 01:27:33.122 So go out forth, try it. If you want to send us one, you can boost in a pic, 01:27:33.162 --> 01:27:36.462 or you can go to linuxunplugged.com slash contact and send one in to us. 01:27:36.582 --> 01:27:37.502 Oh, yeah, it's GPL3. 01:27:37.882 --> 01:27:41.042 Yeah, I thought so. Yeah, we try to check. We try to check. 01:27:41.262 --> 01:27:44.042 That's one of the things, you know, somebody one time sent in a feedback item 01:27:44.042 --> 01:27:46.222 to the show saying, hey, could you check the licenses for the pics? 01:27:46.402 --> 01:27:48.742 And we try to do it every time. We really take your feedback very seriously. 01:27:48.742 --> 01:27:52.962 So it's linuxunplugged.com slash contact, or you can send us a boost. 01:27:53.642 --> 01:27:59.542 Assuming our race against time goes okay, next episode we should be back in 01:27:59.542 --> 01:28:05.302 the studio at our regular Sunday, 10 a.m. Pacific, 1 p.m. Eastern time. 01:28:05.482 --> 01:28:08.482 Yeah, getting some latest and greatest updates on what's going on with the Ubuntu 01:28:08.482 --> 01:28:09.882 desktop in their upcoming release. 01:28:10.022 --> 01:28:14.302 Yeah, and also we'll have our experience of checking in with System76 and getting 01:28:14.302 --> 01:28:17.462 a hands-on tour of the latest and greatest in cosmic development, 01:28:17.502 --> 01:28:19.302 too. Should have a lot to report. 01:28:23.902 --> 01:28:28.782 Of course, we have links and all types of things at linuxunplugged.com. 01:28:28.922 --> 01:28:33.262 It's a website, so there's just stuff you can put on there. It's awesome. 01:28:33.422 --> 01:28:36.282 All the RSS feeds and put in the all-shows feed if you like that. 01:28:36.422 --> 01:28:39.622 Yeah. You want links to what we talked about today? That's there, linuxunplugged.com. 01:28:39.662 --> 01:28:42.982 You can also find ways to watch and listen to us live over there. 01:28:43.062 --> 01:28:45.982 Too. Sure. Mumble info is over there, too. Matrix info is over there, 01:28:46.002 --> 01:28:50.382 too. It's just really, it's a resource. But what should they know if they're a pro listener, Wes? 01:28:50.422 --> 01:28:53.902 Oh, if you're a pro listener with a podcasting 2.0 app, or even, 01:28:53.902 --> 01:28:58.682 you know, these days with Antenapod, well, you get access to our premium podcasting 01:28:58.682 --> 01:29:03.662 2.0 cloud chapters, as well as transcripts with speaker diarization. 01:29:03.822 --> 01:29:07.662 That's right. Speaker diarization in the right app. How fancy is that? 01:29:07.862 --> 01:29:10.842 Thank you so much for joining us on this week's episode, and we'll see you right 01:29:10.842 --> 01:29:12.902 back here next Tuesday, as in Sunday.