Converted images to thumbnails, updated gpg_best_practices
This commit is contained in:
Bastian de Byl
@@ -39,18 +39,14 @@ lost at that target distance of 1 meter.
|
||||
The biggest difference can be seen between the *f/1.7* and *f/4.0* shots. Note
|
||||
the increase in clarity on the pillows fabric.
|
||||
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/aperture-study/f17-f40-comp.jpg" >}}
|
||||
|
||||
## *f/1.7*--*f/2.8*
|
||||
---
|
||||
At *f/2.8* and above I started noticing less increase in perceived sharpness of
|
||||
the image, though the difference in comparison to *f/1.7* was still fairly
|
||||
noticeable
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/aperture-study/f17-f28-comp.jpg" >}}
|
||||
|
||||
## *f/2.8*--*f/4.0*
|
||||
---
|
||||
@@ -59,9 +55,7 @@ difference in shutter speed, the overall difference does not seem as dramatic
|
||||
from *f/2.8* to *f/4.0*. Personally, I'd say that *f/2.8* is the clear winner in
|
||||
finding the best middle-ground between maximum aperture and image quality.
|
||||
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/aperture-study/f28-f40-comp.jpg" >}}
|
||||
|
||||
|
||||
# Individual Photos
|
||||
@@ -69,24 +63,12 @@ finding the best middle-ground between maximum aperture and image quality.
|
||||
Below is the entire collection of all the photos taken of the subject at
|
||||
increasing aperture steps.
|
||||
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumbgallery >}}
|
||||
{{< thumb "/img/aperture-study/f17.jpg" >}}
|
||||
{{< thumb "/img/aperture-study/f20.jpg" >}}
|
||||
{{< thumb "/img/aperture-study/f22.jpg" >}}
|
||||
{{< thumb "/img/aperture-study/f25.jpg" >}}
|
||||
{{< thumb "/img/aperture-study/f28.jpg" >}}
|
||||
{{< thumb "/img/aperture-study/f32.jpg" >}}
|
||||
{{< thumb "/img/aperture-study/f40.jpg" >}}
|
||||
{{< /thumbgallery >}}
|
||||
|
||||
@@ -5,17 +5,23 @@ lastmod: 2019-01-29
|
||||
categories: ["Tutorial"]
|
||||
tags: ["linux"]
|
||||
---
|
||||
This is a guide written on how to install Arch Linux using LUKS for disk encryption, and Systemd-boot as the bootloader.
|
||||
This is a guide written on how to install Arch Linux using LUKS for disk
|
||||
encryption, and Systemd-boot as the bootloader.
|
||||
<!--more-->
|
||||
It is assumed that the reader has basic linux knowledge and understands that examples are given via output commands.
|
||||
The reader may always consult manpages, the [Arch Wiki](https://wiki.archlinux.org/), or other documentation to build a better understanding of the tools and methods used.
|
||||
It is assumed that the reader has basic linux knowledge and understands that
|
||||
examples are given via output commands. The reader may always consult manpages,
|
||||
the [Arch Wiki](https://wiki.archlinux.org/), or other documentation to build a
|
||||
better understanding of the tools and methods used.
|
||||
|
||||
---
|
||||
|
||||
# Partitioning
|
||||
1. Create a partition scheme using partitioner of choice (e.g. `gdisk`, `fdisk`, `cgdisk`).
|
||||
- First partition should be EFI/boot partition at around 256MB+ (type: `ef00`)
|
||||
- Second partition should be Linux LVM partition using rest of disk space (type: `8e00`)
|
||||
1. Create a partition scheme using partitioner of choice (e.g. `gdisk`, `fdisk`,
|
||||
`cgdisk`).
|
||||
- First partition should be EFI/boot partition at around 256MB+ (type:
|
||||
`ef00`)
|
||||
- Second partition should be Linux LVM partition using rest of disk space
|
||||
(type: `8e00`)
|
||||
1. Make the the EFI/boot partition FAT32 via `mkfs.fat -F32`
|
||||
|
||||
# Encryption
|
||||
@@ -24,13 +30,15 @@ The reader may always consult manpages, the [Arch Wiki](https://wiki.archlinux.o
|
||||
# cryptsetup luksFormat /dev/sdaN
|
||||
Enter passphrase:
|
||||
```
|
||||
**Note:** _Remember your passphrase! You will need this every time you boot your computer_
|
||||
**Note:** _Remember your passphrase! You will need this every time you boot
|
||||
your computer_
|
||||
1. Create a mapping for your Linux LVM (LUKS):
|
||||
```
|
||||
# cryptsetup open --type luks /dev/sdaN <map_name>
|
||||
```
|
||||
_Use whatever name you want. Ex. `lvm`, `volume`, etc._
|
||||
1. Create the physical volume, volume group, and logical volumes for `<map_name>` specified in the previous step:
|
||||
1. Create the physical volume, volume group, and logical volumes for
|
||||
`<map_name>` specified in the previous step:
|
||||
```
|
||||
# pvcreate /dev/mapper/<map_name>
|
||||
# vgcreate <volume_name> /dev/mapper/<map_name>
|
||||
@@ -62,7 +70,8 @@ The reader may always consult manpages, the [Arch Wiki](https://wiki.archlinux.o
|
||||
# swapon /dev/mapper/<volume_name>-swap
|
||||
```
|
||||
|
||||
1. Install the base system (_Assuming you have internet connectivity. Use `wifi-menu`, or other, to connect to the internet at this point._):
|
||||
1. Install the base system (_Assuming you have internet connectivity. Use
|
||||
`wifi-menu`, or other, to connect to the internet at this point._):
|
||||
```
|
||||
# pacstrap /mnt base base-devel
|
||||
```
|
||||
@@ -79,12 +88,15 @@ The reader may always consult manpages, the [Arch Wiki](https://wiki.archlinux.o
|
||||
```
|
||||
|
||||
1. Configure `initramfs`:
|
||||
1. Edit `HOOKS` in `/etc/mkinitcpio.conf` using text editor of your choice (e.g. `vi`, `nano`, etc.). Move the `keyboard` hook before `filesystems`, and add `encrypt` and `lvm2` hooks **before** `filesystems`:
|
||||
1. Edit `HOOKS` in `/etc/mkinitcpio.conf` using text editor of your choice
|
||||
(e.g. `vi`, `nano`, etc.). Move the `keyboard` hook before `filesystems`,
|
||||
and add `encrypt` and `lvm2` hooks **before** `filesystems`:
|
||||
```
|
||||
# egrep '^HOOKS' /etc/mkinitcpio.conf
|
||||
HOOKS=(base udev autodetect modconf block keyboard encrypt lvm2 filesystems fsck)
|
||||
```
|
||||
_Read the comment documentation on `HOOKS` in the document to find out more._
|
||||
_Read the comment documentation on `HOOKS` in the document to find out
|
||||
more._
|
||||
|
||||
1. Generate `initramfs`:
|
||||
```
|
||||
@@ -105,7 +117,10 @@ The reader may always consult manpages, the [Arch Wiki](https://wiki.archlinux.o
|
||||
editor 0
|
||||
```
|
||||
|
||||
1. Create the loader entry for the default `arch` entry specified above (_You can edit this name if desired._). Use `blkid /dev/sdaN` to find the UUID of your crypt device, and recall the volume name you gave your device above (_`main` in example below_):
|
||||
1. Create the loader entry for the default `arch` entry specified above (_You
|
||||
can edit this name if desired._). Use `blkid /dev/sdaN` to find the UUID
|
||||
of your crypt device, and recall the volume name you gave your device
|
||||
above (_`main` in example below_):
|
||||
```apacheconf
|
||||
# cat /boot/loader/entries/arch.conf
|
||||
title Arch Linux
|
||||
|
||||
@@ -65,15 +65,31 @@ Once the signature has been verified, the CA can be moved over to
|
||||
`/usr/share/ca-certificates` to add to your CA certificates via `sudo
|
||||
update-ca-trust` (_Arch_) or `sudo update-ca-certificates` (_Debian/Ubuntu_).
|
||||
|
||||
Lastly, the following parameters should be added to your `~/.gnupg/gpg.conf`:
|
||||
### GnuPG Versions >2.1
|
||||
Two following parameters should be added to your `~/.gnupg` configs:
|
||||
|
||||
#### `gpg.conf`:
|
||||
```apacheconf
|
||||
keyserver hkps://hkps.pool.sks-keyservers.net
|
||||
```
|
||||
|
||||
#### `dirmngr.conf`:
|
||||
```apacheconf
|
||||
hkp-cacert /etc/ca-certificates/path/to/CA.pem
|
||||
```
|
||||
|
||||
|
||||
### GnuPG Versions <2.1
|
||||
#### `gpg.conf`:
|
||||
```apacheconf
|
||||
keyserver hkps://hkps.pool.sks-keyservers.net
|
||||
keyserver-options ca-cert-file=/path/to/CA/sks-keyservers.netCA.pem
|
||||
```
|
||||
{{% admonition info "CA Path" %}}
|
||||
On my setup, the full path to the CA certs is:
|
||||
|
||||
`/etc/ca-certificates/extracted/cadir/sks-keyservers.net_CA.pem`
|
||||
{{% admonition tip "CA Path" %}}
|
||||
On my system the full path to the CA certs is:
|
||||
|
||||
- `/etc/ca-certificates/extracted/cadir/sks-keyservers.net_CA.pem`
|
||||
{{% /admonition %}}
|
||||
|
||||
## *Optional* - Ensure keys refreshed through keyserver
|
||||
|
||||
@@ -17,9 +17,7 @@ side, I figured the only way *in* was lifting the mesh cover off. So I went at
|
||||
it, carefully, with a pair of tweezers. I worked my way around the edge and
|
||||
wedged the mesh upwards.
|
||||
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/headphone-fix/IMG_7505.jpg" >}}
|
||||
|
||||
|
||||
# Okay, Maybe Turn It On
|
||||
@@ -31,13 +29,10 @@ right speaker put out no sound._ I checked the known-good left speaker using my
|
||||
**Rigol 1074Z** oscilloscope. This may not have been entirely necessary, but I
|
||||
wanted to find out what to expect when troubleshooting the right channel.
|
||||
|
||||
{{% admonition info "Left Speaker" %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
|
||||
{{% admonition info "Right Speaker" %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/headphone-fix/IMG_7506.jpg" >}}
|
||||
|
||||
{{< thumb "/img/headphone-fix/IMG_7511.jpg" >}}
|
||||
|
||||
Knowing what to expect on the oscilloscope, I hooked up the probe to the right,
|
||||
problematic, speaker. The result was much different, indicating either noise or
|
||||
@@ -49,9 +44,7 @@ disconnected at this point in time to ease the troubleshooting process.
|
||||
Lucky for me the PCB pads were labeled -- even better `SPKL+` (_left_) and
|
||||
`SPKR+` (_right_) were easy to find.
|
||||
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/headphone-fix/IMG_7507.jpg" >}}
|
||||
|
||||
Outside of the bluetooth board hidden under the piece of tape, there's not a
|
||||
whole lot going on in the circuit. It was my guess that the visible surface
|
||||
@@ -60,15 +53,13 @@ search of `AIWI TI` (_as shown in the photograph_) resulted
|
||||
in [the following datasheet](http://www.ti.com/lit/ds/symlink/tpa6132a2.pdf)
|
||||
which verified that to be the case.
|
||||
|
||||
<center></center>
|
||||
<center></center>
|
||||
|
||||
**Bingo!** Now knowing the pinout, I could use my trusty multimeter (_a Fluke
|
||||
115_) to test continuity of the circuit from the known-good and the now
|
||||
known-bad speaker traces back to the `OUTL` and `OUTR` outputs of the amplifier.
|
||||
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/headphone-fix/IMG_7514.jpg" >}}
|
||||
|
||||
Removing the board from the housing required a bit of finesse. I didn't want to
|
||||
bother desoldering the left speaker connections to make removal easier. So, with
|
||||
@@ -92,9 +83,7 @@ Using the 3.5mm mini-jack's solder pads, I found continuity to be true from the
|
||||
chips left and right outputs to the conveniently accessible solder pads. _A
|
||||
bodge wire was in order_..
|
||||
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/headphone-fix/IMG_7515.jpg" >}}
|
||||
|
||||
|
||||
# All's Well That Ends Well
|
||||
@@ -103,9 +92,7 @@ pin to `SPKR+`. Lo and behold it was now closed-circuit! I was very happy to see
|
||||
the expected waveform from the known-good left channel now also appearing on the
|
||||
right channel.
|
||||
|
||||
{{% admonition info %}}
|
||||
|
||||
{{% /admonition %}}
|
||||
{{< thumb "/img/headphone-fix/IMG_7516.jpg" >}}
|
||||
|
||||
At this point I quickly re-soldered the wires to the speaker and enjoyed music
|
||||
now coming into both ears!
|
||||
|
||||
@@ -30,9 +30,7 @@ my GitHub fork of the **Tracks** theme.
|
||||
# Rough Start
|
||||
Right off the bat I noticed the navigation bar seemed a bit off, to say the least:
|
||||
|
||||
{{% admonition info %}}
|
||||
<center></center>
|
||||
{{% /admonition %}}
|
||||
<center></center>
|
||||
|
||||
The links showed as numbers and pointed to `/0`, `/1`, and `/2`
|
||||
respectively. These, of course, lead to 404s. It didn't seem like the intended
|
||||
@@ -78,9 +76,7 @@ The original uses the `.Site.Sections` variable, which I replaced with
|
||||
user-defined `config.toml` nav links weren't ever utilized or populated anywhere
|
||||
on the site.
|
||||
|
||||
{{% admonition info %}}
|
||||
<center></center>
|
||||
{{% /admonition %}}
|
||||
|
||||
I borrowed the code found in `layouts/partials/sidebar.html` (*which also never
|
||||
appears to be used*) to include the nav links and get my desired behavior:
|
||||
|
||||
Reference in New Issue
Block a user