diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..e69de29 diff --git a/articles/guide01.php b/articles/guide01.php new file mode 100644 index 0000000..289b08b --- /dev/null +++ b/articles/guide01.php @@ -0,0 +1,42 @@ + + + + +Guide: Upgrading your Gentoo kernel to 5.17.4/absolute latest Linux kernel + + + + + + +
+

Guide: Upgrading your Gentoo kernel to 5.17.0

+

2022-03-23

+

This guide will go over how to upgrade your kernel on Gentoo GNU/Linux to 5.17.0. If we check the sys-kernel/gentoo-sources package we can see that 5.17.0 is now available as of 2022-03-23. However it is not stable so we will need to unmask it.

+

First, let’s use the su command to change our user to root since many commands will require root permissions. You could use sudo/doas for each command but that’s painful.

+

Now, one pretty unstable way to do this is to simply have ACCEPT_KEYWORDS="~amd64" in /etc/portage/make.conf but this is not stable and will ALWAYS allow “untested” packages to be installed on your system. I and others prefer this but it’s not something you should use if you care about a stable system.

+

So instead, let’s individually unmask this package. Create /etc/portage/package.unmask and add sys-kernel/gentoo-sources to the file.

+ image +

Now, your sources are likely outdated so we will need to update them. To do this, run emerge --sync; emerge-webrsync

+

Once we’ve synced our repositories, let’s try running emerge --ask gentoo-sources. If the version is 5.17.0 or later then you’ve correctly unmasked and synced your repositories.

+ image +

Now emerge this and wait.

+ image +

Once the emerge is complete it’s time to back up our kernel configuration. cd /usr/src/linux and cp kernel /home/user where kernel is the name of your kernel config and user is your user account. You don’t have to back it up to this place but you need a backup of your kernel configuration unless you wanna configure a new one. Now cd /home/user.

+ image +

Now that we have a backup of our previous configuration, it’s time to change our symlink. Run eselect kernel list

+

Then run eselect kernel set number where number is the number of the kernel you will be using (should be 5.17.0)

+ image +

cd /usr/src/linux; cp /home/user/kernel /usr/src/linux/.config; make olddefconfig.

+

This string of commands will copy the kernel config to the 5.17.0 kernel directory. The make olddefconfig will use your old kernel and set the new settings newer kernels offer to the defaults. This should be fine unless you NEED to change them.

+

Once this is complete, make sure your /boot is mounted and then run make -j$(nproc); make install to compile the kernel and copy it over to your /boot partition.

+

Finally, let’s make sure our bootloader can find it. For Grub, you need to grub-mkconfig -o /boot/grub/grub.cfg but if you’re not using Grub then you will have to use searx to find out what to do. +

IMPORTANT: If you are using an initramfs then you need to create a new one. To do this you can use either genkernel or dracut. To use genkernel, run genkernel --install --kernel-config=/usr/src/linux/.config initramfs. Then just repeat the previous step.

+

Now you’re done. Now reboot and make sure your kernel boots. If you cannot boot, you will have to do some troubleshooting..

+

Have a good day and good luck with Gentoo.

+
+ + + diff --git a/articles/guide02.php b/articles/guide02.php new file mode 100644 index 0000000..e26c17f --- /dev/null +++ b/articles/guide02.php @@ -0,0 +1,223 @@ + + + + +Guide: Installing Arch Linux (The chad way) + + + + + + +
+

Guide: Installing Arch Linux (The chad way)

+ image +

2022-05-05

+

This simple to follow guide for chads will be going over an Arch Linux installation. We will also be going through setting up a window manager and X environment so that you can actually use it.

+

Before you get started, I'd like to explain why you should install Arch Linux and I'd also like to warn you that you're going to do this at your own risk. I'm not responsible for any data loss caused by this guide.

+

Once you've taken a deep breath and understand the risks, let's get started with installing Arch Linux.

+

