Browse Source

Added notices. Minor fixes.

dev
Franco Masotti 3 years ago
parent
commit
933c535240
Signed by: frnmst
GPG Key ID: 24116ED85666780A
  1. 20
      _posts/2017-04-24-qemu-ssh-tunnel.md
  2. 16
      _posts/2018-11-18-my-bash-option-parsing-template.md
  3. 5
      _posts/2019-07-04-from-crontabs-to-systemd-timers.md
  4. 5
      _posts/2019-07-08-raid-data-scrubbing.md

20
_posts/2017-04-24-qemu-ssh-tunnel.md

@ -1,19 +1,18 @@
---
title: Qemu SSH tunnel
updated: 2018-12-02 18:33
updated: 2019-08-11 19:35
tags: [qemu, vnc, ssh tunnel]
description: How to use qemu via VNC and SSH
---
*Please note that every step described here, except installations and file
configurations have now been integrated directly in the QVM script. For this
reason you should follow the instructions reported on the
[readme file](https://github.com/frnmst/qvm/blob/master/README.md)*
Hello readers,
I was in need to run a virtual machine to do some experiments an `archiso`
(sic) and `parabolaiso`. My `Intel(R) Core(TM)2 Quad CPU Q8200 @
I was in need to run a virtual machine to do some experiments on `archiso`
(sic) and `parabolaiso`.
<!--more-->
My `Intel(R) Core(TM)2 Quad CPU Q8200 @
2.33GHz` PC desktop processor does not support virtualization technology which
means that when I run a virtual machine it's very, very slow (barely usable).
So I thought: why not use the home server which has newer hardware and
@ -24,6 +23,11 @@ $ lscpu | grep Virtualization
Virtualization: VT-x
```
*Please note that every step described here, except installations and file
configurations have now been integrated directly in the QVM script. For this
reason you should follow the instructions reported on the
[readme file](https://github.com/frnmst/qvm/blob/master/README.md)*
Now, some time ago I've written a
[simple script](https://github.com/frnmst/qvm) to handle my "QEMU needs",
VirtualBox is not available on Parabola and I don't like the available QEMU

16
_posts/2018-11-18-my-bash-option-parsing-template.md

@ -1,25 +1,29 @@
---
title: My bash template for option parsing
tags: [getopts, bash, template, bashisms, shell]
updated: 2019-02-13 16:12
updated: 2019-08-11 19:35
description: a template for option parsing in Bash based on getopt
---
*Please note that the script and the documentation reported here, except for
the introduction and the "Reason" paragraph, is outdated. For this
reason you should refer to the [repository](https://github.com/frnmst/fbopt).*
Hello again,
in the past years I have written a lot of scripts which rely on
`getopt`, a program that parses command line options (both short and long) and
arguments. Getopt is part of the [util-linux](https://www.kernel.org/pub/linux/utils/util-linux/) package.
arguments.
<!--more-->
Getopt is part of the [util-linux](https://www.kernel.org/pub/linux/utils/util-linux/) package.
Please, [don't confuse getopt with getopts](https://unix.stackexchange.com/questions/62950/getopt-getopts-or-manual-parsing-what-to-use-when-i-want-to-support-both-shor)
; they are quite different.
See [this](https://www.mariusvw.com/2013/02/24/bash-getopt-versus-getopts/)
and [this](http://abhipandey.com/2016/03/getopt-vs-getopts/) for a comparison
between the two.
*Please note that the script and the documentation reported here, except for
the introduction and the "Reason" paragraph, is outdated. For this
reason you should refer to the [repository](https://github.com/frnmst/fbopt).*
*Please note that the documentation and source code reported here are old.
Refer to the [fbopt](https://github.com/frnmst/fbopt) repository.*

5
_posts/2019-07-04-from-crontabs-to-systemd-timers.md

@ -1,7 +1,7 @@
---
title: From crontabs to Systemd timers
tags: [bash, shell, crontab, cronie, systemd, timer]
updated: 2019-07-07 13:22
updated: 2019-08-11 19:35
description: The steps I followed to migrate from crontabs to systemd timers.
---
@ -12,6 +12,9 @@ recurring tasks such as backups.
<!--more-->
*Please note that every step described here is directly related to the
[automated-tasks](https://github.com/frnmst/automated-tasks) repository.*
The problem of this method is that you cannot
easily control running processes and you are not provided with a uniform interface.
Systemd service and timer unit files seem to solve these issues. As usual,

5
_posts/2019-07-08-raid-data-scrubbing.md

@ -1,7 +1,7 @@
---
title: RAID data scrubbing
tags: [python, RAID, scrubbing, data, systemd, timer]
updated: 2019-07-08 12:25
updated: 2019-08-11 19:35
description: A simple RAID scrubbing python script and its systemd service and timer.
---
@ -11,6 +11,9 @@ RAID scrubbing checks and fixes errors in RAID arrays.
<!--more-->
*Please note that the source code and the steps described here are included in the
[automated-tasks](https://github.com/frnmst/automated-tasks) repository.*
While I was reading an [Arch Wiki page](https://wiki.archlinux.org/index.php?title=RAID&oldid=572096#Scrubbing),
I found an [AUR package](https://aur.archlinux.org/packages/raid-check-systemd/)
that claims to run periodic RAID scrubbings on the hard drives.

Loading…
Cancel
Save