le Duc Banal TheSirC

QEMU with VirtIO GPU Vulkan Support

With its latest reales qemu added the Venus patches so that virtio-gpu now support venus encapsulation for vulkan. This is one more piece to the puzzle towards full Vulkan support.

An outdated blog post on clollabora described in 2021 how to enable 3D acceleration of Vulkan applications in QEMU through the Venus experimental Vulkan driver for VirtIO-GPU with a local development environment. Following up on the outdated write up, this is how its done today.

Definitions

Let's start with the brief description of the projects mentioned in the post & extend them:

A funky shell thingy that I've never seen before

So you're in posix sh and you want to do the equivalent of this in bash:

foo | tee >(bar) >(baz) >/dev/null

(Suppose that bar and baz don't produce output. Add redirections where needed if that's not the case.)

This worked on 14/May/23. The instructions will probably require updating in the future.

llama is a text prediction model similar to GPT-2, and the version of GPT-3 that has not been fine tuned yet. It is also possible to run fine tuned versions (like alpaca or vicuna with this. I think. Those versions are more focused on answering questions)

Note: I have been told that this does not support multiple GPUs. It can only use a single GPU.

It is possible to run LLama 13B with a 6GB graphics card now! (e.g. a RTX 2060). Thanks to the amazing work involved in llama.cpp. The latest change is CUDA/cuBLAS which allows you pick an arbitrary number of the transformer layers to be run on the GPU. This is perfect for low VRAM.

Clone llama.cpp from git, I am on commit 08737ef720f0510c7ec2aa84d7f70c691073c35d.

The Setup

I wanted to write a module that generates multiple systemd services and timers to scrub some zfs pools at certain intervals. The default scrub config does not support individual scrub intervals for each pool.

I want the config to look like this:

{
  services.zfs-auto-scrub = {
 tank = "Sat *-*-* 00:00:00";

How to setup a practically free CDN using Backblaze B2 and Cloudflare

⚠️ Note 2023-01-21
Some things have changed since I originally wrote this in 2016. I have updated a few minor details, and the advice is still broadly the same, but there are some new Cloudflare features you can (and should) take advantage of. In particular, pay attention to Trevor Stevens' comment here from 22 January 2022, and Matt Stenson's useful caching advice. In addition, Backblaze, with whom Cloudflare are a Bandwidth Alliance partner, have published their own guide detailing how to use Cloudflare's Web Workers to cache content from B2 private buckets. That is worth reading,

	#!/usr/bin/env bash
	set -euo pipefail

	## Defaults
	keepGensDef=30; keepDaysDef=30
	keepGens=$keepGensDef; keepDays=$keepDaysDef

	## Usage
	usage () {
	printf "Usage:\n\t ./trim-generations.sh <keep-gernerations> <keep-days> <profile> \n\n

	# A basic script for uninstalling app packages in Windows 10/11, including those pre-installed with Windows
	#
	# Note: If you get an error about the script not being allowed to run, the below command will change the execution polciy temporarily for one session only:
	# Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process
	#
	# To execute the script, open a Powershell window to the directory with the script and run the following command using your scripts file name (and don't forget the .\ )
	# .\WhateverScriptName.ps1
	# -------------------------------------------------------------------------------------------
	# Script by ThioJoe - https://github.com/ThioJoe

	#!/usr/bin/env bash
	set -euo pipefail

	## Defaults
	keepGensDef=10; keepDaysDef=7
	keepGens=$keepGensDef; keepDays=$keepDaysDef

	## Usage
	usage () {
	printf "Usage:\n\t trim-generations.sh (defaults are: Keep-Gens=$keepGensDef Keep-Days=$keepDaysDef Profile=user)\n\n"

	#!/usr/bin/env bash

	set -Eeuo pipefail
	trap cleanup SIGINT SIGTERM ERR EXIT

	script_dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd -P)

	usage() {
	cat <<EOF
	Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-v] [-f] -p param_value arg1 [arg2...]

	Just a quick test of squashfs compression ratio using different settings.

	I am looking for relatively good and fast compression, that also is quick to decompress.
	I don't care about ultimate end size exactly tho.

	Input (a Debian testing live build with 6240 installed packages):

	$ sudo du -bs ./chroot
	26566785410 ./chroot # 26.6GB
	$