679: The Last Shutdown

Why not make it a Linux Tuesday on a Sunday? Join us Sunday, 10am Pacific, 1pm Eastern. And remember, if you want more show, we got that LUP-LUG every Sunday before the show, getting together. LUP-LUG details at our website. And of course, links to everything we talked about today. Technically, everything we've talked about in the past too. And how to contact us, Mumble Room, Matrix, all that, LINUX Unplugged.com. Don't forget you can support us at boost.jupiterbroadcasting.com. Thank you so much for joining us this week. Whoa, whoa, you're not gonna tell them? We got all kinds of special stuff in the feed. We got JSON, we got cloud chapters, we got transcripts, we got an MP4 file in there! What?! Who put that in there? A whole giant MP4 file. It's actually not that big. Did you stick that in there? Yeah. Alright, alright, we'll see you next Tuesday, as in Sunday. And don't forget about that livestream. See you next week. Same bat time, same bat station. Alright, normally I think we'd be done right here, but before we wrap up, I just want to say thank you to our friends over at Define Networking. Define.net slash unplugged. Go over there and check out Manage Nebula from Defined Networking. It's built on the open source Nebula platform that we love and use right now. And now you can take advantage of their automatic lighthouse, or you can add your own or combo it all up. That's the thing. It's control. And that's what's big for me because it's my infrastructure. It's my network infrastructure. I can own the entire stack. I can turn it on. I can turn it off. I control it. And I can use their lighthouse if I want. I think that's fantastic. And Nebula is lightweight. On systems that are sitting there idle, it uses very little CPU and network. Some of the other solutions, real chatty. Constantly chatty. And that matters a lot when you're running across your entire home lab, on your remote systems. Maybe you're on a Starlink. It matters. And the great thing about Nebula is it's built for scale from day one. With strong encryption, decentralized by design, it stays resilient. So get started. 100 hosts for free. No credit card required. Go to Define.net slash unplugged. That is Define.net slash unplugged. Big thank you to Define Networking. All right, boys. Before we run, we've got some picks to get to. And I wanted to hit you with a strange one. This is a big one. It's LAN Orangutan. And it is a lightweight network scanner that goes through and labels your network. But it is easy and simple. But yet efficient. Take a look at it. What do you think? What was your first impression? Yeah, it's clean. So, like, we've talked a lot about tools vaguely in this camp. But, and sometimes I like this, but often you kind of get information overload. You're like all kinds of details, hardware stuff that I probably don't need for whatever it is the task I'm actually trying to do. And maybe I don't need it for, like, ever, right? I just want to know for a little while so I can spin up real quick. Whereas this just looks like a very clean dashboard you could take a quick glance at and get a sense for what's going on. Here you go, Brent. So when you get moved, when you get your network going, I want you to pop this thing up and take a screenshot for us. All right? It's a self-hosted network discovery tool for home labbers. And it has tailscale support as well. Oh, and there's a CLI. I like that. It's got dark mode. Auto discovers your devices, password protected. What do you think? When you get your new LAN online? It looks like it's been around a while, too. Yeah. I mean, I have not really done very good network monitoring, I have to say. And just last week, I was like, huh, I should probably know what's happening on the network here wherever I am. You know, I'm kind of in charge of the network wherever I seem to end up. So I should do better. And this is maybe a tool that can help me do that. So thank you for the picks. Do better. I like they have a philosophy in here, actually, which we kind of touched on without maybe even fully realizing. LAN Orangutan isn't trying to be the most powerful scanner out there. And that's the point. It's built to be the simplest and the fastest one to reach for. There's a bunch of already excellent, deeply capable tools in this space. And they're the right choice when you need everything they offer. LAN Orangutan is for the other times. LAN Orangutan Also, you know, you could, if you're a Clanker user, you could have the CLI kind of do these audits. And it'll do the output as JSON. And the Clanker can take that in. You could just spin up this thing, do a little network scan, and then get a Clanker report. LAN Orangutan Even CSV if you have like an enterprise Clanker. LAN Orangutan I'm going through like the docs here trying to figure out where the naming comes from. I don't think I found anything. So, listener, if you have any ideas or theories or, I don't know, make up some reason why the Orangutan is the LAN expert, you let us know. LAN Maybe it's a reference to another tool. I don't know. MIT license on that one. And then really quickly, this isn't going to surprise anyone. I just had to give it a shout because it saved my bacon a couple of times in just the last week. I'm kind of embarrassed. It's called LocalSend. I don't know why. It's just there are so many of these stupid open source send a file from one computer to the other that it almost feels embarrassing to even have a pick. But I like LocalSend because it's a local app on every OS. So, like on the desktop, it's a desktop application. On iOS, it's an iOS application. On Android, it's an Android application. I did a little spelunking. Uh-huh. And it's interesting that it's finally landed because we talked about it ages and ages ago on the show. Yeah, I know. You and Alex talked about it on a self-hosted episode. But it felt like maybe it was one of those picks where it's like, oh, this is cool and seems useful. But then if you never actually deploy it, you don't quite use it. So what changed that you're using it? So I was taking pictures of the chickens and whatnot. And I wanted to transfer them to the desktop. And there's just not, from the iPhone at least, not a lot of great options here. If I were on Android, I might use KDE Connect. But so I set this up. But then because it works across Android, it works across Linux and iOS, then it was like, well, let's all just use this. And it'll queue up downloads too. The desktop app's pretty nice. You can auto-accept files from certain favorite people and things like that, which is really nice. Like I just grabbed this and I just want to blast it over to the machine. I don't have to be at my desktop and approve it. And so it's like one of these things where, you know, I've actually been using this. And I don't know if we made it an implicit pick. But we have talked about it before. Also, it's all local, right? So there's no routing through the internet or anything like that. So it's as fast as your LAN can blast the file. This is one of those apps that since the last time we talked about it, it's been installed on my phone. I guess and my laptop, which I, is it? And on my phone, every time I go like, you know, do some spring cleaning on my phone, I'm like, well, I only use this once, maybe twice a year. Yeah. And then I will always land with, well, you never know. I'm going to keep it. So this has been installed for a very long time for me. Used it a couple times. It saved my bacon. But it's nice. What I appreciate about it is like, if I'm transferring some drone footage or I took some pictures of the kids or the chickens and I want to do a batch, it's really good at a whole bunch of files too. And then on the desktop, I get like a visual status progress of all the files transferring and stuff. So I like local send and it's available on FlatHub and it is Apache 2.0. I figured out what's going on here. Well, it's 17.5% rust. Oh, yeah. Do you think that justifies? Well, the rest of it, it's Dart. I know you're a big Dart guy. Big Dart guy. Huge Dart and Flutter fan. Make a lot of choices in life on that. You know? That ATM uses Flutter, I'm picking that bank. Yep. That's how I roll. Now, Brent... Before we get out of here, I have a sneaky pick for you guys. Yeah, I want to know about this. You snuck it and we don't have any idea about it. And I think, I mean... Yeah, the council didn't get to approve it. Usually when that happens, it means it's a banger. So we'll see. Hasn't even been vetted by the bot. I've been toying with this one for the last couple of weeks. We've been on the show really enjoying OpenCode on the desktop to do a great variety of things. And I have deeply integrated that into my everyday workflow. I wanted something similar on the phone. On the phone, it's often just the chat app kind of interaction that at least I've found. And, but I wanted something simple and yet powerful. And maybe that's asking too much. But I came across something called Oxproxion, which surprisingly... Say that again? Oxproxion. That's a fun name to say. Surprisingly, I only like read it once. And then it's a very memorable name for some reason for me. It might not be for other people. Sounds kind of dark maybe. But it's just an Android LM chat interface. But it supports OpenRouter, which we love. And you can also have it support a bunch of locally served models like OLAMA, LMStudio stuff, LAMA CPP. And also, Chris, Hermes Agents. Heyo, really? I like that. So it's kind of like a nice mobile interface to, you know, your favorite providers. But it also has some pretty powerful features in there. And some of it is, and I haven't played with all of these, but some Android tools. So it can do stuff like read files, make files on your Android. Ooh. But also take control of like timers and alarms and calendar events and stuff like that. On your local Android? Mm-hmm. Mm-hmm. Now that is promising. All right. So you can use it to automate like a calendar event on your phone? That's what I'm thinking. Now this has not been tested or vetted by me yet. I see this could be super useful. I do hesitate slightly because I don't know. But it seems very promising. So I've been using this for the last couple of weeks. I will say the interface is all symbols. And therefore, you need to just trip over what the symbols mean and try to figure it out. But once you do, it's pretty powerful. What do you mean? I see tons of text. What are you talking about? Yeah. Like all the model selection is text and everything. Yeah. That's like kind of one of the back interfaces once you hit one of the buttons. Ah. Ah. Yeah. Yeah. Okay. So that's my only gripe about it, I would say. Other than that, you can save conversations and bring them back up and continue them. And I assume you're able to install this with Obsidian, I assume? You are able to install this with Obsidian. Obsidian. No, not Obsidian. What's it called? I always remember this one. I do that all the time. I do that all the time. I see an APK on GitHub, which is usually a good thing. They even kind of have semi-similar icons. I know. That's my theme. It's the worst. Because I have like an all-black icon theme. It's, ah, yeah. So Obsidian grabs basically APKs straight from GitHub. It's awesome. You can definitely do that here. It's also an FDroid. That's where I found it. It also will connect, obviously, to a local Olama instance. Because it's, it's, it's, it's, it's Model Agnostic, which is right. Mm-hmm. Mm-hmm. So? Oxproxion? Oxproxion? Oxproxion. Hmm. Mostly written in Kotlin. And it is Apache 2.0 licensed. Well, there you go. This seems like giving a try. Good find, Brent. Look at him. He's fully immersed now. There's no getting him back. It's your fault. Now all we need is like audio support maybe in this thing. Yeah. Web RTC. Indeed. Hmm. And now it is time for Le Boost. Well, we're going to start out with a heck of a baller boost, boys. So get your seatbelt on because I'm glad we got them retrofitted. Lutris, um. Lucidropy. Yeah. Lucid, kind of like entropy. But with Lutris. Yeah. Right. Comes in with 314,659 cents. Hey, Rich Lobster! That is great. Woo! He says, pie for your efforts. Thanks for all you do. Been trying out Hermes with Open Router using Nemetron super, super, super. Nemetron's gotten surprisingly good. And popular. Mm-hmm. Trying to find a cost-effective model that are also good at network management, say like an OpenWRT and playing with NixConfig. Nice. With the NixOS MCP and troubleshooting on Arch and Ubuntu occasionally and writing some basic Python bash scripts to automate tasks with occasional small coding projects. I've been using Cloud Code for most of this, but want to move away from that. Any suggestions? I prefer it open source. So, Wes, this is probably a best question for you because you've even gone as far as renting some GPU and running some models directly in the open source space. So you probably have the most hands-on experience. It kind of depends on, yeah, are you trying to run it yourself? Then you're going to be mostly constrained by what token rate do you need and how much RAM or VRAM you have. Sounds like he's open to Open Router, though. Yeah. And so for there, I mean, one version is just go take, you can curl their API or have the bot do it, and then it's pretty easy to check out what are good prices and what are currently free. And then you can easily sample all of those. Obviously, there's the latest version 731 of DeepSeek that's been quite popular and works very nicely. Quen 3.7 has been pretty good. There's also a new Quen 3.8 Max, I think, floating around. And there's a bunch of more interesting ones like Ling or Laguna or Longcat that kind of pop around that show you what smaller labs can do that I think can be fun to evaluate. But I probably get the most use in terms of open weight models that I pay for per token out of DeepSeek. And I also like Memo a lot because it's pretty good and it's got vision. I would also add maybe hang on to the Claude subscription for a couple of weeks, try these out, and then audit what they produce with the Claude code. There you go. And then when you find something that you like, yeah, you stick with it. And then you can wrap up the Claude code subscription. I think that's probably a decent way to go. Can I suggest maybe a wild card here? Yeah, you got a wild card? Go for it, you wild man. So I've been doing a lot of these very tasks. Open WRT configurations. Check. Nix configs. Yep. Check. Check. Made that system way better. So I think I fit really well in this one. And I have found an insane amount of value and speed out of DeepSeek V4 Flash. And it is so cheap. It's super fast. Yeah. And it's like with a little bit of structure around it, you know, with your own skills and stuff, super, super powerful. So if you don't want to spend a ton, that is a huge recommendation for me. I don't think it would maybe beat any of the other ones. But if you're looking for something really simple. Get a good harness, get some good skills, and go DeepSeek. See how it goes. I think it's a good tip. Well, our buddy adversary 17 comes in with 56,017 sets. I hold that with your kind covet. Thank you, sir. Reverse Linux process is restoring a backup. You should go in depth about backups. Backups? Sorry, I fell asleep. But that isn't a horrible idea. You did mention it earlier in the show. This is a very on-topic boost. Because you may have noticed things are a little different this time. I think actually the reverse Linux here would be to do a recovery from your backups. Because most of us don't really do that part. And that's the most important part, isn't it? Sure. Sure. Sure. Right. And it's because it's kind of going backwards in time when you do that. Mm-hmm. Yeah. Okay. Well, we got a bunch more from adversaries. Including adversaries has gone to Plaid. What the hell was that? Spaceball 1. They've gone to Plaid. And it's a time travel boost. Cool. Which makes sense given the sound effects. Yeah. A little bit behind, but I just converted my desktop PC to Nix OS. Oh, all right. I used Nix to build a custom installer ISO so that I could verify everything was hunky-dory before doing the needful and having Disco wipe the Pop! OS install. Now that's the way to do it. Doot, doot. In fact, just to celebrate, I mean, the next boost really fits because it's boosty, boosty, boosty, boosty, boost. Oh. Oh. Hold on. That's a special request. You don't just boast those out everywhere. Actually, but for the occasion. Soop, soop, soop, soop. Boop. There you go. Adversaries chooses to run the Zen kernel. Performance, baby. Ah. So we got a Zen friend. Yes. And on top of that, thank you for covering all the kernel stuff. I know it's a lot of work, but I love hearing about it. That AMD regression in 7.2 would affect me since that's what my desktop runs, so I'll keep an ear open for the fix. I assume also you're very concerned about AppleTalk getting removed. Well, naturally. We have a sticker for that. A badge? Yeah. Yeah. We call it a badge. Yeah. A sticker. And the final adversary message here. The backwards show idea sounds so fun. All you got to do is read everything backwards and then have Drew reverse the track. You know, this backwards, we're never going to do that. That's too cliche. We would never do that. All right. What are we doing? Thank you, adversaries. Nice to hear from you. We have a boost here from Greg the Lawyer, 53,403 satoshis. All right. Greg's in the chat, 52 years old, and says, this is a zip code boost. Hey, it's been a minute. Yes. Zip code is a better deal. Did you bring the... You know I did. Oh, good. Here we go. Nice. Why is... We get you the tablet. Why does it make paper sounds? Wes, you're holding it wrong. I hacked those in there. I had to jailbreak it. Yeah. Wes, are you holding the back first? All right. There's still gravy on here from the kids' trip. What is taking you so long? Where is he? Well, this will explain it. Okay. All right. Zip code 53403. Let me double check one more time. Yep. 53403. I got to check the index. Uh-huh. That is located... Is this right? I got to be sure. Oh, my God, Wes. It's racing Wisconsin. Hey! Hello, Wisconsin! Make it so. Thanks, Greg. I mean, on the map here, I see a Mount Pleasant nearby, so it's got to be nice. Oh. Let us know if we got it right. Good to hear from you. And thanks for helping test out the old ZapRite stuff. Yes. Letting us know when it was not working. Dajag comes in with 4,747 sats. Just pump the brakes right there. You guys, you blew my mind with Noster. I played around with it back when you first started talking about it, but I don't think I'd ever really understood what it actually was. I just thought it was ActivityPub with keys. But I think I was missing the point. I don't know if I'm going to use Buzz long term, but I am setting it up now. And if nothing else, this was an eye-opener to the catalyst of connecting all the dots. Nice. Thank you. Well, thank you, Dajag. Awesome. That's amazing. I think it also kind of did a little bit of that for us in a way, too. I agree. It was like, oh, yeah, that's kind of what we were thinking. Here we go. Yeah. Dajag, I would love to hear if you stick with Buzz. Let us know how it goes. Marcel Boussin, 17,014 sats. Tough little ship. Little. You made the torrent analogy again, and I have to push back. I see a huge difference between individuals stealing from companies for entertainment and companies stealing from individuals at scale for profit. It also especially stings because Dario is promising to replace developers with a model trained on open source developer contributions. Nobody sets up the R stack to train a model to replace VFX artists. Now, I'm not arguing that torrenting is ethical, and I don't let the way the model was trained prevent me from using it. The cat is out of the bag. The people who trained it are benefiting. Why shouldn't I? Okay, so I think we're just sort of both talking past each other. What I've talked about before is, you're right, they are not comparable. The tech companies stealing is worse. However, the moral alignment remains the same. If you've stolen content yourself, you really don't have the moral authority to condemn another. But additionally, torrenting the TV shows and the movies does undercut the ability for the industry to produce future movies and TV shows. So there is a similar impact at the end of the day. So I still think it stands that if you have a RAR stack or you've torrented TV shows before, you don't really, really have a lot of moral authority to stand on and be concerned that Anthropic is scanning books or something like that. You cannot like it and you can think what they're doing is worse and I would agree with you. So, but at the same time, you know, it's a nuanced issue. So to each their own. I would also, I think, extend the frame to be like, that's one particular sort of test case, which can be a useful model to have. But the larger issue is sort of like around what do we think about information in the commons and copyright protections and that kind of thing. Yes, yes, yes. Probably that's where to fight to have a consistent framework that we kind of agree on because the current rules we have, I don't think really anyone thinks are optimal. Yeah, like I'd like to see a revolt that steals the rights of Star Trek away from Paramount. Yes. Let's return it to the people. That's right. That's right. Gosh. Well, Gene Bean boosts in three rows of ducks. Here's a quick note for others in the community with kids in Scouts. I just got back from Cub Scout Overnight Camp at Cherokee Scout Reservations in Yanceyville, North Carolina. It was really good and well worth the seven plus hour drive. I'd highly recommend others check it out. CSR.camp. That is a recommendation indeed. Yeah. Listen to podcasts while you do that seven hour drive. It's good for the kids. About Linux Unplugged 677, in addition to the BBS you talked about in this episode, check out TC Squared BBS. It has some code here. It links to it. Yeah, we got a repo GPL3, a BBS server for MeshTastic for posting bulletins, sending mail to users, and a channel directory. Could somebody give us a gift of setting this up so we could play with it? Careful what you wish for there, Chris. No, I mean, we work on a lot of the shows. We never really ask for that, but it would be really great if somebody wanted to set this up and then just kind of show it to us and treat us. That'd be fun. You can have a clanker do it. That's fine. Well, our dear Gene has a last question here for us. Do you all have any suggestions for making the information in many years of Slack conversations available to an agent? Oh, man. It's such... Adding agents to Slack is why Buzz is a thing. Yeah, really. Really. Because that's what you got to do. You got to add it to Slack. You got to do all the API crap, and then you can add it to every single freaking room. Maybe if you pay for Slack, they let you export in a format you could ingest. That's what I was going to say. I would know. That'd be your other action. Yeah. Escape it now, and then you search on the future things. Right. Gene, if you could tell us, let us know. Yeah, if you find out, we're curious. Yeah, please do. Thank you, Gene. Magnolia Mayhem comes in with 2,000 sets. He's a good guy. He's a real good guy. No, he's a great guy. Forgot to boost. So he's coming in hot with a boost. Thank you very much, Mayhem. Nice to hear from you. Time for our member boost. Let's do it, boys. We got some anonymous member boosters coming in. That's always interesting. I thought this was from anonymous. Maybe we just have a member that goes by anonymous. That could be. Yeah. We can't really tell. Great coverage as always. That's one. And then a second anonymous boost. Yes. In the same vein as your OBD2 AI-assisted diagnostics, I've connected my oscilloscope to my agent via its Ethernet interface and standard control protocol SCPI. Oh, man. Now I can have my agent watch waveforms and decode serial connections. You guys got my wheels turning. Thank you. And then we got a scope ID, an SDS1104X0-E. E. Searching. I would love to have an oscilloscope. This is great. See, you know. That's great. You got the. Maybe we help with the wheel turning. If so, thank you. Now you're getting our wheels turning. That's how this works. I'll tell you what I would like to do. And this is. I'd have to have money to burn and time to burn. But maybe in a few years. I want to do a totally agent-managed fish tank. You know. And then we live stream it, right? Managing the levels of pH, everything in there. The temperatures, the water flow, the filtration, the feed, everything. Fully managed. Automated fish tank. It books people online to come clean it. Right. I think like a lot of it would probably be home assistant driven. Like all the sensors and all the data and all of the actuations. That would probably be home assistant driven, managed by an agent or something like that. I think that could be a thing. We have a members boost here from Anton. Hello, Anton. Sorry for the late feedback on Buzz. It was very interesting to me since I'm trying to find a way to create and use AI assistants at work and share them with my team. I sent a message a few weeks ago about using Hermes at work. Do you know if Buzz can be a full replacement for Hermes? Yeah. I mean, it's not feature complete, right? But it is essentially an agent orchestration platform or you could connect a Hermes agent. Yeah, true. That might be the most easy way to go. I think the main thing was that we hadn't quite gone super far into getting a bunch of MCPs configured and that kind of stuff. And that'll be the thing probably if you're trying to do it at an organization that'll really matter. I do think, Anton, though, that is like the scenario for it. Because people, especially that are new to agents, you know, why not start with something like Buzz? And then if you need something more advanced from a Hermes system, you just bring it in later. Yeah, because really it's like where it's lacking is sort of on the harness side. But what it has from the start is the identity layer from Noster and being built with agents and humans co in mind. And the group chat stuff. Right. My turn. Jimmy comes in with a free member boost. Can we ask the video game correspondent why GOG doesn't get more love? We sure can. I think that'd be you, PJ. DRM free means you own it forever and they've got a preservation program. I like Steam, but there's some real overhead there. Just yesterday, I wanted to add a game to my wish list, but couldn't be done without 486 megabyte download. Really? Just to your wish list? That seems small. PJ, why don't you think GOG gets more love in the Linux community? Is it just Steam sucks all the oxygen out of the room? I would say because of convenience and because of all the hard work that Valve is doing to bring gaming to Linux in such massive force with hardware, software, etc. GOG has been around forever. I love DRM free games. I've got a bunch of them. But the convenience of Steam on all of our systems can't beat it. Yeah. Yeah. Yeah. I think there's a big part of it. And then there's branding. And then also, there's got to be a factor of people coming from Windows. True. Very Steam focused. Not that GOG doesn't run great on Windows, but yeah. Maybe we should give it more love, Jimmy. Thank you for that. It's not talked a ton about either, but Valve has given a lot of information to people. Or how do I put this? They've come out and said, you know, we understand we're a software platform, but we're going to ensure these games work even after we're gone. I actually have faith that they're going to do that. So if Valve ever shuts down Steam for whatever reason, I do believe they're going to make your games still accessible and playable somehow, someway. They've come out and said this stuff before. All right. Thank you, Game Correspondent PJ. You want to take a... Digital Jote boosts in with what I'm going to say is a controversial boost. Oh, here we go. Hot boost. I don't understand the issue with Brent's tabs. What's that? I think the song explains the problem. Yeah. Well, Digital here says every time I start Firefox, I open my previous session. Uh-huh. It's currently 712 tabs over 18 windows. Oh! Oh! I'll occasionally trim it down, but this is pretty normal. My goodness. Is that more or less than you, Brent? Do we have a new king? And, like, what is the oldest tab there? A year old? That's a fascinating question. At what point is it, like, stuff like when you move and you just leave it in a box and you never, like, open it? And then you come back to that box five years later and you're like, oh, I can probably just get rid of this. But it's a whole window. 712 tabs over 18 windows. Does that sound on par, Brent, or kind of a little bit beyond what you're doing? I would say it depends what you're measuring. 18 windows, not unusual in any way. 712 tabs has only happened maybe a couple times. Is that because low or high? Wild. Oh, very high. Very high. I feel like we need to stage an intervention. To me, it's just absurd. So maybe it's, is it the windows the real problem here? We've been so focused on the tab thing that's the windows. No, it's like when you discover that a loved one is a massive hoarder and, like, you go in there and, like, oh, this room's pretty bad, but it's probably just this one room. And then you go in the next room's like that and the next room's like that. That's what this is, but it's the digital version. I don't know. I think I can answer the question at least. We haven't quite answered the question yet. Oh, okay. Was there a question? Yeah, I didn't know there was a question. Oh, wait, no, there's just a bunch of statements saying I'm doing it wrong, but yes. No, I think they agree with you. No, I think they're on your page. Oh, oh, oh, I thought they meant what's Brent's issue with the tabs, but they're, no. No, they're normalizing your behavior. Oh, Joe, I like you. This is why we have a problem. No, no, no, you guys are doing it wrong. Mostly my issue is window management and slow boot up times. I'll take Greg the Lawyer, a free member boost, because Greg was also our baller boost. Tesla Model Y update. I'm still rocking the factory LTS software release. Oh, yeah, right. There's, when you get the car, there's like a delay. They don't want to like change anything on it. I see, yeah. I'm already blown away by FSD, and I'm anxiously awaiting my first official rolling release update. In other nudes, I have always bounced off terminal multiplexers, but I'm really enjoying Herder, H-E-R-D-R, and its agent awareness. I'll have to look that up. Yeah, that's one I've been looking at as well. It's kind of nice. The runtime your coding agents live on. Apache 2.0 license written mostly in Rust. Jeez, I like the UI. Huh. Yeah, love FSD. It's going to be a shocker once people try it out. It's the number one feature of the car. Thanks, Greg. Congratulations. Thanks for the report and for the pick. SensorSmile has a member's boost here. I couldn't wait, so I just spent several hours during vacation last week learning Hermes. Ended up pushing me to tune a Llama CPP quite a bit, as well as spinning up a second Llama 3B for compressing context window. Been working on a side project I never thought I would get to. Thank you for convincing me to do this. Dude, you're doing it great, too. I think that's a pretty good strat, having a separate agent just monitoring your context and doing compression for you and probably being really smart about it. Paul comes in about copyright. For books, audiobooks, and music from mostly small local indie brands, I handle it this way. Can I buy it in a way I fully own it? Physical media, DRM free. Then I pay and vote with my wallet. Otherwise, I don't. With games, I prefer DRM free, but often buy on Steam as well. Yeah, it does get tricky when living in a small space to have that kind of stuff, but I have quite a bit of books just sort of scattered around the RV, and I may still end up grabbing the audio version, too, or something. But I've been an Audible customer since forever. I probably put one of their kids through college by now. I kind of wish that in the RV you just had a big, dedicated rack of cassettes, took up a huge amount of space in the limited area, but you insisted on it. Yeah. Dragging it around the country. Sorry, kids. No road trips anymore. We got to keep Dad's tapes. Hey, what did we find? We found a really nice physical media and all my stuff when we were moving me out. Oh, yeah. You did have a good collection. Yeah, you did. What was that? It was a seven, like a video disc? No, that big, huge. Oh, yeah. Yeah, the laser disc. Yeah, laser disc. Jackets, bags, and laser discs. That's what Brent collects. That's what we learned. If anyone wants to pay me a lot of money for a video disc, please reach out. You want to take our last one there, Wes? So, hey, I'm gee. Remember, boosts in. If other professions like doctors, electricians, or civil engineers screw up, they face scrutiny, sanction, and possibly a ban from their profession. But if the computer people pull this CrowdStrike, US East 1, or Cold Guard, they say oops, and it's largely forgotten. Is licensure overdue? The duct tape is coming apart. Mmm. Hot take. Hot take. I don't know. It's tough to say, right? Because you never really know, especially in free software, how someone's going to use it, and what conditions it might be under, and then what edge cases might get exposed. Like, it's tricky. Pretty, pretty quick. But I've always wondered if one day we won't be at some, like, this software was written by a certified human. You know? Something like that. And I mean, I suppose you've seen more with things that do get, like, security audits or other, you know. I wonder how much sort of curation or post hoc verification will become, you know, a necessary prerequisite. Right. Right. There'll probably be entire specialties around it. All right. That's all the boosts above the 2,000 sat cutoff and our member boosts. Thank you, everybody. Also, you sat streamers out there, 16 of you stream sats, and collectively stacked 28,069 satoshis. Make it so. Thank you very much. When you combine that with our fiat boosts and our regular boosts, I think it was all regular sats, actually, this week, we stacked a grand total of 454,606 satoshis. Thank you, everybody. This show really does live and die on our memberships and our value. If you hear dynamic ads, that means we're scraping by and we need your support. And then we have quite the hole to dig ourselves out of. In the meantime, you can boost at boost.jupiterbroadcasting.com. We always love your participation because this is, for us, the most fun segment of the show. And we really have no idea what you're going to bring up. And, of course, it's a great way to get a message in, too, while sending a little value our way. Boost.jupiterbroadcasting.com. I've been taking my Berkeley Life Nitric Oxide support daily, and it's been pretty easy to stick with because it's just two after a meal. Even I can remember that. You know, initially, what caught my attention, right, is the connection between nitric oxide, blood flow, cardiovascular wellness, energy, and just vitality overall. But I have sleep apnea, and so my sleep is just not where it should be as a baseline. And that kind of stuff, it compounds over time. So I've been especially interested in finding simple, proactive ways to support my energy and my wellness. What I'm really liking about Berkeley Life and what makes it stand out is the ability to test your own levels at home. This trip's taking me about 15 seconds to use. I tested before I began this, and my levels were very low. Like, oh, but I got a baseline to work with, at least, right? So I've been continuing to monitor, updating my numbers. I like what I'm seeing, and I like having something measurable instead of just wondering if the supplement is doing anything. You know I'm tracking that data. That's the appeal of the No Starter Kit. You get the nitric oxide support supplement along with the test strips, so you can follow your own progress over time at home and with me. So go to berkeleylife.com and use the promo code LINUX15 to get 15% off your first order. That is B-E-R-K-E-L-E-Y-L-I-F-E.com and use the promo code LINUX15 to get started. These statements have not been evaluated by the Food and Drug Administration. The product is not intended to diagnose, treat, cure, or prevent any disease. Well, you boys helped me move out of my place recently, and I've been jumping around all over the place and thinking, uh, how many computers do I own? So some decommissioning has happened on my side, or at least thinking about it. But the studio has far more systems than I even can count over there, and so we've been thinking about changing things up a little bit. It has become time to decommission an old box. A beloved box! A box that's still technically working just fine. It's one of those things, right? You're kind of like, well, you're not actively making yourself a problem. You're not the thing that's preventing the show. You're not constantly getting in our way. And yet. And yet. We find ourselves here. Yeah, it's the problem is it just is an old Linux box with sort of forgotten services that's been running for years. I think it's, you know, it's a four and a half year old box install, but the hardware itself is extremely old. It's a Dell T5400 with quite the energy budget. It has a Xeon processor in it, and it also has eight four gigabyte modules, so 32 gigs of ECC RAM. How many secret Xeons you got running around in this studio? That's right, baby. I love ECC. I knew about this box, but I didn't know it was a Xeon. Yeah, an E5430, so that gives you an idea of the age, at 2.66 gigahertz. Now, if you didn't have it fully loaded up, it would approximately use 1,120 kilowatt hours a year. But it is loaded up, so it probably uses more than that. So it's got a pretty serious steady power drain. The hardware is old. It produces quite a bit of heat. The BIOS is dated August 21st, 2008. Great vintage for BIOSes, yeah. The root file system was created January 5th, 2022. So it's about four years and seven months old. So this is the box. Something tells me it's got a real new kernel on there, probably, right? Okay, so it's running Ubuntu 20.04.6, which is no longer supported, running Linux 5.4. That's so ancient in our computers. I know. This is just a bygone era. So much has changed in four years on how we manage systems. Yes. So I think that the job is to figure out what's using this that we don't know about or anything weird about this system that maybe we've forgotten. Because it's probably a lot. Yeah. And then see if we can safely decommission it. Now, the role that this machine plays, and Wes, I don't know, can you SSH into it? Are you able to SSH? You'd have to be on my tail net. Yeah, let's take a peek here. Otherwise, I can SSH in. I have quite a fond connection to this box, I will say. Uh-huh. I was wondering if you remember. Uh-huh. I didn't know it existed until this very moment, and somehow it just showed up ready for the job. But this was, what, five years ago? Something like that, it feels like. Chris and I sat down. Four years, seven months. Four years, seven months ago. Chris and I sat down one winter and came up with some crazy ideas. And the boosts came out of this very moment where we just loaded a box. This was a temporary box. We were just doing a little bit of testing and see how things would go. And here we are many years later. And this box has been critical for the show in many ways. I think the, don't the boosts, I don't know, somehow this, the boost read off this thing. It's been important in the past. That's one of the things we got to look into is if this is in the boost scraper pipeline, we got to look that up. We got to figure that out. Because it may be powering some of the backend infrastructure stuff there. Mm-hmm. So for me, it was like a new era when this box got turned on. Oh, we learned so much that January. Yeah. Yeah, we did. You're right, though. I forgot this was temporary. This was going to be a temporary. Well, what is temporary? You know? All right. So that's the system. It's time to shut her down. I'm expecting when we log in, we're going to see a handful of containers. I think. Oh. Oh, yeah? I recall. Oh, there's memories around this thing. We're going to see plenty of free space. I don't think that's going to be an issue. But I bet, you know, in fact, I bet it even has enough RAM. The problem with this thing is that the disks are slow, slow disks. All right. So, Wes, what is the – it sounds like you've already found something fun. What are you spelunking into over there? Would you like to guess how many containers we are running? Well, okay. Yeah, I could. You take a guess, and then I'll stay and listen for a while. So you got – let's see. Poor – Okay, let's hand one done. Okay, so I'm going to say this thing should be able to do everything in seven or eight containers. Everything you need should be done in – okay, what do you think, Brent? Well, I have memories around you troubleshooting containers specifically on this box, and it was – I've never seen you more angry at a computer. Right. Because – Well, because the issue here is it's like this – they bring this node management software called Umbral brings their own, like, Docker orchestration layer. Seems like a great idea. They're Bash scripts, and then they have a monitoring script called Karen. And I don't know if they call it this anymore, but it's still on my system called Karen. And then Karen starts screaming about issues because she's like a system monitor. And so you have their Docker manager scripts, their start and stop scripts, and their Karen scripts. And that's how they managed everything. And you had to use that to interact with it. And that's how they did, like, boot dependency resolution and all kinds of stuff. So what do you think? What do you think the number is, Brent? Give us a number. Well, I recall it being surprisingly multiplicity. So I'm going to say 18. All right. All right. It should be doable in seven containers. He says 18. What do we got, West Payne? What is our counter? 59. What is it doing? That's 50 more containers than it needs. What is it doing? Wait, what is happening? Can you give me an overview of what some of that is? Wow. So a lot of it is, like, sidecar Tor. Tor for everything. Oh, right. Everything has its own Tor sidecar. Oh, my. So there's AppProxy. There's L&D, of course. A bunch more Tor. Lightning Terminal. Tor is just not the way to self-host stuff. Electrum Wallet. Oh, my gosh. Elements Web. Sure got it. Something we just call, oh, Mempool's Front End. Yeah, got it a Mempool. You got to have a Mempool widget server. Uh-huh. Uh-huh. You got a widget server. Restarting 54 seconds ago. Oh, yeah, that one's not good. Mempool Back End. Yeah, got it a bit. I2PD. All right, all right. I get it. I get it. It's a lot of stuff. God. Just the Tor containers alone. Something from CryptoSharks 131. What? That wouldn't surprise me at all. Oh, wow. Okay, okay. You were right, though, in terms of usage of things on here. End Prox shows for free dash H here. We got 20 gigs available, 31 total, 10 use. So we're sitting pretty nice there. And on disk, we got 450, 460 gigs on the root drive. Okay. But only 34 use. So that's only at 8% use. So tons of space on root and then on slash serve, where all the app data lives. That's a 7.3T setup and only 1.1T is used. So that's a 15% fault. So there's tons of disk. Wait a minute. Wait a minute. Wait a minute. You've been looking for disk. I mean, yeah. I want to turn this thing off because it's loud and hot and uses a lot of power. But I don't also just want to throw away seven terabytes almost of disk. It's ButterFS, too, if I recall. So, you know, there's that. There's another one of our mini ButterFS. Yes, that's right. SDB1 is a ButterFS array. So cancel the segment. We're going to keep it on. Is that what we're doing? Wait a minute. Hold on. It's only one disk. It looks like. I just see an SDB1. Yeah. Yeah. I think that was part of the temporary. Yeah. We found this disk in one of your drawers in the studio. Yeah. That's why this is only going to be one of the reasons it's only going to be temporary. Right. We meant to. We did a single disk setup for something that's kind of central to the. Sorry, guys. And then forgot about that. That's. That honestly is a little bit of a surprise to me. I not normally. I don't normally for these kinds of systems just do a single disk. I'm pretty sure we had a to-do list somewhere. Probably. Probably. Probably. I mean, it feels like, you know, looking at this box, it's like, it's like ancient, like, Linux archaeology here. I mean, look at this. 180 pending security updates. Seven pending security updates that are covered by ESM apps. These are just this. And by the way, these are just what's in the extended support. So not even really everything that's in the repo. These are just what they're willing to patch through extended support. 180 pending for infra. Seven pending from apps. And then six ordinary packages from the repo need upgraded. Docker is old as crap. I mean, like I said earlier, it's on a kernel 5.4. For some reason, there's a folder in your home dirk called Cardano. Yeah, yeah, yeah. Well, I thought Cardano was an interesting product. Like, well, what's the date on that? Good question. A while ago. And I looked at that and like, that alone was like, oh my God. January 2022. Yeah, it was a real mess. It's not still running, right? I didn't see anything running. No, this was just, I was just taking a peek in the home dirks here. That would be funny if that was running all these years. Oh my God. Yeah, it's a mystery box to me, really. Been up for 180 days. That's not bad. 2.72 load average. Yeah, yeah. It's really just. Yeah, 2008 era Xeon. It's disk IO bound, right? It's about 12% of like the system pressure is just disk IO. Is really like what I saw when I went in there. Oh. ButterFS reports device missing. Looks like a multi-device ButterFS frame that may be missing a member disk. Nothing. Wait, did we put two disks in here and you stole one out of it? I don't know, man. I can't remember. Honestly, this is one of the things that's changed. One of the things that really strikes me is today, the system would be designed in such a way that it's self-documenting. Yeah. And you would just go look at that and you would understand how it works. But this was thrown together while we were just doing a project. It was going to be temporary and there wasn't really any documentation. And we were trying to even just figure out how it works. Yeah, boosts, lightning, all of it. So this is a real problem. I guess I have a big question here. How in the world are we going to figure out what is using this box? Do you think the boost scraper is using it? Well, it must be for doing the check to see if there's any unique boost that came in on that node. Yeah. So we'll want to make sure that wherever we migrate that split to, we are also checking in the scraper. And we're going to need to collaboratively close the channels on it because we're moving to a different system. So that's something. And then I think, yeah, we'll just have to monitor the traffic and see. It's a real problem. But we already have the host to migrate to. We're moving to a service for it. And so it's really just a matter of spinning down the channels, I think, letting the fun settle, and then us kind of monitoring what uses it. Leave it, you know, leave, shut down some of the services, but leave the box online for a bit. Monitor it maybe. I think we'll probably plan for like later this week. Yeah, we could probably do, we could do like a network cut or something if we want. Just sort of take it offline and see what barks at us. Yeah, see what breaks for a little bit. Well, Jeff did that to us one time, if you remember. I do recall. And some things broke, yes. Yeah, he just cut the power to this box. You know, not think it was important or anything. A couple times. Oh, yeah. You guys also, remember you blew the circuit that one time? Well, you got to blow a circuit or two to get progress. Yeah. So it's, you know, but it was a tough call because like Wes said at the start, there's other things that are also not working as well that could maybe be fixed sooner. But it just feels like now is the time to start pruning older infrastructure that you're not actively maintaining. Right. And like a lot of the value was we didn't know what we were doing. I mean, we needed something that could set up the pieces because we didn't even know what all the pieces were or which ones were necessary. Yeah. We understand a lot of that better now. Right. And so like we would never set it up this way. We don't really want to operate it in this setup. Right. It actively goes against most of the things we'd prefer to have it do. So it's nice to retire it, but it is. You're right. It was like it's sort of nostalgic too. And I'm really glad it held up. It was also very early in the like boost ecosystem. I remember for a couple of weeks there, we were changing things pretty quickly on this box just because all of the developers were evolving things. And it was a really exciting time. Is this where we were doing a little, we were trying out some of the IPFS podcasting maybe too, right? It's good times. It was a lot of fun. And that box was very educational. But it is time to wind her down. Well, we live in a world where more than ever, we're close to being able to summon software out of the void. And whether you should trust that software or not is a separate discussion. But one thing I find fun about that is you can kind of, you can try out more ideas because in theory, you could get some help to make it happen if the idea made any sense. And I think that means thinking about new ideas is what we should be doing. And I was just musing. If you could just add one feature to the kernel, you know, that Linux kernel you're running. Not that you needed other people to run. Not that you're endorsing is a good idea. But something that you would love to see put into kernel space and taken out of user space. What would it be? You know, or if you want to take something out, that could work too. Or another way to phrase it, like if I was king of the kernel for a day. I mean, you could just fork it, right? And add your own thing too. You don't have to be king of the kernel. It's a fun idea. I'll tell you what I would do. I know right away exactly what I would do. If I could. Oh, yeah. Oh, it's so obvious. First of all, I'd rip out Samsung's SMB server that I've never liked. And I would use that hole to put in something way more useful. Ready for this, boys? Kernel SSH. I call it K-SSHD. Thank you very much. Thank you. Thank you. And you might think this is crazy. And we get close. There are projects like Drakkut SSHD and others that get very early. So like even before the disk is decrypted, but not at the kernel level. However, this is actually quite possible. In fact, there's a project out there called Wolf SSH. Wolf SSH, which is probably the most realistic existing implementation you could already use and port it into a Linux kernel module. It's designed to be an embeddable SSH v2 library rather than a Unix daemon. It works without file system support and is designed for embedded configurations where there's no file system or they have to use their own virtual custom I.O. And the cryptographic library, Wolf Crypt, already in the Linux kernel. It's already in the Linux kernel. And so what Samsung did for KSMBD, and I think this is what I would do, is they divided SMBD into two pieces. The kernel stuff has the protocol, the crypto signing, session management, open read write handling, locking of files, VFS operations. That lives in KSMBD in your Linux kernel right now. And then in the user space, they manage the user accounts, the Samba config, your share info, RPC protocol, policy type operations is in user space. And KSMBD creates a real TCP server entirely inside the kernel. It maintains generic Netlink interface between the kernel and the KSMBD mounts. And it manages the protocol between the kernel and user space, which includes things like login response and RPC requests and crypto authentication and signing. All the things you need for SSH. So you could take KSSHD, put it in this space, break it up like they broke up Samba where the SSH framing, the key stuff, all the channels, the host keys, pub key verifies, handled by the kernel demon, which then drops to user space for user lookup, authorized key, PAM, PTY creation. All that policies, environment, you know, your user stuff is in the user space. And it would be dramatically smaller than KSMBD. I had the clanker do a little mock-up comparison. When's version one? My idea, my idea would make the kernel leaner and probably be more useful for all of us. And the Benny would be SSH remains available when your user space is totally crapped out. And it is even theoretically possible you could SSH in and monitor the init process. So you're basically tired of forgetting to turn SSH on? You're just like, if I build it in at the kernel level, then it's always on. Well, I just got thinking, like, think about for, like, provisioning at scale or even, like, IoT devices, some sort of, like, LAN-based SSH. I just think it could be really useful. Like, the little tiny microserver you could deploy that has a little teeny tiny secure SSH by default. Or you could get Disco to sort of get into the kernel right there and then take things over and make sure it's a Nix machine. That's what I'm saying. Every time it boots. That's obviously it. That's obviously it. You know, this would have helped me recently. When we were together, I was, like, remember I was pounding that server with just backups? Yeah. And I did something, I don't even remember what, but SSH just dropped out. And I was remote and I was trying to do a bunch of backups, like, in the middle of the night. And I couldn't do it because, like, I'm not going to go to the other place where people are sleeping and, like, hit the on-off button or whatever. And SSH just dropped out. But everything else was fine. And, like, the kernel's still up and all that. IBM I? No, my. I got SSH built in. Right? Boom! Nailed it. Okay, Wes, if you could add a feature to the kernel. Yeah, I was just thinking, okay, you know, for a long time, the kernel's had the ability to, like, migrate virtual machines over the network, right? Yeah. And it can, like, handle keeping the memory in sync. Why don't we have that for applications? Hmm. I want the kernel to be able to just take my app from one machine I got and then just, poof, make it show up on the other machine. Why do I got to be syncing everything? This feels right. This feels really right. You know? I'm biting with this. Like, app teleport is part of the kernel. They form a little kernel mesh. They auto-discover it, iApple Talk style. We'll put that back in. You wonder, too, could you do something like where maybe you identify an application, you migrate all of its processes to a namespace, you isolate that namespace, and then you can somehow group it up and move it. Yeah. And you start a new namespace on the system. Some of its storage is, you know, shared network mount or something already. Yeah, right. You'd have to do something with storage. But if you could transport the memory content securely. Mm-hmm. Why not? And, you know, we'll have everything on a NIC store so, like, the binaries will be available. Install it. If it's not there, just run it. Oh, that's good. All right. I'm not sure which one I like more. I think I might like that one more. I think I would use that maybe more in my day-to-day. Well, I was going to say put, you know, like a Lisp REPL in the kernel, but I thought this might be more useful. Okay, Brent, if you could add somebody to the kernel, what do you think you'd add? Are we saying tab management? Is that the appropriate thing? Firefox accelerator. Like a scheduler for my tabs. Kernel space Firefox. There you go. There you go. I was thinking just like a lot of the essential tools that we seem to use on every single machine. Things like R-Sync has been around forever. I don't know. It's as close as I feel an application is feature complete. Like, let's just throw it in there. Every single person should be using it on their Linux box. I don't know if they are, but I certainly do. So, I don't know. Maybe I'm just tired of installing stuff. I just want it all in one neat little box. You know, I got a big idea for you. K-SystemD. Whoa. Right? That's like K-D bus to a whole new level. Bring it all together. One giant kernel. I mean, you know that's where it's going anyways. Let's do it. Yeah, but we're still kind of waiting for SystemD to have a good text editor, right? Yeah, we do need that. You're right about that. We need SystemD EditD. All right, BoostIn. Let us know which one of our features you would vote for if you had to back one of us and what you would add or take out of the Linux kernel yourself. Boost.JupyterBroadcasting. Code submissions for a compilable module do get extra points. It's true. I like your thinking there, Wes. Boost.JupyterBroadcasting.com. That way we can put it in our kernel. Well, I just want to mention, if you haven't joined our Matrix community, it's still going. And if you have become disillusioned with Discord, go to jupyterbroadcasting.com slash Matrix. We have a couple of chat rooms going all the time in there. The JB chat, kind of our general chat. We have an agent operations chat, if you're into that kind of thing. And we have also chats in there for like the launch, the Linux Unplugged dedicated chat. But you can get started at jupyterbroadcasting.com slash Matrix. And then just for your extended calendar planning, Texas Linux Fest is on our radar. We don't have our details locked down yet, but it's October 3rd through the 4th. Oh, this is the old website. I believe it's November now. Yeah, yeah. November 6th through the 7th, 2026. Oh, man. See, here's what happened to me is if you Google for the Texas Linux Fest, the first result is the 2025. Come on, Googs. What are you using all these AI GPUs for? Figure it out. 88 days, 13 hours, 13 minutes, 40 seconds. That's getting to be sounded soon. That's why I wanted to mention it. We're planning to be there. We don't know how we're going to get there, but we may ask for help. Something fuel lines. Maybe we start putting a plan together and we actually get our crap together soon. Maybe that's what we're doing. We say that every time. Maybe this time. Ah, we should be starting our home lab holidays. Oh, right, right, right, right. Speaking of stuff we started behind on already. How do we get it so bad? How do we get it so bad? You're right about that. All right. Maybe we just do an episode where we catch up on stuff. Would that be fun for anybody? Would that be? I don't know. But before we go any further, I want to say time appropriate greetings to our virtual lug. Hello, Mumble Room. Thank you. Thank you. Hello, Brent. Hello. Hello, guys. Hello. Thanks for sticking around. Hope you've been enjoying the episode so far. It's just about out of here, as they say. Just about to get started. So today on the show, we're going to throw you for a loop because it turns out we're actually going to do it in reverse. We'll tell you about decommissioning a system, about the kernel features we'd like to add, and then we'll wrap it up. Well, actually, we'll start it with some boosts and some picks. So there you go. That's it. Hope you enjoyed the Reverso episode. We'll see you next week. I'm Brent. We're out of here. No, we're done.