mirror of
https://github.com/Brandon-Rozek/website.git
synced 2024-11-09 10:40:34 -05:00
Fixed several broken links
This commit is contained in:
parent
e55a365666
commit
f0eb3f37d8
5 changed files with 6 additions and 4 deletions
|
@ -99,7 +99,7 @@ I save each toot in an individual markdown file under `content/toots`.
|
|||
|
||||
## Conclusion
|
||||
|
||||
My full [script](https://github.com/Brandon-Rozek/website/blob/master/refreshtoots_v2.py)
|
||||
My full [script](https://github.com/Brandon-Rozek/website-toots/blob/main/.scripts/refreshtoots.py)
|
||||
is on GitHub.
|
||||
The script will let you know of any toot IDs that are created
|
||||
and/or updated. I then add these toots to Git for version control
|
||||
|
|
|
@ -2,6 +2,8 @@
|
|||
title: "Getting started with Digital Modes in Linux"
|
||||
date: 2019-09-04T09:52:21-04:00
|
||||
draft: false
|
||||
aliases:
|
||||
- /blog/digialmodes
|
||||
tags: [ "Amateur Radio" ]
|
||||
---
|
||||
|
|
@ -7,7 +7,7 @@ tags: [ "Linux", "Storage" ]
|
|||
|
||||
[MergerFS](https://github.com/trapexit/mergerfs) is a great filesystem for an expandable storage system in a homelab. Mostly since it allows you to add disks one at a time without having to, for example, resilver a ZFS pool. MergerFS won't be as efficient as a filesystem that stripes your data across disks, but in the case of a disk failure the disks unaffected will still have part of the data.
|
||||
|
||||
[Plenty](https://blog.linuxserver.io/2017/06/24/the-perfect-media-server-2017/) of other [people](https://www.teknophiles.com/2018/02/19/disk-pooling-in-linux-with-mergerfs/) described MergerFS, so I'll keep this post simple.
|
||||
[Plenty](https://blog.linuxserver.io/2017/06/24/the-perfect-media-server-2017/) of other [people](https://web.archive.org/web/20200130103849/https://www.teknophiles.com/2018/02/19/disk-pooling-in-linux-with-mergerfs/) described MergerFS, so I'll keep this post simple.
|
||||
|
||||
First install MergerFS,
|
||||
|
||||
|
|
|
@ -23,7 +23,7 @@ Though that begs the question, what is sufficiently complicated? Here are some t
|
|||
- I believe `bc` is the easiest command to use to process arithmetical expressions. Though this also then involves constructing strings to pass into bc. For example: `result=$(echo "1 + 5" | bc)`
|
||||
- Anything requiring abstract data types
|
||||
- (Associative) arrays in bash are scary to me
|
||||
- Slawomir's functional programming in [bash library](https://github.com/ssledz/bash-fun) makes it more bearable. ([My fork](https://github.com/Brandon-Rozek/bashfun))
|
||||
- Slawomir's functional programming in [bash library](https://github.com/ssledz/bash-fun) makes it more bearable. ([My fork](https://github.com/Brandon-Rozek/bash-fun))
|
||||
- Argument Parsing
|
||||
- Attempted to [parse arguments in bash](/blog/bashpartialargparse/), but [parsing arguments in Python](/blog/python-argpase/) is much cleaner to me.
|
||||
|
||||
|
|
|
@ -19,4 +19,4 @@ To run:
|
|||
xvfb-run application
|
||||
```
|
||||
|
||||
For more customization, I hear that it's better to use [xpra with Xdummy](https://xpra.org/trac/wiki/Xdummy). I haven't tried this myself yet, but if you experience issues with the application expecting `randr` or `glx` extensions, give it a shot.
|
||||
For more customization, I hear that it's better to use [xpra with Xdummy](https://web.archive.org/web/20200926082251/https://xpra.org/trac/wiki/Xdummy). I haven't tried this myself yet, but if you experience issues with the application expecting `randr` or `glx` extensions, give it a shot.
|
Loading…
Reference in a new issue