WEBVTT 00:00:11.501 --> 00:00:16.021 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.241 --> 00:00:16.941 My name is Wes. 00:00:17.161 --> 00:00:18.041 And my name is Brent. 00:00:18.481 --> 00:00:23.001 Hello, gentlemen. Coming up on the show today, you know, after all the AI hype 00:00:23.001 --> 00:00:28.681 is finally over, I think there will be one real game changer that stands and 00:00:28.681 --> 00:00:30.701 sticks around, and it impacts Linux. 00:00:30.981 --> 00:00:33.701 We're going to tell you what it is, and we're actually going to test it out 00:00:33.701 --> 00:00:35.341 and see where it's at today. 00:00:35.501 --> 00:00:38.261 And then we'll round it out with some great picks, some boosts, 00:00:38.301 --> 00:00:41.461 some shoutouts, and a lot more. So before we get to all of that, 00:00:41.681 --> 00:00:45.001 we've got to do the right thing and say time-appropriate greetings to our virtual 00:00:45.001 --> 00:00:46.061 lug. Hello, Mumble Room. 00:00:46.481 --> 00:00:48.981 Hello. Hey, Chris. Hello, Brent. 00:00:49.601 --> 00:00:53.321 Hello. Thank you for being in there. We'd love to have you join us. 00:00:53.621 --> 00:00:56.621 You can join us on a Sunday morning or whatever it is in your time. 00:00:57.561 --> 00:01:01.381 JupyterBroadcasting.com slash mumble for that. And then, of course, 00:01:01.581 --> 00:01:05.281 jblive.fm for the stream. It's a vibe. That's what I always say. 00:01:06.622 --> 00:01:07.202 You don't think so? 00:01:07.402 --> 00:01:10.422 No, I do think so. I'm here for the vibe. 00:01:10.602 --> 00:01:11.402 You know so. 00:01:11.502 --> 00:01:15.302 Well, I've, you know, it's got a different feel. You never know what we're going 00:01:15.302 --> 00:01:16.082 to say, and we don't either. 00:01:17.462 --> 00:01:19.202 You never know what Neil's going to say, you know? 00:01:19.922 --> 00:01:20.322 Hi! 00:01:21.962 --> 00:01:25.542 Also, good morning to our friends at defined.net slash unplugged. 00:01:25.682 --> 00:01:29.822 Go meet Manage Nebula from Defined Networking. 00:01:29.942 --> 00:01:33.802 It's a decentralized VPN that's built on a true open source platform that you 00:01:33.802 --> 00:01:38.042 completely self-host and own yourself, or you can lean into their managed system, 00:01:38.202 --> 00:01:39.462 which makes it really easy. 00:01:39.582 --> 00:01:43.162 You go to define.net slash unplugged. You can try it on 100 devices for free. 00:01:43.422 --> 00:01:46.222 So unlike traditional VPNs, Nebula is decentralized. 00:01:46.902 --> 00:01:50.642 And that means there's a certain resiliency you can choose to build into this. 00:01:50.722 --> 00:01:53.662 And there's also a community of resources to help you make it more resilient. 00:01:53.842 --> 00:01:56.182 So this is great for a home lab, of course. 00:01:57.242 --> 00:02:01.422 This is also fantastic for a global enterprise. Best in class encryption. 00:02:02.862 --> 00:02:06.342 Fantastic community. and battle-tested. 00:02:06.682 --> 00:02:09.242 You know, in history of being my teacher and all, when it comes to something 00:02:09.242 --> 00:02:14.542 as foundational as how I network everything, I want to own that stack, 00:02:14.662 --> 00:02:17.122 and I want to own that stack end-to-end because when I'm building something 00:02:17.122 --> 00:02:19.362 for myself and my wife and my kids to use... 00:02:20.960 --> 00:02:24.720 I'm trying to take like five-year views, 10-year views if I can. 00:02:25.460 --> 00:02:29.780 And I'm not digging on anybody. It's just a fact. When you tap venture capital 00:02:29.780 --> 00:02:33.040 over and over again, it gets mixed into the tools that you rely on. 00:02:33.400 --> 00:02:36.600 And sometimes your core infrastructure tools go different directions over time 00:02:36.600 --> 00:02:39.680 because the priorities start to shift as they tap more and more VC money. 00:02:40.300 --> 00:02:44.700 And when I thought about it long term when I think about what I want to be running 00:02:44.700 --> 00:02:48.760 what I want to build on years from now for both JB and my personal infrastructure, 00:02:49.820 --> 00:02:53.660 I want a project that's truly built around the value of ownership it's a big 00:02:53.660 --> 00:02:57.860 deal when you think about it long term and there are a lot of options out there, 00:02:58.680 --> 00:03:02.260 and some of them have like self hosting options kind of begrudgingly like you 00:03:02.260 --> 00:03:04.000 know there's like different variations of it, 00:03:05.500 --> 00:03:10.240 nobody does it like Nebula and so you know You can make the mistake of like I did. 00:03:10.360 --> 00:03:15.640 I made a rookie mistake of linking a big tech login to my VPN provider. 00:03:15.820 --> 00:03:19.540 And I don't like that at all. And now in retrospect, years later, 00:03:19.580 --> 00:03:22.540 I wish I hadn't done that. That type of stuff is what I'm talking about. 00:03:24.080 --> 00:03:27.420 Nothing does it like Nebula. And nothing has Nebula's level of resilience, 00:03:27.740 --> 00:03:29.020 speed, and scalability. 00:03:29.320 --> 00:03:32.700 Go get started with 100 hosts. Absolutely free. No credit card required. 00:03:32.840 --> 00:03:35.560 Go to defined.net slash unplugged. 00:03:37.680 --> 00:03:41.020 Well we got a wee bit of housekeeping this week because some events are coming 00:03:41.020 --> 00:03:43.920 up that we'd like you to know about it's the 13th edition of Seagull, 00:03:45.442 --> 00:03:49.062 And that's happening next week at 8 a.m. to 6 p.m. 00:03:49.202 --> 00:03:52.842 Friday and Saturday, November 7th and 8th at the University of Washington. 00:03:53.362 --> 00:03:54.402 What do you know about it, Wes? 00:03:54.682 --> 00:03:58.282 Well, it's our local Seattle Linux Fest, you know? 00:03:58.662 --> 00:03:59.302 Yeah, downtown. 00:03:59.802 --> 00:04:03.242 Well, it has been kind of downtown or Capitol Hill area, but now it's over at 00:04:03.242 --> 00:04:05.482 the University of Washington, which is kind of its own little corner. 00:04:05.742 --> 00:04:06.482 Okay, that could be nice. 00:04:06.702 --> 00:04:09.902 Yeah. So there should be lots of stuff nearby. I think they've got some meetups 00:04:09.902 --> 00:04:13.622 and stuff going on after the fest. There's like a tea swap thing. 00:04:13.622 --> 00:04:16.622 If you want to get some interesting teas, that sounds like it's a pretty good time. 00:04:16.622 --> 00:04:19.062 Is that like gossip or is that the kind you drink? 00:04:19.102 --> 00:04:20.122 Like I think the kind you drink. 00:04:20.302 --> 00:04:20.622 Oh, okay. 00:04:20.682 --> 00:04:22.802 Yeah, it's called Teagle. That's like a little subcom. 00:04:24.402 --> 00:04:28.022 That's so Seattle. That's great. All right. Okay, that's good to know. 00:04:28.162 --> 00:04:30.962 So seagull.org slash schedule. We'll have a link in the show notes. 00:04:31.942 --> 00:04:34.262 Over 50 sessions or something around 50 sessions is going to be there. 00:04:34.262 --> 00:04:37.162 Yeah, it looks like some good stuff. Dev stuff, DevOps stuff, 00:04:37.342 --> 00:04:41.342 of course, Linux stuff, and then just general community and open culture. 00:04:41.802 --> 00:04:45.162 And then probably should be on people's radar, LinuxFest Northwest, 00:04:45.802 --> 00:04:49.302 Scale, PlanetNix26, all putting out their call for papers. 00:04:49.522 --> 00:04:52.522 Yeah, and they all close sooner than you'd think. So if you're interested in 00:04:52.522 --> 00:04:56.862 contributing, talking, speaking at any of those kind of events or volunteering 00:04:56.862 --> 00:04:59.502 maybe too, but you might consider taking a peek. 00:04:59.662 --> 00:05:03.182 Yeah, we want to let you know now because what's going to happen to you is the 00:05:03.182 --> 00:05:04.342 holidays are going to hit you. 00:05:04.342 --> 00:05:04.462 Yes. 00:05:04.662 --> 00:05:07.782 Right in the face and you're not going to think about the call for papers and 00:05:07.782 --> 00:05:12.322 then the events coming around. And, you know, if you can get a talk accepted, 00:05:12.582 --> 00:05:16.102 a lot of employers will pay for that to get you there to, you know, 00:05:16.822 --> 00:05:19.062 do your talk and maybe promote the thing a little bit that you do. 00:05:19.522 --> 00:05:24.122 It's totally worth it. So, Scale, Planet Nix 26, and Linux Fest Northwest all 00:05:24.122 --> 00:05:26.462 call for papers. And Siegel is next weekend. 00:05:26.662 --> 00:05:27.562 And we hope to see you there. 00:05:27.682 --> 00:05:30.582 I have a couple of other things to get to before we start the show. 00:05:30.662 --> 00:05:33.662 We have decided we are going to do another config confessions. 00:05:33.662 --> 00:05:39.902 So please send your configs in either boost with a link or go to our contact page and add a link, 00:05:40.852 --> 00:05:43.192 And we'll start collecting those. We already have some in the bag. 00:05:43.212 --> 00:05:45.692 If you already sent them in, we still have those. Most of those, 00:05:45.812 --> 00:05:47.152 at least. Depends if Brent lost them. 00:05:47.812 --> 00:05:51.152 And we'll get to config confessions very soon. So send those in. 00:05:51.712 --> 00:05:54.872 And a great way to support the show would be send us a link with a boost and, 00:05:54.872 --> 00:05:56.412 you know, two birds and all that. 00:05:57.032 --> 00:06:02.492 Also, while you got that boost button hot, I got something I have to just level set with you guys. 00:06:03.012 --> 00:06:06.612 I'm having a hard time understanding something. And I really want to take the 00:06:06.612 --> 00:06:11.112 temperature here. When we first started talking about what everybody now calls 00:06:11.112 --> 00:06:15.952 AI on Linux Unplugged, it was years ago. 00:06:16.532 --> 00:06:20.212 And we really referred to it at the time as machine learning because the tools 00:06:20.212 --> 00:06:22.052 that we were really looking at were machine learning tools. 00:06:22.532 --> 00:06:27.812 And in the context of Linux, it really wasn't a huge topic, seemingly didn't 00:06:27.812 --> 00:06:28.752 deserve its own episode. 00:06:29.352 --> 00:06:37.452 And then three years ago, October of 2022, we finally did a dedicated episode on the topic. 00:06:39.188 --> 00:06:44.208 And it was all about AI generation. Episode 481, the internet is going crazy 00:06:44.208 --> 00:06:45.428 with AI-generated media. 00:06:46.028 --> 00:06:49.228 What's the open source story and is Linux being left out? 00:06:49.968 --> 00:06:53.808 And that's when we dedicated an episode to this thing called stable diffusion, 00:06:53.808 --> 00:06:56.728 where people could generate images. 00:06:57.488 --> 00:07:02.208 And we talked about the morality of it. Three years ago, we talked about the 00:07:02.208 --> 00:07:06.148 power use issues in that episode. And of course, we talked about the Linux story around these tools. 00:07:06.608 --> 00:07:11.568 And we even stood up a live instance of a web version of Stable Diffusion and 00:07:11.568 --> 00:07:14.708 unleashed it on the live stream and let them crank out issues or images on our 00:07:14.708 --> 00:07:15.608 VPS. Do you remember that? 00:07:16.328 --> 00:07:17.168 Yeah, that was a lot of fun. 00:07:17.368 --> 00:07:23.308 It was three years ago. So back then, it just didn't have the hype around the topic. 00:07:23.648 --> 00:07:25.688 And it wasn't as charged as it is now. 00:07:26.328 --> 00:07:29.728 And you didn't see the counter reaction to the hype that you see now. 00:07:29.728 --> 00:07:35.368 And I cannot really, to be honest with everyone, wrap my noodle around how controversial 00:07:35.368 --> 00:07:37.328 every little new technology is these days. 00:07:38.008 --> 00:07:42.928 From programming languages to technology platforms to AI, it's just, it's remarkable. 00:07:43.928 --> 00:07:46.948 And I'll explain my position on AI next week if people are interested, 00:07:47.008 --> 00:07:52.188 but I wanted to take the colony's temperature on where you are at with AI. Do you hate it? 00:07:53.947 --> 00:07:56.987 Explain yourself. Are you ambivalent? Explain yourself. Are you excited? 00:07:57.207 --> 00:08:00.587 I want to know why. So help me, help us wrap our noodle around this because 00:08:00.587 --> 00:08:04.347 as people that have been talking about this since like 2021-ish, 00:08:04.547 --> 00:08:09.007 these were just tools and then all of a sudden they got really heated. 00:08:09.507 --> 00:08:11.407 And I'd like to know where you're at on this stuff. 00:08:11.967 --> 00:08:16.287 Because the premise of this episode this week is despite how much you hate it, 00:08:16.467 --> 00:08:21.247 there's at the end of this, what we might call an AI bubble or AI hype session, 00:08:21.467 --> 00:08:25.367 there's no doubt going to be a few tools that remain standing. 00:08:27.067 --> 00:08:30.247 That's where we're going to find what worked and didn't work, 00:08:30.387 --> 00:08:34.967 what was hype, what was silly, what LLMs were horrible at, and what LLMs were great at. 00:08:35.427 --> 00:08:37.567 And that might be a little while from now. 00:08:39.067 --> 00:08:43.347 But the people that hate this stuff have got to realize it's not going away. 00:08:43.647 --> 00:08:45.287 Some of this stuff's going to stick around. 00:08:46.367 --> 00:08:52.727 And what I've realized recently, and I'll get to why soon, is that Linux in 00:08:52.727 --> 00:08:55.707 particular is going to be one of the most affected areas. 00:08:57.527 --> 00:09:03.587 And you start to see hints of it this week when both Red Hat and SUSE made announcements 00:09:03.587 --> 00:09:05.187 around their enterprise-grade distros. 00:09:06.647 --> 00:09:11.467 So Red Hat has announced an AI assistant designed for application and migration 00:09:11.467 --> 00:09:13.667 and modernization tools on the RHEL platform. 00:09:13.667 --> 00:09:16.687 They said the launch of the Red Hat developer Lightspeed platform, 00:09:16.887 --> 00:09:19.567 a portfolio of AI solutions, will equip developer teams with, 00:09:19.627 --> 00:09:22.507 quote, intelligent context-aware assistance through virtual assistance. 00:09:22.847 --> 00:09:29.487 The company said this will help speed up non-coding-related tasks, 00:09:29.507 --> 00:09:33.787 including development of test plans, troubleshooting applications, 00:09:34.107 --> 00:09:35.447 and creating documentation. 00:09:37.351 --> 00:09:41.291 And then even more recently, Sousa says, with the release of Enterprise 6, 00:09:41.591 --> 00:09:45.631 it is the Enterprise Linux that, quote, integrates agentic AI. 00:09:47.211 --> 00:09:48.931 Sorry, I can't help not laugh a little. 00:09:48.931 --> 00:09:51.031 I know. I know. I agree. Go ahead, Brent. 00:09:51.351 --> 00:09:55.471 A release of Enterprise 16. You mentioned Enterprise 6, but I think we're moving 00:09:55.471 --> 00:09:57.751 a little further. 16. You did. 00:09:57.891 --> 00:09:58.291 You did. 00:09:58.591 --> 00:10:01.171 See, 6 AI can solve that for you, Chris. 00:10:01.551 --> 00:10:05.011 Well, I'm reading with the LLMs. No, I'm kidding. um i 00:10:05.011 --> 00:10:07.991 i want yeah i agree with wes and probably a lot of you listening like 00:10:07.991 --> 00:10:11.851 this stuff that integrates agentic ai it's it's 00:10:11.851 --> 00:10:16.611 okay anyways they say quote this is the industry's first enterprise linux that 00:10:16.611 --> 00:10:20.551 integrates agentic ai and reduces operational costs and complexity through ai 00:10:20.551 --> 00:10:25.311 readiness so this is the phase we're in jargon heavy hype heavy gotta gotta 00:10:25.311 --> 00:10:29.191 slap ai on your product in order to sell it do you think it's a coincidence 00:10:29.191 --> 00:10:31.591 that these two announcements were made so close to each other? 00:10:32.491 --> 00:10:36.851 No, that's no coincidence at all. That was very intentional. 00:10:37.191 --> 00:10:40.411 It is very much each position trying to jockey or each company trying to jockey 00:10:40.411 --> 00:10:41.651 their position in the AI race. 00:10:41.931 --> 00:10:46.411 And all of that is exhausting. And all of that is tiring. And all of it seems 00:10:46.411 --> 00:10:48.811 unsustainable. And that's all true. 00:10:49.951 --> 00:10:53.971 That is all true. But what we want to talk about today, I think, 00:10:54.151 --> 00:10:57.711 is the stuff that will remain after all of this passes. 00:10:58.091 --> 00:11:00.451 So as those of you who've been listening to the show for a while, 00:11:00.591 --> 00:11:05.031 you know that I have been rolling my own distro that I call Hypervibe for a while. 00:11:05.451 --> 00:11:08.751 I'm just at like the three-month mark now, if you can believe it. 00:11:09.391 --> 00:11:13.211 On average, I've made two or three notable changes per week as I've used it. 00:11:14.851 --> 00:11:17.891 Some weeks more, some weeks less, kind of averages out. 00:11:18.731 --> 00:11:25.191 And all of this has been done as an experiment using an LLM. 00:11:25.931 --> 00:11:27.751 Every little tiny change. 00:11:28.591 --> 00:11:32.311 And I started as a joke because I thought it was going to be a total disaster. 00:11:34.053 --> 00:11:37.633 And I somehow walked away with a working system. 00:11:37.873 --> 00:11:41.433 And then having refined this more as I actually start to use it on my day-to-day 00:11:41.433 --> 00:11:44.473 to get job work done and start taking it seriously and less as a joke. 00:11:44.573 --> 00:11:46.173 Actually depending on it to be your desktop. 00:11:46.833 --> 00:11:50.693 I've realized that LLMs are good at text. 00:11:51.593 --> 00:11:56.233 And everything I'm doing is a configuration file. And between the ability for 00:11:56.233 --> 00:11:58.353 the LLM to do web searches and 00:11:58.353 --> 00:12:03.173 to write configuration files and understand simple YAML or config files. 00:12:04.113 --> 00:12:06.393 This is an area it's actually particularly strong at. 00:12:07.753 --> 00:12:09.373 And I think we will see... 00:12:11.442 --> 00:12:16.042 A future where if you don't take advantage of these tools, you're not going 00:12:16.042 --> 00:12:19.302 to have your job replaced by AI, but you will have your job replaced by people 00:12:19.302 --> 00:12:20.922 that are taking advantage of these tools. 00:12:21.962 --> 00:12:25.682 Last week, I was having an issue with my network card dropping off the network. 00:12:26.602 --> 00:12:29.082 And especially bad in the morning for some reason. I don't know what that's 00:12:29.082 --> 00:12:33.322 about. I'd come in in the morning and I'd just have issues for a couple of hours every few minutes. 00:12:33.442 --> 00:12:35.782 Looks like my nick would just drop off the network. And one of the ways I'd 00:12:35.782 --> 00:12:38.142 have to fix it is unplug and plug it back in. 00:12:38.602 --> 00:12:41.922 And then it would come back to life and it would start working again. 00:12:42.922 --> 00:12:47.142 And I was a, it was a morning before the launch. I was rushed to get to the 00:12:47.142 --> 00:12:48.342 show live because we do it. 00:12:48.482 --> 00:12:50.982 We do a little bit earlier or no, we do a little bit later, but it's just a 00:12:50.982 --> 00:12:53.042 more complete, complicated show. So it feels like it comes earlier. 00:12:54.022 --> 00:12:57.742 And, um, I needed to fix this issue because I had to get my job done. 00:12:58.042 --> 00:13:01.922 And so while I was going about prepping the show, getting voicemails, 00:13:02.102 --> 00:13:06.982 doing all that stuff, I opened up another application and in the, and I just had a prompt. 00:13:06.982 --> 00:13:11.482 I said, I want you to review my logs, look at my network driver and the recent 00:13:11.482 --> 00:13:15.462 Linux kernel releases and figure out why my network card is dropping. 00:13:16.122 --> 00:13:19.222 And then I completely forgot about it. And when I came back, 00:13:19.422 --> 00:13:23.402 it had figured out what it was. There was a change in the upstream in the Linux kernel. 00:13:23.682 --> 00:13:27.922 And now I need to make an adjustments to my power settings for my particular Intel NIC. 00:13:29.182 --> 00:13:33.342 And it did all of that and figured all of that out while I was going about my 00:13:33.342 --> 00:13:35.582 other work. And I came back and it's like, OK, when you reboot, 00:13:35.682 --> 00:13:36.802 the fix is in and you're good to go. 00:13:37.302 --> 00:13:37.742 Has it been? 00:13:39.138 --> 00:13:39.778 That's great. 00:13:40.018 --> 00:13:43.818 And it went through, it read the log files, it read the kernel change log, 00:13:43.818 --> 00:13:46.958 it did all of that work, and then it made that change to my system. 00:13:46.978 --> 00:13:51.778 And because it's just changing the output in my Nix config, and it's apparently 00:13:51.778 --> 00:13:54.698 very adept at Nix, it handles it just fine. 00:13:55.398 --> 00:14:00.118 And you could extrapolate that out to a network engineer who needs to make a 00:14:00.118 --> 00:14:04.418 modification so every machine uses a new IP for something, right? 00:14:05.438 --> 00:14:12.198 Yeah, I mean, if you try to read through some of the buzzwords in the ASUS stuff, right? 00:14:12.298 --> 00:14:16.158 They're making an MCP server, which is basically a JSON API to interface with 00:14:16.158 --> 00:14:19.498 pieces of the OS, including, I guess, some more stuff on top of Cockpit to help 00:14:19.498 --> 00:14:24.018 you do, you know, LLM-enabled changes and updates or check in on what your system's doing. 00:14:24.498 --> 00:14:28.698 And just as an aside, doing all of this, it's given me an appreciation for how 00:14:28.698 --> 00:14:32.818 much edge case solving distro builders have to deal with and maintainers. 00:14:32.938 --> 00:14:35.858 Like, it's constantly, like, things change upstream. 00:14:36.038 --> 00:14:39.198 Sometimes it's just the name of a package, but you have to go through and constantly 00:14:39.198 --> 00:14:40.898 make those little tiny changes. 00:14:41.838 --> 00:14:43.338 Yeah, the integration is real work, right? 00:14:44.118 --> 00:14:47.758 Not for me. I just have the LLM do it. I do. I just have it check it, 00:14:47.838 --> 00:14:49.418 and then it goes through, oh, yeah, these things have changed upstream. 00:14:49.578 --> 00:14:51.238 Okay, I'll go through. I'll make sure I change these for you, 00:14:51.258 --> 00:14:52.758 and then it's ready to go for the next build. 00:14:53.638 --> 00:14:56.058 It makes maintaining my own distribution possible. 00:14:58.158 --> 00:15:01.318 And I thought, okay, let's put this to the test. And so that was one of the 00:15:01.318 --> 00:15:05.278 things we wanted to do this week is we wanted to put it to the test and see 00:15:05.278 --> 00:15:09.058 how far we could push this and kind of figure out where it breaks and really 00:15:09.058 --> 00:15:10.358 how realistic is this now. 00:15:12.158 --> 00:15:15.338 But I think this isn't going to work for every Linux. This isn't going to work 00:15:15.338 --> 00:15:18.078 for every problem. It's going to work specifically well for Ansible, 00:15:19.201 --> 00:15:24.801 for NICs, those types of things, declarative systems, it already is here. It's here. 00:15:24.941 --> 00:15:27.541 Yeah, especially where it's like a lot of the same common repeated patterns 00:15:27.541 --> 00:15:30.541 that maybe just need to be squeezed into particular context. 00:15:31.081 --> 00:15:35.041 It is fair to say that, you know, we're at a stage where it doesn't always produce 00:15:35.041 --> 00:15:37.261 the cleanest system, you know? 00:15:37.521 --> 00:15:38.861 Yeah, that is for sure. 00:15:39.081 --> 00:15:41.001 There's sometimes things are a little hacky and a mess. I mean, 00:15:41.061 --> 00:15:43.841 it works, but it might not be how you would do it. 00:15:43.941 --> 00:15:47.101 And it often works kind of the best for things like that, where you care more 00:15:47.101 --> 00:15:50.601 about in our testing sort of from a black box perspective where you're just 00:15:50.601 --> 00:15:52.701 like, okay, I can verify the things that I need do work. 00:15:52.901 --> 00:15:57.701 I don't care that much about exactly how it's doing it or exactly how, 00:15:57.861 --> 00:15:59.321 if it did it the way I would do it. 00:16:00.201 --> 00:16:03.941 And I think the other thing to acknowledge at this point is it can be very expensive, 00:16:05.041 --> 00:16:08.021 if you're doing a lot of this, depending on how you pay for it. 00:16:09.081 --> 00:16:14.061 After we spent hours, we spent all day on a call yesterday working this out, 00:16:14.121 --> 00:16:14.941 which we're about to get into. 00:16:15.861 --> 00:16:20.761 And after we got off the call, I wanted to see how feasible it would be to just do it with a local LM. 00:16:21.821 --> 00:16:26.121 And there's a lot of ways to crack that nut. But to really make it simple that 00:16:26.121 --> 00:16:30.421 anybody could do is I went and I downloaded the app image of LM Studio. 00:16:30.641 --> 00:16:31.241 Oh, nice, yeah. 00:16:31.401 --> 00:16:36.281 Classic, right? Which has Hugging Face integrated. And it supports downloading 00:16:36.281 --> 00:16:40.121 a, well, a bunch of different models, obviously. But one of them it supports 00:16:40.121 --> 00:16:41.301 downloading is DeepSeq. 00:16:41.461 --> 00:16:44.361 And also like the Quinn ones, which are like 8 billion parameters. you 00:16:44.361 --> 00:16:47.601 need a lot of parameters and you can just download them and 00:16:47.601 --> 00:16:50.341 then in the system tray icon you can just enable the server 00:16:50.341 --> 00:16:53.481 and then you go over to something like zed zed editor 00:16:53.481 --> 00:16:56.221 which is great and one of the options is just 00:16:56.221 --> 00:17:00.501 a local connection to lm studio zed just automatically connects to lm studio 00:17:00.501 --> 00:17:05.521 and all of the prompting is done locally with whatever model you've loaded in 00:17:05.521 --> 00:17:11.041 lm studio be it deep seek or quen or whatever it is and it's slow on my system 00:17:11.041 --> 00:17:14.301 of course but But it's actually using the AMD Vulcan acceleration. 00:17:15.121 --> 00:17:19.421 So if you're not in a rush, it's usable. So after we got off the call, 00:17:19.481 --> 00:17:20.981 I had a couple of things to fix, which I'll talk about more, 00:17:22.351 --> 00:17:25.251 Went and had dinner while it was doing stuff and came back and checked on it 00:17:25.251 --> 00:17:26.751 like a half hour later and it was done. 00:17:27.791 --> 00:17:31.991 So you can absolutely do this depending on the system with local tools. 00:17:33.091 --> 00:17:38.391 But there is still a quality gap. Like the big stuff, the big models hosted 00:17:38.391 --> 00:17:41.651 by your chat chippities or your clods are still superior. 00:17:41.791 --> 00:17:43.891 They're still faster and they're very expensive. 00:17:44.491 --> 00:17:48.751 So these are real limitations. As right now it works, but it'll build a system 00:17:48.751 --> 00:17:51.391 maybe the way you wouldn't if you're not really on top of it. 00:17:51.951 --> 00:17:55.051 And if you don't know to catch something there was something you brought up 00:17:55.051 --> 00:17:57.731 yesterday west it was like oh i'm really glad you said that because i wouldn't 00:17:57.731 --> 00:17:59.391 have caught it and the ai wouldn't have caught uh. 00:17:59.391 --> 00:18:03.511 Maybe it was the the bit about like all the extra work it was doing with uh a rofie setup. 00:18:03.911 --> 00:18:05.471 Yeah something it was something like it. 00:18:05.471 --> 00:18:08.051 Introduced like basically an abstraction to deal with having to use multiple 00:18:08.051 --> 00:18:10.251 multiple rofie packages that just no longer was needed. 00:18:10.251 --> 00:18:13.931 Whatsoever yeah it was a solution to a problem that no longer existed and it 00:18:13.931 --> 00:18:18.831 hadn't caught that that's a great example and And so there's still that level of human engagement. 00:18:19.651 --> 00:18:24.431 But we learned some lessons with this. And it is, in my mind, 00:18:25.831 --> 00:18:28.151 sticking around. And I don't know what this is going to be called. 00:18:28.611 --> 00:18:30.831 This is one of these things I always take a lot of crap for. 00:18:31.731 --> 00:18:36.671 It's not obvious to everyone two to three years out. But as we get two or three 00:18:36.671 --> 00:18:38.171 years down this road, it's going to be so obvious. 00:18:38.331 --> 00:18:44.851 And it's going to be called something like prompt ops or DevOps prompts or Linux by prompt. 00:18:45.711 --> 00:18:49.071 Really? Like, you know, like you're going to have a Linux machine as a system 00:18:49.071 --> 00:18:50.351 administrator and you're just 00:18:50.351 --> 00:18:52.731 you're going to have something on the command line that you work with. 00:18:52.871 --> 00:18:58.011 If you go over to GitHub.com and you look at the CLI tag and you look at the 00:18:58.011 --> 00:19:02.631 most popular projects in the CLI category, every other project practically is 00:19:02.631 --> 00:19:04.711 some sort of LLM tool on the command line. 00:19:04.891 --> 00:19:07.951 I mean, even back at Summit, Red Hat came out with Lightspeed and their little 00:19:07.951 --> 00:19:09.291 C tool for the command line. 00:19:09.431 --> 00:19:09.491 Yeah. 00:19:11.073 --> 00:19:14.953 That kind of stuff is going to be the norm. It's just going to be one of the 00:19:14.953 --> 00:19:18.433 tools on your, you know, like you have some stuff that can suggest commands. 00:19:18.533 --> 00:19:19.873 There's going to be LM tools that do that. 00:19:20.273 --> 00:19:24.133 And there's just going to be a name for it. Like DevOps became a thing. 00:19:24.393 --> 00:19:27.513 I mean, that's already one of the uses, just especially that like throwaway 00:19:27.513 --> 00:19:31.353 scripts, quick little things to clean up files or like do a particular manipulation 00:19:31.353 --> 00:19:34.733 that it's maybe not worth me scripting, but like a script would be better than 00:19:34.733 --> 00:19:36.813 me doing it manually. I love that. 00:19:36.813 --> 00:19:44.373 And I actually think there is a future where small local micro LLMs or whatever 00:19:44.373 --> 00:19:47.213 you want to call them are actually going to be better at this particular stuff 00:19:47.213 --> 00:19:51.913 that we're about to talk about than the chat GPTs or the clods. 00:19:52.313 --> 00:19:57.153 There will be in the future models that you can run in your text editor that 00:19:57.153 --> 00:20:04.673 will be possible on a desktop machine that is just super focused on config files 00:20:04.673 --> 00:20:07.573 or PHP or whatever it is that you do. That's its whole world. 00:20:07.813 --> 00:20:11.013 That's kind of some of what Red Hat is offering with some of this new development. 00:20:11.373 --> 00:20:15.473 Like they have stuff targeted at enterprise migrations of legacy software or 00:20:15.473 --> 00:20:17.353 migrate into containers and stuff like that. 00:20:17.473 --> 00:20:21.633 But it's, you know, you have models you can self host that they've figured out, 00:20:21.793 --> 00:20:24.233 optimized for these particular types of problems. 00:20:24.533 --> 00:20:28.713 And right now, man, if you get LM Studio and you load DeepSeq or whatever the 00:20:28.713 --> 00:20:33.333 hell you want and you open up Zed, it's all happening locally on your machine. 00:20:33.513 --> 00:20:36.053 It's all completely self hosted with just two desktop applications. 00:20:36.053 --> 00:20:38.573 You didn't have to start a single container or anything. 00:20:38.853 --> 00:20:41.613 And it's got a nice GUI to help you find the new models. You don't even have 00:20:41.613 --> 00:20:42.373 to know what the hell you're doing. 00:20:42.693 --> 00:20:45.033 And it's approachable right the F now. 00:20:45.573 --> 00:20:51.013 And so this is only going to accelerate. You're seeing Red Hat and SUSE lean into it. 00:20:51.113 --> 00:20:55.013 It is going to be so obnoxious for a while. And I really sympathize for those 00:20:55.013 --> 00:20:56.793 of you that are so sick and tired of this stuff. 00:20:56.933 --> 00:21:00.813 But I'm trying to give you your medicine with a little bit of sugar this episode 00:21:00.813 --> 00:21:03.773 because what we're about to talk about ain't ever going away. 00:21:07.511 --> 00:21:14.551 Onepassword.com slash unplugged. That's the number one password.com and then lowercase unplugged. 00:21:14.711 --> 00:21:17.931 Take the first steps to better security for your team by securing credentials 00:21:17.931 --> 00:21:22.911 and protecting every application, even the unmanaged ones you didn't know about. 00:21:23.091 --> 00:21:26.291 There's more to secure than just passwords. 00:21:26.811 --> 00:21:31.631 Managed and unmanaged SaaS applications, for instance, are a huge issue these days. 00:21:32.011 --> 00:21:36.151 That's where Trellica by one password secures your apps without leaving your 00:21:36.151 --> 00:21:42.751 employees behind, without creating that odd and difficult tension between IT and your end users. 00:21:42.891 --> 00:21:45.711 And if you are an IT professional or if you're in IT security, 00:21:45.931 --> 00:21:49.471 you know about the mountain of assets that's growing all the time and the sprawling 00:21:49.471 --> 00:21:53.351 applications that are out there as a service that users are signing up for all the time. 00:21:54.165 --> 00:21:59.285 It's a big problem. That's where Trellica will help you to discover and secure these applications. 00:21:59.545 --> 00:22:03.885 It'll find out where you have redundancies, where maybe you could cut back on spend. 00:22:04.205 --> 00:22:08.665 And Trellica by 1Password has pre-populated app profiles that'll assess the 00:22:08.665 --> 00:22:13.045 SaaS risks, let you have a better understanding of really what you're dealing with. 00:22:13.305 --> 00:22:18.325 And like I say, optimize that spend while you're enforcing best practices across every app. 00:22:18.445 --> 00:22:22.545 It really is truly the missing piece, something that I have struggled with when 00:22:22.545 --> 00:22:25.185 I was in IT because there wasn't anything like this on the radar. 00:22:25.365 --> 00:22:30.465 When 1Password came along, getting better password hygiene seemed like a huge leap forward. 00:22:30.565 --> 00:22:33.185 And of course, you know about their award-winning password manager, 00:22:33.385 --> 00:22:36.645 but they're securing a lot more than just passwords now. 00:22:36.745 --> 00:22:40.005 So check out 1Password Extended Access Management. 00:22:40.165 --> 00:22:45.565 You get started by going to 1Password.com slash unplugged. That's where you'll find out more. 00:22:45.765 --> 00:22:49.205 You'll learn if your employees are bypassing your best practices to use unapproved 00:22:49.205 --> 00:22:54.905 apps, how you can get your hands around that, and how you can get one dashboard to manage it all. 00:22:55.065 --> 00:22:59.665 So take a look at 1password.com slash unplugged. Take the first steps to better 00:22:59.665 --> 00:23:04.185 security for your team by securing credentials and protecting every application, 00:23:04.445 --> 00:23:06.145 even the unmanaged shadow IT. 00:23:06.385 --> 00:23:10.925 Go right now, 1password.com slash unplugged. Support the show and learn more. 00:23:11.065 --> 00:23:14.785 That's 1password.com slash unplugged, all lowercase. 00:23:15.065 --> 00:23:17.285 1password.com slash unplugged. 00:23:20.804 --> 00:23:24.384 Well, your three hosts yesterday got on a call because, well, 00:23:24.564 --> 00:23:30.884 I had an inclination at least that Chris's dear Hypervibe needed some love on the back end. 00:23:30.984 --> 00:23:34.064 We had a couple of listeners say, I think things could be better. 00:23:34.224 --> 00:23:37.724 And we had some PRs come in and we figured we should have a look at this. 00:23:37.944 --> 00:23:39.184 And Wes, what did we find? 00:23:40.124 --> 00:23:44.224 Well, first off, as usual with our community, we found like just incredible 00:23:44.224 --> 00:23:48.184 pull requests and issues and just a lot of wonderful engagement, 00:23:48.184 --> 00:23:50.924 including someone had like sopsified it with 00:23:50.924 --> 00:23:53.784 sopsnix and written just an incredible readme about 00:23:53.784 --> 00:23:56.584 how to use it and work with it so we'll have to look more in that for 00:23:56.584 --> 00:23:59.484 sure but you know hypervibe has has done 00:23:59.484 --> 00:24:02.424 well it's obviously been working well from from chris's experience reports 00:24:02.424 --> 00:24:05.384 here but it's really kind of it started as a 00:24:05.384 --> 00:24:08.184 one system thing that got extended to a two system thing right 00:24:08.184 --> 00:24:11.304 rvb and next station is are the names here yep and 00:24:11.304 --> 00:24:14.104 then at one point earlier we did try kind of a first round of 00:24:14.104 --> 00:24:16.904 this where we were like well you have a lot of shared functionality between these 00:24:16.904 --> 00:24:19.744 two configs that you probably don't including a whole bunch 00:24:19.744 --> 00:24:22.624 of janky activation script stuff that is sort 00:24:22.624 --> 00:24:27.884 of a bunch of crappy bash yes i'll own that yeah i guess you vibed into existence 00:24:27.884 --> 00:24:31.924 to not use home i did not want to use home manager i will own that yeah and 00:24:31.924 --> 00:24:34.964 so that each one had their own version of that was but it was pretty much identical 00:24:34.964 --> 00:24:38.304 right so it's like took an early stab at trying to refactor some of that into 00:24:38.304 --> 00:24:42.084 actual modules that you could then i was use in your host config like. 00:24:42.084 --> 00:24:45.844 I was doing a backwards approach of taking two linux boxes that We're totally 00:24:45.844 --> 00:24:48.204 separate systems set up years apart from each other. 00:24:49.059 --> 00:24:54.499 With very different, you know, display setups. And I wanted to unify them into one experience. 00:24:55.039 --> 00:24:58.959 You know, try to create one ultimate Linux desktop for myself that I use across all my machines. 00:24:59.379 --> 00:25:03.659 So I essentially tried to backwards integrate them. And I got to a working point 00:25:03.659 --> 00:25:05.199 for like those two systems. 00:25:05.479 --> 00:25:09.499 But it was not in a very good state if you wanted to onboard a new system. 00:25:09.679 --> 00:25:12.619 Yeah. Which eventually I do. And I wanted you to try it too. Right. 00:25:12.619 --> 00:25:15.159 It also meant like if anyone else wanted to use it, right? There was a lot of 00:25:15.159 --> 00:25:17.319 work you had to figure out and like copy your structure. 00:25:17.319 --> 00:25:21.299 Not really do it the nix native way at all and or i mean not the like easiest 00:25:21.299 --> 00:25:24.819 way anyway and to boot right we talked about the problems of the stuff that 00:25:24.819 --> 00:25:27.479 you know we wanted to refactor but there's also stuff we needed to make more 00:25:27.479 --> 00:25:31.379 variable just in that like you had hard coded in a few things including your 00:25:31.379 --> 00:25:34.219 username you know the wonderful chris f yeah. 00:25:34.219 --> 00:25:37.579 I mean i thought everybody would just run as chris f but turned out they didn't want to do that. 00:25:37.579 --> 00:25:41.159 Yeah so we needed to expose stuff there and there were a couple pull requests 00:25:41.159 --> 00:25:45.459 already to do that so people had taken a few stabs at basically using the module 00:25:45.459 --> 00:25:50.839 system and exposing those as configuration options for a Hypervibe module that 00:25:50.839 --> 00:25:53.419 would say, like, what user are you using? 00:25:53.479 --> 00:25:56.339 Because we need to, like, put that in some of the scripts and plan for that. 00:25:56.539 --> 00:25:58.519 Yeah, so it's something you could add to an existing system. 00:25:58.559 --> 00:26:03.039 It'd be a Hypervibe module that you could add to a Nix box that already exists, 00:26:03.099 --> 00:26:07.939 and then you could define run as this user. Run as Wes instead of Chris F. 00:26:07.939 --> 00:26:12.499 The goal was like you could import this module from Chris and then enable it 00:26:12.499 --> 00:26:16.139 and set whatever required options like what your local username you're going 00:26:16.139 --> 00:26:18.779 to use it with is and just have it work. 00:26:18.899 --> 00:26:21.839 But to get there, we had the problem that in our first attempt, 00:26:21.979 --> 00:26:25.459 well, one, we didn't have the optionality on username at all. That was hard coded. 00:26:25.619 --> 00:26:29.339 But then in our attempt to simplify things before, it kind of pulled some stuff 00:26:29.339 --> 00:26:34.219 out into shared modules, but it put it under a shared namespace instead of hyper 00:26:34.219 --> 00:26:35.959 vibe namespace. So we're going to have to replumb. 00:26:36.119 --> 00:26:36.259 Yeah. 00:26:36.259 --> 00:26:39.759 That's more of like a find and replace almost, so stuff that it should be pretty decent at. 00:26:39.939 --> 00:26:45.499 It's not, at first it wasn't obvious to me what should be machine-specific configurations 00:26:45.499 --> 00:26:48.279 and what do I want on all my systems. 00:26:48.539 --> 00:26:53.239 Right, and that's where either you have to put your judgment or rely on it's... 00:26:53.711 --> 00:26:54.611 Quote unquote judgment. 00:26:54.871 --> 00:26:58.711 And it's something I hadn't thought a lot about. So it is an example of if you 00:26:58.711 --> 00:27:00.171 don't think of it, it won't necessarily. 00:27:00.591 --> 00:27:04.511 It doesn't mean you can't go back and refactor, which is what we decided to 00:27:04.511 --> 00:27:08.431 do is essentially re-architect the way this thing is completely done. 00:27:08.431 --> 00:27:12.751 In order to make it possible for, say, somebody like Wes to run it on their system, 00:27:13.071 --> 00:27:19.871 we had to extract out machine-specific stuff and try to put the overall Hypervibe 00:27:19.871 --> 00:27:23.551 experience of Hyperland, the chosen application, the theming, the Waybar, 00:27:24.291 --> 00:27:27.151 the performance optimizations, the Zen kernel. 00:27:27.471 --> 00:27:32.011 We wanted all of that to be something that would be a shared thing across all systems. 00:27:32.011 --> 00:27:35.911 Yeah, and that's where it's you as the crafter here who's trying to figure out 00:27:35.911 --> 00:27:39.231 enough of what your vision is if you're going to have it be able to be executed by something else. 00:27:39.671 --> 00:27:43.711 Part of the problem, too, was the first attempt had pulled some stuff out, 00:27:43.711 --> 00:27:48.411 not the way we wanted, but it hadn't necessarily always deduped that, right? 00:27:48.471 --> 00:27:51.171 It didn't always update all the configs to use that new functionality. 00:27:51.371 --> 00:27:55.711 So then there was now, instead of deduping, it just duped again. 00:27:55.751 --> 00:27:57.831 So we had even more cleanup to start with, really. 00:27:58.311 --> 00:27:59.311 Yeah, that is true. 00:27:59.311 --> 00:28:02.351 And that's just kind of stuff you got to, you know, watch for if you're going 00:28:02.351 --> 00:28:03.711 to be using some of these tools sometimes. 00:28:03.971 --> 00:28:11.531 The goal that we wanted to pull off was to task the machine to re-implement 00:28:11.531 --> 00:28:17.431 this into a way that could be shared and not break the existing system while doing so. 00:28:17.591 --> 00:28:20.731 Because we were basically switching. You were redefining and picking an interface 00:28:20.731 --> 00:28:25.571 that would be Hypervibe and you needed your two existing machines to still use 00:28:25.571 --> 00:28:28.491 that and not use their old hard-coded previous version. 00:28:29.742 --> 00:28:34.262 That's kind of a tall ask. I mean, that is not managing a simple Nix OS config 00:28:34.262 --> 00:28:36.702 for one workstation. That is a little more abstract. 00:28:36.942 --> 00:28:38.882 And you're really trying to 00:28:38.882 --> 00:28:42.382 change the plumbing of how this entire thing is built while it's in use. 00:28:42.522 --> 00:28:46.262 And the more you realize, oh, I have to solve for this edge case. 00:28:46.442 --> 00:28:49.722 Oh, I have to solve for this edge case because these machines have this resolution 00:28:49.722 --> 00:28:51.562 and these machines have this resolution. 00:28:52.002 --> 00:28:56.122 It just keeps increasing the scope. And as we were doing it, 00:28:56.182 --> 00:28:58.442 I know, Brent, you were like, I don't think this is going to work. 00:28:58.442 --> 00:29:00.282 This is, we're getting too far out there. 00:29:00.522 --> 00:29:06.762 Oh, I was skeptical. I mean, just the expressions that you had watching some 00:29:06.762 --> 00:29:11.422 of its progress go by and you're the quote unquote expert at this particular, 00:29:11.762 --> 00:29:13.422 uh, let's call it an operating system. 00:29:13.562 --> 00:29:16.382 Right. And you're like, well, I don't know if we should be doing that, but I'll say, okay. 00:29:17.202 --> 00:29:20.502 And you were freaking like the higher, the number of files touched count. 00:29:20.622 --> 00:29:23.022 You're like, well, why is it touching that? Why that one? 00:29:23.802 --> 00:29:28.302 And all level headed West was like, no, no, it's okay. It'll be okay. We'll just fix it later. 00:29:29.342 --> 00:29:31.802 I was getting more, because it was getting more and more complicated. 00:29:31.802 --> 00:29:35.582 And I thought the more complicated this gets, it feels like the more little 00:29:35.582 --> 00:29:37.682 side edge pieces it won't think of. 00:29:38.262 --> 00:29:42.122 Can you talk a little bit about the setup that we had to make all of this work? 00:29:42.942 --> 00:29:46.262 What did you use to actually like make these modifications? 00:29:46.462 --> 00:29:50.502 I know it seemed like a pretty cool setup from what I was looking at, 00:29:50.642 --> 00:29:51.782 but give us the nitty gritty. 00:29:52.162 --> 00:29:56.902 You know, there is a thousand ways to do this. So don't take this as the blessed 00:29:56.902 --> 00:30:03.182 path, but this is what's worked for me, is I got the Cursor application and I connected it to GPT-5. 00:30:03.622 --> 00:30:07.742 And then later I connected it to a local LM after we got off the call. 00:30:07.782 --> 00:30:09.522 But that's a whole other process and it was really a pain in the ass. 00:30:09.802 --> 00:30:11.322 And I wouldn't recommend it with Cursor. 00:30:12.491 --> 00:30:15.571 But back to my point, I wanted something that would work quickly for us while we were on the call. 00:30:15.831 --> 00:30:21.711 And so what's great about Cursor is it's essentially a re-skinned, modified VS Code. 00:30:22.191 --> 00:30:25.171 So if you have used VS Code before, you'll be at home in Cursor, 00:30:25.191 --> 00:30:27.291 and you know how it can open up entire directories. 00:30:27.491 --> 00:30:32.471 Well, that entire directory becomes the context for Cursor and the LLM. 00:30:32.611 --> 00:30:36.691 And so it becomes, and that would be all my config files, and they're all in 00:30:36.691 --> 00:30:40.731 a different hierarchy in one directory, and it knows all of them. 00:30:40.731 --> 00:30:42.791 And it can read across all of them. 00:30:42.951 --> 00:30:45.811 And when you ask it a question, it considers the entire scope. 00:30:45.991 --> 00:30:50.211 And so one of the ways I've made this work is I've put all of this for all of 00:30:50.211 --> 00:30:52.811 my hosts in a build directory in my home folder. 00:30:53.091 --> 00:30:57.271 And so everything I'm doing is in that build folder. That's what gets checked in and out of GitHub. 00:30:57.851 --> 00:31:02.451 And so it has the context of all of the machines because it's looking at that one directory. 00:31:02.791 --> 00:31:07.491 And then you can just open up a chat session and say, tell me about this. 00:31:07.631 --> 00:31:11.311 Or it can be something as simple as What key bind am I using for XYZ to, 00:31:11.611 --> 00:31:14.071 all right, let's refactor this thing, 00:31:14.511 --> 00:31:22.631 which we, I would say it took longer in the sense that I thought we'd be done in a couple of hours. 00:31:23.011 --> 00:31:26.211 I thought we'd be done at noon and I think we wrapped up around 530. 00:31:26.371 --> 00:31:28.391 Yeah. Maybe 430. 00:31:28.611 --> 00:31:33.531 Okay. However, I think if we had done that manually, I think it would have taken us three days. 00:31:35.609 --> 00:31:38.389 You know possibly what do you think. 00:31:38.389 --> 00:31:41.249 I think i think we're taking me three days maybe 00:31:41.249 --> 00:31:43.909 you one day yeah there we go i think that's about right yeah yeah i think 00:31:43.909 --> 00:31:46.609 it probably would have taken about a day maybe regardless just because there 00:31:46.609 --> 00:31:49.869 was a certain amount of like i had to catch up on what had all because i took 00:31:49.869 --> 00:31:52.829 a snapshot look at it a couple months ago but you've continued 00:31:52.829 --> 00:31:55.509 vibing right along so like enough stuff had changed i need 00:31:55.509 --> 00:31:59.149 to get enough exploratory work to like wrap my head around what was happening and 00:31:59.149 --> 00:32:03.269 then just like some of the stuff are just kind of mechanical changes that you 00:32:03.269 --> 00:32:06.489 got to do that are actually kind of perfect work for the element because it 00:32:06.489 --> 00:32:09.669 is kind of thoughtless really um and then some of it that maybe would have gone 00:32:09.669 --> 00:32:13.829 faster is if we had used more human abstract reasoning for some of the like 00:32:13.829 --> 00:32:17.029 more stuff to be obvious to us that it was struggling with. 00:32:17.029 --> 00:32:23.049 What really struck me chris throughout was would you even attempt something 00:32:23.049 --> 00:32:27.189 like this without this tool because now that you're in it you're like okay well 00:32:27.189 --> 00:32:28.889 I could probably have figured it out, 00:32:28.989 --> 00:32:32.209 but I'm not so convinced you would have started the project in the first place. 00:32:32.329 --> 00:32:36.589 I would have started over from scratch. I would have started over and just sort 00:32:36.589 --> 00:32:39.409 of rebuilt the whole thing with this new model in mind. 00:32:40.409 --> 00:32:43.109 And I don't think I would have ever had the time for that, so I don't think 00:32:43.109 --> 00:32:44.289 that's actually what would have happened. 00:32:44.569 --> 00:32:48.869 But if I were to take this on without a tool like this, that's how I would have had to go about it. 00:32:50.146 --> 00:32:52.986 So beforehand, we kind of had like this scattered configuration, 00:32:53.366 --> 00:32:57.086 activation scripts that were defined in different machines and sort of a lot 00:32:57.086 --> 00:33:01.526 of duplicate efforts, duplicate paths for stuff. We had my username hard coded. 00:33:01.766 --> 00:33:03.306 We made it really hard for somebody 00:33:03.306 --> 00:33:05.726 to come along and just add it to their machine and just define a user. 00:33:05.726 --> 00:33:10.746 And what we got to at the end of our call was a single declarative source of 00:33:10.746 --> 00:33:14.166 truth for Hyperland, Waybar, Shells, all the system fine tuning, 00:33:14.266 --> 00:33:18.306 and then per host overrides for certain config options, 00:33:19.246 --> 00:33:23.606 users, maybe resolution monitor, 3D, you know, driver stuff. 00:33:23.726 --> 00:33:25.646 And there's definitely a lot of work that could still be done, 00:33:25.826 --> 00:33:28.506 you know, like one, I think just in general would be good to kind of just audit 00:33:28.506 --> 00:33:33.486 the whole thing and delete as much as you can without breaking it just as a, you know, cleanup item. 00:33:33.486 --> 00:33:36.786 But then mostly, yeah, I think there's some improvements to be made on the interface 00:33:36.786 --> 00:33:40.366 of like what stuff that we have as fallbacks and isn't required, 00:33:40.366 --> 00:33:46.046 but it's more just like a good default because I had to override or comment 00:33:46.046 --> 00:33:50.326 out some stuff in my code to make that work super easily, as easily as we'd like. 00:33:50.706 --> 00:33:53.866 So we got really close to the interface we want, but it's not quite there. 00:33:53.866 --> 00:33:59.466 But that said, you know, after 250 lines moved from per host stuff to a single 00:33:59.466 --> 00:34:03.766 module or a couple of modules, we got a new namespace for Hypervibe. 00:34:03.866 --> 00:34:08.746 Like, we got it pretty far. So the real test was, after we got it working in 00:34:08.746 --> 00:34:10.946 a VM, could you get it working on physical hardware? 00:34:11.966 --> 00:34:16.646 And I'm happy to report, Wes Payne, ladies and gentlemen, running it right now 00:34:16.646 --> 00:34:19.566 on the laptop, switched during the pre-show. 00:34:20.226 --> 00:34:21.786 How's it going so far? What do you think? 00:34:22.526 --> 00:34:23.726 Yeah, it's been fast. 00:34:23.726 --> 00:34:24.446 Does it feel faster? 00:34:26.050 --> 00:34:27.690 You know, I got to do more tests. 00:34:27.870 --> 00:34:29.330 It feels faster to me. That's all I know. 00:34:29.970 --> 00:34:33.290 It was easy, though. Like, I did have to, like, there's some stuff you have 00:34:33.290 --> 00:34:37.670 for, like, the garbage collection for the Nix Demon that I had slightly different settings. 00:34:37.890 --> 00:34:40.530 So, like, that's a conflict, right? So, some things like that is what I mean. 00:34:40.630 --> 00:34:42.850 Oh, yeah, yeah. I suppose because you weren't starting from, like, a fresh. 00:34:43.030 --> 00:34:45.450 No, I had to put it on. It's just my existing NixOS configuration. 00:34:45.730 --> 00:34:45.770 Right. 00:34:45.850 --> 00:34:48.930 But even then, right, it's mostly, there's a couple of changes. 00:34:49.010 --> 00:34:52.810 I don't know, under five things I had to come in on my config or adapt or override. 00:34:52.810 --> 00:34:56.030 You could do a make force kind of thing, too. and then in the flake you just 00:34:56.030 --> 00:35:00.070 kind of you know i had to add your hypervibe as an input i had that uh hypervibe 00:35:00.070 --> 00:35:02.770 module and then i set enable equals true user equals west. 00:35:02.770 --> 00:35:07.850 So it's four or five lines you added to your nix configure or your flake and 00:35:07.850 --> 00:35:12.030 now you have a hypervibe system that's pretty great right i mean you took it 00:35:12.030 --> 00:35:17.230 you it was a plasma system for years you added three or four lines to your flake 00:35:17.230 --> 00:35:19.390 oh yeah i did also commented out some stuff i did also. 00:35:19.390 --> 00:35:20.590 Comment out the plasma stuff. 00:35:20.590 --> 00:35:23.710 Yeah but if you were on a fresh box i mean you wouldn't even have to do that yeah. 00:35:23.710 --> 00:35:28.110 For our first test we just got a vm going from like a default uh no graphical 00:35:28.110 --> 00:35:30.650 environment nix os install from the installer so. 00:35:30.650 --> 00:35:31.570 Yeah and. 00:35:31.570 --> 00:35:32.290 That worked pretty well too. 00:35:32.290 --> 00:35:37.870 The machine had produced us a success a successful reproducible version of hypervibe 00:35:37.870 --> 00:35:41.710 which we had not gotten to before so that was very impressive that it actually 00:35:41.710 --> 00:35:46.650 did manage to properly refactor it into shared modules into you know host overrides 00:35:46.650 --> 00:35:49.850 and then deliver us something that we could actually get to. 00:35:49.850 --> 00:35:50.650 A working state yeah. 00:35:50.650 --> 00:35:53.410 That and it's that's on your system right now that's incredible, 00:35:55.610 --> 00:36:00.950 To do that, we had to completely rip apart my home system, the system that was 00:36:00.950 --> 00:36:03.430 working, sort of the original box. 00:36:03.630 --> 00:36:05.050 Oh, did you want that to keep working? 00:36:05.590 --> 00:36:11.910 And because we were on a call through that system, I couldn't build and reboot and see if it worked. 00:36:11.930 --> 00:36:13.230 We could build it. We just couldn't boot. 00:36:13.290 --> 00:36:17.170 I couldn't reboot because I would drop off the call. And so I had to wait till 00:36:17.170 --> 00:36:21.470 we were all done and so find out if I had a working box or not. 00:36:21.990 --> 00:36:28.690 And I don't know how to properly convey the amount of rearranging of the guts 00:36:28.690 --> 00:36:29.870 of this system that we did. 00:36:30.010 --> 00:36:33.550 I don't know if I – it's like an entirely new distribution. 00:36:35.570 --> 00:36:38.570 Oh, yeah, we should definitely – I don't think we updated the readme at all, so that's – Oh. 00:36:38.630 --> 00:36:38.910 I know. 00:36:38.950 --> 00:36:39.910 Add that to the to-do list. 00:36:39.910 --> 00:36:44.570 Yeah, I realized that as I was looking at it this morning. I had no idea if 00:36:44.570 --> 00:36:45.690 anything was going to work anymore. 00:36:45.990 --> 00:36:50.910 I didn't even expect it to boot. So I got off the call, went ahead, 00:36:51.230 --> 00:36:54.750 did one last rebuild boot, hit the old reboot button. 00:36:56.908 --> 00:37:01.968 And it came up. I think I have one error message during the activation phase. 00:37:02.788 --> 00:37:05.768 But GDM launched, and it came up, and I thought, oh, my God, 00:37:05.868 --> 00:37:06.868 I can't even believe I got this far. 00:37:06.868 --> 00:37:07.628 Okay, that's positive. 00:37:07.828 --> 00:37:11.148 I got GDM, and it booted. 00:37:12.168 --> 00:37:17.128 And everything works fine except for one thing, and it's so funny. 00:37:18.568 --> 00:37:22.808 GDM launches, and instead of saying my name, it now says Hypervibe. 00:37:22.888 --> 00:37:24.508 It's still Chris F for the user. 00:37:24.708 --> 00:37:26.088 Yeah, okay, that's another thing we need to set. 00:37:26.088 --> 00:37:26.748 We're. 00:37:26.748 --> 00:37:30.028 Setting that user description and to make it work i think we had it probably 00:37:30.028 --> 00:37:31.288 uncommented just like i did. 00:37:31.288 --> 00:37:32.188 But you don't get. 00:37:32.188 --> 00:37:34.348 Your username you get a generic hypervibe user. 00:37:34.348 --> 00:37:38.468 Because all my dot files were the same and all the software was the same but 00:37:38.468 --> 00:37:42.608 the system was completely reconfigured that was the only thing that was wrong 00:37:42.608 --> 00:37:45.148 is that my full name for my username was hypervibe, 00:37:45.948 --> 00:37:49.748 and i was sitting there going wow i cannot i cannot believe we just vibed our 00:37:49.748 --> 00:37:54.248 way to a completely re-architected system, and that's the only problem I have? 00:37:54.868 --> 00:37:57.708 That's the only problem I have? You've got to be kidding me. 00:37:57.748 --> 00:37:59.448 And I sat there just like my jaw. 00:38:00.448 --> 00:38:05.628 We ripped this thing apart and just walked away. I just couldn't believe it. 00:38:06.208 --> 00:38:12.368 And so it's working just fine. It's working absolutely. I later on used DeepSeek to fix the username. 00:38:13.348 --> 00:38:16.928 But we should fix it in a way where it's set for everybody. That would be the better way to go. 00:38:18.068 --> 00:38:19.628 Oh, yeah, did you just override it locally? 00:38:19.628 --> 00:38:21.648 Yeah, and I just, you can change the display name. 00:38:22.723 --> 00:38:26.143 But what do you think, Wes? What do you think about sticking with it for a little 00:38:26.143 --> 00:38:29.343 bit? See what you think trying out the Hypervibe lifestyle for a few days. 00:38:29.763 --> 00:38:30.023 Okay. 00:38:30.403 --> 00:38:31.223 Yeah? Are you going to do it? 00:38:31.223 --> 00:38:31.983 Yeah, I'll do it. 00:38:32.123 --> 00:38:33.143 I think if you and I try it out. 00:38:33.143 --> 00:38:35.483 I might have to ask you some questions, though, that you can vibe for me. 00:38:35.663 --> 00:38:38.643 What do we need? Yeah, I need to update the readme, put a cheat sheet on there 00:38:38.643 --> 00:38:40.923 of all the key binds, because there's a lot of key binds to know about. 00:38:41.703 --> 00:38:44.283 You and I battle test it for a little bit. Then, you know, the next stage, 00:38:44.443 --> 00:38:47.223 Brent, we've got to get you to do a bug test on it. We've got to get you to 00:38:47.223 --> 00:38:47.883 run it for a little while. 00:38:47.883 --> 00:38:51.243 Well, that's really up to you when you want to pull me in if you're ready for it or not. 00:38:51.243 --> 00:38:53.063 Right? Or are you ready for it? 00:38:53.143 --> 00:38:55.023 Oh, I'm ready. Are you ready? 00:38:55.603 --> 00:38:59.103 I don't know, actually. I don't know. I haven't been so good with keeping up 00:38:59.103 --> 00:39:01.603 with the issues and PRs, but I do appreciate people that sent them in. 00:39:02.063 --> 00:39:08.063 One of the things we were able to do is Cursor can also, you can add links to GitHub as context. 00:39:08.723 --> 00:39:12.883 So where we actually started is we pulled in a few of the pull requests and 00:39:12.883 --> 00:39:17.303 a couple of the issues and had it analyze those and compare it to the existing 00:39:17.303 --> 00:39:21.123 system because there was a pretty big change since those issues were submitted. 00:39:21.787 --> 00:39:24.687 Three months ago almost and we had it look at the differences 00:39:24.687 --> 00:39:27.487 and see what would be practically possible to apply and how we might 00:39:27.487 --> 00:39:31.967 apply it to the existing configuration and so we started with an analysis of 00:39:31.967 --> 00:39:35.267 those poll requests and issues that people submitted and were able to kind of 00:39:35.267 --> 00:39:38.247 iterate from there that's really how we even started down this direction and 00:39:38.247 --> 00:39:40.627 we just had to give us an overview what they said what would what we would need 00:39:40.627 --> 00:39:45.027 to change and that was kind of our launching off point which is pretty powerful just that right there. 00:39:45.027 --> 00:39:46.527 Yeah thanks to the community really. 00:39:46.527 --> 00:39:52.147 Yeah, it was longer than I wanted, but we ended up with something that is much 00:39:52.147 --> 00:39:55.207 more shareable, much more reproducible for me on a new system. 00:39:55.207 --> 00:40:00.627 So if I one day finally do get a new laptop, this is now completely deployable for me. 00:40:00.747 --> 00:40:02.327 In particular here, props to 00:40:02.327 --> 00:40:07.407 FBit818, SAMH, and Shift because they've all made excellent looking PRs. 00:40:07.407 --> 00:40:09.887 Yes. Thank you, everybody. Go check it out. If you want to see it, 00:40:09.947 --> 00:40:13.567 it's at github.com slash chrislasset. We'll put a link in the show notes and 00:40:13.567 --> 00:40:16.787 try to get the read me updated pretty soon to explain how to get it working. 00:40:17.227 --> 00:40:21.167 It's been a lot of fun and I've learned a whole new appreciation for the people 00:40:21.167 --> 00:40:24.627 out there that are maintaining distributions for us and how much of it is just 00:40:24.627 --> 00:40:28.767 little chicken ass that they have to deal with on a week to week basis that 00:40:28.767 --> 00:40:32.207 keeps them busy along with all the other stuff you have to think about with 00:40:32.207 --> 00:40:33.067 the architecture level. 00:40:33.347 --> 00:40:38.827 It's been a great experiment to kind of not put myself anywhere near their shoes, 00:40:38.827 --> 00:40:41.867 but I'm in the same room as their shoes and I can smell them. 00:40:41.967 --> 00:40:45.107 You know, and I've gotten I've got a much better appreciation for the smell of their shoes now. 00:40:49.002 --> 00:40:52.302 Join crowdhealth.com promo code unplugged. 00:40:52.402 --> 00:40:55.562 The open enrollment is now so take your power back and join crowd health to 00:40:55.562 --> 00:40:59.162 get started for just $99 for your first three months. 00:40:59.542 --> 00:41:03.662 I struggled to solve healthcare as a small business owner with just a really 00:41:03.662 --> 00:41:07.482 small team. There wasn't a great option for me. And I looked for years. 00:41:07.942 --> 00:41:11.802 I tried everything but the cost just kept getting absolutely bonkers. 00:41:12.002 --> 00:41:13.942 And I needed to make an informed decision. 00:41:14.182 --> 00:41:17.902 And so I did a deep dive into crowd health. I have been a CrowdHealth member 00:41:17.902 --> 00:41:22.462 for over three years, and it has been a peace of mind for myself and for my wife. 00:41:22.642 --> 00:41:26.682 And we've participated in the Crowd helping others with their health needs, too. 00:41:27.062 --> 00:41:30.142 Don't take my word for it. Trust yourself. Go take control of your future with 00:41:30.142 --> 00:41:34.402 CrowdHealth. It is a health care alternative for people who want to make their own decisions. 00:41:34.562 --> 00:41:37.622 So you don't have to play the insurance game. You join CrowdHealth, 00:41:37.682 --> 00:41:41.322 which is a community of people like myself, funding each other's medical bills 00:41:41.322 --> 00:41:44.142 directly. No middleman, no networks, no nonsense. 00:41:44.762 --> 00:41:48.242 And I can tell you, it works better than I initially expected. 00:41:48.462 --> 00:41:51.242 I was just hoping for anything that would be functional. 00:41:51.542 --> 00:41:54.702 And I would say it's far beyond my expectations. 00:41:55.042 --> 00:41:58.742 There's a great app to let you manage all of this, including looking at your 00:41:58.742 --> 00:42:01.542 status in the community, seeing what the requests that come in, 00:42:01.602 --> 00:42:04.162 where things are at, and also getting information. 00:42:04.855 --> 00:42:08.355 Including, like, you know, taking care of things when they come up, 00:42:08.735 --> 00:42:10.555 unfortunately, and all that kind of stuff. 00:42:10.855 --> 00:42:15.955 It has dramatically saved my family so much money. This is CrowdHealth. 00:42:16.075 --> 00:42:17.775 It's a health insurance alternative. 00:42:18.015 --> 00:42:20.035 It's health care for under $100. 00:42:20.435 --> 00:42:24.535 You get access to a team of health bill negotiators, low-cost prescriptions, 00:42:24.795 --> 00:42:28.795 and lab testing tools, as well as a database of low-cost, high-quality doctors 00:42:28.795 --> 00:42:30.675 that have been vetted by CrowdHealth. 00:42:30.755 --> 00:42:35.535 And it works. And if something major happens, you pay the first $500 and the 00:42:35.535 --> 00:42:37.375 crowd steps in and helps fund the rest. 00:42:37.975 --> 00:42:40.655 It feels like everything has been messed up for the few years. 00:42:40.815 --> 00:42:44.315 And with health care, it's just getting so much worse this year in particular. 00:42:44.795 --> 00:42:48.615 So if you join the crowd, you take care of each other. You get outside that system. 00:42:48.895 --> 00:42:53.715 That system is going to be overpriced. It's not really taking care of your health. 00:42:53.815 --> 00:42:56.155 It doesn't incentivize you to take care of your health. 00:42:56.555 --> 00:43:00.855 And it's so, so complicated now with all the subsidies and the things that are expiring. 00:43:01.595 --> 00:43:05.135 It just is not something I even want to have to participate in anymore. 00:43:05.995 --> 00:43:10.435 CrowdHealth has saved members over $40 million in healthcare expenses because 00:43:10.435 --> 00:43:12.215 they just refused to overpay for healthcare. 00:43:12.475 --> 00:43:14.935 They do it right, they figured it out, and it's working for me. 00:43:15.235 --> 00:43:18.055 The open enrollment is now, so take your power back. Go join CrowdHealth. 00:43:18.155 --> 00:43:20.695 Get started for just $99 for your first three months. 00:43:20.975 --> 00:43:26.715 Use the promo code UNPLUGGED at joincrowdhealth.com. That's joincrowdhealth.com, 00:43:26.795 --> 00:43:29.155 and then our promo code is UNPLUGGED. 00:43:29.695 --> 00:43:32.375 CrowdHealth is not insurance. opt out, take your power back. 00:43:32.575 --> 00:43:37.515 This is how we win. Join crowdhealth.com promo code unplugged. 00:43:39.540 --> 00:43:43.520 Unraid.net slash unplugged. Unleash your hardware. 00:43:43.800 --> 00:43:48.320 Go check out Unraid, the powerful, easy-to-use NAS operating system for those 00:43:48.320 --> 00:43:52.140 of you that want control, flexibility, efficiency, and you just want to play 00:43:52.140 --> 00:43:56.020 around real quick with the stuff we're talking about. Unraid is your gateway to that. 00:43:56.160 --> 00:44:03.760 And Unraid 7.2.0 just landed. Yes, the new stable release of Unraid is here. New, fresh features. 00:44:04.120 --> 00:44:09.160 First and foremost, the web GUI is now responsive. So it's going to look great on a lot of devices. 00:44:09.480 --> 00:44:15.360 And then you ZFS users, you're going to love the fact that you can expand a RAID Zed pool one by one. 00:44:15.840 --> 00:44:19.580 Whatever that means, I know you're going to love it. And it's here. 00:44:19.760 --> 00:44:24.060 That's right. You now have solid NTFS support. If you have a bunch of disks, 00:44:24.180 --> 00:44:26.160 like I have a couple of old Windows disks that I want to use, 00:44:26.260 --> 00:44:27.980 but I want to copy the data off, boom! 00:44:28.560 --> 00:44:30.540 NTFS support's in there. You would be blown away. 00:44:31.687 --> 00:44:36.787 You would be blown away. Can I just mention how blown away you would be if you 00:44:36.787 --> 00:44:40.127 knew about the just excellent file system support in Unraid? 00:44:40.287 --> 00:44:43.847 I mean, we talk a lot about the awesome virtualization support for passing through 00:44:43.847 --> 00:44:46.807 hardware and doing VMs and containers next to each other. 00:44:46.947 --> 00:44:51.407 We talk about the luxurious community application catalog and the fact that 00:44:51.407 --> 00:44:54.087 they're always maintaining this thing and putting out new versions and making 00:44:54.087 --> 00:44:56.507 it super easy to upgrade and safe. Your data is always safe. 00:44:56.647 --> 00:44:57.727 Like that's stuff I talk about. 00:44:58.067 --> 00:45:02.787 But what I don't really mention enough is like, it's got you covered on file systems. 00:45:03.087 --> 00:45:06.687 And one of the things that a lot of people who script are going to be happy 00:45:06.687 --> 00:45:10.867 to see, they now have a built-in open source API. 00:45:11.687 --> 00:45:17.367 And I've already seen the community working on some apps around this. It's chef's kiss. 00:45:18.047 --> 00:45:21.347 And I don't know, I guess the community is at a point with maturity where these 00:45:21.347 --> 00:45:24.607 applications are just bangers. It's just really impressive. 00:45:24.847 --> 00:45:27.887 So the new Unraid's great. And if you haven't checked out Unraid yet, 00:45:28.087 --> 00:45:30.847 we've got a deal for you Because not only can you support the show by going 00:45:30.847 --> 00:45:35.167 to unraid.net slash unplugged, but you can check it out 30 days for free, 00:45:35.327 --> 00:45:38.447 no credit card required, unraid.net slash unplugged. 00:45:38.567 --> 00:45:41.447 And if you decide to pull the trigger, they got a lot of nice price options 00:45:41.447 --> 00:45:42.567 at different points you're going to like. 00:45:42.787 --> 00:45:45.027 And that's just kind of locking in the guaranteed maintenance, 00:45:45.187 --> 00:45:46.187 the continued improvement. 00:45:46.567 --> 00:45:48.467 I mean, they just hit 20 years and they're still going strong. 00:45:48.967 --> 00:45:52.627 So this has got a long runway and it's something you can run for a very long 00:45:52.627 --> 00:45:55.927 time with the hardware you have today. It's that great. 00:45:56.667 --> 00:45:58.907 Unraid.net slash unplugged. 00:46:02.189 --> 00:46:06.689 We have a little piece of mail here from our dear olympia mike hey mike it's been a while, 00:46:07.709 --> 00:46:10.569 mike writes hey guys um i'd love to get 00:46:10.569 --> 00:46:14.049 in on that roast my nix config action this 00:46:14.049 --> 00:46:16.989 isn't my personal config of course but it's the main 00:46:16.989 --> 00:46:19.789 nix module for the nix book project that i've been working 00:46:19.789 --> 00:46:22.969 on for nearly a year the nix book install script 00:46:22.969 --> 00:46:25.789 basically just adds this base.nix as an 00:46:25.789 --> 00:46:28.709 import and before you jump all over this 00:46:28.709 --> 00:46:32.229 no the project doesn't use flakes yet mainly 00:46:32.229 --> 00:46:35.449 because one technically flakes are still experimental 00:46:35.449 --> 00:46:38.589 and i'm trying to be conservative here it's 00:46:38.589 --> 00:46:42.149 also just complicates the installer and number two flakes 00:46:42.149 --> 00:46:45.349 seem to also be very host specific but 00:46:45.349 --> 00:46:49.049 i won't know what host name a user of nixbook wants 00:46:49.049 --> 00:46:51.749 either way this has been running well for the most 00:46:51.749 --> 00:46:54.669 part notable parts of this config is the 00:46:54.669 --> 00:46:57.789 nixbook config updating itself sending notifications 00:46:57.789 --> 00:47:00.529 to users when you don't know the usernames of the 00:47:00.529 --> 00:47:05.689 users on the system and the automatic way to switch channels when i bump the 00:47:05.689 --> 00:47:11.269 channel version biggest issue nixbook users are having currently is printing 00:47:11.269 --> 00:47:18.309 oh yeah yeah i have a vahi uh enabled and it finds the printers but for some reason, 00:47:18.829 --> 00:47:22.429 the user still needs to go into CUPS, modify the printer, select the driver, 00:47:22.569 --> 00:47:24.129 and then enter their password. 00:47:24.829 --> 00:47:29.489 Curious how this can be more automatic, like the way Linux Mint or other distros do it. 00:47:29.609 --> 00:47:31.709 That could be something anybody out there knows. Let us know, 00:47:31.789 --> 00:47:32.929 because I don't think I have an answer for that one. 00:47:33.629 --> 00:47:38.849 Please roast away, boys. Call me out on my jank and make the Nixbook project even better. 00:47:39.129 --> 00:47:42.849 Well, I think this email seals the deal, gentlemen. Yeah. 00:47:47.840 --> 00:47:50.100 Yeah, I think we're going to do another episode of Config Confessions. 00:47:50.420 --> 00:47:51.780 It doesn't have to be a NixConfig. 00:47:51.940 --> 00:47:55.720 It could be whatever you are working on, including a Docker Compose file, 00:47:55.840 --> 00:47:58.240 maybe an Ansible. I'd love to see a few Docker Composes. 00:47:58.480 --> 00:48:03.080 And, of course, your NixConfig. Send them in either via a Boost link or at the contact page. 00:48:03.540 --> 00:48:06.520 There'll be a Mike's in there. We've got a few others in there we'll be talking 00:48:06.520 --> 00:48:09.140 about. And, you know, of course, I think you better prepare yourself because 00:48:09.140 --> 00:48:10.680 a lot of the answers is flake it up, Mike. 00:48:11.120 --> 00:48:14.520 Like, number one, the number one problem you listed you wouldn't even be having. 00:48:15.000 --> 00:48:17.480 And number two, you need to knock that experimental stuff off. 00:48:17.480 --> 00:48:23.520 But we'll get to that we'll get to that he does I'm just telling it like it is that is that is you. 00:48:23.520 --> 00:48:24.640 Gotta listen to the episode. 00:48:25.820 --> 00:48:29.100 That's big channel propaganda is what it is it's big channel propaganda and 00:48:29.100 --> 00:48:33.120 I'm not standing for it on this show I just feel I just feel strongly about 00:48:33.120 --> 00:48:36.920 that alright but thank you and prepare prepare yourself, 00:48:38.020 --> 00:48:43.800 we got some boosts into the show this week as well KS Koba comes in as our baller 00:48:43.800 --> 00:48:47.060 booster with 88,887 that's. 00:48:50.467 --> 00:48:52.947 I like it. I like it a lot. Thank you very much. 00:48:55.507 --> 00:48:59.867 And I feel like that number means something, but what it really is is a bunch of ducks. 00:49:00.047 --> 00:49:04.067 He says, I watched a great interview with DHH and Primogen about the perfect 00:49:04.067 --> 00:49:06.207 storm of Windows 11 dropping the ball, 00:49:06.787 --> 00:49:11.367 macOS getting stale, and Linux getting good, or at least good enough to finally 00:49:11.367 --> 00:49:17.487 make the 2025-2026 the year of the Linux desktop, desktop, desktop. 00:49:18.787 --> 00:49:22.547 Kind of echoes what Chris was saying recently about a new demographic of users. 00:49:22.747 --> 00:49:28.147 I've been able to shift fully in my life now to Oma Archie on all of my laptops and desktops. 00:49:28.427 --> 00:49:31.947 Still some learning to do, like how do I install from a tarball? 00:49:32.207 --> 00:49:37.847 But overall, it feels so fresh and I'd say unobtrusive. And OS just gets out of the way. 00:49:38.127 --> 00:49:40.227 That's great to hear. And thank you for the boost. 00:49:40.727 --> 00:49:48.067 I really appreciate that. But I love knowing that it's working for more and more people out there. 00:49:48.127 --> 00:49:53.127 I do think there has been a particular audience that Oma Archie has locked in on. 00:49:54.687 --> 00:49:57.227 And I think that's fantastic. As far as running from a tarball, 00:49:57.567 --> 00:49:58.687 well, that's a little complicated. 00:49:58.807 --> 00:50:01.547 It depends on what you downloaded. You might need to extract it and mark it 00:50:01.547 --> 00:50:02.847 executable and then run it. 00:50:03.007 --> 00:50:06.007 But generally, you want to try to install something from your package manager 00:50:06.007 --> 00:50:07.507 if you can and not from a tarball. 00:50:07.967 --> 00:50:09.987 Because you're not really installing it. You're just running it. 00:50:09.987 --> 00:50:14.327 So there's that little hot tip for you but thank you Kay, appreciate that baller 00:50:14.327 --> 00:50:16.367 boost you're the best around. 00:50:17.107 --> 00:50:22.667 Well turd Ferguson boosts in with 22,200 and 22 sets, 00:50:24.667 --> 00:50:30.267 I already thought we were called the Jupiter Colony we have colonyevents.com 00:50:30.267 --> 00:50:35.927 how quickly we forget ouch that's. 00:50:35.927 --> 00:50:40.487 A good point that's true and the matrix server is the Jupiter Colony Yeah, 00:50:40.547 --> 00:50:41.687 I'm going with it. I'm leaning in. 00:50:41.807 --> 00:50:44.747 I'm leaning in. We're calling the audience a colony, and I am fine with that. 00:50:45.047 --> 00:50:45.407 Colonized. 00:50:45.667 --> 00:50:46.907 Yeah, I agree. 00:50:47.967 --> 00:50:50.847 Well, Oppie 1984 boosted in 4,000 sets. 00:50:54.488 --> 00:50:59.208 Here's a quote lifted from last episode's boost. A quote, I'm assuming home 00:50:59.208 --> 00:51:02.168 assistant here. And Chris, that was your response to some feedback. 00:51:03.448 --> 00:51:07.508 Well, Oppie says, insert Picard face bomb here. 00:51:07.668 --> 00:51:10.728 I only happen to leave out the most important details in my feedback. 00:51:10.948 --> 00:51:12.568 Yep, I'm switching a home assistant. 00:51:13.148 --> 00:51:17.608 Little update on my mom using Mint, though. She's trying a live USB, 00:51:17.648 --> 00:51:19.948 and so far it's positive about it. 00:51:19.948 --> 00:51:21.328 That's an interesting way to 00:51:21.328 --> 00:51:25.088 slip it in for old mom there, is give her a USB live stick. I like that. 00:51:25.348 --> 00:51:29.428 She does, of course, like that it looks and feels just like Windows 7. 00:51:30.108 --> 00:51:33.328 She's still not ready to take that plunge, though, but I'm on the lookout for 00:51:33.328 --> 00:51:36.748 one of those Windows 10 laptops people are getting rid of when moving to Windows 00:51:36.748 --> 00:51:40.568 11, and then I'll just do a full install so she can try the full experience 00:51:40.568 --> 00:51:41.588 before making the switch. 00:51:41.848 --> 00:51:46.568 She needs a new laptop anyways, so two netbirds with one gemstone. 00:51:46.988 --> 00:51:49.728 Ah, that's big kidneys right there. I like that. Good thinking. 00:51:49.968 --> 00:51:52.888 That's a perfect little snipe. You know, those laptops are still going to be plenty good. 00:51:53.648 --> 00:51:56.388 Nice thinking. Thank you for the update, Oppie. It's good to hear from you. 00:51:57.228 --> 00:51:59.908 Not the one comes in with 2,000 sats. 00:52:01.548 --> 00:52:05.348 Should be lup rats instead of lab rats. Oh, and plus one for another config 00:52:05.348 --> 00:52:06.848 confession. I love the deep dives. 00:52:07.108 --> 00:52:11.008 Even if it's a topic I don't have a use for. Now that is the perfect listener. 00:52:13.288 --> 00:52:14.848 Thank you. We really appreciate that. 00:52:16.148 --> 00:52:19.028 Hybrid sarcasm boots in with 10,000 sats. 00:52:19.068 --> 00:52:21.468 Are you serious? Thank you, hybrid. 00:52:21.468 --> 00:52:25.888 Love the recent baller boost. And just a reminder that a free Jupiter Party 00:52:25.888 --> 00:52:29.728 membership goes to the listener that boosts the most total sets in 2025. 00:52:30.188 --> 00:52:30.348 Right. 00:52:30.548 --> 00:52:32.208 There's still time to get those boosts in. 00:52:32.388 --> 00:52:34.968 Yeah. We're going to have to put something together for the end of the year 00:52:34.968 --> 00:52:39.368 because we're not, well, we haven't, we technically ended the tuxies last year. 00:52:39.668 --> 00:52:42.308 That doesn't mean we'd have to do something, but we should, you know, 00:52:42.348 --> 00:52:44.388 get together, have a beer, and discuss what we're going to do. 00:52:45.428 --> 00:52:48.428 And maybe eat some food too. You know what I mean? We should probably eat some food too. 00:52:50.259 --> 00:52:52.919 I mean, do listeners have ideas of what we should do? I'd be open to that. 00:52:53.039 --> 00:52:56.819 I mean, we could party, we could road trip, we can go to space, whatever you want. 00:52:57.039 --> 00:52:59.279 What? Okay. All right. Okay. 00:52:59.859 --> 00:53:01.959 The suggestions have to come with funding proposals. 00:53:06.319 --> 00:53:10.399 Well, Moon and I boosted in 5,135 sats. 00:53:13.679 --> 00:53:17.599 Now, this is a live boost from a train running under the San Francisco Bay, 00:53:17.779 --> 00:53:20.639 135 feet below sea level. Is that a new record? 00:53:21.039 --> 00:53:25.699 I wonder what the record is for lowest and highest elevation. Live boost, anyone? 00:53:26.159 --> 00:53:32.019 That's got to be it. At least below sea level, 135 feet below sea level live during the show. 00:53:32.259 --> 00:53:32.699 Impressive. 00:53:32.939 --> 00:53:35.419 I bet you somebody could beat them on altitude for sure. 00:53:35.579 --> 00:53:37.699 And, you know, we welcome all elevation boosts. 00:53:37.779 --> 00:53:42.239 This is a great idea. If anybody is above 1,000 feet, we're at sea level right 00:53:42.239 --> 00:53:44.639 now. So if you're above us, boost in and let us know your elevation. 00:53:45.119 --> 00:53:48.919 I wonder if anybody's on a mountain out there. And can I come live with you? 00:53:50.279 --> 00:53:53.919 Thank you, everybody who boosts. We have the 2000sat cutoff just for on-the-air 00:53:53.919 --> 00:53:57.139 timing and all of that, but we save all of them in our show notes and we read them. 00:53:57.299 --> 00:54:01.239 We also had a nice batch of you stream. 24 of you just streamed those sats as you listened. 00:54:01.419 --> 00:54:05.379 You collectively stacked a nice humble 21,058 sats for the show. 00:54:05.519 --> 00:54:09.279 It's not a strong week for us, but, you know, it's a showing up, 00:54:09.419 --> 00:54:10.919 and it's still appreciated. 00:54:11.199 --> 00:54:15.999 The episode, which gets split between myself, Wes, Brent, 00:54:16.359 --> 00:54:19.619 Editor Drew, the podcast index, and the creator of the app, we all 00:54:19.619 --> 00:54:22.979 collectively stacked 153,802 sats 00:54:22.979 --> 00:54:28.379 thanks to you that's like an investment in the future of the show and we really 00:54:28.379 --> 00:54:32.599 appreciate that and of course it's also a signal if you like that episode gives 00:54:32.599 --> 00:54:35.739 us an idea of what content really works for you there's no better vote than 00:54:35.739 --> 00:54:39.999 a boost and you can use fountain fm to do that or albi hub there's lots of options there. 00:54:53.331 --> 00:54:56.871 And thank you to our members, our core contributors, and the Jupyter.party. 00:54:56.871 --> 00:55:00.551 You put that support on Autopilot, and it's our foundation. We appreciate you 00:55:00.551 --> 00:55:01.631 very much. Thank you, everyone. 00:55:10.391 --> 00:55:15.951 And we do have some picks before we get out of here. And we've mentioned this on air once before. 00:55:16.171 --> 00:55:19.551 It was a sly mention, but it's never made it into the pick category. 00:55:19.551 --> 00:55:22.751 And I need to elevate it up because the team's done great work. 00:55:22.751 --> 00:55:27.231 It's a very useful application, and it's got a great name. 00:55:27.411 --> 00:55:32.531 They had a release on September 8th. It's called Duff, D-U-F, 00:55:32.771 --> 00:55:39.051 and it is a free disk usage utility that is, I think, the best visualization, 00:55:39.411 --> 00:55:42.351 especially if you've got some media shares or photo shares. 00:55:42.491 --> 00:55:45.071 If you have a NAS and you need to kind of get your head around what on your 00:55:45.071 --> 00:55:48.811 NAS is eating up a bunch of space, Duff is the way to go. 00:55:48.891 --> 00:55:52.511 It's MIT licensed, and they've just been doing great stuff. 00:55:52.751 --> 00:55:57.791 And so think less DU, more DF in terms of where its role is. 00:55:57.851 --> 00:56:02.031 Because you get just a really nice breakdown of what file systems you have mounted, 00:56:02.191 --> 00:56:05.691 including like it'll call out special devices, like places like slash dev and 00:56:05.691 --> 00:56:07.791 slash run and slash sys differently. 00:56:08.091 --> 00:56:12.191 So then you kind of get to see like your actual more physical real disks all in one place. 00:56:12.731 --> 00:56:17.491 Handy rendering in the terminal, including like little progress style bars to 00:56:17.491 --> 00:56:22.131 indicate how full your disk is, color coded. It's just really easy to read. 00:56:22.131 --> 00:56:25.771 And a nice breakdown. Also, like the type of the file system is so handy to 00:56:25.771 --> 00:56:26.931 have just right there. I just love that. 00:56:27.071 --> 00:56:31.151 And you'll love this Wes, outputs to JSON, packaged for just about all the distros 00:56:31.151 --> 00:56:36.111 you might possibly want, including Arch and Nix, Fedora and Ubuntu and others. 00:56:36.871 --> 00:56:39.551 So Duff, D-U-F, that's the first pick. 00:56:40.484 --> 00:56:44.724 But we've kind of fallen into this habit of having more than one pick because 00:56:44.724 --> 00:56:46.324 there's so much good stuff these days. 00:56:46.424 --> 00:56:47.024 A cup runneth over. 00:56:47.264 --> 00:56:51.164 It does. And this one's a little bit different. It's called cheat.sh, 00:56:51.644 --> 00:56:55.044 and it bills itself as the only cheat sheet you will ever need. 00:56:55.664 --> 00:57:00.124 And the idea is you install this on your machine, and you forget a command, 00:57:00.304 --> 00:57:02.304 and you use cheat sheet to pull it up. 00:57:02.324 --> 00:57:08.324 And one of the things that the project talks about here is they focus on crazy great performance. 00:57:08.804 --> 00:57:13.884 Like they want it to be back with an answer in like you know two milliseconds 00:57:13.884 --> 00:57:18.304 or something like that and it covers 56 different programming languages a thousand 00:57:18.304 --> 00:57:22.424 of the most important Unix and Linux commands a bunch of other stuff is in there, 00:57:23.084 --> 00:57:29.904 and it's called cheat.sh it's pretty nice and I think it's probably one of the 00:57:29.904 --> 00:57:31.924 handiest tools I've seen in a while it's mostly written in Python, 00:57:33.244 --> 00:57:36.284 and did I mention it's MIT licensed I'm not sure if I did or not No. 00:57:36.384 --> 00:57:37.124 You got the last one, though. 00:57:38.184 --> 00:57:38.344 Yeah. 00:57:38.544 --> 00:57:42.144 Now, Wes, on our call yesterday, I specifically remember you disabling, 00:57:42.144 --> 00:57:46.344 was it man pages on the Hypervibe? 00:57:46.944 --> 00:57:49.084 I was wondering, would you install this instead? 00:57:50.024 --> 00:57:54.624 You know, I haven't. That's a good question. As long as you have a system that's 00:57:54.624 --> 00:57:58.144 constantly connected, yeah, it might work pretty decently. 00:57:58.264 --> 00:58:01.664 Yeah, you want to be able to look up. It's very fast, but it does require internet 00:58:01.664 --> 00:58:02.844 connection, so there's that. 00:58:03.044 --> 00:58:06.664 It can be used on the command line for command completion. It could be used inside code editors. 00:58:07.384 --> 00:58:13.264 They aim for sub 100 millisecond response times, so you don't have to sit there and wait for it. 00:58:15.680 --> 00:58:18.940 I think there might be a way to do it. Yeah, there is a way to do it offline 00:58:18.940 --> 00:58:20.220 as well. You can store it for offline. 00:58:20.440 --> 00:58:21.020 Oh, that's nice. 00:58:21.200 --> 00:58:24.620 I thought so. Yeah, it's pretty great. So it's called cheat.sh. 00:58:24.880 --> 00:58:29.560 So two great apps we'll have linked in the show notes, D-U-F, Duff, and cheat.sh. 00:58:31.360 --> 00:58:35.740 Yeah, I'll be honest. I've been leaning into these types of things recently 00:58:35.740 --> 00:58:39.380 just because like fish showed me the way. 00:58:39.600 --> 00:58:43.180 And if I can get another fish-like experience that makes it just, 00:58:43.340 --> 00:58:45.560 oh, yeah, that command I do every six months. 00:58:45.680 --> 00:58:51.100 That kind of stuff love that love things that make that simpler i don't remember 00:58:51.100 --> 00:58:52.180 all that stuff like i used to 00:58:52.180 --> 00:58:54.800 i want to print out a cheat sheet actually and put it to my monitor just. 00:58:54.800 --> 00:58:56.480 Like all that for learning neovim. 00:58:56.480 --> 00:59:03.160 Well done sir well done maybe one day wes you never know could always be a challenge well. 00:59:03.160 --> 00:59:05.180 Maybe with the lm helping you it'll go a little. 00:59:05.180 --> 00:59:09.180 Easy nice nice i think that's a burn i think that was a sick burn actually call. 00:59:09.180 --> 00:59:09.620 It a burn. 00:59:09.620 --> 00:59:14.580 Yeah but topic relevant oh Well, let's see. What should we tell people about? 00:59:14.700 --> 00:59:16.820 Should we tell them about our fancy features that we have? 00:59:17.040 --> 00:59:21.120 Yeah, absolutely. Not only do we have chapter markers, you can go right to the 00:59:21.120 --> 00:59:24.780 stuff that you like or don't like or skip around or listen in reverse order. I don't know. 00:59:25.000 --> 00:59:29.040 We also have transcripts of the whole thing with who said what dumb stuff. 00:59:29.260 --> 00:59:33.280 Yeah, and a lot of that stuff is compatible with the OG podcast apps, 00:59:33.360 --> 00:59:35.720 the 1.0 apps. We'll bake it into the MP3. 00:59:35.940 --> 00:59:40.820 And if they support the standard for the... 00:59:40.820 --> 00:59:42.440 And TenantPod does a great job with the transcripts. 00:59:42.440 --> 00:59:44.560 Yeah, TenantPod's great for the transcripts. If they support the transcript 00:59:44.560 --> 00:59:49.080 standard, like Apple, actually, Apple Podcasts does of all. They support the transcript standard. 00:59:49.340 --> 00:59:52.700 So it just kind of depends on the player. And then if you have a nicer 2.0 player, 00:59:52.860 --> 00:59:54.060 you get even more features. 00:59:54.160 --> 00:59:57.800 You get better chapters. You get perhaps more features with the transcript depending on the client. 00:59:57.960 --> 01:00:01.420 And then additionally, you get the lit support and potentially the boost support too. 01:00:01.680 --> 01:00:05.600 So check us out. Yes, we are live. We do a Sunday, Tuesday show. 01:00:06.120 --> 01:00:09.600 Sundays, 10 a.m. Pacific, 1 p.m. Eastern over at jblive.tv. 01:00:13.710 --> 01:00:16.850 We have that mumble room, too. You can join us. There's always more in that 01:00:16.850 --> 01:00:19.490 mumble room. And if you're a member, be sure to get the bootleg version. 01:00:19.750 --> 01:00:24.230 It's clocking in at over an hour and 42 minutes right now of content just for our members. 01:00:24.850 --> 01:00:25.790 Now, links to everything we 01:00:25.790 --> 01:00:30.610 talked about today, those are over at linuxunplugged.com slash 639. Woo! 01:00:31.710 --> 01:00:37.790 Woo! Almost to 640. How about that? Also, our RSS feed, our contact form, all that good stuff. 01:00:37.870 --> 01:00:40.690 Matrix room, all linked over there. You can find it. It's a website. 01:00:40.830 --> 01:00:43.310 It's got links. You're going to love it. Thank you so much for joining us on 01:00:43.310 --> 01:00:45.330 this week's episode of Your Unplugged Program. 01:00:45.550 --> 01:00:49.530 And we're going to see you right back here next Tuesday, as in Sunday.