 that I actually got it right in the, um, what you call it, I got it right in one part of it, I got a mute my phone, a lot of people that message me do any messages that happens sometimes such as life, such as life. Um, but first things first, why am I doing it early? Um, same reason why I do it late. There's, there's like scheduling conflicts. And I mean, maybe I could do it while I was driving. That seems unwise because I would like to answer questions, but I do have a semi self driving car. So, you know, I probably could do that. Uh, but I'm on my way today to the Ohio Linux vest. So I thought I'd bring that up first. And, uh, you know, that's going to be fun, a fun event. I imagine, uh, some of you will be there just be sure. Hey, for those of you who watch my studio tour, you may know there's a space heater really close to me. It was a little bit too close when I faced this particular camera. So I just moved it over. You wonder what those are. So we got things to do today. Yes, we do. Um, many, many things to do, but first things first, uh, though is just me mentioning that I'll be the next couple of days at Ohio Linux vest. As I said, that's why it's in the title. I realized I did this kind of backwards. I probably should put like, you know, where Tom's going to be first and then 45 drives or XTP and G, but I think we're going to talk about XTP and G updates. Um, I am in, I have a finite amount of time, uh, today, because I actually am trying to accomplish all the things. So I'm going to have to wrap this up here at 11 because I already scheduled another appointment. And, uh, so it's not like my usual where I can just babble on, uh, but I don't want to bump the appointments around. So. Hey, thanks for mentioning how Ohio Linux vest earlier this week. I'm looking forward to it, uh, but can only attend Saturday. Well, I'll be there, uh, today. There's something going on. I don't know much about what's going on, but I seen as a thing, uh, some gathering of people, um, but whatever I like getting, I'm, I, I'm getting in on Thursday. So I'm just coming a little bit earlier. It's not that far of a drive. I think it's two and a half hours or three hours or something like that, uh, but I'll be there Saturday and I'm leaving on Sunday morning. So, uh, good morning question. Do you surveillance camera system? Yes, we surveillance camera system. Uh, I actually, I've thought about doing a follow-up video on this because now that they've been here like a year and I've done a several videos in general about my surveillance station. We definitely sell a lot of these as a solution. Um, but yeah, I have this one at my house. Uh, the nice thing about having one at my house is I can share this because I give myself permission to share, um, all the leaves that have blown into my garage and then you can, uh, see my barn or see my backyard. This one, this one camera does this sometimes. It kind of just pauses. It's my front porch. It doesn't do it all the time. Uh, it just pauses sometimes. Now it's always recording. There's no delay in recording, but, uh, yes, we do, uh, Synology Surveillance Stations. Yes, we really like the Synology Surveillance Systems. Um, and it's just a, uh, it's just a great system overall. We're really, uh, we definitely, uh, are happy with it as a product that scales well. And I might do a follow-up video on all the cameras I use to say, hey, how do they hold up after a year? Which by the way, these are some of the same cameras we've installed for customers. So I think I have a couple that might have failed and I'm trying to compile that list because sometimes things happen. Um, so I'll talk about which ones work, which ones in, but for the most part, the Amcrest that we've been going with work really, really well. So that's been good. Stream is good in the Midwest. Someone said stream is not good in Toronto. I already have an idea why that camera does that. Oh, good. Me and Travis, uh, we'll have to chat about that later. So, uh, let's see. Hi from San Francisco. And my stream is good all the way in Europe. So then the next thing though, that I actually wanted to talk about, and it's going to be, uh, oops, that's not, I should have, I should have had the links ready, right? Um, there we go. But this has been, oh, by the way, StreamYard. Thank you. StreamYard is a tool I use for this. Um, and they've made it easier for me to switch tabs. This was a feature they had, and I don't know why it went away. I don't know if it's a problem with Chrome or whatnot, but I couldn't just, uh, choose a different tab. So there's actually a button that says share this tab or share this tab, and I can just quickly now jump between all the tabs I have open instead of actually happen to, uh, go through like several menus to do it. It's the little things that make me happy. This, like that feature, that feature really is one of them. But XO, there's been some more changes on this, and I thought, you know, I, I don't know if I should do dedicated videos to it. They have dedicated videos, but you know, I like raising some awareness and testing it, but the thing I'm playing with now, or I should say can play with now is warm migration. I just think this is a really neat feature, uh, that they're integrating. So it's the ability to, uh, get two separate servers synchronized in terms of all the data, the VDIs and everything like that, and then finalize that synchronization and minimize downtime when you have to do a migration to a server that you can't just live migrate to. So ideally you want a hot migration. Let's just go ahead and synchronize it between this new server, which is also one of my favorite magical things about virtualization. You come in, you drop a new server in, you configure it, you tie it to the existing pool, and then without any downtime, I migrate the existing servers over to the new servers, and the client doesn't experience downtime, and the servers are all still up and running magic. Well, that magic breaks with things like changing processor design. So if you go from an Intel to an AMD-based system, you have to restart that server. Now restarting, it's not a big deal, but shutting it down, migrating it, then restarting it. That might be a little bigger deal. So that's where this warm migration system comes up. And it's just slick. It's just a, it's a way to take things. Let me find if I have some, something I can, you know, I don't even know if I can really warm migrate it. So I can't, I don't know if I'll be able to do this demo live, but I can show you where the button is and goof around with it. Also, I'm going to do the over provisioning of CPUs. That's something that people have questions about as well. What happens when you over provision, which is really nothing. So if we go, it's like VM 1, and then we'll go to VM 2 here. Actually, well, this is what servers are they on now? So both of these have 24 cores assigned to them, which is only 24 cores available on the host. By the way, there's plenty of other VMs running on the host, but yes, you can over provision them. But I'm going to run some Veronica's benchmarks to get that going. But the reason I did this was we can talk about the warm migration option. So you can say, Hey, where do you want to send this? And let's, you know, we could send this over to our lab. And then warm migration is a process and get that bigger warm migration. We'll first create a copy of the VM on the destination while the source VM is running, then shut down the source VM and send the changes that are happening during the migration destination and minimize downtime. So it's kind of just an automated way to do this. I mean, you can do this manually, keep it synchronized, and then finally do a shutdown migration. But being able to just click a button and automate this, I didn't switch tabs. So share this tab. There we go. Yeah, change tabs, please. Thank you. I should pay attention to what I'm doing. But yeah, this is the warm migration option. So back to the CPU over provision though, just so go backwards in time to talk about what I was doing. Here are two machines both running with 24 CPUs allocated and are running on a host with only with 24 CPUs along with lots of VMs. I just got to set up a demo where I'm using Pheronics and showing you what happens when you take 12 and 12 because it's 24 CPU. So we take two VMs 12 and 12, we run them, we get a benchmark. What happens when we run that same benchmark that is CPU intensive where we have 24 and 24? How does it split? Do we get the same results? Too long didn't watch the results are very, very similar to very close. They're not substantially different. And that's kind of the point. The hypervisor does a great job of handling the CPUs and figuring out how to balance all of that together. So definitely pretty neat. It's definitely just the magic of virtualization, you know, it just makes me happy. But back to the warm migration. Yeah, I'll play with that later in a separate video because I think it's just, I actually just needed an entire long in depth getting started with Zen and all the features of Zen server combined with XC PNG, because it's just impressive everything that you can do with it. And every time I check, there's always some new feature that gets added, you know, like, hey, warm migration, who knew we needed this? Let's just migrate that to our lab and we'll do a warm migration and get it, you know, like pride, we're doing it live, right? Lab pool, sure. I don't know how this task works. Let's see what happens. Oh, look at importing contents, five minutes. All right. So that's how it works. Now we know. I will go back over here to YouTube projects. Oh, and there's our warm migration. So it tells me that it's doing it neat. All right. So now we know how it works. We're all learning. I just updated this this morning, because it just came out yesterday. This blog post was yesterday for 577. So warm migration. This is neat, too, for people that are trying to get clever with things. You can do, I think this is really neat. A REST API now has two endpoint requests, VM snapshot and BDI snapshots, you can fetch any info related to your snapshots, VM or disk. This was just a neat way to be able to use APIs to call things in there to build automation around it. That's really cool. And I will be testing this soon, the new XO lite. This is the request that a lot of people have is that it natively has some type of UI without having to load the full Zen orchestra VM, and that's something to work on it. I don't use Nagios, but they apparently they improve Nagios reports. I never tried removing TOTP for a user. I thought it was interesting that I guess removed TOTP. I guess once you add it, you can't. I never tried to remove it, so I didn't know that was a problem, but it turns out you couldn't remove it. So now you can hit remove on TOTP to unlock someone, if need be. So in our interoperability quest, we've always allowed people to try our platform. So the try our platform, get decent standard support from VM format, so you can export to VMware, KVM or anything supporting OVA format. This is just great. They took the time, which very few companies do. They usually do not want to ever build a feature like this because they're like, no, no, no, no. Once you come into our ecosystem, we would never want you to leave our ecosystem. So I think that's kind of neat that they have been working on that. Backup resiliency, merge process refactoring, made easier tests to maintain, fixed edge cases. Yeah, I've posted about edge cases. Their forms are a great place on that, and they're also unmasked on. So that's the whole changelog for Zen Orchestra. I figured I'll bring it up here. Curious how fast migration is going. Anecdotal experience is that disk transfers are fairly slow. Don't use nearly entire network bandwidth available. Yes, the TAP disk currently V1 API is not... There's a whole write up I did recently. If you watch my video, I explained it better in how Zen handles storage. There's a problem, basically, and I'll use my own word, spaghetti code. The spaghetti code that is the current version of the way they handle disk is old and was written a long time ago. Now it's safe, it's secure, and security in Zen is really high, but that also brings forth challenges of making it fast. Because by creating all these isolated processes, you end up with a really secure environment, but a harder to work with environment. So the individual disk processes have a lot of dependencies built on that security model, which make it slow. But the new version, still maintaining security that they're working on, will be out probably sometime next year, I think, is going to be substantially faster. So their new implementation... I linked to all the... There's a series of blog posts that they have on the topic. So if you have a slower processor, you will have slower transfers when it comes to moving it, and you won't hit your bandwidth limits of your interconnect. That's definitely true. It seems to have had an error, I think. I seen an error. Oh, it didn't start. No host available because there's too many. Now, I already know why I failed, not because of a problem. This. The lab pool only has 12 cores. So that's why it failed. So that's kind of fun. Let's do... Let's destroy this VM because it's not important to me at all. Let's remove it. Let's play that game again. So remove because we don't need it. We'll go to YouTube. Stop this one. Let's rename it. So this is going to be actually... Where does it go? Is there a better icon? There we go. Can I... I've not tried this. Let's see if this breaks something. There we go. Why not? I think this should be capitalized. It'll bother me. Here's our warm migration test. First, let's reduce it to four cores. Let's reduce it to... I don't want to overload our lab server, which is not that fast. Of note, CPU limits for... All right, cool. If you don't do this, you're trying to move it to something that may not have the same CPU limits for scalability. So you may run into other problems. But nonetheless, here's our warm migration test that we're going to do again. And now that we have less cores assigned to it, it should actually work. That's my theory. So make sure it boots up. Actually, let's go to YouTube. Yeah, good news is because it didn't start on the other one. It didn't move it. But I also told it not to delete. That's an option. And let's actually do that too. So I don't really need these. So let's go ahead and remove them. Wait to VMs. All right. This has started advanced warm migration. Move it over to the lab. Start the migrated VM. That's one of our things we want to do. So we're going to delete the source VM. We're going to do that. We're doing it live because, well, if it breaks, I'm not too worried about it. Hit okay. All right. Let the process begin. And it'll now do that transfer over there. All right. Is that water bottle rum or coke? Well, I don't like rum and coke. I don't like sweet drinks. I like whiskey. But all day, I drink water. I drink coffee in the morning, sometimes some tea later, but mostly water. Because I'm boring like that. Then whiskey is my nighttime drink. So that's my drink for the year. Is there a good online kicker for Germany approximate rewrite differences of various flavors, DFS, disc combinations? Yes. There's this place called, so if we look for it, here we go. Let me throw a link to this. This is a link to my write up that contains links to everything you want to know about DFS, lots of choosing layouts from Clara systems who does amazing jobs, Clara Inc. But there's also benchmarks in here. DFS performance integrity. There's so many things I put together in here. So lots and lots of reading, including even a whole thing from IAC systems on this too. The answer is, it's complicated. So there's not an easy answer for it, but I do break it down and explain it in this entire link. And actually, I keep this maintained. I've actually updated this link several times to talk about, you know, six metric measuring performance. If you look, there's a lot of edits where I've added more things to this. It's kind of a cumulative knowledge on there. How big is that VM in terms of disk space? Good question. Let's go ahead and share this tab instead. I can show you how much is assigned to it, but that's actually not going to give you the answer you're looking for. So 60 gigs is assigned, but I already know it's not 60 gigs. I think this is installed, actually. But why not teach people something fun? Anyone use Duff, D-U-F? I can use D-F. That's obviously going to give you the answer, but Duff is prettier. There we go. Oh, Duff isn't color coded here. I don't know why. Anyways, used is eight gigs. So this is an eight gig VM, eight plus the 250 for boot. So that should help answer that. Oh, hey, look, it's, it's gone. It's, it's finding a new home. So here's its new home, war migration test. And do we delete, is it going to delete the old one? Does it wait till it boots? I don't know. Let's find out. We have two of them now. Oh, cool. It's, it started. It's got the same IP address. Now we get to watch the last process of purging the old VM. I'm assuming it'll do that automatically. So let's see how that works. Still no deletion. Huh. It started. It just isn't, well, I guess we just got to wait for it to delete. Free BSD ping CVE announced today. Neat. Let's look that up real quick, because why not? That sounds interesting. There we go. VulnDB has it. Type BSD was announced. Let's see. Vulnability free BSD operating systems are ready to critical. It affects issue per pack being giving the manipulation with an unknown input leads to stack based overflow. So we have a CVE reserved for it, but not a lot of, not a ton of info here on it. Ping Utility invoked with IPv4. Let's see here. Make sure it's readable for everyone. Request have IP followed by struck time removal. I'm sure more padbyte she's she's buffer over effecting PRPAC function can be leveraged cause stack overflow could lead to a crash or remote code execution in ping. Oh, so you get the ping from BSD to make that happen. If I'm reading this correctly, copies received IP nice and enter stack buffers. So if you're pinging from free BSD and someone replies with the exploit, it can overflow the destination by up to 40 bytes. Okay. Bad. Hopefully, I'm sure it's a fix. Here's their security advisory. Let's pull that up, which is pulling up really slow. But yeah, I'll dig into this. That's interesting. Yep. No workaround is available. Upgrade your frontal system to supportive free BSD stable release branch. So yep. Update if you have that issue. So interesting. Back over to share this tab. So the test worked. I just didn't, it just didn't delete the VM. I don't know why. But here we are running with the VM at the new location with the same IP address. So we'll go with it worked other than other than the deletion part more migration for the first iteration of it here seems to have worked. Same IP address, same everything new VM running old VM off on pool of Zen new VM running on lab server. So cool. That part worked. Last thing I was going to talk about, we got a few more minutes, we can goof off and I'll answer questions if people throw them at me, by the way. But let me find the link to the other thing I'm working on. Where did it go? Or maybe I don't know, it's not on. I'll just pull photos up of it. But we are working on some new stuff that would be sharing with the 45 drive servers. I have been doing some more testing with their Houston OS. So I'll be doing some new videos on that coming soon. That was always going to talk about for 45 drives in didn't have a whole lot to say about it. But it's, you know, it's a it's an I like their platform, the ZFS manager is pretty cool. I moved the server into the other area. And I don't think I plugged the right network cable into it. So because it's not I can't get to the IP address on it. So I'll have to sort that out after my live stream. But nonetheless, I have some upcoming videos on 45 drives with Houston. Those would be some things I'm talking about. So hopefully that's exciting to someone. I think I think people are interested in seeing it. You know, I do plenty of true NAS videos, why not do a few 45 drives videos. Next, a lot of salt and true NAS core was able to pass external data set to that power external data set shows a sub folder. Well, then you passed it through in the wrong spot. You have to pass it through. So it's not a sub folder, you have to change the root of it. What else we got in here, just lots of hello from all over the place, because I don't have I did not come prepared with a lot of things to talk about today, mostly just playing with things here. Actually, remove that out of the way. So I want to change something. Yep, that's what I thought. I just realized that when you have the OTP authentication, it always it always shows it once you're logged in, you can see it again. So you can see the keys. So I want that's why I thought I was hiding that. You know, this is a feature not everyone knows me scroll down. So it hides my OTP key, or a QR code. But when you're doing this, you can change your default filters for things like production VMs, I can change it to like Tom's projects. And once you do that, if it changed the default for this. So I have like these right here. There's a lot of little things like I thought about doing like a UI tips video on some of the little things you can do in here that are just really good practice, not practices as much, but you know, like life help, life hacks, like, hey, use this right here. These tips and tricks will save you time type thing. There's a lot of that in here when you have all these different VMs, and you want to start tagging them differently, whether it's lab or Tom's projects that Tom's working on, like Portainer. Yes, I'm gonna work on a video for Portainer, but I forgot to turn it on. So I guess I should boot it up. I'll be talking about some of those things soon. We need more likes. I'll go with that. Definitely need more likes. More likes are good. What's a good way to find quality engineers from MSE we're offering way above the standard in your area, in our area. Start to find qualified engineers that know what they're doing. Good question. Finding people, I mean, it's not easy and it's partly a fault of the industry because the industry is not matured enough to have a concise way to determine what is or is not a good technician. I mean, we have some certifications. It's getting better. It's substantially better than it was 25 years ago, but it's a challenge because you kind of have to look at candidates. This was a LinkedIn post the other day, and you may see if I can find the post because I thought this was a good way that Huntress looks at. It's one of the things I really look at too. I thought this was just insightful from this write up and I'm going to find it so I can share it here. So posts. Where did that go? Sometimes I post too much. There we go. Share this tab instead. So here's a good article that I will throw a link in here for, but let's just jump to the too long didn't read portion. And this is how they hire. Huntress has hired a really top team of individuals and these are the top three things that they're looking for. And please note that number one is community involvement. Now granted, we're talking about people who are in the cybersecurity space and threat hunting space, but the reality is the community involvement you have will drive a lot of your job offers. I know from working in the open source community, that's how a lot of people, a lot of my friends, not just security friends, but other developers by working on public projects and open source that has led them to really, really good job offers at places. Matter of fact, people seek them out. So they don't put job postings. They go around seeking them out because they're aware that they worked on a lot of public facing projects. You go to the events, you know, where you may find network engineers and things like that, you're more likely to find the candidate you're looking for rather than trying to get them to come to you. And the other challenge right now is if you're good, you're in demand and you're not usually looking for jobs. You almost have, I don't say have to, but it's almost why it's probably why a lot of people go trying to poach those people. For example, Facebook just laid off Metta, whatever you want to call them, laid off 11,000 people. And I'm like, you know how hard it is to get a job at Metta? Those 11,000 people, people are already calling them before their layoff. The time from layoff to job has everything to do with their choice, not whether or not they can find a job. It's qualified people are hard. And it's actually, I think it's a good thing that some of these large companies might be letting some of them go to give smaller companies an opportunity to hire them. But yeah, that definitely, it's just one of those things you really got to think about is like, maybe you have to seek some of them out. Just throwing it out there, the most qualified candidates are always employed. And they just kind of make the decision. I've never, even when I was, you know, people always offered me jobs I never, I haven't looked for a job since I was 16. And I got an attack at like 18. And once I got an attack, I got job offers. I haven't filled out a resume since I was 16. And I, I did job hop a little bit, just offers I got, but people knew me, people knew I was capable of doing things. I always had a long, you know, a lot of people I interacted with, and that sometimes led to them calling me for other jobs. So, one of the best experience, what is the best way to get experience in your resume? What are in what you're interested in? Or what your boss wants to do? I don't, I don't know. I just always ran out and did things and started working on them a lot. So I don't, I don't have an easy answer for that one. Like I always knew what I wanted to do. So I wonder if they have head hunting firms for IT like they do for executive talent. Oh, they more than have head hunting teams, they'll drive you bananas. Go go. I don't know how bad it is on LinkedIn anymore. But I know for a while, a few of my friends, one of them, he developed some of the training for Cisco. And it was wild, just how many job offers he got constantly. He got a recruiter once he had this, he's kind of obnoxious occasionally. But he really got sick of the recruiter. So he would have them do things. Like one time he got them to have a lawn service come and mow his lawn. He said after they did that, then they would, he would consider one of her job offers and things like that. It was kind of funny sometimes. But he was just getting so many job offers. He was just like, I don't know, I'll make them compete with each other. I don't know, do something with them. Thoughts on land sweeper and PRTG. I don't use either of them. So I have no thoughts on them. The other problem too, the want a new job, want a new job thing, there's a lot of terrible offers that are misaligned. Jay told me a great story though of someone calling him, making them a job offer, a headhunter. And it turns out that the place that wanted to hire him, they wanted to hire him for the place he worked to replace him. But the recruiter was disconnected from who he was replacing. So it was kind of a fun story. Homelab was good stuff to put on a resume. Yeah, there's no doubt. Homelab were, I've met people who worked on large open source projects and things like that too. So if you can see him, but you didn't select a delete of him. Oh, I didn't select it. Okay. I thought I did. So that explains, so that probably explains the old VM existing. So let's do this. So let's, let's delete it and remove. Thank you people who notice the details Tom doesn't know. Go back to YouTube, rename this as a nice clean name. All right, we'll take this tag off of it. It's currently in the lab pool. We want to do a warm migration back over to here, delete source, start the VM. So if this works, we've now checked both delete the source for virtual machine and start the VM once it's migrated. So hit okay. So let this run in the background while I babble about things for five more minutes. Are there any cases for which you would hire an IT contractor rather than DIY? I don't understand the question. IT contractor or do it yourself? I mean, we use contractors. So I guess I that's why I don't understand the question. As needed, we use contractors and working in collaboration with other IT companies or IT contractors. So I don't understand the DIY. I guess you mean do it internally? I would read it as that. But yeah. Well, if I'm going to answer a really obvious question here, is this my problem? Should I delete media and go straight to root? If you're seeing a nested destination, because you mounted it at the wrong spot, then the answer to that is yes. So probably if you want it not to have a nested destination, point the root at wherever you did the mount point at. Do you think hyper V core is overlooked? I think hyper V here, call me out on this. I predict Microsoft in five years drops hyper V as a supported product. I think it's hot garbage is my personal opinion of it. I would not run a Microsoft hypervisor. I don't I don't trust Microsoft. They can't even get patching right. Microsoft is a fickle company. They decide where they can make money. And then they put effort there when they don't want to make money, they'll still keep selling the product. But if they think the ratings on the wall, i.e. exchange, they go, you know, we're just going to keep selling the product. But we're going to give you the most worst support ever. Because what are you going to do use something else like our hosted thing? So yeah, I wouldn't surprise if Microsoft gets bored with it because they haven't really built a big monetization model around it. They want you to use their cloud. So I wouldn't build anything future facing out on hyper V. But you do you. And I'm not right about everything. I'm not going to claim I'm right about everything. I think I'm right about this. That's why I'm saying it. But I can you can feel free in five years from now. Hey, time member in blog 307 when you set hyper V and now everyone's using hyper V I'd be utterly shocked. But yeah. So nonetheless, Microsoft just wants stuff to the cloud. XC PNG is getting bigger on things for good reasons. Hey, I'll end this blog at the same time that this finishes. So when this is finished, the blog's over. So you have three minutes remaining while it does the migration, do moving it from here to there. Look at that go. But yeah, skip 45 drive went to disk shelf route, net app, disk array works amazing. Yeah, use whatever works. I like them. I like the 45 drives ones. They there's a reason there's a few more of them at my office that we're doing videos on. I'm too early can't watch because of a meeting. Yeah, I'll be driving later. So hey, look, it's starting. Now I did make sure I checked the delete button. Let's see if it actually deletes. That's where that's where we're waiting on right now. I bet it deletes one that detects the tools running, because that's how it's going to know that it started and worked. So it's probably waiting for the tools to run, you'll know when they run because an IP address will pop up here. That's when you know it's communicating properly. So by the way, this is their first iteration of it. So XC PNG is great. I wish your documentation was good as Microsoft. Well, I'm not going to say the Microsoft has great documentation. And I am among the people contributing to the documentation, like I make a lot of things talking about XC PNG. So I selected delete last time you don't think it's working expected. Okay. I think you might be correct. I thought I did last time someone says I didn't but that's fine. I think the very first time I did not do it. So there is some truth to it. But nonetheless, here we are. But I don't really I don't think in production I would ever click the delete button. I would rather do it exactly as it did it. Move it over, get it started. And that's it. Like, hey, cool, it's over here now. I don't need it over here now. So let's go ahead and remove it. Because it's over here now. Also, now that I know I can use these icons in here, guess, guess what Tom's going to do? I'm going to see what breaks if I put icons everywhere in here. I don't think it matters. But I'm wondering what happens if you name all of these. Now, the VMs are actually all done by these UUIDs right here. That's how they're managed in the backend. But we have these user friendly names up here. And if I put icons and things, wouldn't that be cool? I think that's just novel. Well, anyways, I got to go. I got to go do the next thing. Let's see. Are you better off installing package jails or using a Trinascore thoughts? I don't use jails and Trinascore. So I don't I mean, I kind of do but not much. I prefer to install next cloud as its own thing usually but you do you. Have you ever used watch card? I used them. I hated them. I can't understand why people like the product. I found it not intuitive and nothing impressed me about it. But some people really like it. So if you like it, I don't think they've had too many security issues. Did you cover anchors, cameras, security fast go yet? I recommend Synology for surveillance station. So I didn't look at anchor security cameras. Wait 10 days and delete production. Yeah, pretty much. How is the compatibility XC PNG problems like with providers like OVH? Well, I don't use OVH or Henser. So I don't know. And what Travis said, we like Synology surveillance stations. And a couple of us use you not if I protect. Yeah, I like it better as a Linux VM. But you know, that's my I don't really use next cloud though. I we don't use it in production at all. I play with it. It's not a production thing for me. So I'm not a next cloud expert. We have zero customers using it. And I have zero customers that I will be pushing to next cloud. I don't think anyone the cost savings you get by not paying Microsoft is cool for home users. The cost savings for business is not always as much because the the maintaining can be harder are more expensive. I don't know. Have you sound I've tested it, it works, but I don't use it. I think I have one client using it. I mean, talk a bit more about it because they've got some cool things they do for synchronization. We've we've got a couple clients, I think, using it right now. They're using the drive that the sync locations are using it. So not specifically using drive, but I think it's you know, a a function of drive to do the synchronization, I have to look at it. You know, I should have came out and address this, maybe I'll do a video on it. Last pass hack does not really news. It's just a disclosure. I don't know, everyone seems to get excited about it. There's no meat there. It's like, of course, there's going to be a security incident. They're big. It's saying that this couldn't happen to insert name of smaller company. It may have and they don't know there's one option. It also may be that if I'm going to if I'm a threat actor, where do I put my effort? Do I put my effort in the company with the biggest jackpot or the small company with 100 users just so I can own those users and say, look, they can't say that this product didn't get hacked. You have to think about it from that perspective. The problem is it's a double ledged sword of doing disclosure of you can lose trusting your product because so many companies don't always disclose things very well. And until we understand what was hacked, it's not news. We know that there's an investigation. Great. We know that they have a zero trust architecture model like all the other companies. Awesome. So those at least are some mitigations that should prevent it from being a bigger disaster. I would like to see the debrief. Mandiant has been engaged with this particular last pass event. Mandiant does great jobs on write ups. Awesome. Here we are. That's it. That's enough information for me for now because anything else is just a lot of speculative news and a bunch of news companies trying to be first with the article that has no more information than I just told you. Go read the last cast blog. There's just not much not much to read in there yet because they don't know either. They said there's an incident. Well, they may know some more internally, but they're not ready to release a detail. So they're just following up going, Hey, something happened. There was a thing going on. And we hired the smart people to go look at the thing. More news later, not now. So, you know, we'll see what outcomes of it. If it turns out that they're actually inept, well, that's interesting. And we can talk about that. Oh, yeah, they made some poor choices as a company, but don't shame the victim because reality is someone, a threat actor broke in their door. If someone kicks down my door and you say, Tom, why didn't you use a better door? Why didn't you put a bank vault on the front of your house? I mean, at what point do you think about what's reasonable? And obviously, if your last pass, hopefully you do have a pretty solid door, but you kind of think about that, it's, there's this weird amount of victim blaming when reality is the threat actors are the real problems here. I don't know how to stop them. And obviously, that's a whole different topic. But you got to really think about things in a very objective way, because just subjectively saying, Oh, yeah, of course, last pass got hacked doesn't really help move the security bar forward or think objectively about what's actually going on or provide any real intelligence. By the way, I don't like last pass for other reasons. So security things aside, I'm a bit more user. But you know, I just always like to throw out there, think very objectively about things, as opposed to just getting excited about the news. So build a safe room. There we go. Just get rid of the door. There you go. Doors aren't secure. Exactly. All right, I'm out of here. Have fun, everyone. And then for those of you that are joining me in Ohio Linux, I'll see you next couple days later.