First step is to make sure you meet the requirements below.

+ +

Before we get started, why would you want to install Arch Linux?

+ +

I will be installing in a virtual machine but the steps are identical. Just a few minor differences that I will be explaining later on.

+

Part 1: Creating the USB drive

+

First, let's head over to the Arch Linux website and download the latest ISO.

+ image +

If you've already got an ISO, you don't need to download a new once since we will be using the pacstrap command anyway which will download the latest packages.

+

You can choose how to download the ISO. I prefer using the torrent because:

+ +

If you don't have a torrent client set up, just download the ISO using your web browser. Arch Linux will not come to your house asking for money, don't worry.

+

Now that we have your ISO file it's time to write it to a USB drive.

+

If you're going to be installing in a VM then you can skip this part since you can boot directly off the ISO.

+

Creating the USB drive (Windows)

+

To create the USB drive on Windows, you can use the free software tool "Rufus".

+ image +

(Not my image, I don't use Microhard Binbow$ which steals all my data)

+

Rufus looks something like this. You'll want to select the Arch Linux image. Then select whether your computer supports UEFI/BIOS.

+

Most modern machines released ~2012 or later should support UEFI. If you use an Intel Mac from 2007-2019 then you'll want UEFI (EFI). If you're unsure you can go with the default option (BIOS) since it supports both.

+

Then just write it. There are other ways to write on Windows such as using WSL with 'dd' which you can do or by using balenaEtcher (Which you shouldn't be using since it's not free software, it's open source spyware which is extremely bloated and uses Electron)

+

Creating the USB drive (Linux/macOS)

+

On Linux or macOS, writing the image is a lot easier. We're going to do this from the command line without installing any additional software using the dd command.

+

Make sure your Linux/macOS box is able to run commands as root (ie. sudo/doas). Finally, make sure you have the Arch Linux ISO.

+

To write it, fire up a terminal (I use st) and change your user to root using the su command.

+

Now, to check what devices are available on your system, run lsblk. Make note of the devices and make sure to not pick the wrong one. If you do then you WILL lose data.

+

I'm pretty sure macOS won't let you erase your drives due to SIP but this command is nicknamed 'disk destroyer' for a reason. PLEASE be careful when using it.

+

Now, lsblk should return something like this.

+ image +

If you're on macOS, it's going to be diskXsY instead of sdXY.

+

Now, run the command dd if=X of=Y as root where X is the path to your Arch Linux ISO and Y is your drive (For example, /dev/sdb).

+

Be extremely careful and hope you didn't enter the wrong drive.

+

If you did, then I feel slightly bad for you because you may have just lost your massive collection of anime porn.

+

Now, the dd command will by itself not output anything. But be patient and do not close down your terminal.

+

Once you can enter commands into your terminal and see your prompt, it's all done and you can reboot your computer.

+

Part 1.5: Booting from the USB drive

+

Now that we have a USB drive, we need to use it. Stick it into your soon-to-be Arch box and reboot/power it on. You'll need to get into your BIOS/UEFI. If you have enough computer knowledge to get into the BIOS then you can follow on with the guide. Simply boot from the USB. Else, simply go back to using Windows like a normie, this guide is for chads only.

+

Also while you're at it, take your computer to the Microsoft Store and ask them to fix it for you.

+

Now, let's continue.

+

Part 2: Partitioning

+

Now, let's install Arch Linux. Upon booting, you should see something like this

+ image +

Simply press enter on the first option UNLESS you have specific needs.

+

The second option is good if you're blind and need speech.

+

The third option is good if you only have one USB port but need another for.. say a USB WIFI dongle. This will allow you to remove your USB drive and run the installer from your RAM.

+ image +

Once it's done booting from the USB you'll see this fancy message. It tells you to RTFM but obviously since you're reading my guide you're too based for that.

+

It also tells you that there's a fancy """EASY JUST WERKS""" Arch installer but it's really just harder.

+

Now, run lsblk to see how many drives you have and their NAME.

+ image +

From my image, we can tell that sda is my only drive. So this is the one we will be installing Arch Linux to.

+

Now, run cfdisk /dev/sdX where X is your drive NAME.

+ image +

Then you'll get a few options.

+ +

The other options are completely irrelevant for us.

+ image +

If you picked MBR then it's going to look slightly different. You will have a bootable option which.. makes your partition bootable. You will want to have this selected for your boot partitions.

+

Other than that, you can follow along.

+

Press enter on [NEW] and enter how big your boot partition should be. This is where your kernel, initramfs and bootloader is going to be. For this guide we will be using Grub but there are other bootloaders that can be used with Arch Linux. You might choose to use the systemd bootloader since it comes with your init system.

+ image +

A good size unless you'll have many kernels is 128MB. If you need more, I'd go up to 256MB. More than that is probably not necessary.

+

If you're using EFI then set the Type to 'EFI system'. Otherwise leave it as default.

+

Now it's time to add Swap. If you have 8GB or more RAM then you probably don't need swap. How much swap you wanna add is fully up to you. I prefer having no swap personally.

+

Again press enter on [NEW] and set the size to however much swap you have. I'd recommend double your RAM unless you have a lot of RAM in which case you probably don't need swap anyway.

+

The type for swap should be 'Linux swap'.

+

I won't be setting swap because I think it's useless.

+

Now unless you have specific needs such as having a separate /home partition or something, we can allocate the rest to our root partition.

+

The [Type] for your root partition should be 'Linux filesystem'. Once you're sure it all looks correct, you can [Write] the changes.

+

Here's what a setup might look like.

+ image +

Part 2.5: Creating file systems and mounting

+

This part is really easy. We need to begin by again running lsblk.

+ image +

In my case, /dev/sda1 is our /boot partition and /dev/sda2 is our root partition

+

Now, we need to decide what file system to use. I recommend either ext4 or BTRFS. I will personally be going with BTRFS.

+

We also need a file system for our boot partition. I will be using FAT32 aka VFAT for this.

+ +

Output of these commands should be something like this:

+ image +

Now, if you created a swap partition, we'll need to set that up as well.

+
To create a swap file system, run mkfs.swap /dev/sdXY where X is your drive and Y is your partition.
+

That wasn't so hard was it? We just created Arch Linux partitions and set them up.

+

With that done, let's mount our drives so we can begin actually installing Arch.

+

To mount your root partition, type mount /dev/sdXY /mnt where X is your drive and Y is your partition.

+

For EFI: Then, to mount your /boot partition, type mkdir /mnt ; mount /dev/sdXY /mnt/boot where X is your drive and Y is your partition. This will create /boot and mount our boot partition to it.

+

If a swap partition was created, type swapon /dev/sdXY /dev/sdXY where X is your drive and Y is your partition.

+

Congratulations, we're done mounting and partitioning your drives. Now, we just need to make sure we have a connection to the internet so we can download our packages.

+

Part 2.5: Connecting to the internetz

+

The internetz are useful for two things; Installing Arch Linux and bragging about having installed Arch Linux

+

If your computer is connected using Ethernet, it should just work with absolutely no setup required. If you are using WIFI then it will not work out of the box.

+

To set up WIFI on your Arch box, type iwctl station list. Make note of the output. For example, it may be wlan0 or wlan1.

+

Once you're sure which device it is, type iwctl station 'station' connect SSID where station is the WIFI device we got earlier and SSID is the name of your WIFI network.

+

Press enter and type in the password your network has. If it doesn't ask you for a password then it probably doesn't need one or you entered the wrong SSID.

+

Part 3: Installing base system

+

Now we're connected to the internet. How fancy is that? To actually use this, we need to install some packages. This would normally be pretty painful but Arch Linux has a command called pacstrap which will basically do the entire process for us. Arch Linux also offers a few bundles of packages like base and base-devel which contain essential packages.

+

Now, to install packages to our Arch system, we'll need to decide what packages to use. base is basically essential. It contains the base Arch Linux system. Then, if you're going to be using development tools (Required for compiling dwm which we'll do later on) then you'll also want to install base-devel. Keep in mind this also comes with Sudo which you might not want (I certainly don't). But these can later easily be removed using pacman -R

+

Now, we need a kernel. The Linux kernel is obviously what we want since it's Arch Linux. There are many different variations of the Linux kernel. You can run pacman -Ss linux to see all that are available in the Arch Linux repositories. Here is a small list of them.

+ + image +

If your hardware configuration requires proprietary blobs then you'll also wanna add the linux-firmware package.

+

If you're going to use WIFI then you'll want to add iwd to your list. There are other ways to manage WIFI but iwd is the one we used during Part 2.5 and it's also the easiest to set up.

+

If you're going to use Ethernet, you'll need some way to manage networks. I tend to just install dhcpcd though but you can use NetworkManager or something if you want

+

You'll also need some way to edit text. The base package might come with Nano or something but Nano is unusable so we're gonna install vim as well.

+

You can use something else like nano or pico to edit your text but they're terrible text editors that only people who wanna make their life harder use.

+

Finally, we'll need our bootloader which for this guide will be Grub. If you're going to be dual-booting then you'll also want the os-prober package. If you're on an EFI system then you'll want the efibootmgr package.

+

Now, our package list looks like this: base base-devel linux linux-firmware dhcpcd grub efibootmgr vim

. +

And the command we wanna run is: pacstrap /mnt base base-devel linux linux-firmware dhcpcd grub efibootmgr vim.

. + image +

Wait unless the command finishes installing packages to your new root

+

Part 3.5: Creating an fstab

+

Arch Linux requires an fstab to boot. An fstab is really just a file with a list of partitions to mount and how to mount them.

+

Writing one manually isn't hard but Arch Linux made it easier by including a nice command called genfstab.

+

All we need to do is run genfstab -U /mnt > /mnt/etc/fstab

+

The -U flag uses UUIDs instead of the disk identifier. This is important to make sure our fstab is always correct.

+

The > points it to /mnt/etc/fstab.

+

Now, finally we need to chroot into our new root. Do this by running arch-chroot /mnt.

+

Part 4: Setting time zone and locale

+

Now that we're in our new root we need to set our timezone and then locale.

+

First, run ls /usr/share/zoneinfo

+

Then run that previous command but with your region. In my case Europe. /Europe

+

Finally, run ln -sf /usr/share/zoneinfo/Region/City /etc/localtime where Region is.. your region (for example Europe) and where City is your city. (for example Stockholm).

+

Now, you'll want to edit /etc/locale.gen. Uncomment the locale you need. Edit it using your editor of choice, for example vim /etc/locale.gen. For en_US, uncomment en_US.UTF-8 UTF-8. You can use / to quickly find text in Vim. For example, sv_SE.UTF-8 UTF-8 would be the locale for Sweden.

+

Part 4.5: Setting your hostname

+

Now we need to set our hostname. To do this, run the following command. Replace archbox with what you want your hostname to be. echo "archbox" > /etc/hostname. +

Part 5: Installing a bootloader

+

In order to boot Arch Linux after we're done installing, we need to install a bootloader. If you followed this guide exactly as it's written you should have Grub as your bootloader.

+
For GPT users
+

grub-install --target=x86_64-efi --efi-directory=/boot ; grub-mkconfig -o /boot/grub/grub.cfg

+
For MBR users
+

grub-install /dev/sdX where X is your drive.

+

Part 5.5: Enabling services and setting your root password

+

Enable the services. If you installed dhcpcd, run systemctl enable dhcpcd. If you installed iwd, run systemctl enable iwd. Now, the final part before we can reboot and begin setting up our Arch Linux box. Setting the root password. By default, the root password isn't set so you can't actually log in. You can set it yourself by running the passwd command. Once you've set the password, it's time to reboot. To do this, simply type exit to exit the chroot environment and then reboot to reboot the system.

+

Part 6: Setting up users and permissions

+ image +

Now that we've got a base Arch Linux install set up, log in as root with the password you set earlier.

+

Once you're logged in, run useradd -mG wheel,audio,video,users user where user is your user name. I will name my user 'speedie'.

+

The -m flag creates a home directory for the user. The -G flag will add it to the groups. wheel is the group that we will allow sudo or doas to give root access to. audio will allow us to use ALSA (Advanced Linux Sound Architecture) for audio. video will allow us to start an X session. users is a group all users should be in.

+

Now let's set his/her password by running passwd user where user is the account we created. Once you have access to this account you can set the root account password to random text if you want security.

+

If you wanna use sudo, you can do so by editing /etc/sudoers using your favorite editor.

+ image +

Above is an example of how to set up sudo +

If you installed base-devel then sudois already installed. Otherwise you can install it if you want.

+

I will be using doas instead however because sudo is more bloated than it needs to be.

+

If you wanna use doas, you can install it using pacman -Sy doas.

+

To set up doas, simply run echo "permit :wheel" > /etc/doas.conf or alternatively echo "permit nopass :wheel" > /etc/doas.conf if you don't want to enter your password every time you try to run a command as root. It's not very secure but I personally prefer it.

+

Now that we have set up our account and permissions, run exit and log in with your new account.

+

Part 7: Setting up dwm

+

Let's set up Xorg and then the window manager which will be dwm. Start by installing Git. Do this by running pacman -S git libXinerama. libXinerama will be used to compile dwm with support for multiple monitors. We also need libXft but we will be installing libXft-bgra since otherwise dwm will crash if it sees a color emoji.

+ +

Run cd to change directory to ~. Now we can mkdir -pv .config and cd .config.

+

Before we can install dwm, we need libXft. To do this, run the following command git clone https://aur.archlinux.org/libxft-bgra ; cd libxft-bgra ; makepkg -i. This will install libXft-bgra. Now you can go ahead and cd back into ~/.config.

+

If you've already got a build of dwm, go ahead and clone that instead. If you don't, git clone https://git.suckless.org/dwm ; cd dwm. Now that we're inside the dwm source code, simply run make clean install as root. This should install dwm. If you're using my build you also need imlib2 and harfbuzz.

+

You'll also likely want dmenu for our run launcher and st for our terminal. Otherwise you'll need to edit the dwm source code.

+

To install dmenu, cd ~/.config ; git clone https://git.suckless.org/dmenu ; cd dmenu ; doas make clean install.

+

To install st, cd ~/.config ; git clone https://git.suckless.org/st ; cd st ; doas make clean install.

+

Part 8: Setting up Xorg

+

The 8th and final part of this guide; setting up Xorg.

+

First, run pacman -S xorg-server xorg-xinit xf86-input-libinput as root. This will install our server, xinit and xf86-input-libinput necessary to use our keyboard and mouse with Xorg. Then also run pacman -Ss xf86-video as root and look at the output. You don't technically need xorg-xinit, you can use sx which I covered in my RSS post. However it's not very good for new users and not very well documented so I suggest you use xinit.

+ image +

These are display drivers. You'll want to install the one you need. If you're in a VM like me, it's xf86-video-vmware for VirtualBox or VMware and xf86-video-qxl for QEMU/KVM. These are correct for everyone except nvidia users who will want the nvidia package instead. Run it for yourself and install the driver you need.

+

We need to set up xclip for our clipboard and picom for our compositor. You can also choose to install xorg-xrdb if your software supports .Xresources however I will not be covering that in this guide.

+

You can do this by running pacman -S xclip picom as root.

+

Finally, let's edit our .xinitrc file. This file will run every time you run the command startx.

+

vim ~/.xinitrc

+

Now add these three lines to the file:

+
picom
+
xclip
+
dwm
+

Then save the file using ':wq' and run startx. That should be everything. If you did it correctly you should be in dwm. If it fails to start then you're probably missing fonts. I suggest installing terminus-font. It's a nice font.

+ image +

Now you can install maim and neofetch so you can brag about having installed Arch on r/unixporn or whatever. Thanks for reading this guide, I hope it helped you set up Arch Linux. Have a good day!

+
+ + + diff --git a/articles/guide03.php b/articles/guide03.php new file mode 100644 index 0000000..91a2545 --- /dev/null +++ b/articles/guide03.php @@ -0,0 +1,38 @@ + + + + +Guide: Upgrading Suckless software (gigachad edition) + + + + + + +
+

Guide: Upgrading Suckless software (gigachad edition)

+

2022-05-09

+

In this guide I tell you how to upgrade Suckless software like dwm, st, dmenu, surf and more to a newer version without abandoning your fork and starting from scratch.

+

I'm not sure if I'm the only one who's used this method but it works great. It even works if you have 30+ patches like I had with my build of dwm. I was still able to easily upgrade from 6.2 to 6.3 in around 10 minutes.

+

First, create a directory anywhere on your system. I created mine in my home directory. Then open a web browser and navigate over to the suckless website.

+

Then select the software you're using. For this guide I will be using dwm. Now copy the link to the latest tarball and open up a terminal and change directory into the new folder.

+

Download the latest tarball using the wget command. Now download the tarball for the release your build of dwm is on. You can see this by looking at config.mk. It has a version variable at the top which is the version of the software you're on.

+ image +

Now, you can unpack both of these tarballs using tar -xpvf tarball.

+ image +

If you did it correctly you should have two folders with two different versions.

+

In my case, there's dwm-6.2 and dwm-6.3. Now, what we're going to do is create a patch that we can apply to our riced fork of (in this case) dwm.

+

In this case you can do this by running diff -up dwm-6.2 dwm-6.3 > dwm-patch.diff. Obviously change the names if yours are different. If we run this command we should get a patch. We can apply this to any dwm build which is exactly what we're going to do.

+

Copy the .diff to your dwm/st/whatever source code folder and then change directory into it.

+ image +

Now, run patch < patch1.diff where patch1.diff is your patch. If you're on a relatively clean build, it should apply just fine. If it doesn't, you'll want to manually add in the chunks. If you're not familiar with patching then it may be slightly difficult for you. What you'll want to do is look at the .rej files and copy them into the regular files. Once you're sure everything looks good and it patched properly then you can go ahead and make clean install as root.

+ image +

As you can see, it compiled just fine and if you look at the config.mk you'll see that we've suck-less-ly upgraded our dwm version from 6.2 to 6.3. Again, this can be applied to any of their software.

+

Hope this guide helped you out. If it did, feel free to share it around or donate some Monero.

+

Have a great day suckless chad!

+
+ + + diff --git a/guides.php b/guides.php new file mode 100644 index 0000000..924688c --- /dev/null +++ b/guides.php @@ -0,0 +1,23 @@ + + + + +Guides + + + + + + +
+

Guides

+

These are text guides I've written.

+
Guide: Upgrading Suckless software, written 2022-05-09
+
Guide: Installing Arch Linux, written 2022-05-05
+
Guide: Upgrading your Gentoo kernel to 5.17.0 (and later), written 2022-03-23
+
+ + + diff --git a/img/guide-01-img-1.png b/img/guide-01-img-1.png new file mode 100644 index 0000000..1921f0a Binary files /dev/null and b/img/guide-01-img-1.png differ diff --git a/img/guide-01-img-2.png b/img/guide-01-img-2.png new file mode 100644 index 0000000..0e10668 Binary files /dev/null and b/img/guide-01-img-2.png differ diff --git a/img/guide-01-img-3.png b/img/guide-01-img-3.png new file mode 100644 index 0000000..8baeaae Binary files /dev/null and b/img/guide-01-img-3.png differ diff --git a/img/guide-01-img-4.png b/img/guide-01-img-4.png new file mode 100644 index 0000000..a5d4fe0 Binary files /dev/null and b/img/guide-01-img-4.png differ diff --git a/img/guide-01-img-5.png b/img/guide-01-img-5.png new file mode 100644 index 0000000..e194c79 Binary files /dev/null and b/img/guide-01-img-5.png differ diff --git a/img/guide-02-img-1.png b/img/guide-02-img-1.png new file mode 100644 index 0000000..1952f7b Binary files /dev/null and b/img/guide-02-img-1.png differ diff --git a/img/guide-02-img-10.png b/img/guide-02-img-10.png new file mode 100644 index 0000000..dd475f0 Binary files /dev/null and b/img/guide-02-img-10.png differ diff --git a/img/guide-02-img-11.png b/img/guide-02-img-11.png new file mode 100644 index 0000000..81e131f Binary files /dev/null and b/img/guide-02-img-11.png differ diff --git a/img/guide-02-img-12.png b/img/guide-02-img-12.png new file mode 100644 index 0000000..3bab729 Binary files /dev/null and b/img/guide-02-img-12.png differ diff --git a/img/guide-02-img-13.png b/img/guide-02-img-13.png new file mode 100644 index 0000000..e7f03f4 Binary files /dev/null and b/img/guide-02-img-13.png differ diff --git a/img/guide-02-img-14.png b/img/guide-02-img-14.png new file mode 100644 index 0000000..589ca6b Binary files /dev/null and b/img/guide-02-img-14.png differ diff --git a/img/guide-02-img-15.png b/img/guide-02-img-15.png new file mode 100644 index 0000000..b91c67e Binary files /dev/null and b/img/guide-02-img-15.png differ diff --git a/img/guide-02-img-16.png b/img/guide-02-img-16.png new file mode 100644 index 0000000..3d7212e Binary files /dev/null and b/img/guide-02-img-16.png differ diff --git a/img/guide-02-img-17.png b/img/guide-02-img-17.png new file mode 100644 index 0000000..ababada Binary files /dev/null and b/img/guide-02-img-17.png differ diff --git a/img/guide-02-img-18.png b/img/guide-02-img-18.png new file mode 100644 index 0000000..700cf6a Binary files /dev/null and b/img/guide-02-img-18.png differ diff --git a/img/guide-02-img-19.png b/img/guide-02-img-19.png new file mode 100644 index 0000000..b52ed77 Binary files /dev/null and b/img/guide-02-img-19.png differ diff --git a/img/guide-02-img-2.png b/img/guide-02-img-2.png new file mode 100644 index 0000000..8a8210f Binary files /dev/null and b/img/guide-02-img-2.png differ diff --git a/img/guide-02-img-3.png b/img/guide-02-img-3.png new file mode 100644 index 0000000..245f0aa Binary files /dev/null and b/img/guide-02-img-3.png differ diff --git a/img/guide-02-img-4.png b/img/guide-02-img-4.png new file mode 100644 index 0000000..95f5aca Binary files /dev/null and b/img/guide-02-img-4.png differ diff --git a/img/guide-02-img-5.png b/img/guide-02-img-5.png new file mode 100644 index 0000000..56a192b Binary files /dev/null and b/img/guide-02-img-5.png differ diff --git a/img/guide-02-img-6.png b/img/guide-02-img-6.png new file mode 100644 index 0000000..305d75b Binary files /dev/null and b/img/guide-02-img-6.png differ diff --git a/img/guide-02-img-7.png b/img/guide-02-img-7.png new file mode 100644 index 0000000..774f2a3 Binary files /dev/null and b/img/guide-02-img-7.png differ diff --git a/img/guide-02-img-8.png b/img/guide-02-img-8.png new file mode 100644 index 0000000..3d53f2e Binary files /dev/null and b/img/guide-02-img-8.png differ diff --git a/img/guide-02-img-9.png b/img/guide-02-img-9.png new file mode 100644 index 0000000..d65de8c Binary files /dev/null and b/img/guide-02-img-9.png differ diff --git a/img/guide-03-img-1.png b/img/guide-03-img-1.png new file mode 100644 index 0000000..cb61dce Binary files /dev/null and b/img/guide-03-img-1.png differ diff --git a/img/guide-03-img-2.png b/img/guide-03-img-2.png new file mode 100644 index 0000000..7d12e19 Binary files /dev/null and b/img/guide-03-img-2.png differ diff --git a/img/guide-03-img-3.png b/img/guide-03-img-3.png new file mode 100644 index 0000000..82c8eb9 Binary files /dev/null and b/img/guide-03-img-3.png differ diff --git a/img/guide-03-img-4.png b/img/guide-03-img-4.png new file mode 100644 index 0000000..cbbfa9b Binary files /dev/null and b/img/guide-03-img-4.png differ diff --git a/index.php b/index.php index f04e6e5..f4673d5 100644 --- a/index.php +++ b/index.php @@ -10,18 +10,20 @@
+

Notice: This page is completely new and because of this, expect missing images, CSS, and pages or links that don't work. Please report such issues, but do expect them.

Hello world, I'm speedie!

Hello world, I'm speedie, a free software enthusiast.

The website you stumbled upon is a personal blog, and all opinions are all my own, honest opinions. It's not just a blog, however my blog is the main part of this website. Feel free to take a look around!

About me

-

I'm go by the online name 'speedie'. I live in Sweden and have an interest in technology and free software. I work on small programming projects sometimes but I don't consider myself a serious programmer, I just write code sometimes on the side to get the most of my technology and do things efficiently.

+

I live in Sweden and have an interest in technology and free software. I'm not really a programmer, I just write code sometimes to get the most of my technology and do things efficiently.

I work on projects sometimes such as:

I've also preserved old (previously) rare channels and other media for the Wii through a now dead community called 'Forwarder Factory' although nowadays I'm not really doing Wii things anymore. See the links below for that.

@@ -46,7 +48,7 @@

List of text guides I have written. Most of them are about various GNU/Linux topics.

  • Projects
  • My projects. I am not really a programmer however I do work on some small projects which they can be found here.

    -
  • Overlay
  • +
  • Overlay
  • I maintain a Gentoo overlay, that is an unofficial Gentoo repository with custom packages written by myself which extend the packages you can install on a Gentoo system.

    About this page

    diff --git a/overlay.xml b/overlay.xml new file mode 100644 index 0000000..219a5b1 --- /dev/null +++ b/overlay.xml @@ -0,0 +1,12 @@ + + + speedie-overlay + speedie's Gentoo GNU/Linux overlay + https://codeberg.org/speedie/speedie-overlay + + speedie@duck.com + speedie + + https://codeberg.org/speedie/speedie-overlay.git + + diff --git a/projects.php b/projects.php index 2116db8..c9e8ce5 100644 --- a/projects.php +++ b/projects.php @@ -10,14 +10,41 @@
    -

    Projects

    -
    -
    -

    iron

    -

    iron is a minimal, customizable, hackable rautafarmi textboard client for GNU/Linux written in Bash. iron is the successor to rchat, and is the first client to support the new, faster, JSON rautafarmi API.

    - About iron -
    -
    +

    Projects

    +

    Here's a list of most software projects I've worked on/currently work on or people still use.

    +

    Note that it is not a full list, for a full list see my GitHub and my Codeberg.

    + + + +