 We are here today with a special guest and this guy didn't just write the book on ZFS, he wrote two and then he wrote Get Commit Murder and SSH Mastery and everything on this table has been written by Michael W. Lucas. Hi. This guy right here. So if a lot of you have heard of him and if you haven't you're just not reading enough tech books, I'm just gonna throw that out there. This is well known in the BSD communities, the ZFS communities. We know him here because he's a local celebrity. You run the local BSD group and what else do you do, Michael, besides when you're not right all. So there's a little bit of background like what got you into writing and tech and all this fun stuff? Well, I started writing when I was very young. I was like four or five when I discovered that books were written by people and that you could do this as a living. This could be a career. Wow, you can? Yeah, you can. No, Tom, I quit. You have to be this good. I'm just gonna throw it out there. I would like my job back. Okay. And I kept writing all along and then one day in the late 90s I picked up a copy of a magazine. I'm not gonna name the magazine. But it was on technology and I read an article and I said, this article is so badly written, I could do better in the bathroom. And on the next page were the submission guidelines. So I wrote an article at my desk, not in the bathroom. Okay, that was gonna be my question. Okay. I just read there. Right, right. And same. And they published it. They sent me a check for 800 bucks. Wow. And yet at the time there was money in magazines. That's 1990s money. Yes. That's before everything began with WWW. Yes. So at that point, I just started writing more articles and then someone that I knew who had gotten a gig as an editor for O'Reilly's website, they wanted to start a BSD section. He asked me if I wanted a column. So my big scary daemons column ran for a few years. And that turned into Bill Pollock at no starch press contacted me and asked if I wanted to write a book. And things just kind of snowballed after that. It's been so BSD, how did you get started in that little niche? Well, it was I got my first account on a Unix system in the late 80s. I don't remember exactly when I started college in 95. And so I was a BSD user then, because that's what you were. And in 95, the National Science Foundation said that commercial companies could compete on the internet. And they were starting to step back from the internet and just hand the whole thing over to commercial interests. So well, you were companies like UUNet and and ANS from Ann Arbor. I think it was an ANS. I think so. There was a UUNet connection. That was my first connection. I worked in IT back then was all through UUNet. Right. And at the time, basically, you could get a job working for one of these new commercial internet backbones. If you could do basic math, and had rudimentary hygiene, and could answer the phone coherently. Now probably tripped up a lot of people. That trip up a lot of people. The last one. And it was a lot of sink or swim. Yeah, it was, you worked as a gas station attendant. So you had to pass the math test to make change before they'd let you have the job. We'll give you a try. So there was, you know, 90% attrition in the first month. I think it was interesting. That was at a time of such rapid growth. No one knew where it was going. Just like, yes, stuff. It's online. WW, hurry up, hire someone. Yes. And all I knew was I had been a library book cataloger up until then. And I loved the people I work with. I love books. The job was so tedious. So I took the jump. I decided I was going to swim because rent. Money. Yeah, it's always something. And one day I came in to find out that I'd been promoted to DNS administrator. Oh, nice. That's a good promotion. Oh, yes. Yes, except they couldn't keep any of the name servers running. Would have been bind back then, right? Oh, it was always. Yes. It was bind. But systems were having trouble coping with the load. So and I quickly developed an attitudes towards software that that I keep to this day. Good software lets me sleep. Yes, that's a good good software lets you sleep. I worked nights from 11pm to 730am or so. Yeah. So if I got paged during the day or someone called during the day I got woke up. And essentially FreeBSD 2.0 something was the only OS that didn't wake me up. We had a Sunbox that kept dying. I suspect that was because it had about 30 sysadmins. But still it kept dying. All the cooks in the kitchen. Yes, all the cooks in the kitchen. Everyone had root, right? Why wouldn't you? Exactly. We had a Unix wear box that wasn't happy. We tried Windows NT. That let the magic smoke out real quick. Yeah. We tried Linux. No, it it's a different story. Now 1995 was a little different. It's a scalability too. I don't think at the time you could have had that many state tables or anything in Linux and early kernels. It kind of in some ways is still ahead. They're more imperative like you say now. But back then. Yes. And and even now, I firmly believe competition is good. Yes. You'll see things like Facebook hired engineers trying to get the Linux TCP stack up to where it could compete with free BSD. Yeah. And they still haven't managed that. But the the BSDs in general really are very solid. And they've they've turned into my community. I've always been a fan of BSD like for the firewalls, PF Sense, IBC, their the support for ZFS, you know, which of course led me to your talks and the books and things like that. I mean, it's always been really extensive. I always felt Linux better on the desktop. Because I'm just used to it and the driver support for Wi Fi is just mediocre sometimes in BSD. Well, drivers drivers in general. Yeah. Driver support is kind of if the operating system doesn't support the drug, the card I have in my hand, the operating system sucks. Yeah, it doesn't matter. You can support a million network cards perfectly. But if it doesn't support this one, yeah, this one. So there's way to day driver support will change. Yeah. Yeah. So, so as your system in experience, is that what led you to things like SSH mastery? Yeah, this is my new book. I'm thrilled that it's in hard cover. I have all of these books. But this one has nice pointy edges. It sure does. So if someone says that they need their password reset for SSH, and the boss won't let you keep a two by four at the desk, corners are useful corners. Yes. And basically, that goal, that book had the goal of kill all the passwords. Yes. That's why I wrote it. Once you've done key based authentication, you don't know how you ever lived without it. Yes. And so many things are stacked on top of it. So yes, I would, I have a couple tutorials on Ansible. Ansible without SSH keys is not no, it's, it's just not. And there are many things you can do with SSH. There are many things that SSH is a wonderful Swiss Army knife. And there are times you should and should not do things. I've been in companies where the security officer forbid SSH to leave the network because of reverse port reverse tunneling. Yeah. And I've, I've had their job and I'm sympathetic to that. And I try to explain when you should and shouldn't do things. But yes, you can even run a VPN over SSH if you have absolutely no other option. It the reverse tunneling is something cool. Something I thought was neat. And at your talk, I believe you talked about the ways to essentially manage and distribute keys. Yes, things I didn't know what would be that category. And I've been using SSH a long time. I'm like, it does that. Yeah. Well, you can teach an old dog new tricks. You can and, and assessments, we have to continually learn new tricks. Yes, SSH now will, you can centrally manage both host and user keys. If you're using a lot of servers, you might look at a certificate authority. Because an open SSH CA really does save a lot of people trouble. I had discussions with people at BSD can how they are actually ripping out Kerberos to put in SSH CA's. So if you have hundreds or thousands of servers, you might look at it. Now, it's, it's impressive, because you've gone from SSH here, and the ZFS, which I'll read them a couple things. We have talked about and done videos on this channel about the resiliency and amazing properties of ZFS. And a lot of it I learned from, you know, talks that he's done. I've skimmed through this book. I'll, I will, I have not read it cover to cover. That's okay. Did you pay for it? Yeah. Yeah. Okay, I'm happy. Yeah. Yeah, that's really all that matters. I know Mary read it cover to cover. Tony has Tony bought a copy too. So we've all I know he hasn't read his, I don't care if you read them, just send me money. But it's the depth of knowledge you have on ZFS is impressive. Because I try to explain some of your concepts and that makes me have to go I got to read the book again, so I can explain. But it's absolutely amazing. Of a file system. And of course, if you kind of think it's amazing, actually read through what it does in a book, because as many things are as unlocked with Freeness, there's still a few more features that are on there, like the ZFS replication, and some of the ins and outs of that work is it's so much it's substantially superior than our sync, everyone's like, well, we're just going to our sync the stuff. Yeah, until you get to scale, then you have that problem versus BSD, or ZFS on BSD, just, oh, yes, what would you call like our sync on steroids. So yes, yes. First, I have to clarify something here. This book has a co author, Alan Jude. He actually does the BSD now podcast. And he is a ZFS master. So between the knowledge in there is not it's all mine now. But you had a you had a co conspirator. Yes, and I extracted a lot of information from that poor guy. He was so sick of me. It's not even funny. So if you see Alan Jude, he doesn't drink but buy him dinner because he's still recovering. And that's what's actually nice is that you you put a lot of time into very accurate technology. That's something that is wonderful. That's one of the questions. So like, I mean, you have all of these books, there's so much knowledge in these books. I mean, did you did you gain all the knowledge that you have, like in the research for writing them? Or do you did you kind of like I have this, I'm going to put it in a book. And was it or was it kind of like, you know what, I want to learn about that thing. So I'm going to do some research and write a book. Because I started in your background. Oh, yes, tech. Yeah. Well, the the most valuable thing I did as assistant man is I have paper notebooks. Actual paper, you documented as assistant man. I documented for me. Okay, which is very different than documenting for other people. That doesn't happen a lot either. You know, one of those things that the thing I really documented was context and connections. When I figured something out when I had that light bulb moment that two pieces of information came together and I said, Oh, this is how it works. That is what I wrote down. Okay, because that is what a book is for. Anyone can read the man page and get the facts or read the source code and get the facts. But to make a book work, what you're trying to do as an author, you build this mental structure of knowledge in your brain and how it all fits together. And then you practice telepathy. You you take that structure and you break it down into component pieces. And you encode that in these little black marks, and you hand it to another person and inside that person's head, they rebuild that same structure. And the connections, the connections between facts are what makes that hold together. So that's some profound knowledge right there. We all just learned something here. I'm sorry, I like it, though. No, that's really good. Good analogy. I like that. Oh, thank you. You've got a few things that have to happen there. One, I have to make note of those connections. I have to be able to convey those connections to you. So there's this old saying of write what you know. And that is really hard to do because you know it, right? I tend to write something. I tend to write about things that I want to learn more about. One, because then I make sure that I write down the connections between the various facts. And two, because I want to learn about it. Yeah. But I will at times, I mean, by the time I had written the first free BSD book or the first open BSD book, I had been using open BSD for years. I dug through my old notebooks, looking for revelations that I had and use those to assemble the book. And did you rewriting textbooks before the fiction or? Oh, no, I've been writing fiction for deck since I was four or five. But the market for fiction is very different than the market for technology books. Technology books. There was a time where you had to go to the bookstore. And because of the economics of publishing, all of the books were yay thick, and they cost 80 bucks. Yeah. And at times I had bought a tech book for two chapters. Yeah. So unfortunately, everybody knew how that worked and I could expense it. Yeah. But so I'm sorry, what was the question? I had a point. The economics have shifted. Yes. We will shift a little bit because we have not just all these tech books. So I've talked about that we didn't even get to like Pam Mastery all the other previous T. Sissettman books. But occasionally, you should probably stop working and get some fiction in you. Yeah. And that's that's the other side of Michael Lucas. Yes, I've I'm no publishing fiction. All of it with a tech bent or no, no, there is definitely when you have a title like get commit murder, there is definitely some there is some genius. I mean, thank you. We love this. This one in Savage by System D. There's I mean, come on Linux erotica. Hang on that. That's strictly speaking. That's satire. Okay. People either love or loathe that story. It exists. That's that's the most important stuff. For many people it is I I was buried deep in writing the new absolute free BSD. And I one day my brain totally froze up. It absolutely refused. I was writing this section of absolute free BSD on file systems. Which if you look at these books, I have written four of four of these on free BSD file systems and my brain said no, no, no, you also had to take a break from I had to take a break. And so I just started, I said, I'm going to take today. And I'm going to write the most messed up one day piece of work I can. And that turned into Savage by System D. Which is software satire software software. Well, it's fairly explicit. If you accept the software hardcore, if you if you accept the fact that software can have anatomy. Well, hey, um, there seems like there's a time coming when that will be more of a reality. Please no, please no. I don't know. Are we ready for that as a race? Yeah, even your fiction topics. So there's a lot of variation here. They're not under just one theme. I see something more mystical and oh, yes, genetics. And so what's the range here that we should expect from Michael Lucas fiction? Well, mostly science fiction thrillers. I really like the kind of fiction where at any time someone with a flamethrower may run into the room. Okay, yeah. This is what I want out of storytelling. Yeah, these are not all here. Here's the one I was the Savage by System D. Yes. And erotic Unix encounter. I'm sorry. I'm very sorry. It's okay. It exists. And that is a random page and oh goodness. I'm sorry. Wow. I apologize many times. So yes, I've got but I think there's a there's a big choices you have here. So you know, like I said, besides all the big books on technology and deep dives into BSD file systems and Pam authentication, which wow, you wrote a book on that. So any yes, well, Pam had to happen. That's the world is full of Pam. And so many people look at Pam and they either avoid it, or they copy a line off of Stack Exchange and hey, things seem to work. And then the red team comes along and yeah, and rips you wide open Pam is knowable. But don't just stack exchange copy pasta. No, no. And I do have to say I'm really fond of this cover because the smaller books I do parody art covers and you know, American man gothic here is I have that on a shirt. I do like this. And you know, it's funny because I mean, I remember the struggles of setting up Pam years ago when I ran my own mail servers and dovecott integrations with yes, anything else. I just talked to a client this morning and talked him off the ledge because he thought he wanted to spin up open VPN with his own Pam stack and start writing scripts for I'm like, read Michael's book first. I actually said that. I said, once you completed it, tell me if you still want to complete your own stack for this, because he's not an experienced developer. And I'm like, don't start with a security product with open VPN. Start with something integrated as a product and then yes, Pam is a wonderful product. Once you have read Michael Lucas this book and have a clear understanding of what you don't know. I don't know that I'd agree with that it's wonderful. But it exists. And we're here. We have to live with it. Yeah. So it has integrated is how as an obscure historical point. The original painting American Gothic is a farmer with a pitchfork and his daughter. It's not his wife. Oh, I didn't know that. So yes. Okay. So which is one of the reasons why and it's the actually the the person the guy posing is not even if he's a dentist, right? Was he the artist? Yes. Yes. A dentist. Yeah, he just said, you have a good look. Come come with me. Here's a pitchfork. Yeah. So father and daughter pitchfork. Yeah. Hey, how could I not? Yeah. The whole thing's a lie then. Yes. Okay. If this isn't do you think? Do you think at any point you will ever write a BSD BDSM book? No. Okay. Well, just think it seems to go together like it just is. I mean, does play on words. It does. It's a play on words in the middle for a reason, Marvin. After we dug it out. That's probably not the first Michael Lucas book you should get. No, no, it really is the first one. But it may be the last one you have. Exactly. I'm sorry. I cannot recommend that. I would like to see a college course taught. Just just slip it in. It's like slipping in is like like recommended reading like, you know, you're gonna need the required books of free BDS or BSD. I was gonna do it. The SSH mastery and recommended Savage by System D and then just see how many people actually get it and read it. Yes. No. No, no, no. I believe that is why universities have academic conduct committees. Well, this is why you do not work at one having having having worked for a large university in the area. They don't catch everything. Trust me. Someone has an academia background. So someone would complain that book. If you look on Amazon, there are no three star reviews. Well, I am going to fix that immediately. It's overwhelmingly five star and one star. You love it or hate it. Yes. Which as a writer is what I would like. Yeah, sure. Well, yeah, the worst thing. Yeah, the worst thing someone can say is that it was okay mediocre. Yeah, sure. No, no, mediocre is death. Hate me or love me. Nothing in between. Absolutely. Yep. So where can we learn more about Michael Lucas and all his books? Well, I have a website at MWL.io. Alright, we'll stream that here. We're gonna link it all in a doobly-doobly. That has links to fiction. No, no. I bought that specifically for cell phone users. Okay, gotcha. That links I have a separate site for fiction and nonfiction and that links to everything and has my autobiography stories, things like yo, why I hammered myself in the crotch during the most important academic encounter of my life. Okay. And how I want a car. Interesting. Why I only have two thumbs, things like that. Only two. Only two. This was a major issue at one point. Okay. Sometimes there's a need for more occasionally. Occasionally, yes. So two, right? Yeah. Any other trivia you want to share with anyone? Oh, no, no, no. Oh, that's right. You got to go to his Patreon. You got to go to your Patreon page. Go to Michael. Oh, yeah. Go to like Lucas's Patreon links to all this below and for some some support, you can learn two very important pieces of biological trivia about Mr. Michael Lucas. Michael W. He's always going to put there. I have no idea. And it is Michael W. Lucas, not Michael Lucas the porn star, right? Right, right. Michael Lucas. If you both very talented men. Oh, yes, yes. If you're going to be named Michael Lucas, rocket. Oh my God, whatever you do, rocket horror. So no, this has to be turned into a movie starring Michael, Michael Lucas written by Michael W. Lucas starring Michael. No, I didn't. You know what? We're starting a Kickstarter. We're going to make this happen. This is going to happen. This is my new mission in life. I can assure you that the film rights for that story will be very expensive. You you heard him. We need that Kickstarter going right now. Most of it's just to fund the film rights. Yeah, the rest of it won't be on production. He is like, I'm ready for it. You guys talk me into it with this stack of cash. So the cash stack is about as high as his book stack. And it's all right. Yeah, he's like just just keep counting on $100 bills till he says stop. So any conferences you're speaking at coming up? Conferences. I'm submitting to Ohio Linux Fest. Okay, so that'll be the 2018 Ohio Linux Fest. Yes, yes. I don't know if they'll accept you. You're washing this way in the future. Especially not after you've spent the last however many minutes talking about System Deer Attica. They may ask me to stay out of the state. Yeah, not Ohio. Ohio is not worth going to but I mean the Linux Fest is. It's a great Linux Fest. I'm probably going to be there this year. That's uh all it's on the agenda for the moment. That's all that's on the agenda for this year. I'm really trying to focus on making books this year. Okay. Because travel even for a weekend. You spend a bunch of the week before preparing. You spend a bunch of the week after recovering. So all these stacks. This represents how many years of writing? Well, this is about 20 years. Okay. Okay. So how many books would you say you kick out in a year? It depends on the year. Okay. Um the year that I caught gangrene was not a very good year. It's a bad year, yeah. Yeah. I think that was a bad year. You have gangrene. It's a bad year. And and my wife and I have this have a role. I've been with her since about when the Berlin Wall fell and we have a role that only one of us gets to do something stupid at a time. Okay. Okay. Which when I was working full time, this meant uh maybe I was writing a big tech book. Maybe she was getting her master's degree as a nurse practitioner. But but as a family, you can really only support one of those things at a time. Yeah. Because someone has to do the laundry. Yeah. Right. So we would talk it through. There are years I produced zero books. There are years I produced six books and a bunch of short stories. Okay. So so life of the writer is a it's constant up and down. Okay. And yeah, that that's one reason I decided to do the Patreon. Sure. Because uh it it's a very easy to say yes, I have an extra $30,000 coming in this year. So, I'm going to save it for next year. Uh but then your car explodes. There was one time. You get gangrene. You get gangrene. Yeah. All happened. And there was one one really memorable royalty check. No starch press sent me a royalty check for one of my big BSD books and I looked at it and said thank you. I am going to get ahead. This is a check for $8,000 and we can put this in savings. And the next day I walked into my office upstairs and there's this little dark patch in the corner of the ceiling. It's about a $20,000 roof, right? Actually, the roof was $8,000. Okay. Hey. Perfect. Perfect. So, give it and take it the way. Yeah. That's why there's a Patreon. It's it's a lot of work, especially the the level of depth you need to go into to write. Like you said, you had to query other people to co-author like the ZFS book. There's just a lot of time. You have to have a passion for it. You really really do. It's what I love to do. Yeah. Um it it's indoor work. No heavy lifting except when like yeah. But you bring these in. We were all sweating trying to carry these books in. Uh and it it lets me do especially these days I can do some really fun things. Um here's that here's here's the advanced ZFS book uh that I did with Ellen Jude and Ellen put up with a lot. So, I did this special edition of the book for him. Uh it's the Canadian edition because Ellen is Canadian. We had a long running disagreement. Is it ZFS or ZFS? Ah. And so. So, as if you're in Canada. Yes. So, this one everywhere that it says ZFS in the regular edition, it says ZFS here. Okay. Okay. And those kind of you. Yeah. Yes. Not in the commands. And most of my textbooks have footnotes in them. With uh generally at some kind of snark. There is definitely snark in the books by the way. So, spoiler. Yeah. Well, it's enjoyable. That's one of the roles of writing. Speak the truth. Yes. And the truth is the IT business sucks. Oh yes. Anyone who's worked in it there's the glamour until you first if you can survive the meat grinder of desktop support. Yes. And work your way in there. It doesn't get better. It really does. Yeah. What were we just talking about on a vlog Thursday a couple weeks ago was I got my computer degree so I could fix people's printers. All day. All day. That's what Kyle said. Yeah. Now, here's my one disappointment about the cover for the Canadian edition is he should have a toucan. Well, that would have a touc. That this was done in a hurry. It's it's a wraparound cover by the way which and the the it's based on a famous painting but we of course put Beastie on the back and the the saint on the back may or may not look like Matt Aaron's one of the ZFS authors. But this one. That's awesome. Since it's a special edition I put an extra footnote in. Oh. Only five of this will ever exist. I got one. Really? We auctioned one off at BSD can and Alan got three. And I destroyed the electronic originals. So they I could make another one but only five exist and to the best of my knowledge Alan still doesn't know. Oh. Where that special changes and I accidentally leaked it during this talk. So please don't tell him. That's fun. It smells like maple syrup. Maple syrup scented books just for the people. That's just the Canadians. So I do things like that now and then. I mean there's a person I did this book Ed Mastery on Ed the the text editor. Oh, that's there is a free BSD foundation project lead called Ed Mast. That's his real name. So here is the Ed Mast edition of Ed Mastery. Of course. Nice. We auctioned five of those exist again. We auctioned one off for charity. I have one. Ed got three. It lets me do fun things like that. Yeah. And all the language stuff. This is not in my language. No, I'm that's Korean I think. That's just Korean. Yeah. Probably the yeah. I've been translated into nine languages. Wow. So, the the pilots are kind of a cheat because most of the ones that got translated are the thick books which makes it look more impressive. This one is um not English. It's Polish. Oh. Oh. Well, good news because whenever you vlog Thursday and I know for statistics check. I can't tell the difference. I think that's check. We have about a 40% audience outside the US. Yeah. So, yeah, we just know from the stats that YouTube gives us. So, yes, there's you if it's you don't have to just force yourself to learn English to do this. No. It has been translated uh many times over to even whatever the language that we can't we're we're Americans. We only know it. Yeah. We're gonna we're gonna go. We're gonna go. I believe that's check. Let's just go check. Uh so yeah and that that's kind of uh in in my contract with no starch press which does the the big books. It says I get two copies of every translation which sounds great until you've written 30 some books. They've been translated into nine languages and you have to store them. Oh. I think you're like yeah. Yes. Yes. This one's German. Oh, yes. There's German, Russian, Japanese. Wow. French. French. They're often served in German. Oh, yes. I love that. Serving name is how you say server name in. That's great. In German. Yes, they're they're fun to look at and not that I read any of the languages but you wrote it once. You're like, I don't need to read it in other languages. Right. I can't stand to look at finished books. You gotta move on to the next one. Yep. That's awesome. You'll just are you gonna be at the next uh Penguin Con? I will be at Penguin Con. Alright. Probably speaking there too. I I generally do eight to ten talks at Penguin Con. Yeah. And uh so if you are going to Penguin Con, I've talked about a few times in this channel. Uh he at least will pretty consistently be there unless he's got gangrene or something. Uh yeah. If I get gangrene all bets are off. I consider doing any gangrene cosplay while you're there. I could but but it was inside. Oh. So oh goodness. I I could be gangrene cosplaying right now. Then we would never know. And and the really the only way anybody could tell initially we was because of the flatulence. Smelled like almonds. No, that cyanide. Oh you you. So when somebody said, God, did something die in you? You could actually be like, yes. It absolutely did. Yes. Yes. Wow. That's terrible. The annoying part was they wouldn't let me take it home. What? Yeah. I know, right? It was yours. It's it's real. It's personal. Yeah. Yeah. You had been very attached to it. I was. Oh. Well, I think we'll let it go with that. Yes. Yes. Moving on. Well, we'll leave links to where you can find out all this wonderful stuff about Michael Lucas and where you can get his books and uh if you happen to be a Penguin Con or if he is accepted to Hyo Linux Fest 2018. Golden. That's is always a good time or anywhere else but I'm sure you have an itinerary on there and you tweet and you do all that stuff. Yes. You can find me on Twitter. You can find me on Mastodon. You can I have a Facebook fan page although it's basically useless because Facebook. Yeah. Um because we will leave links to all the places you can find Michael. All the places you can find his books and of course his website and he's like I said, he's a social media person so he's tweeting away all day. So, I I rant a fair amount. Yeah. Sorry. That's what you're supposed to do. Social media is for. Social media is for rants and tech people are for ranting. Yeah. Yes. And there's a lot to rant about. Oh, so much ranting. A couple hundred pounds of ranting here, I think. At least it was a lot to get on the table. Alright, thanks. So, thanks Mike for hanging out. Appreciate it. Thank you. Thank you. Alright. Anytime, sir. Thanks for watching. If you like this video, go ahead and click the thumbs up. Leave us some feedback below to let us know any details what you like and didn't like as well because we love hearing the feedback or if you just want to say thanks, leave a comment. If you want to be notified of new videos as they come out, go ahead and subscribe and the bell icon that lets YouTube know that you're interested in notifications. Hopefully, they send them as we've learned with YouTube. Anyways, if you want to contract us for consulting services, you go ahead and hit lornsystems.com and you can reach out to us for all the projects that we can do and help you. We work with a lot of small businesses, IT companies, even some large companies, and you can farm different workout to us or just hire us as a consultant to help design your network. Also, if you want to help the channel in other ways, we have a Patreon. We have affiliate links. You'll find them in the description. You'll also find recommendations to other affiliate links and things you can sign up for on lornsystems.com. Once again, thanks for watching and I'll see you in the next video.