 Have you ever wanted to create your own Arch Linux based distribution? That's what we're going to do today. What I'm going to do is I'm going to use the Arch ISO program. Arch ISO, it's the program that builds the Arch Linux ISO. Arch Linux releases an ISO every month and how do they build that ISO every month? Well, they run the Arch ISO program. The cool thing with Arch ISO though is you can customize the files that are within Arch ISO before you build it, which means you can actually customize it. It doesn't have to be a vanilla Arch Linux ISO that you build. You can add some stuff to it and you can modify it a little bit to make it your own. And one of the things I'm going to do is I'm going to make sure that we also add the Calamari's installer to the Arch ISO that we build. That way, we could share the ISO with others if we wanted to. And it will have a graphical installer, the Calamari's installer that they could run through. You can click OK three or four times and boom, you have your custom distribution on their machine. Now, before I proceed, I do want to warn you that these are deep topics that will require a lot of time invested. If you really want to build your own distro using Arch ISO and the Calamari's installer, because it takes a long time to kind of figure out how Arch ISO and how Calamari's work, those two programs, there's a steep learning curve to them. Now, I did a video about three months ago. I did a video on build your own distro with Arch ISO. And that video is about a 35 minute long video. I spent a few days playing with Arch ISO before I made the video. And even then, you know, I was struggling with some of the things in Arch ISO. Again, it's kind of a deep topic. Now, there is a Arch ISO Wiki page over on the Arch Linux Wiki. I strongly suggest reading that. I also strongly suggest before watching this video, watch that first video on Arch ISO, because I'm not really going to cover the basics with Arch ISO on this video. We're going to actually cover mostly configuring Calamari's and getting Calamari's to build on our Arch ISO. Now, probably what most Linux maintainers do is they have their own custom build of Calamari's that they maintain. Obviously, I'm not a distro maintainer and I don't want to be a distro maintainer. I don't want to put out ISOs for the public and actually be anybody's support channel. And also, I don't want to maintain a Calamari's installer that sees frequent updates, right? So I'm just going to maintain my own version of Calamari's, but it's strictly going to be the Calamari's from the AUR, right? Just the vanilla Calamari's installer that somebody is nice enough to maintain over on the AUR. I'm actually going to get this package build, so I'll go grab the package build. And what I'm going to do is I'm just going to add this to the DTOS Core Repository, DTOS-Core-Repo, which is my own custom repository of software for DTOS. And then when we build the Arch ISO, I'm just going to make sure that I have Calamari's listed as a package that will install during the building of the Arch ISO. So I've covered maintaining my own repository of software on a video in the past. Matter of fact, this video right here, the AUR removed my packages so I created my own repo. I did that video about three years ago where I first decided I was going to create my own repository of Arch Linux packages and maintain it myself. And that shortly became the DTOS Core Repository. So let me switch to this workspace here. I'm going to launch a graphical file manager if I can type correctly. This is PCMan FM, and I have a repository here called DTOS-PackageBuild. And x86 underscore 64 is the architecture. If I go in there, there are all the packages and their package builds for DTOS. And one of the folders in here is Calamari's, and there is the Calamari's package build. Again, I just grabbed that straight from the package build over on the AUR. Then I also have these four extra files that are also needed when I build the Calamari's binary because the package build requires them. If I actually open this, let's open this with Emacs here. And I go down to this block here, which is Source. I'll zoom in a little bit. Make it full screen. You can see Source. It's going to pull down the Calamari's source code from this GitHub repository, but it also expects these four files here to also be present. So that is why it's not just the package build that I have in this directory. I also have those other files as well. And then at that point to actually build the package, I would just open a terminal, and I would CD into the DTOS PackageBuild Repository. Slash x86 underscore 64 slash Calamari's. Do an LS. There's the package build. All I would do at this point is I would do a make package, and I will require my packages to be signed. All the packages for the DTOS repo are signed packages. And then that will build the binary for me. And then the binary will be in this folder here, and I will move that to this repository I have called DTOS-Core-Repo and then go into x86 underscore 64 in this repo. And this is just all the binary packages that I build along with the accompanying signatures. So you can see there is the Calamari's binary that I've already built today, and there is the signature for the Calamari's package as well. Now I don't want to spend too much time talking about packaging for Arch Linux. I've done videos about this in the past, but other than Calamari's, I'm also, I created my own DTOS-Calamari's-Settings package. And all this is, this is a package build that will pull down some config files that Calamari's will read if they're present on your system. And it will pull this down from DTOS slash Etsy slash DTOS-Calamari's-Settings. And they're inside that folder. This is Etsy, so this will be Etsy on the eventual DTOS installation and it will place inside slash Etsy slash Calamari's. It will place all of this, branding, modules, and settings.com. And these are the actual config files that we're going to play with for Calamari's. So let me right click and I'll open this with NeoVim this time. This is the settings.com. Now this file here, I'll zoom in a little bit. All this does is it tells Calamari's which modules are going to be used when the installer runs because there are dozens of modules that could be included in a Calamari's installer. Not all the modules work on all Linux distributions. One of the things with the Calamari's installer that makes it so complicated is it's kind of built as a generic installer for all Linux distributions, but not all Linux distributions are the same. So it's very different using Calamari's on a Debian-based distribution, for example, than it would be on an Arch-based distribution. There's also plugins and modules for building NixOS and Calamari's and things like that. But if I scroll down, we'll eventually get to this block here of Sequence. And under Sequence, we have Show. And then if you've ever run through a Calamari's installer at all, I mean what's the first thing in the Calamari's installer? It's a welcome screen, right? And then typically you pick your locale, and then after that you typically tell it what keyboard layout you want to use. And then you decide the partition, right? Do you want to erase the disk or install alongside another operating system? And then of course you create your username and their strong and complicated password. And then finally you get a summary that tells you everything that you've chosen in the previous sections. And then finally you click OK and the installation begins. And once the installation begins, that is the exec part here. And I have many of the modules commented out. I'm not using very many, but I am going to use the partition module where it partitions the drive, mount, unpacking the file system, machine ID, FS tab, so that's your file system table. So it's going to set all that up automatically for you, right? Then locale, keyboard, you know, I've got a lot of things here. Many of these are just the defaults for Calamaris, but a lot of these modules I have edited a little bit, and I will show you exactly how I edited them. As far as branding, I have default. Now what this is, this is the name of a folder. So if I go back to the file manager, inside slash etsy slash Calamaris slash branding, it expects a folder. The folder will have a name. Whatever the name is, that is the name you need to put here. I'm just using default, but I could rename it DTOS. If I rename the folder DTOS, then the branding needs to be DTOS, so it knows which folder to look in. Other than that, we have some other variables to assign, mostly just setting stuff true or false. I believe I left all of these as defaults, but let's go back to the exec section and all of these modules. Where would you find this? Well, let me go up a directory, because other than branding, we had modules. If I go into modules, there are all the modules that I have played with as far as I needed to edit them in some way. Now some of the modules in the exec section, you can see I actually don't have a config for, so if I don't have a config for it here, what it's going to do is just going to use the default Calamaris files, config files. But if I have my own, it will use my own. Most of these module configs are pretty self-explanatory. Let's look at the users.conf file. So this is the user module where it will create users. You can see the default groups. I'm going to be a member of a video network storage, obviously the wheel group. We need sudo privileges. We need to be a member of the audio group as well. You can see the sudoers group is set to wheel. When I say Calamaris, it's kind of complicated because not all distributions are the same. Not all distributions have a wheel group. For some distributions, the sudoers group is actually a group called sudo, not wheel. But for arch-based distributions, it'll be wheel. And then if I scroll down, one other thing you want to do is allow weak passwords. I set that to true. That way I don't have to use a really long and complicated password. I hate that, especially when I'm testing things in VM. So I'm going to allow weak passwords. I'm also going to set the default user shell to slash bin slash fish. And then finally, hostname. I'm going to set to DTOS-CPU. So when you're running through the Calamaris installer and I create my user DT, and then it's going to ask about the hostname of the computer. If I don't enter one by default, it'll just create that as DTOS-CPU, which is typically x8664. You can see forbidden names for hostname. You can't name your hostname localhost. So that's forbidden. So that was the users.com. Some of the other ones I've played around with, bootloader.com. Let's open that and zoom in. And mainly, you need to edit this for branding purposes. So for me, bootloader entry name, I'm going to make sure that the entry name is DTOS because obviously by default when we're doing the ArchEye, so it'll name everything as Arch. And we've got displaymanager.com. I'm going to use SDDM as the display manager. You can see display managers here are some of the ones that are available. Let's take a look at the mount.conf. And this is just going to be listing out some mount points, say extra mounts, extra mounts, EFI, and then butterfs, sub volumes, and then also have packages.conf. There's really only one thing that you need to worry about here back in. What package manager are you using? On an ArchBase system, obviously, there used to be Pac-Man. Let's close that out. We have removeuser.conf. So it removes a user after the Calamari installer has finished and I want you to remove the user DTOS because in the ArchISO, I've already set up the ArchISO to create a user called DTOS. So I'm telling Calamari, say when you run through an installation, delete the user DTOS. The DTOS home folder and all of that. And then I have a shellprocess.conf. I called it actually shellprocess-final.conf because it's descriptive, because it's obvious what this does. It's after the DTOS installation, after the Calamari has finished unpacking everything and it's pretty much done. I want it to run these particular scripts and I've got these scripts located in user local bin. The first script is remove after installation. This is a list of packages I want Calamaris to remove after it finishes the installation. There's two things I want it to remove. I want it to remove the Calamari installer itself because you never need to run through Calamaris a second time. It's very dangerous to leave the installer on a system. So remove Calamaris after the installation and also remove G-ported because I have G-ported on the ISO if you're running it as a live USB stick. But if you actually run through a proper installation, then after that, remove G-ported from the installation. Then I have a script here for configuring Emacs. This is just starting the Emacs daemon two or three times and answering yes to a few questions so that my Emacs config is ready for use as soon as we're done with the installation. And finally, I have the script fix packman keyring. What this will do, it's going to do a packman-key-init to initialize the keys and then it's going to do a packman-key space--populate archlinux populate with the archlinux keyring. Basically, this should just make sure that packman works for us when we're done because sometimes there'll be issues with the keyring. So let's close that out and most of these other modules I really didn't play too much with and that's really all you have in slash etsy slash Calamaris. You have the settings.com which lists all the modules and the order that they're going to be executed in and then you have the modules themselves and then you have branding, branding, default and here is all of like the slides that get displayed and any kind of artwork. So I have banner.ping here. Let me open this in SXIV so I created this simple little DTOS logo and then I have about four slides here and then you have a file called show.qml open here in NeoVim and essentially this is just the slideshow and I have four different blocks here for slide for four different images. This is one dot ping and this is two dot ping, three dot ping. I may create more images but I created four pretty simple images in GIMP just to have a working slideshow during the installation and you have squid dot ping which I believe is the artwork that appears in the sidebar, at the top of the sidebar where you go through welcome and partitioning and all of that so this is just an image that will appear in that left-hand sidebar typically and then the most important file here is branding dot DESC so let's open that and here you're going to assign various values to various variables some of the most interesting ones though are strings and product name my product name will be DTOS version number, I'm going to say my version number is 2023.7 because it's July 2023 I'm also going to give it a code name I'm going to call it arid armpit since this is the very first DTOS ISO I'm building right we might as well go with the A so arid armpit seemed like an appropriate code name then we have various URLs because there will be buttons that appear in the Calamari's installer you'll typically have a support button release notes things like that and I have given URLs for all of that stuff then we have images I left all the images as the default values I commented out this one here wallpaper dot ping I'm not going to use it but everything else I'm just using the standard images or the names of the images but I have replaced the images like squid dot ping it used to be like a squid like an octopus I actually branded that as a DTOS kind of logo banner dot ping is another big DTOS logo then finally you got style down here which is assigning some color values to things like the sidebar background sidebar text and text current and also background current as well so let me close that out so let's actually build an arch ISO so in my home directory I have a folder that I created called ISO I could have named it anything and in there I have two sub directories I have DTOS 2304 and DTOS 2307 DTOS 2304 was the video I made three months ago on arch ISO that is the ISO that I built DTOS 2307 are what we're about to build so if I click on DTOS 2307 we have this folder Relang now Relang where you need to get that if I go back to my browser here and go to the arch ISO wiki what you need to do is you need to copy recursively slash user slash share slash arch ISO slash config slash Relang over into whatever directory you are copying that over to so I've already copied the Relang folder and inside the Relang folder we have AI root file system right AI root FS so if I go into this you can think of this as the file system that will be built on the ISO as it's created so you have the standard top level directories in here like slash etsy slash root slash user and then slash etsy there's going to be a lot of things that are here by default but I went ahead and added a lot of things that weren't here for example I added sddm.conf file because I'm going to use sddm as a login manager I'm going to make sure sddm is installed when we build the ISO now I've covered a lot of this stuff on the previous video on arch ISO so I won't cover that but some interesting things you need to know about you need to know about the scale directory so this will be a user's home directory once they create a user using the Calamaries installer for example or they could create a user in the terminal you know after the Calamaries installer anytime you create a user on the system where does it get the default configs for a Linux distribution well typically slash etsy slash skill is where they get that default bash rc that gets created or the default fish config zsh rc whatever it happens to be I'm creating a lot of default configs because I'm going to have a default config for the alacrity terminal and also for xmone add and xmobar and kube browser kutall and polybar and I'm going to have a lot of config files in slash etsy slash skill so when I create my user in Calamaries all of this stuff automatically gets placed in my user's home directory that's created some other things in slash etsy is slash etsy slash default slash grub so what this file is by open it and zoom in really I just have this so I can set grub distributor to DTOS so obviously that is distribution name I want to be displayed otherwise we're going to get arch Linux displayed in the grub menu I also created sddm.conf.d so this is the sddm config directory and I have kde underscore settings.conf so what this file does is if you're using sddm for a login manager it allows me to select the default theme for sddm so I'm going to install my custom multicolor dash sddm theme a package of my own that I maintain so that will load our login manager theme slash etsy slash systemd if you go into this you may need to play with some systemd stuff you may need to go into slash etsy slash systemd slash system and you definitely want to have a sim link for display dash manager dot service what display manager do we want to load by default and of course we want to load sddm for our display manager you can see execute start is slash user slash bin slash sddm so that ensures that sddm automatically launches when we boot our computer and let me go back up into the ai root file system so that was slash etsy there is some stuff in slash user so I have slash user local bin and these are various scripts that are needed for things like poly bar, x-mode bar some of these scripts are also used as part of the shell process module for the calamaris installer for example after calamaris finishes the installation it's going to run this script here remove after installation and if I open this and show it to you I'm just doing a sudo pacman dash or calamaris and g-parted remove calamaris and remove g-parted and you can see I prepended it with the yes command just in case pacman asked do I really want to remove it I've already answered the question yes so other than that in slash user I also have a slash user slash share pacman key rings and then I've created my own dtos.gpg and dtos dash trusted for the key ring now I've shown you some of this in the previous video three months ago on arch iso but one last thing I want to cover before I actually build the iso is once again I want to take a look at this so in the relaying directory you should have a file called packages dot x86 underscore 64 so these are all the packages that the arch iso will install when it builds the arch iso so what I've done is here at the top these are all of the packages that the arch iso packages dot x86 underscore 64 file had by default so this is just a vanilla arch iso installation so it's not going to install any graphical programs it's not going to install XOR or Wayland or anything like that right this is when you're done all you've got is the tty right that's a base arch linux install and then I've got this new section of packages that I'm actually going to add to the iso including the calamaris installer now I've already added the dtos core repository to pacman.com so calamaris will be available for installation through pacman as well as all of these other things from the dtos core repository including my config files for dmenu and alacrity the awesome window manager my fish config bash config and various other things I'm going to use lx appearance to set gtk themes lx session will be my session manager and then we have multi-color sddm theme for sddm which is also here shell color scripts of course my shell color scripts that appear every time I launch a terminal and the three window managers that I'm going to install a list of fonts I'm going to install some important GUI applications just to make sure I have some basic stuff installed including emacs mpv pavu control both volume control q browser will be the browser I install there's three shells that I'm going to install some themes and then various command line utilities mostly that I would like to have on the system or in some cases they're actually required dependencies for some other things I'm going to do and then this lengthy section here for xorg related things so there's some xf86 drivers there's various xorg programs including the most important one the xorg server itself I also need xdo tool because it's required for some of what I do with xmobar also I'm going to install a render which is a GUI front end to x render so that allows you to easily change your display resolution so that is the packages.x86 underscore 64 so let's actually install this thing so let's build the ISO so I'm going to zoom way in I'm going to cd into that ISO directory by doing ls let's cd into dts-2307 and if I do another ls there is relaying now from the parent directory of the relaying directory I'm going to run this command here I'm going to do a sudo mk arch ISO so sudo make arch ISO I'm going to give it dash v's the dash v flag is for verbose so we actually get output as it's building then dash w so this is the working directory so it's going to create a working directory in my home directory slash ISO slash dts-2307 slash output so it's going to create this output directory in the same directory that relaying is in and finally we need dash o so this is the output this is actually where it's going to actually place that that ISO that it's going to build I want you to place it in ISO dts-2307 output so the working directory we created is also where I want you to place the ISO once it's finished and then finally we need to specify a directory for arch ISO to actually use as far as you know the AI root file system config files and everything and it's going to use the relaying directory that is in this directory and assuming I've done all of this right if I hit enter it's going to ask for a sudo password of course and it's going to install it looks like 1,226 packages so a base arch Linux installation if I just done the base arch ISO without any of my extra packages no xorg no window managers nothing like that it would have been probably I don't know three or four hundred packages I'm not sure what the base arch install is these days but because I installed Xmonad especially with all the Haskell libraries that it has to install Qtile needs a lot of Python stuff I also installed the awesome window manager which will pull down some Lua stuff you know I've got quite a number of packages that it's going to install typically building this ISO it's going to take I don't know probably five to ten minutes I'm actually going to step away for a minute I'm going to go grab a cup of coffee and the arch ISO finished building you can see the fish shill told me it took eight minutes for that to actually finish building so by doing ls now I have a new directory that was created called output because I told it to create the output directory by cd into output and doing ls I now have dts-23 dot 07 x86 underscore 64 so that is the ISO so what I'm going to do is I'm going to create a virtual machine and let's see if this ISO actually works let's see if calamaris actually launches and then let's run through an installation with the calamaris installer to see if it actually installs correctly so I spun up a VM here invert manager and we get our boot menu and I changed the splash screen here from the arch Linux logo which would typically be here to DTOS right I created this in GIMP in just a couple of minutes and then DTOS install medium so I've removed off the arch branding except for the top of the menu here says arch Linux so I need to go back and correct that it was very tricky to actually remove all of the arch Linux branding from the various files in the arch ISO there's so much there's so many mentions of arch Linux it's kind of hard to come in and change all of the branding and it boots up welcome to DTOS and then we get all the system D start jobs that are running and then eventually it should get to the system D start job for launching SDDM for our display manager yep started SDDM and let's see if it launches with the correct theme that I specified yeah and there it is so let me hide my head so you guys can see that that is a theme created for SDDM now let me change the window manager from Qtile Wayland to Xmodad for one thing I didn't install any Wayland related stuff so I doubt Qtile Wayland would even work so let's go ahead and log in now on the arch ISO I specified the arch ISO to create a live user called DTOS and then slash Etsy slash past WD I specified the DTOS user his password is also DTOS so that is the login credentials if you need them and Xmodad is loading Polybar is loading as well where is that Xmodar I think by default it's using Xmodar and let's go ahead and launch a terminal and let's fix the screen resolution so Calamari's auto started as well let's do a Xrander space dash S 1920 by 1080 fix the screen resolution for whatever reason this sidebar navigation it's just black it's a black background black text you can't read anything if you hover over it it gives you some information that's welcome that's location keyboard partitions users all the steps that the Calamari installer is going to go through but I'm not sure why that is the way it is I actually used several different Calamari's configurations out there on the internet because so many Linux distributions have their Calamari's modules and configuration files on GitLab and GitHub and all of them that I tried I would always get this black rectangle I don't know if it's maybe a missing dependency if anybody has any idea why that is the case help me out on that and I'll go ahead and push this arch ISO build to my GitLab later that way you guys can actually run through the same building at the ISO and then if you wanted to you can try it out in a VM yourself but let's go ahead and see if the installer actually works I'm going to hide my head here I hate the default picture here for the languages this was just an image that comes with Calamari's out of the box but that is really just a horrible picture so I probably should swap that out for something else or create my own kind of language banner but by default American English is chosen I'm going to click next and then geolocation is working because it is correctly chosen the central time zone in the US for me so I'm just going to click next keyboard is English so that's good I'm just going to click next and then finally partitioning we have erase disk or manual partitioning if I do erase disk I'll just give the entire drive of this virtual machine over to DTOS we'll create a swap file swars file systems I have several to choose from and I specified this in the Calamari's config but by default we're going to go with extend for then I'm going to go ahead and click next let's go and create our user I'm going to call my user DT as always and let's create a strong and complicated password for the DT user repeat the strong and complicated password and then click next and then we get our summary location keyboard partitions yet all of this looks good so I'm just going to click the install button and away it goes we should get our slideshow because we've created four slideshow images just to have something going on during the installation so the slideshow is definitely working yeah kind of cool obviously some of my slides you know for DTOS I got to mention emacs and I got to mention wallpapers I always talk about wallpapers every time I install a Linux distribution obviously if I create my own distribution it's all about the wallpapers and then it's going to cycle back through the slides again so I'm going to pause the video this will probably take about five or ten minutes to finish the installation I'll be back once the installation has completed and the installation has completed although I did get an error here at the very end of the Calamari installer when it was running one of those shell processes that I specified the shell process was a fixed pacman key ring so this was going to run through a pacman key and yet in a pacman key populate and for whatever reason it did not do this correctly so let's open a terminal so I'm going to cd into slash user local bin ls and this was the script that it tried to run there at the end of the Calamari installer and for whatever reason it could not run it I try to run it myself yeah watch this thing actually work without an issue when I just run it myself but for whatever reason when it ran part of the Calamari installer it got an error somewhere but it actually completed without it I have no idea so why why that worked when I ran it from the terminal but when it executed here as part of the Calamari installer I'm going to leave this in so if you guys follow this to my get lab later for whatever reason when you run through the Calamari installer and it gets to this if it you get installation filled that's not the case the installation completed because this was the very last part of the installation and so you'll be fine with that just run the script manually to fix the pacman rings so let's go ahead and I'm going to reboot the virtual machine just to verify that this worked let me go into the VM settings first and make sure that it's going to boot in the correct order yeah it's going to boot off the disk so it's already detached the ISO so let's see what our freshly installed DTOS looks like DTOS Linux right there in the grub menu so that worked and we get to our login manager and now my username is DT because that's the user I created right and then let's give the super secure password let's also switch from Qtile Wayland which will not work over to Xmoned and Xmoned launches fine XMobar and khaki let me fix the screen resolution here so once again I'll do an X render dash s 1920 by 1080 and let's fix the wallpaper as well I'm going to do a quick restart of Xmoned to get khaki in the right place and then let me do super pb to set a background wallpaper and I'll just pick one of these and then I'll hit M on the keyboard to mark it supershift C to close that and yeah so this is the VM of our freshly installed DTOS and it installed with the Calamari installer although it did have that error I'll have to investigate that error but what I'll do let me get out of this what I'm going to do is I'm going to go ahead and put all of this on my GitLab if you go to my GitLab at com slash dwt1 that's my GitLab page dwt1 and go to groups and under groups I have a group called DTOS this is all the DTOS related repos and I just created DTOS dash ISO and there is exactly the falls DTOS dash 2307 slash relaying so this is everything you guys need to build an ISO the exact same ISO I just did all you need to do is do a Git clone of this repo and then after you get clone the repo CD into the repo and just run this command that I showed you on camera a minute ago the make arch ISO command and you will build an ISO the exact same ISO that I just built and then of course you can then install it in a VM again just like I just did on camera so there you go how you can create your own customized arch based distribution using the arch ISO program and the calamaris installer again not everything was working quite as expected but I spent about three full days trying to prepare for this particular video I really spent the last three days working on getting calamaris to work just correctly for me and building a lot of packages for my repo to get ready for today's video and the arch ISO video I did about three months ago also took me a few days to actually make that video because again these are kind of deep topics I had to learn a lot just to get to this point now I'm going to go forward with this I doubt it I'm not going to put the ISO that I created out for public consumption I'm not going to go create an account over at SourceForge and start putting ISOs over on SourceForge of DTOS for you guys to download no no no the purpose of this video is for educational purposes as far as how to make your own ISOs so if you want the DTOS ISO I'm not putting it on SourceForge what I want you to do I want you to go to my GitLab get clone that repository and with the make arch ISO command I want you to build the ISO yourself and of course building the ISO yourself you can obviously customize it that way you can add packages remove packages from the build before you actually make the ISO if you want to you can use what I've done here in this repository for you to eventually start your own Linux distribution if that's the route you want to go now before I go I need to think a few special people I need to think the producers of this episode Gabe names Matt, Paul, Royal West, Armor Dragon, Commander Angry, George Lee, Methos, Nate, Er, Yon Paul, Peace Archimvedor, Realities 4 Less, Red Prophet, Roland, Tools Devler, Vorge N2, Anaboon 2 and Willy these guys they're my highest tiered patrons over on Patreon well these guys this episode about Arch ISO and the Calamari Installer it would not have been possible the shows also brought to you by each and every one of these fine ladies and gentlemen all these names you're seeing on the screen right now these are all my supporters over on Patreon without these guys I couldn't do what I do I don't have any corporate sponsors I depend on you guys if you like my work subscribe to Distro Tube over on Patreon alright guys Peace