Posts Tagged ‘Ubuntu’
RISC-V Production Ready
TL;DR RISE did it’s job, and in the past couple of years RISC-V support has found its way into stable releases of key infrastructure software like Debian. So from a software perspective, it’s arguable that RISC-V is now ready for production. Progress has been a little slower on the hardware front, but hardware is… hard; […]
Filed under: technology | Leave a Comment
Tags: Alpine, android, cloud, Dart, Debian, GhostWrite, Linux, RISC-V, riscv64, Scaleway, SOC, Trixie, Ubuntu
Silent PC upgrade
TL;DR After 6.5y+ of service my PC needed a refresh – so it has a new motherboard, CPU, RAM and SSD, and I’ve taken the opportunity to switch to Linux. It’s still completely silent, but noticeably faster :) Background I built a Silent PC based on a Streacom DB4 case back in the summer of […]
Filed under: technology | Leave a Comment
Tags: benchmark, CPU, DB4, Intel, Kubuntu, Linux, motherboard, PC, QuietPC, RAM, silent, ssd, Streacom, Ubuntu
Python script dependencies
TL;DR ‘–break-system-packages’ sounds scary, but (after some careful evaluation) is likely to be the right way to go for infrastructure automation, at least until uv is ready for production. Python venvs seem to be what we’re expected to use, but introduce additional complexity and associated fragility, which seems to make them a poor choice for […]
Filed under: code | Leave a Comment
Tags: --break-system-packages, APT, automation, deb, Debian, dependencies, externally-managed-environment, infrastructure, package, PyPI, python, Raspberry Pi, script, system, Ubuntu, uv, venv, virtual environment
TL;DR pymarkdownlnt provides an easy way of checking that any Markdown you’re working on is complying to some sensible guidelines. If you’re comfortable with Python virtual environments you won’t really need the rest of this post. Why? I’ve spent a bunch of time recently adding OpenSSF Scorecards to the key Atsign repos. Build better security […]
Filed under: howto | Leave a Comment
Tags: Actions, github, lint, lints, Markdown, Pip, pymarkdown, pymarkdownlnt, python, scorecard, Ubuntu, uv, venv, venvs, virtual environment
Apache 2.2 on Ubuntu 14.04
Apache 2.4 changes things a lot – particularly around authentication and authorisation. I’m not the first to run into this issue, but I didn’t find a single straight answer online. So here goes (as root): If you want mpm-worker then do this instead:
Filed under: howto | Leave a Comment
Tags: 14.04, 2.2, Apache, Ubuntu
TL;DR Apple and Google have both launched laptops in the past few days that are both amazing and seriously flawed. If only somebody could make a machine that has the best of both worlds. MacBook The leaks were pretty much spot on, so in the end the new MacBook brought few surprises. I really want […]
Filed under: could_do_better, technology | 2 Comments
Tags: apple, Canonical, Chromebook, ChromeOS, google, laptop, MacBook, Pixel, Pixel2, Ubuntu, USB-C
I wrote a few days ago about my first failed attempt to do this. After some perseverance, and with some lessons learned along the way I’m pleased to say that I now have it working. Given that VXLAN (at least in the Linux kernel implementation) needs multicast I’m still not sure that this is a […]
Filed under: Docker, networking | 3 Comments
Tags: 14.04, bridge, Docker, iproute2, multicast, network, open vswitch, tunnel, Ubuntu, vxlan
This seemed like a good idea, as VXLAN has been in the Linux kernel since 3.7. TL;DR – this doesn’t work as I’d hoped. The two major issues being: VXLAN needs a multicast enabled network, which rules out most public clouds. Instability – I’ve managed to provoke multiple kernel panics on stock Ubuntu 14.04. Background […]
Filed under: Docker, networking | 2 Comments
Tags: bridge, Docker, fail, gre, iproute2, multicast, network, open vswitch, tunnel, Ubuntu, vxlan
Chris Swan's Weblog 