How-To

openSUSE Kernel cmdline INSECURE=1 to boot test ISO’s without signed repositories on the image Build ProductBuilder images outside of openSUSE:Factory Grab the following packages 000product installation-images skelcd-control-* Example repository configuration for building: <project name="home:sfalken:kalpa:images"> <title>Kalpa Images Devel Project</title> <description/> <person userid="sfalken" role="bugowner"/> <person userid="sfalken" role="maintainer"/> <build> <disable arch="i586"/> <disable arch="i586" repository="openSUSE_Tumbleweed"/> </build> <publish> <disable/> <enable repository="product"/> <enable repository="images"/> <enable arch="x86_64" repository="openSUSE_Factory"/> <enable arch="x86_64"/> <disable arch="i586" repository="openSUSE_Tumbleweed"/> <disable arch="i586" repository="images"/> </publish> <useforbuild> <disable arch="i586"/> <disable arch="i586" repository="openSUSE_Tumbleweed"/> </useforbuild> <repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Factory" repository="snapshot"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="images"> <path project="home:sfalken:kalpa:images" repository="openSUSE_Tumbleweed"/> <path project="openSUSE:Factory" repository="standard"/> <path project="openSUSE:Factory" repository="snapshot"/> <arch>x86_64</arch> </repository> </project> Grab prjconf from openSUSE:Factory ...

So you want to do fedora packaging in a Distrobox? It takes a couple of extra steps, particularly if you want to be able to do mockbuilds: $ distrobox create -i quay.io/fedora/fedora:latest -n fpkg --root --init --additional-packages 'systemd vim zsh fedora-packager copr-cli' If you happen to be on an openSUSE based system, such as MicroOS, Aeon, or Kalpa (and probably Leap, Tumbleweed, or anything else), you’ll need to do the following: ...

The story of the day As some of you may, or may not know, in general, when it comes to CLI tools for Kalpa, the existing recommendation is to use a Distrobox, and do your stuff there. This really is a perfectly fine way to do things, but it does add a layer of abstraction, running those things in a container, and can sometimes be a pain in the arse, when it comes to accessing certain things, like USB devices, etc. ...

The Scenario If you’re anything like me, you use Discord for things, and if you use their “Official” Linux electron client you know what a wonderful piece of software it is, and how the developers have helpfully chosen default window/panel sizes for you, because obviously they use your computer, and know what your screen configurations, preferred window arrangement, and everything else are. Now, you can certainly go to a third party client/mod like Vencord, or BetterDiscord, both perfectly valid choices. ...

What prompted this blog post? So if like myself, you’ve got a large number of openSUSE machines on your network, it can be advantageous to run a local mirror, for updates. And it just so happens that one of the openSUSE developers, firstyear, has put together a nifty caching server that really speeds all this up, the proxy-cache itself isn’t the point of this blog post, but if you want to know more, you can find it at: opensuse-proxy-cache ...

The Story. I have a machine, setup as a NAS, that lives in my closet, running TrueNAS Scale, which I also use to run some various Virtual Machines, because why not, it’s relatively beefy hardware for a NAS (Ryzen 7 5600G, 64MB of Ram), and when I built the thing, It had 4 X WD Red 2TB Drives, in a RAIDZ1, and a spare 256GB SATA SSD from an old machine, that I used for the boot-pool. ...

So if you’re anything like me, you’re aware that tools like Docker and Podman exist, which allow you to run containers on your host. Simple enough. You might also be aware of things like Docker Compose and Quadlets for automated management and bring up of those containers. Problem is, I had a pretty stupid simple little container that I wanted to bring together, and have running on a server. And for the life of me, I couldn’t find a relatively simple “How-To” online to do what I wanted to. All of the offerings that I found were dealing with big pre-built containers for things like Wordpress that have multiple containers, and setup pods, and such. All overkill and more complicated than I needed. ...