purged history and reuploaded file without password ;)

Signed-off-by: Aiden Gerbrandt <aiden.gerbrandt@entropic.pro>

Arch.md

@@ -3,5 +3,43 @@ tags:
   - Arch
 ---
 
-[[Setup]]
-[[Local Host Names]]
+- [Arch Setup](ArchSetup.md)
+- [Local Host Names](LocalHostNames.md)
+
+## Package Management
+### pacman
+- The package manager for Arch distributions
+- Graphical Software Management tools are not compatible and the command line must be used
+- Packages are installed with `pacman -S <package>`
+- `pacman -Syu` will update all the software on your system
+
+### pacnew
+Sometimes while updating you system you may get a warning about a ".pacnew" file being created.
+This is because when a package updates it's default configuration file but you have changed the current config file to something other than the default pacman cannot automatically replace it with the new one. 
+
+So will keep your current config as it is and create a `/path/to/config/file.pacnew` file wth the new config.
+
+Since sometimes updates bring new features that need to be configured, you should address this right away:
+
+
+1. Run `vimdiff /path/to/config/file /path/to/config/file.pacnew` To view the differances between the files
+    - This requires the `vim` package installed
+2. Edit the current config as needed to add what is missing, either directly in vimdiff or with your text editor of choice.
+3.  Once you are happy you should delete the .pacnew file.
+
+### yay
+- yay is a wrapper for pacman and uses pacman for normal package management
+- yay additionally will automate the proccess of installing and updating packages from the [AUR](https://wiki.archlinux.org/title/Aur)
+- It functions the same but `yay` is a shortcut for `yay -Syu` (to update the system)
+- Software from `aur` should not automatically be trusted (see below)
+  - yay will ask if you want to "view diffs" when installing or updating, this is a quick way to check the pkgbuild and the differences to the new pkgbuild when updating
+
+### Arch User Repository
+The AUR is a collection of packages uploaded and maintained by the Arch community, and not the offical Arch maintainers.
+It is a great resource as an easy way to install software not provided in the main Arch repos, but it is worth noting that anyone can upload anything, and there have been known cases of people uploading malware.
+
+The nice thing is that the entire package format (known as the pkgbuild) is accessbale and human readable.
+This does mean that any issues are eventually caught, but as with any case of downloading software off the internet, sticking to well known packages with lots of eyes on them is usually a good idea.
+It is also a good idea to inspect the pkgbuild yourself, especially pay attention to the URLs within the file and ensure they are pointing to the correct place.
+
+Packages in the AUR are not offically supported or considered by the Arch Maintainers when pushing updates, so if anything on your system will break from an update, it's more likely to be an AUR package.

ArchSetup.md

@@ -1,10 +1,10 @@
 Links:
-[[Arch]]
+[Arch](Arch.md)
 
-### Secure Boot
+## Secure Boot
 If setting up secure boot with EndeavourOS, don't use the preset grub. do it from scratch.
 The wiki is wrong and your ${GRUB_MODULES} needs to be in ""
-#### Steps
+### Steps
 1. [Install grub following the shim-lock info ](https://wiki.archlinux.org/title/GRUB#Shim-lock)
 	- If you do not have any drives with a ZFS filesystem, you should exclude the zfs* modules (As they require the ZFS [DKMS](https://wiki.archlinux.org/title/DKMS) Module)
 2. Move `grubx64.efi` into the `esp/EFI/BOOT` directory and ensure is has that name.

ConnectingSMBShares.md

@@ -4,25 +4,28 @@ tags:
   - Bazzite
 ---
 
-Make sure you can connect to the share using hostname.local. see [[Local Host Names]]
+## Important Notes
+1. Make sure you can connect to the share using hostname.local. see [Local Host Names](LocalHostNames.md)
+2. **If changing location of the scripts** you need to update the script name to match the path exactly
+3. Replace `<server-name>` everywhere below with the name of your server 
+4. If running [Bazzite](Bazzite.md),  becuase of how fedora immutable distros are setup you need to use `/var/mnt`. the actual path is `/var/mnt` and `/mnt` is just linked to it.
 
-**if changing location of the scripts** you need to update the script name to match the path exactly
-
-Create a file called `.tardis-creds` in your home dir and set it so it's only readable by you like before.  
+## Create systemd mount file
+Create a file called `.<server-name>-creds` in your home dir and set it so it's only readable by you like before.  
 Put
 
 ```
-username=tess 
-password=tess`
+username=<username>
+password=<password>
 ```
 
 in the file
 
-create the file `/etc/systemd/system/mnt-tardis.mount`  
+create the file `/etc/systemd/system/mnt-<servername>.mount`
+(this will be mounted to `/mnt/<server-name>`)
+
 In the file put the below:
 
-
-
 ```
 [Unit]
 Description=Mount SMB share Tardis
@@ -33,14 +36,14 @@ Wants=network-online.target systemd-resolved.service
 
 Mount] #
 "What" is what will be mounted. ie our NAS SMB share
-What=//tardis.local/files
+What=//<server-name>.local/<shared-folder>
 # "Where" is where it will be mounted in the filesystem
-Where=/var/mnt/tardis
+Where=/var/mnt/<server-name>
 Type=cifs
 # Let the mounted filesystem be read/write-able
 # Let the mounted filesystem be owned by the 'tess' user/group
 # Use the specified credential file for the connection 
-Options=rw,uid=<uid>,gid=<gid>,nofail,credentials=/home/**username**/.tardis-creds
+Options=rw,uid=<uid>,gid=<gid>,nofail,credentials=/home/**username**/.<server-name>-creds
 # Lets quit trying after 30 seconds 
 TimeoutSec=30  
 
@@ -54,44 +57,46 @@ They will probably both be 1000 (so `uid=1000,gid=1000`), but you can check wit
 
 This is telling systemd how to mount your drive.
 
-Now create the automount file `/etc/systemd/system/mnt-tardis.automount`  
+## Create systemd automount file
+Now create the automount file `/etc/systemd/system/mnt-<server-name>.automount`  
 In that file put:
 
 ```
 [Unit] 
-Description=Automount SMB share Tardis  
+Description=Automount SMB share <server-name> 
 
 [Automount]
 # Adjust mount location to match yours.
-Where=/mnt/tardis
+Where=/mnt/<server-name>
 
 [Install]
 WantedBy=multi-user.target`
 ```
 
+## Test and Apply configuration
 Now we want to make the directory it will be mounting to  
-`sudo mkdir /mnt/tardis`  
+`sudo mkdir /mnt/<server-name>`
 
 Then we reload systemd  
 `sudo systemctl daemon-reload`
 
 First we start the .mount, and check for errors
 ```
-sudo systemctl start mnt-tardis.mount 
-systemctl status var-mnt-tardis.mount
+sudo systemctl start mnt-<server-name>.mount 
+systemctl status var-mnt-<server-name>.mount
 ```
 Then if there's no issues we can stop the normal mount and enable automount
 
 ```
-sudo systemctl stop mnt-tardis.mount 
-sudo systemctl enable --now var-mnt-tardis.automount
+sudo systemctl stop mnt-<server-name>.mount 
+sudo systemctl enable --now var-mnt-<server-name>.automount
 ```
 (`enable` means we are telling it to run on boot, and `--now` it telling it to also start it now)  
+
 We could just enable the normal mount and have it mount on boot, but automount will mean it will only connect to the samba drive when we try to access it.
 
-now we should see it show up under `/mnt/tardis`  
+Now we should see it show up under `/mnt/<server-name>`  
 And if we reboot it should show up still.
 
+## Additional Notes
 For reference Aiden based it off  of  [This](https://www.reddit.com/r/SteamDeck/comments/ymjnjy/mounting_smb_shares_with_systemd/) this post, just modified to this situation and me
-
-if running [[Bazzite]],  becuase of how fedora immutable distros are setup you need to use `/var/mnt`. the actual path is `/var/mnt` and `/mnt` is just linked to it.

Debian.md

@@ -0,0 +1,12 @@
+---
+tags:
+  - Debian
+---
+
+## Package Management
+### apt
+  - The package manager for Debian-based distros such as Ubuntu and Mint
+  - Graphical Software Management tools such as KDE Discover and GNOME Software are compatible
+  - Packages are installed with `apt install <package>` and uninstalled with `apt remove <package>`
+  - `apt update` will pull the latest information to know what packages have new versions
+  - `apt upgrade` will then update your system and installed programs

Distros.md

@@ -3,16 +3,46 @@ tags:
   - Arch
   - Bazzite
   - Debian
----
-[[Arch]]
-- EndeavourOS
-
-[[Bazzite]]
   - Fedora
-- Gaming focused
-- immutable OS
+---
+## Distro List:
+### [Arch](Arch.md)
+- Installed from scratch, without an installer program
+- Rolling Release
+- The latest versions of software, drivers, ect possible available
+- Less time for changes to be tested, so more risk of breaking changes
+  - Fixes are usually pushed out quickly
+- The [ArchWiki](https://wiki.archlinux.org/) is an amazing resource
 
-[[Debian]]
-- Server focused
-- Stable
-- Older versions
+### [Bazzite](Bazzite.md)
+- Fedora-based
+- Gaming focused
+- [Immutable OS](PackageManagement.md#immutable-os)
+
+### [Debian](Debian.md)
+- Stable Release
+  - New stable release every 2 years and it thoughly tested.
+- Extremely resistant to breaking changes
+  - A favorite for Servers due to this
+- Will never have the lastest version of any software
+  - Security and Bugfix patches are still brought regularly
+
+### EndeavourOS
+- Arch-based
+- Is nearly identical to Arch
+- Unlike Arch it has a nice installer to set the OS up for you
+
+### [Fedora](Fedora.md)
+- Stable Release
+  - New stable release every 6 months
+- Usually a good balance between something like Debian and Arch
+  - Relatively recent software and well tested together
+- Commonly used for non-windows Enterprise Desktops
+
+## Rolling Release vs Stable Release
+Rolling Release distros will package updates for any software and send it out to be updated on your system as soon as they determine it is good to go.
+
+Whereas a Stable Release distros will accumulate new versions of software, testing them all together before pushing all the updates together at once and a new "version" of the OS.
+
+For desktop use Rolling Release is perfectly good and can be nice in the sense you don't have to wait for a new version of your OS to get the lastest update for your software. 
+But stable release distros have the advatage of getting more time to test to catch and fix any weird problems a new update may have.

LocalHostNames.md

@@ -1,4 +1,4 @@
 the ability to use hostname.local is managed by avahi
 To use a configured avahi, avahi-daemon.service needs to be running and port udp 5353 needs to be open in your firewall
 
-needs to be set up to [[Connecting to samba shares (tardis)]]
+needs to be set up to [Connecting to samba shares (tardis)](ConnectingSMBShares.md)

PackageManagement.md

@@ -0,0 +1,56 @@
+---
+tags:
+  - Arch
+  - Debian
+  - Bazzite
+---
+
+# Installing Software on Linux
+## Package Management
+### Windows
+In windows usually software is installed by going to that software's website, downloading and running the installer, and programs are responsible for keeping themselves up to date. 
+### Linux
+In Linux you should almost always install software through an official repository. Usually the maintainers of a linux distribution will maintain an official repository of software (including everything from system libraries and utilities to graphical applications), that can be downloaded and installed. 
+### Package Manager
+Instead of manually downloading, installing updating individual software packages, your system will have a Package Manager, which does exactly that. 
+
+You tell it what software you want, it'll download it and all its dependencies and install them. That also means you can tell your package manager to update and it'll manage making sure all your software is up to date, without programs have to individually manage it themselves. Traditionally you interacted with these package managers through the command line, but people have made graphical front ends for some of them, which allow you to browse and install software, and update your system through them.
+
+#### Examples
+- ##### [apt](Debian.md#apt)
+- ##### [pacman](Arch.md#pacman)
+- ##### flatpak
+  - Unlike other package managers, flatpak is built to work on any linux distribution and installs software entirely seperate from your system
+  - Graphical Software Management tools such as KDE Discover, GNOME and Bazaar Software are compatible.
+  - Flatpak programs can be installed system-wide or just for a single user.
+  - There have been no known cases of malware from flathub, but the usual disclaimers of downloading programs applies.
+    - Flatpak packages are often maintained by community members.
+    - "Verified" only means that the devlopers of that software are the ones maintaining that package.
+
+## Immutable OS
+There are now some Linux Distrobutions which are refered to as "Immutable"
+
+What this means is that base system is a fixed, unchangeable thing. Which means you can't install software in the same way.
+
+You can picture you system exisiting as 3 layers:
+### 1. System Layer
+The system is the base layer which includes all the software that runs your Operating Systems.
+In immutable systems, this layer is a fixed unchangeable thing.
+This means when you have a system update, the entire new system layer is downloaded and swapped in to replace your current one on the next reboot.
+- This ensures system updates are very clean, and it means the old system layer can be kept around, and used if there is something wrong with the new version.
+
+Normally new software is installed directly to the system, but that is not possible in this case, since the System Layer cannot be edited. This is where the next two layers come from.
+### 2. Package Layer
+Usually software can be installed in the User Layer (see below), but sometimes software needs to be install onto the system itself, such as programs the interact directly with hardware.
+
+In this case packages can be installed on top of the Base System in this layer. 
+Packages installed here integrated tightly with the system and do add complexity, so if a program will work fine installed with other local options, then that should be chosen.
+But there are cases where this is the correct and best option.
+
+On Bazzite programs are installed this way with `rpm-ostree install <package>`
+And it will install Fedora packages.
+
+### 3. User Layer
+The User "layer" is everything that is installed and changed by each individual user and will all be contained to within their `/home/<username>` directory.
+For the most part in immutable systems, additional software will be installed here.
+Package managers such as [flatpak](#flatpak) (Graphical programs) and Brew (Command-line programs) will install programs locally.