diff options
Diffstat (limited to 'public/articals/linux')
| -rw-r--r-- | public/articals/linux/ArchLinux/Cleaning.html | 57 | ||||
| -rw-r--r-- | public/articals/linux/ArchLinux/Optimizing.html | 62 | ||||
| -rw-r--r-- | public/articals/linux/info/FileHierarchy.html | 90 | ||||
| -rw-r--r-- | public/articals/linux/info/Terminal.html | 48 | ||||
| -rw-r--r-- | public/articals/linux/media/BurningIsos.html | 69 | ||||
| -rw-r--r-- | public/articals/linux/media/EncryptingUSB.html | 94 | ||||
| -rw-r--r-- | public/articals/linux/media/FormattingUSB.html | 67 | ||||
| -rw-r--r-- | public/articals/linux/media/cd.html | 76 | ||||
| -rw-r--r-- | public/articals/linux/server/git.html | 197 | ||||
| -rw-r--r-- | public/articals/linux/tools/TarGz.html | 52 | ||||
| -rw-r--r-- | public/articals/linux/tools/Ventoy.html | 74 |
11 files changed, 0 insertions, 886 deletions
diff --git a/public/articals/linux/ArchLinux/Cleaning.html b/public/articals/linux/ArchLinux/Cleaning.html deleted file mode 100644 index dc32a02..0000000 --- a/public/articals/linux/ArchLinux/Cleaning.html +++ /dev/null @@ -1,57 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Cleaning Arch Linux</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>How to Clean Arch Linux π§Ή</h1> - <h3>Date: 21-7-2024</h3> - <p>In this artical I will be telling you how to clean up your <a href="https://archlinux.org">Arch Linux system</a> in the same way I do so.</p> - <hr> - <h2>Package Cache</h2> - <p>The first thing you want to do is clean the Pacman cache, as Pacman does not automatically clean it. This is because Pacman retains the cache in case you need to downgrade a package or reinstall it after uninstalling. To clean the cache, use the following commands:</p> - <div class="code-box"> - <p>sudo pacman -Sc # Remove packages from cache not installed</p> - <p>sudo pacman -Scc # Remove packages from cache both installed and not installed</p> - </div> - <p>Some people like to automate this task of cleaning the cache with <a href="https://wiki.archlinux.org/title/Pacman#Cleaning_the_package_cache">paccache</a>, but personally I would not because it is something that takes around five minutes max to do. However, it is your choice if you want to do so to avoid the trouble of doing it manually. Regardless of whether you choose to do this manually or automatically, I suggest cleaning the cache monthly. - </p> - <hr> - <h2>Removing Orphan Packages</h2> - <p>Orphan packages are those installed as dependencies for other software but are no longer needed. For example, when you install <a href="https://librewolf.net/">LibreWolf</a>, it downloads a package called librewolf-debug as a dependency. Once the installation is complete, librewolf-debug becomes an orphan package because it is no longer used by LibreWolf.</p> - - <div class="code-box"> - <p>sudo pacman -Qtdq # Identify orphan packages</p> - <p>sudo pacman -Rns $(pacman -Qtdq) # Uninstall orphan packages</p> - </div> - <p>I suggest uninstalling Orphan packages every month or so, just like cleaning the Pacman cache.</p> - <hr> - <h2>Cache</h2> - <p>Sometimes you want to clean out the ~/.cache directory, as it can accumulate a large number of files from various programs on your system. The cache directory contains temporary files used by different applications to speed up their processes. In general, it is safe to delete all items in this directory, but be cautious if you have specific applications with unusual caching mechanisms. To clean the cache directory run the following command:</p> - <div class="code-box"> - <p>rm -rf ~/.cache/* # Clear the cache directory</p> - </div> - <hr> - <center> - <p>That is all for now, I hope this artical has helped you clean your system.</p> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/ArchLinux/Optimizing.html b/public/articals/linux/ArchLinux/Optimizing.html deleted file mode 100644 index 0596aa8..0000000 --- a/public/articals/linux/ArchLinux/Optimizing.html +++ /dev/null @@ -1,62 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Speeding up Pacman π</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>How to speed up Pacman π</h1> - <h3>Date: 23-7-2024</h3> - <hr> - <p>It is very easy to speed up Pacman, and we can do it in a few easy steps, so follow this guide, and your favourite package manager will be fast as anything!</p> - <hr> - <h2>Pacman.conf</h2> - <p>Pacman can download packages in parallel, meaning you are able to download more than one package at a time, which makes the process of installing and updating packages way faster!</p> - - <p>The first thing you want to do is go to the location of pacman.conf, which is located in <b>/etc/pacman.conf</b>. So you would want to run a command like this but with your preferred text editor:</p> - <div class=code-box> - <p>sudo nvim /etc/pacman.conf</p> - </div> - <p>Now that you are in the configuration file, you want to navigate to a section where it says <b>Misc options</b>. You want to uncomment the line where it says <b>'ParallelDownloads.'</b> It should look something like this:</p> - <div class=code-box> - <p># Misc options<br> - #UseSyslog<br> - Color<br> - #NoProgressBar<br> - CheckSpace<br> - #VerbosePkgLists<br> - ParallelDownloads = 5<br> - ILoveCandy</p> - </div> - <p>If you have a keen eye, you may have spotted the last line, which says 'I Love Candy,' and the reason why this line is here is because it gives the Pacman prompt when you run it a bit of styal with the pound signs being replaced with Pacman!</p> - <hr> - <h2>Mirrors πͺ</h2> - <p>If you did not know, a mirror is a server where the packages you install are hosted. Ideally, you want to download all of your packages from the fastest mirrors, so let me show you how to do that!</p> - <p>The first thing you will need to do is install the reflector program and run the reflector command.</p> - <div class=code-box> - <p>sudo pacman -S reflector<br> sudo reflector --latest 10 --sort rate --save /etc/pacman.d/mirrorlist<br>sudo pacman -Syy # To update package list from server</p> - </div> - <p>After running this command, your download speed should be way faster!</p> - <hr> - <center> - <p>I hope this has helped you in making Pacman not only look better but function better!</p> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/info/FileHierarchy.html b/public/articals/linux/info/FileHierarchy.html deleted file mode 100644 index fcc6682..0000000 --- a/public/articals/linux/info/FileHierarchy.html +++ /dev/null @@ -1,90 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Linuxx file hierarchy</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>The Linux File Hierarchy</h1> - <h3>Date: 05:8:2024</h3> - <hr> - <p>Like any other operating system Linux has a File Hierarchy, due to the fact that the Linux operating system is a <a href="https://en.wikipedia.org/wiki/Unix-like">Unix-like</a> operating system the infomation in this article can be applied to BSD and any modern versions of Unix like <a href="https://www.oracle.com/solaris/solaris11/">Solaris</a> or <a href="https://www.ibm.com/products/aix">IBM's AIX</a>.</p> - <hr> - <h2>/ (root)</h2> - <p>Every single varient of Linux has a root directory reposented by the forward slash symbol '/' it is the highest level directory in Linux and it stores all the system files that make it possable to run Linux.</p> - <hr> - <h2>/bin</h2> - <p>The bin directory is where all of the executable binaries are stored, this allows you to use commands like ''cd', 'mkdir' and all the commands you can type into your command line.</p> - <hr> - <h2>/boot</h2> - <p>The /boot directory holds all the files needed for you to be able to boot up your Linux system. It includes configuration files for whatever bootloader you are using and other components, such as the installed kernel and the initial RAM disk. The kernel is the main part of every operating system, from Windows to Linux to BSD. Its goal is to allocate resources to programs and allow them to run, while the initial RAM disk is just there to mount the root filesystem at boot. If you have more than one kernel installed, it will be stored in the /boot directory, so if you plan to install more than one kernel, I would strongly suggest allocating some more space to this directory.</p> - <hr> - <h2>/dev</h2> - <p>The /dev directory contains files that represent the hardware devices of your computer, such as hard drives, terminals, and such. These device files allow the operating system and software to interact with the hardware. For example, if you have ever installed Arch Linux or Gentoo /dev/sda would be the first SATA drive on your computer, while something like /dev/tty20 would represent the twentieth terminal on the system. Also the /dev directory includes virtual device files, such as /dev/null, which discards all data written to it, and /dev/random, which generates random numbers. These virtual devices provide various system functions that do not interact with the physical hardware.</p> - <hr> - <h2>/etc</h2> - <p>The etc directory contains configuration files for all of the system-wide settings. It includes configurations for system services, users, and various applications. A few essential files in /etc would be the fstab file which defines how all the disk partitions are mounted on boot and if this is not present well your computer will not mount propally meaning you will not be able to boot, /etc/passwd which contains user info, and /etc/hostname which has the systemβs hostname whithin it. This directory is needed for managing your Linux system because it holds many aspects of system behavior and configuration.</p><hr> - - <h2>/home</h2> - <p>The /home directory is where users' files are stored. Each user on the system has a subdirectory within /home, normally named after their username, where they can store personal files, configurations, and other personal files. For example, my user is "shipwreckt" and I have my home directory in /home/shipwreckt. This directory is essential for normal computer use.</p><hr> - - <h2>/lib</h2> - <p>The /lib directory holds all of the shared library files that are needed by programs. In these libraries is the code for various programs to run; an example would be the C library, which is essential for programs written in C (who would have guessed). This directory is critical for the running of programs and your system as a whole.</p><hr> - - <h2>/lib64</h2> - <p>The /lib64 directory is basically the same as /lib but it holds 64-bit libraries. If your Linux system runs on a 64-bit architecture, /lib64 contains the needed libraries required for 64-bit programmes. While /lib normally contains 32-bit libraries, the separation helps in managing libraries for different system architectures.</p><hr> - - <h2>/media</h2> - <p>The /media directory is used for mounting removable media like USBs, CDs, and if you are old floppy disks. When a removable device is plugged into the computer, it should be mounted to the /media directory. On some Linux systems, like Arch Linux, there is no /media directory but there is a /run/media directory. Removable media is not automatically mounted, so you might need to do this manually, be that through your file manager or the terminal.<p><hr> - - <h2>/mnt</h2> - <p>The /mnt directory is used for mounting other hard drives on your computer. On my computer I have two drives my NVME drive that has Arch Linux installed on it and my secondary drive that I use for backups, the drive is in /mnt sadly there is not much to say about /mnt but this is all I know about it.</p><hr> - - <h2>/opt</h2> - <p>The /opt directory is used for installing third-party software are not part of the default system. Software installed here does not normally need core system components. In my /opt I only have the <a href="https://nuclear.js.org/">nuclear music player</a> and to my knowlage only programs written in higher level programming langauges like python and java are installed here.</p><hr> - - <h2>/proc</h2> - <p>the /proc directory is a virtual filesystem that gives us a view into the kernel's internal data structures. This directory contains infomation about system processes and a bunch of kernel parameters. Files in /proc are not readable files but are created over time by the kernel. For example /proc/cpuinfo holds a bunch of useful infomaiton about your CPU, whilst /proc/meminfo shows memory usage. This directroy is needed ofr monitoring and managing system performance</p><hr> - - <h2>/root</h2> - <p>If you did not know root is technically a user and its home directory is not in /home instead it is in the /root. It is used to store anything a normal user would use their home directory for.</p><hr> - - <h2>/sbin</h2> - <p>The /sbin directory contains essential binaries and commands that are used by the root user. Unlike the /bin directory which includes binarys for basic programs for all users to use /sbin holds commands that can only be used by the root user. It contains lots of useful programs like 'fsck' and more.</p><hr> - - <h2>/srv</h2> - <p>/srv stands for "service" and is used to hold files that are served by various system services such as web servers. By default I beleve on all Linux systems /srv has two files in it, being http and ftp both being types of web servers. There is not much to say about /srv but you are only really going to use it if you are messing around with websites.</p><hr> - - <h2>/sys</h2> - <p>The /sys directory is a virtual filesystem that allows us to examine the kernel's hardware and device model in greater detail. /sys is specifically made to interact with and set up kernel subsystems and hardware devices. Similar to /proc, the contents of this directory are generated in real time by the kernel and are important to understanding the hardware of your Linux system.</p><hr> - <h2>/tmp</h2> - <p>The /tmp directory is used for storing temporary files created by programs and system processes. It serves as a place for programs to dump their data that is only needed temporarily. Files in /tmp are normally deleted on reboot or after a certain period of time. This directory is needed for many programs to work. There is not much else to say apart from do not store normal files here just in case they disappear!</p><hr> - <h2>/usr</h2> - <p>The /usr directory is a very important part of the Linux filesystem, it stores user related programs and data. It contains a lot of the system's executable programs, libraries, and more. Within /usr you will find a few important directories /usr/bin that holds binaries /usr/lib that holds libraries, /usr/share which contains documentation and configuration files. /usr is made for files to be used by all users. It is essential for programs to function.</p><hr> - <h2>/var</h2> - <p>The /var directory is used to store variable data that changes all the time while yout system is powered on. Important things such as logs, mail spools, and temporary files. If you are running a server I do suggest giving /var its own partition because it allows for easy backup and recovery.</p><hr> - <h2>Overview</h2> - <p>This has took me a while to write because I have had to double check everything and put it in my own words so I understand it! If there are any issues please with this artical please report it.</p> - <p>As normal thank you for reading!</p><hr> - <center> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - - </main> -</body> -</html> - diff --git a/public/articals/linux/info/Terminal.html b/public/articals/linux/info/Terminal.html deleted file mode 100644 index 1578211..0000000 --- a/public/articals/linux/info/Terminal.html +++ /dev/null @@ -1,48 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Terminal > GUI</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>Why the terminal will always beat the GUI π¨βπ»</h1> - <h3>Date: 27-08-2024</h3><hr> - <p>I want to say this now, I do not care if people use a GUI option for things, Linux is all about choice and if you choose to use a GUI instead of using the terminal that is your choice!</p><hr> - - <h3>1) The Terminal Simplifies Tasks With Fewer Steps:</h3> - <p>Using the terminal can be way faster and more straightforward than navigating a GUI. For example, updating your Linux system requires one simple command in the terminal. In contrast, using a GUI software centre involves way more steps: opening the software center, navigating to the update section, and then updating all the programs. The terminal streamlines all of this which makes it way more efficient.</p><hr> - - <h3>2) Enhanced Efficiency</h3> - <p>A GUI is essentially the command line dressed up with buttons and such, allowing users to execute commands through the elements of the GUI. While this is useful for those who are less familiar with computers, for technical users like you and me, we seek greater efficiency. By learning how to use the command line, we can perform tasks more quickly with only a few words. This not only saves us time but also enhances our productivity.</p><hr> - - <h3>3) Understanding The System</h3> - <p>By learning all of these command-line tools over time, you will start learning how a Linux system works and operates, and this will help you fix any issues that pop up in the future. For example, if you wanted to format a USB stick, while yes, you could use <a href="https://apps.gnome.org/DiskUtility/">Gnome-disk</a>, it is faster just to use <a href="https://linux.die.net/man/8/fdisk">fdisk</a> and <a href-"https://linux.die.net/man/8/mkfs">mkfs</a> for formatting a USB stick.</p><hr> - - <h2>Kool TUI / CLI programs</h2> - <ul> - <li>MPV - Video player</li> - <li>FEH - Image viewer</li> - </ul> - <hr> - <p>For now that is all I have on why terminal is better!</p> - <hr><center> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/media/BurningIsos.html b/public/articals/linux/media/BurningIsos.html deleted file mode 100644 index 6bcab23..0000000 --- a/public/articals/linux/media/BurningIsos.html +++ /dev/null @@ -1,69 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Burning an ISO π₯πΎ</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>How to burn an ISO to a USB stick πΎ</h1> - <h3>Date: 24-08-2024</h3> - <hr> - <p>Burning an ISO onto a USB stick on Linux is very easy, and you only need to use a few commands!</p> - <hr> - <h2>What you will need π</h2> - <ul> - <li>A USB drive</li> - <li>A computer with Linux π§π₯</li> - <li>The ability to read instructions and to follow them π§ </li> - </ul><hr> - <h3>Warning β οΈ</h3> - <p>Make sure there is no valuable information on the USB stick.</p><hr> - - <h2>How to burn an ISO to a USB π₯πΎ</h2> - <p>1) You need to have an ISO file. I am guessing you already have one, but if you do have one, I would suggest checking out <a href="https://distrowatch.com">Distrowatch</a>.</p><hr> - - <p>2) Now that you have the ISO file, you need to plug in the USB stick. After doing that, you need to identify the name of the USB with the following command:</p> - <div class=code-box> - <p>lsblk</p> - </div> - <p>The USB name will be something like sdb or sdc; if you are unsure, check the size of the USB and the size of the device listed.</p><hr> - - <p>3) We need to make sure the USB is unmounted, and we do this with this command. Remember to use your USB name:</p> - <div class=code-box> - <p>sudo umount /dev/sdX</p> - </div><hr> - - <p>4) Now it is time to burn the ISO to the USB stick, use your USB name and your ISO name with this command!</p> - <div class=code-box> - <p>sudo dd if=debian.iso of=/dev/sdX bs=4M status=progress oflag=sync</p> - </div><hr> - - <p>5) After waiting a bit for it to burn, you now need to eject it so you are able to use it with this command:</p> - <div class=code-box> - <p>sudo eject /dev/sdX</p> - </div><hr> - - <h2>Finished β
</h2> - <p>After following all of these steps, your USB should have the ISO image burned into it. I hope this has helped you burn a Linux or BSD distro to a USB!</p> - <hr> - <center> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/media/EncryptingUSB.html b/public/articals/linux/media/EncryptingUSB.html deleted file mode 100644 index bb2287f..0000000 --- a/public/articals/linux/media/EncryptingUSB.html +++ /dev/null @@ -1,94 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Encrypting USB with luks</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>Encrypting USB with luks</h1> - <h3>Date: 17-02-2025</h3> - <hr> - <h2>What you will need π</h2> - <ul> - <li>A USB drive</li> - <li>A computer with Linux π§π₯</li> - <li>The ability to read instructions and to follow them π§ </li> - </ul><hr> - - <p>1) Install cryptsetup - <div class="code-box"> - <p>sudo pacman -S cryptsetup</p> - </div> - - <hr> - - <p>2) Backup any information on the USB stick because this process involves formatting the USB drive.</p> - - <hr> - - <p>3) Formatting USB.</p> - <div class="code-box"> - sudo fdisk /dev/sdX - </div> - <p>The X being your USB drive.</p> - <p>Press the following keys: <br> o <br> n <br> Press enter for the rest <br>w</p> - - <hr> - - <p>4) Encryption time! - <div class="code-box"> - sudo cryptsetup luksFormat /dev/sdX1 - </div> - <p><a href="../../internet/safety/02Passwords">Make your password secure please!</a> - - <hr> - - <p>5) Decrypt USB</p> - <div class="code-box"> - sudo cryptsetup luksOpen /dev/sdX1 USB - </div> - <p>Note: The first password is your root user password, not the encryption password. I have sadly made this mistake in the past.</p> - - <hr> - - <p>6) Format the Encrypted Partition</p> - <div class="code-box"> - sudo mkfs.ext4 /dev/mapper/USB - </div> - <p>Depending on the size of the USB, this may take some time. For me, it took 3 minutes.</p> - - <hr> - - <p>Step 7: Mount the Encrypted Partition</p> - <div class="code-box"> - sudo mkdir -p /mnt/USB - <br> - sudo mount /dev/mapper/USB /mnt/USB - </div> - - <hr> - <h2>Finished β
</h2> - <p>Your password better be good dude. Make sure to memorize it!</p> - <hr> - - <center> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/media/FormattingUSB.html b/public/articals/linux/media/FormattingUSB.html deleted file mode 100644 index 5e3728b..0000000 --- a/public/articals/linux/media/FormattingUSB.html +++ /dev/null @@ -1,67 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Formatting USBs with Linux ππ₯</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>Formatting USBs With Linux ππ₯</h1> - <h3>Date: 23-08-2024</h3> - <hr> - <p>Formatting a USB in Linux is easier then <a href="01BurningIsos">burning an ISO</a> and only needs a few quick commands!</p><hr> - <h2>What you will need π</h2> - <ul> - <li>A USB drive</li> - <li>A computer with Linux π§π₯</li> - <li>The ability to read instructions and to follow them π§ </li> - </ul><hr> - - <h2>Formatting the USB</h2> - <p>1) The first thing you want to do is plug in your USB stick and identify the USB stick's name.</p> - <div class="code-box"> - <p>lsblk</p> - </div> - <p>Normally the USB will be something like sdX; a tip on identifying it is by looking at the size of the USB in the table that lsblk gives you!</p><hr> - - <p>2) Now you need to use a program called <a href="https://linux.die.net/man/8/fdisk">fdisk</a> that will allow you to create a new partition table for the USB, this will format the USB.</p> - <div class="code-box"> - <p>sudo fdisk /dev/sdX</p> - </div> - <p>You will need to press the following keys to make a new partition table for the USB.</p> - <ul> - <li>o - Creates a new DOS partition table</li> - <li>n - New partition, press enter to all that follows</li> - <li>w - Writes the partition table</li> - </ul> - <p>Give fdisk a minute to write the new partition to the USB.</p><hr> - - <p>3) Now is the time to give that partition a file system. You should look into this beforehand to see what file system you want, but I will use fat32 because it works with all operating systems.</p> - <div class="code-box"> - <p>sudo mkfs.fat -F 32 -n "Backup-USB" /dev/sdXx</p> - </div> - <p>The small x represents the number of the partition; the -L flag is used to give the USB stick a name.</p><hr> - - <h2>Finished β
</h2> - <p>All done! Now you have an empty USB stick you can use for all your files!</p><hr> - - <center> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/media/cd.html b/public/articals/linux/media/cd.html deleted file mode 100644 index b44d15a..0000000 --- a/public/articals/linux/media/cd.html +++ /dev/null @@ -1,76 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Burning optical media in Linux</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>How To Format A USB with Linux πΏ</h1> - <h3>Date: 23-08-2024</h3> - <hr> - <p>This is a quick tutorial to show you how to burn any file to a piece of optical disk media!</p> - <hr> - <h3>Warning β οΈ</h3> - <p>Once you burn an optical disk you cannot reburn it.</b> - <p>Optical media does not have the best storage, normally under 1GiB so make sure your files align with the size of the optical media.</b> - <hr> - <h2>What you will need π</h2> - <ul> - <li>Optical drive capable of writing to a CD</li> - <li>A computer with Linux π§π₯οΈ</li> - <li>The ability to read instructions and to follow them π§ </li> - </ul> - <hr> - - <h2>Steps to burn π₯</h2> - <p>You will only need one program to burn media to a CD; the name of that program is <a href="https://linux.die.net/man/1/wodim">wodim</a>, and it is part of a collection of programs called <a href="https://packages.debian.org/source/sid/cdrkit">cdrkit</a>, as in thename ofe this collection of programs that allow you to do a whole variaty of things withopticall media!Β - <hr> - - <li>1) Install cdrkit, on some Linux distrobutions cdrkit is already installed, but on my main Linux distrobution <a href="https://archlinux.org">Arch Linux</a>, it is not so check you have it installed, the package on your distro will most likely be called cdrkit.</li> - <br> - <div class="code-box"> - <p>sudo pacman -S cdrkit</p> - </div> - <br> - - <hr> - - <li>2) You want to get whatever data you want into an ISO file, so if you had a file called movies that held movies you would use the command. As an example, I will be using the location of the Fallout 1 installation files on my system.</li><br> - <div class="code-box"> - <p>mkisofs -o Fallout.iso -V "Fallout 1" ~/Downloads/Fallout</p> - </div> - <p>Fallout.iso being the output ISO and ~/Downloads/Fallout being the directory with the movies in there.</p> - - <hr> - - <li>3) Now the last command is the actual event of burning the optical media! So insert it into your optical drive and type this command.</li><br> - <div class="code-box"> - <p>cdrecord -v dev=/dev/cdrom ~/Downloads/Fallout.iso</p> - </div> - <p>movies.iso being the output ISO from the last command.</p> - - <hr> - - <li>4) Now it is time to sit back and wait for it to burn; do not get impatient; give it time, and it will burn. When it is done, you may enject the optical media from the CD drive, and it should have all the files you desire.</li><br> - <center> - <hr><p>That is all the required steps to burn optical media on Linux, I hope this has helped you!</p> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/server/git.html b/public/articals/linux/server/git.html deleted file mode 100644 index c02953c..0000000 --- a/public/articals/linux/server/git.html +++ /dev/null @@ -1,197 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Git server setup!</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>How to start your own epic Git server!</h1> - <h3>Date: 23-02-2025</h3> - <hr> - <p>Quick guide on how to set up a git server with stagic html website.</p> - <hr> - - <h2>What you will need π</h2> - <ul> - <li>A computer with Linux π§π₯οΈ</li> - <li>A VPS with Linux instaled π§ποΈ</li> - <li>Some terminal knowlage π§ </li> - <li>Ideally have a domain name</li> - </ul> - <hr> - - <h1>Setting up Git server</h1> - <hr> - - <li>1) Install Git</li> - <br> - <div class="code-box"> - <p># sudo apt install git</p> - </div> - <br> - - <hr> - - <li>2) Create git user.</li><br> - <div class="code-box"> - <p># sudo adduser git</p> - </div> - - <hr> - - <li>3) Now you need to add your SSh keys.</li><br> - <div class="code-box"> - <h3>On server</h3> - <p># su git</p> - <p>$ cd</p> - <p>$ mkdir .ssh && chmod 700 .ssh</p> - <p>$ touch .ssh/authorized_keys && chmod 600 .ssh/authorized_keys</p> - </div> - - <br> - - <div class="code-box"> - <h3>On computer</h3> - <p>$ cat .ssh/id_rsa.pub</p> - <pre>ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCyXwuFdbWHloGPOfFq6p5Dt..... me@shipwreckt.co.uk</pre> - <p>Copy and paste your ssh key to .ssh/authorized_keys on your server. - </div> - - <p>If you want to allow other people to use your Git server, add their SSH keys alongside yours.</p> - - <hr> - - <li>4) Nearly done, now all you need to do is make a git repo.</li><br> - <div class="code-box"> - <p># chown git:git /srv/git</p> - <p># su git</p> - <p>$ cd /srv/git</p> - <p>$ mkdir yourrepo.git</p> - <p>$ cd yourrepo.git</p> - <p>$ git init --bare</p> - </div> - - <hr> - - <li>5) Time to add your server to your local repo</li> - <div class="code-box"> - <h3>On computer</h3> - <p>$ cd yourrepo</p> - <p>$ git init</p> - <p>$ git add .</p> - <p>$ git commit -m 'Initial commit'</p> - <p>$ git remote add origin git@gitserver:/srv/git/project.git</p> - <p>$ git push origin master</p> - </div> - - <p>If you already have a Git repository from another server, you can do the following to add your new Git server alongside your old one.</p> - - <div class="code-box"> - <h3>On computer</h3> - <p>$ cd yourrepo</p> - <p>$ git remote add server git@gitserver:/srv/git/project.git</p> - <p>$ git push server master && git push origin master</p> - </div> - - <p>You can now do this for all of your repos!</p> - - <hr> - - <li>6) If you want to enable anybody to clone from your website do the following!</li> - - <div class="code-box"> - <p># sudo git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ &</p> - <p># sudo systemctl enable git-daemon</p> - <p># sudo systemctl start git-daemon</p> - <p># su git</p> - <p>touch /srv/git/project.git/git-daemon-export-ok</p> - </div> - - <p>Cloning your git repo</p> - <div class="code-box"> - <h3>On computer</h3> - <p>git clone git://your-server-ip-address/repository.git</p> - </div> - <p>Now you should be able to be able to clone without a ssh key!</p> - - <hr> - <h1>Setting up Stagit for personal git website</h1> - <p>Now that you have a Git server, you probably want a way to show off all of your repositories. I personally use Stagit for this because it is lightweight and stylish. I will assume you know how to make a website using Apache or Nginx.</p> - - <hr> - <li>1) First you need to install stagit, I have my own custom fork to make it easier to setup.</li> - <div class="code-box"> - <p># cd /var/www</p> - <p># git clone git://shipwreckt.co.uk/stagit-fork.git</p> - <p># mkdir git</p> - <p># chown git:git git</p> - <p># mv stagit-fork/* git</p> - <p># cd git</p> - <p># sudo make clean install</p> - </div> - - <hr> - <li>2) Setup website.</li> - <div class="code-box"> - <p># cd htmldir</p> - <p># sh example_create.sh</p> - </div> - <p>Your static stagit website should be generated for you! Check by going to git.yourdomain.com. - - <hr> - - <li>3) Next you want to set up ownership, links, and descriptions for stagiit to display</li> - <div class="code-box"> - <h3>Descriptions</h3> - <p># This is my git repo > /srv/git/yourrepo.git/description</p> - </div> - - <div class="code-box"> - <h3>URL</h3> - <p># git://yourdomain.com/yourrepo.git > /srv/git/yourrepo.git/url - </div> - - <div class="code-box"> - <h3>Owner</h3> - <p># owner > /srv/git/yourrepo.git/owner</p> - </div> - - <div class="code-box"> - <h3>Update stagit</h3> - <p># sh /var/www/git/htmldir/example_create.sh</p> - </div> - - <p>Now repete for all of your repos till all is correct!</p> - - <hr> - <li>3) Now you want it so stagit updates whenever there is an update, thankfully for you I have modified the script to work whenever a git commit is made!</li> - <div class="code-box"> - # cp /var/www/git/example_post-receive.sh /srv/git /srv/git/yourgitrepo.git/hooks/post-receive - </div> - <p>Now whenever you push a commit everything should update!</p><hr> - - <h1>Overview</h1> - <p>I hope this guide has helped you setup a kool git server! If there are any problems please contact me!</p> - - <center> - <hr> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/tools/TarGz.html b/public/articals/linux/tools/TarGz.html deleted file mode 100644 index d84c883..0000000 --- a/public/articals/linux/tools/TarGz.html +++ /dev/null @@ -1,52 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>tar.gz a directory π</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>How to tar.gz a directory π</h1> - <h3>Date: 13-04-2025</h3> - <hr> - <h2>What you will need π</h2> - <ul> - <li>A computer with Linux or BSD π§π₯οΈ</li> - <li>The ability to read instructions and to follow them π§ </li> - </ul> - <hr> - - <h2>Why?</h2> - <p>Main reason why you want to tar.gz a directory is because it compresses a directory and all of the data inside of it. It is also good for backing things up too.</p> - <hr> - - <h2>The command</h2> - <div class=code-box> - <p>$ tar -czvf file.tar.gz /Location/Of/Directory</p> - </div><hr> - - - <h2>All done β
</h2> - <p>Really easily done, only one command and done!</p> - - <center> - <hr> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - diff --git a/public/articals/linux/tools/Ventoy.html b/public/articals/linux/tools/Ventoy.html deleted file mode 100644 index dcbe206..0000000 --- a/public/articals/linux/tools/Ventoy.html +++ /dev/null @@ -1,74 +0,0 @@ -<!DOCTYPE html> -<html lang="en-GB"> - <head> - <meta charset="UTF-8"> - <meta name="author" content="Shipwreckt"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Installing Ventoy</title> - <link rel="stylesheet" href="../../../styles.css"> - <link rel="icon" href="../../../Images/favi.png" type="image/x-icon"> - </head> - <body> - <header> - <nav> - <ul> - <li><a href="../../../index.html">Home</a></li> - <li><a href="../../../links.html">Links</a></li> - <li><a href="../../../projects.html">Projects</a></li> - <li><a href="../../../contact.html">Contact</a></li> - </ul> - </nav> - </header> - <main> - <h1>How to Install Ventoy with Linux π§π</h1> - <h3>Date: 25-08-2024</h3> - <hr> - <p>Installing Ventoy is pretty easy, just a few quick steps and you will be there!</p> - <hr> - <h2>What you will need π</h2> - <ul> - <li>A USB with over 10GiB</li> - <li>A computer with Linux π§π₯οΈ</li> - <li>The ability to read instructions and to follow them π§ </li> - </ul> - <hr> - <h3>Warning β οΈ</h3> - <p>If the USB has any useful data, please back it up before following this guide.</p><hr> - - <h2>Installing Ventoy with Linux π§π</h2> - <p>1) The first thing you want to do is get a few .ISO and .IMG files. <a href="https://tails.net/install/download/index.en.html">Tails</a> is a must-have on Ventoy, and you can also have a little look on <a href=https://distrowatch.com>distrowatch</a> for other distros that peak your curiosity!</p><hr> - - <p>2) Install ventoy.tar.gz from <a href="https://ventoy.net/en/index.html">https://ventoy.net/en/index.html</a>, the website tells you to install it from <a href="https://sourceforge.net/projects/ventoy/files/v1.0.99/">source forge</a>, make sure it is the linux.tar.gz file.</p><hr> - - <p>3) After installing the tar.gz, you need to run the following command; this will open the compressed file, which will allow you to use Ventoy.</p> - <div class=code-box> - <p>gunzip ventoy-<version>-linux.tar.gz && tar -xvf ventoy-<version>-linux.tar</p> - </div><hr> - - <p>4) Next you want to enter the Ventoy directory and identify what your USB name is</p> - <div class=code-box> - <p>cd ventoy-<version>/ && lsblk</p> - </div> - <p>Normally the USB with the lowest amount of storage will be your USB; to make sure, check the size of your USB compared to the devices listed under lsblk.</p><hr> - - <p>5) This command will install Ventoy to the USB. Make sure your USB name is correct; it will be something like sdb. A good way to identify the USB is by running lsblk when the USB is out and then running lsblk while the USB is plugged in.</p> - <div class=code-box> - <p>sudo sh Ventoy2Disk.sh -i /dev/sdX</p> - </div> - <p>Replace the X with your device letter.</p><hr> - - <p>6) The last command is just ejecting your USB</p> - <div class=code-box> - <p>sudo eject sdX</p> - </div><hr> - - <h2>All done β
</h2> - <p>After following all of these steps Ventoy should be installed on your USB stick, now the only thing to do is plug the USB in and put the ISO and IMG files into the USB, I hope this has helped you!</p> - - <center> - <hr> - <pre text-align=center> <a href="../../linuxlist.html">Back πͺ</a> - </main> -</body> -</html> - |