luckylittle

[Unit]
Description=IRSSI service

[Service]
RemainAfterExit=yes
ExecStart=/usr/bin/screen -S irssi -dm irssi
ExecStop=/usr/bin/screen -S irssi -X quit
User=lmaly

[Install]

luckylittle

ServerName			"ProFTPD server"
ServerIdent			on "FTP Server ready."
ServerAdmin			root@localhost
DefaultServer			on
DefaultRoot			~/Downloads
PassivePorts			49181	49189
Port				54320
DefaultAddress				0.0.0.0
AuthPAMConfig			proftpd
AuthOrder			mod_auth_pam.c* mod_auth_unix.c

luckylittle

echo '" Disable automatic comment insertion\nautocmd FileType * setlocal formatoptions-=c formatoptions-=r formatoptions-=o' | sudo tee --append /etc/vimrc

luckylittle

Keybase proof

I hereby claim:

• I am luckylittle on github.
• I am lmaly (https://keybase.io/lmaly) on keybase.
• I have a public key whose fingerprint is E7D6 9540 CBDF 724E F21B 6FB9 12CD BBCD 6D90 FD00

To claim this, I am signing this object:

luckylittle

#!/bin/bash

ls -1 *.mkv | rev | cut -d '.' -f2- | rev | xargs mkdir -v
for i in $(ls -1 *.mkv); do mv -v ${i} ${i%.mkv}; done

# Before:
# [lmaly@localhost The_Man_in_the_High_Castle]$ ls -1 *.mkv
# The.Man.in.the.High.Castle.S01E01.720p.WEBRip.x264-BATV.mkv
# The.Man.In.The.High.Castle.S01E02.720p.WEBRip.x264-SERIOUSLY.mkv
# The.Man.In.The.High.Castle.S01E03.720p.WEBRip.x264-SERIOUSLY.mkv

luckylittle

#!/usr/bin/env bash
# MIT License
# Copyright (c) 2020 Lucian Maly, <lucian@redhat.com>
# Raspberry Pi sometimes need more env to be built correctly, depending on the ARM version:
# `GOOS=linux GOARCH=arm GOARM=7 CGO_ENABLED=0 go build` worked for my Raspberry [ARMv7 Processor rev 5 v7l]

cyan=`tput setaf 14`
beige=`tput setaf 215`
white=`tput setaf 15`
black=`tput setaf 0`

luckylittle

# Sometimes there are moments, when you construct JSON in a really dirty way by just appending key/value pairs and adding comma at the end.
# You will end up with something like this:

# {
#   "big_key": {
#     "small_key1": "small_value1",
#     "small_key2": "small_value2",
#     "small_key3": "small_value3",

# And then to make this valid JSON, you need to replace the last comma with curly braces.

luckylittle

YAML Multiline Strings

Block scalars

Find the right syntax for your YAML multiline strings:

There are two types of formats that YAML supports for strings: block scalar and flow scalar formats. (Scalars are what YAML calls basic values like numbers or strings, as opposed to complex types like arrays or objects.) Block scalars have more control over how they are interpreted, whereas flow scalars have more limited escaping support.

1. Block Style Indicator: The block style indicates how newlines inside the block should behave. If you would like them to be kept as newlines, use the literal style, indicated by a pipe (|). If instead you want them to be replaced by spaces, use the folded style, indicated by a right angle bracket (>). (To get a newline using the folded style, leave a blank line by putting two newlines in. Lines with extra indentation are also not folded.)

luckylittle

Red Hat Enterprise Linux Diagnostics & Troubleshooting (RH342)

Last update: Fri Jul 26 08:23:20 UTC 2019 by @luckylittle

---

1. Troubleshooting principles

2. Generic issues

luckylittle

% Contents of listings-setup.tex
% Example: pandoc -f markdown_github --listings -H listings-setup.tex -V geometry:margin=0.3in RH342.md -o RH342.pdf
\usepackage{xcolor}

\lstset{
    basicstyle=\ttfamily,
    keywordstyle=\color[rgb]{0.13,0.29,0.53}\bfseries,
    stringstyle=\color[rgb]{0.31,0.60,0.02},
    commentstyle=\color[rgb]{0.56,0.35,0.01}\itshape,
    backgroundcolor=\color[RGB]{248,248,248},