funky-monkey

#! /bin/bash
# Information came from https://apple.stackexchange.com/questions/358651/unable-to-completely-uninstall-zoom-meeting-app
# I just added more stuff to delete so there is no manual stuff to execute.

echo Zoom cleanup 🧹 
echo Cleaning Application Cached Files...
sudo rm -rf ~/Library/Application\ Support/zoom.us
sudo rm -fr ~/Library/Application\ Support/ZoomPresence

echo Cleaning Application...

magnetikonline

Backblaze B2 via rclone cheatsheet

• Create B2 remote
• Tasks
  • List buckets
  • Synchronize local files to bucket
  • Synchronize local files to bucket - checksum
  • Verify local files against bucket
• Reference

codyde

job "frontend" {
  datacenters = ["humblelabvm"]

  group "frontend" {
    network {
      mode = "bridge"
      port "web" {
        to = 80
      }
    }

hydrz

#!/bin/sh
set -e
set -o noglob

# Usage: ./install.sh [options]
#
# Example:
#   Installing on first master node run:
#     ./install --num 3 --vip 192.168.2.10 --iface eth0
#   Installing on other master nodes run:

beriberikix

Create system drive

qemu-img create -f qcow2 alpine.qcow2 16G

Install image

Linux

marvkis

Introduction

I was playing around with kubevirt.io (v1.2.0) on a Radxa ROCK 5 Model B. When I tried to boot a VM, I just had the qemu-kvm process eating 100% CPU with no output to the console.

I built an alternative setup based on ubuntu 22.04 and qemu worked with KVM without any problems. After some investigation I had the idea that it might be related to the (U)EFI bios used. I transferred the /usr/share/AAVMF/AAVMF_CODE.fd files from the 22.04 setup into the kubevirt compute container, started an additional qemu-kvm with -bios AAVMF/AAVMF_CODE.fd and voila - KVM booted correctly.

Findings

My findings so far:

bvierra

#!/bin/bash
# Made by u/BinkReddit
# Taken From: https://www.reddit.com/r/linuxadmin/comments/1hcrge3/kernel_patch_changelog_summary/
# set -x

if ! command -v curl >/dev/null 2>&1; then
    echo "This script requires curl."
    exit 1
fi