Gabe/techWebsite
1
0
Fork 0
Code Issues 9 Pull requests Projects 1 Releases Wiki Activity

Spelling, caplitalization, and duplicate word removal.

Browse source
This commit is contained in:
Gabe Venberg 2023-10-27 10:34:42 -05:00
parent 3cf20c608d
commit c2ffa5a577
3 changed files with 20 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
content/posts/archInstall.adoc
View file

@ -31,7 +31,7 @@ Full disk encryption will not protect you from anything while you laptop is powe
Also, I did am not encrypting the boot partition, and Im not setting up any sort of secure boot.
This means that an attacker could hypothetically replace your boot partition or firmware and keylog your password, so if you suspect your computer has been tampered with, *DONT* boot it up.
To reiterate, this setup by itself only protect your data if your powered down machine is stolen. It does not protect you data from being stolen in any scenario where your laptop is powered on after or during tampering.
To reiterate, this setup by itself only protect your data if your powered down machine is stolen. It does not protect you data from being stolen in any scenario where your laptop is powered on during tampering or you log in after it has been tampered with.
== Things you should do first
@ -111,11 +111,11 @@ $ timedatectl set-ntp true
Create partitions using the tools of your choice. I will be using the following partition map.
an EFI partition of 512M
An EFI partition of 512M
a swap partition with a size equal to your RAM.
A swap partition with a size equal to your RAM.
a btrfs partition containing the rest of the space.
A btrfs partition containing the rest of the space.
== Encryption
@ -137,7 +137,7 @@ $ cryptsetup luksFormat /dev/sda2
$ cryptsetup config --label="swap" /dev/sda2
{{</highlight>}}
now open the newly encrypted partitions
now open the newly encrypted partitions.
{{<highlight console "linenos=false">}}
$ cryptsetup open /dev/sda2 swap
@ -195,10 +195,10 @@ $ swapon /dev/mapper/swap
== installing base system, generating *stab
Install the base packages. Adjust the package list to suit your needs. change intel-ucode to amd-ucode if using an AMD processor.
Install the base packages. Adjust the package list to suit your needs. Change intel-ucode to amd-ucode if using an AMD processor.
{{<highlight console "linenos=false">}}
$ pacstrap /mnt linux linux-firmware base base-devel btrfs-progs zsh neovim git stow tmux connman wpa_supplicant openvpn fzf htop rsync tree xdg-user-dirs python tree openssh w3m curl intel-ucode
$ pacstrap /mnt linux linux-firmware base base-devel btrfs-progs zsh neovim git stow tmux networkmanager openvpn fzf htop rsync tree xdg-user-dirs python tree openssh w3m curl intel-ucode
{{</highlight>}}
Generate an fstab
@ -285,7 +285,7 @@ Install systemd-boot
$ bootctl install
{{</highlight>}}
Create /boot/loader/entries/arch.conf containing:
Create /boot/loader/entries/arch.conf containing: (again, change intel to amd depending on processor.)
{{<highlight console>}}
title Arch Linux
@ -295,7 +295,7 @@ initrd /initramfs-linux.img
options root=/dev/mapper/btrfs rootflags=subvol=/root resume=/dev/mapper/swap
{{</highlight>}}
edit /boot/loader/loader.conf and add:
Edit /boot/loader/loader.conf and add:
{{<highlight console>}}
default arch.conf
@ -360,4 +360,3 @@ Include = /etc/pacman.d/mirrorlist
{{</highlight>}}
Congrats! You now have a barebones, but functional, encrypted arch install!

15
content/posts/capsToCtrl.adoc
View file

@ -72,7 +72,7 @@ As such, our keymap patch looks like:
keycode 58 = Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control Control
{{</highlight>}}
Now just put it in in '/usr/share/kbd/keymaps/', and set it as your keymap with 'sudo localectl set-keymap [filename without .map extention]'.
Now just put it in '/usr/share/kbd/keymaps/', and set it as your keymap with 'sudo localectl set-keymap [filename without .map extention]'.
== Full keymap
@ -95,10 +95,15 @@ Then you can (optionally) re-zip it with 'sudo gzip [filename]' and set it as yo
There we go!
Our caps lock key is now a second control key!
Note that localectl does not seem to propogate our change to X11, unfortuanately.
To do it in X as well, simply run
{{<highlight console "linenos=false">}}
setxkbmap -option ctrl:nocaps
To do this in X as well, create a file in `/etc/X11/xorg.conf.d/`, named something along the lines of `90-keyboard.conf` with the config:
{{<highlight console>}}
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbOptions" "ctrl:nocaps"
EndSection
{{</highlight>}}
In your .xinitrc.
Some people may suggest `setxkbmap` as a way to do this.
However, unfortuantely, `setxkbmap` tends to be overwritten when a usb input device is plugged in or unplugged, and `xorg.conf.d` is the only persistent way to set it.

2
content/posts/dotfileManagement.adoc
View file

@ -119,7 +119,7 @@ This is for you to put any scripts you develop that may be called by/aliased by
Stow can be found on pretty much every linux distributions package manager. If for some reason it is not, building from source is... suprisingly easy.
You can find the source http://ftp.gnu.org/gnu/stow/[here], download `stow-latest.tar.gz`, and decompress it with `tar xvf stow-latest.tar.gz`. cd into the the uncompressed folder, and simply run `autoreconf -iv`, `./configure`, and `make`. The binary will be in `./bin/stow` free for you to move it into your `$PATH`.
You can find the source http://ftp.gnu.org/gnu/stow/[here], download `stow-latest.tar.gz`, and decompress it with `tar xvf stow-latest.tar.gz`. cd into the uncompressed folder, and simply run `autoreconf -iv`, `./configure`, and `make`. The binary will be in `./bin/stow` free for you to move it into your `$PATH`.
== Conclusion, or something