As a bored sysadmin you might SSH into one of your servers and run htop or tail -f access.log.
Last Sunday was one of those tail -f access.log days.
You take a cursory look at your web server logs slowly scrolling past and see a bunch of requests come in. They look a bit odd.
Suppose you log into a server with your own SSH user, have password-less sudo access and want to access files as root over SFTP.
Your attempt would probably look like this:
# sftp user@remote Connected to remote. sftp> cd /root sftp> ls remote readdir("/root"): Permission denied sftp> sudo ls Invalid command.
Not possible, right?
As I increasingly use distributions that rely on firewalld over the old ways of manually configuring iptables this article notes down some common patterns encountered.
Before HDR came into wider use, working with video was easier. You didn't have to care about colorspaces [1], it would display fine everywhere and working with it was painless. Ok, this is oversimplified. But you get the point.
With HDR it's not so simple anymore: To display it a process called tonemapping needs to be applied and you even need a HDR-capable output device in order for a meaningful difference to be visible (compared to SDR, Standard Dynamic Range).
Suppose you want a Windows installation for your computer, but a bit more portable. You might think to use an external USB but the truth is Microsoft doesn't want you doing this and prevents it in the Windows installer.
This post isn't for the basic operations like installing stuff, because those are easy to remember or easy to figure out if you're missing them.
It recently occurred that I had the need to route all traffic by a certain application through a VPN. While premade solutions for this exist using Docker (especially in combination with BitTorrent clients), I preferred looking for something that really just isolates what is needed and leaves the rest alone.
This post contains Q&A-style notes on compiling software for OpenWrt or compiling OpenWrt itself.
With Raspbian (now named Raspberry Pi OS) having been released as 64-bit, I can finally write a proper sequel to the previous post that dealt with virtualizing ARM/Linux distributions headlessly using QEMU.
You can read the original article here: Virtualizing Raspbian (or any ARM/Linux distro) headless using QEMU. Since the process is the same I will skip detailed explanations here.
