today's howtos
-
Using anacron to run periodic tasks
When you need to regularly run a program on your workstation that isn't powered 24/7 or even not every day, you can't rely on cronjob for that task.
Fortunately, there is a good old tool for this job (first release June 2000), it's called anacron and it will track when was the last time each configured tasks have been running.
I'll use OpenBSD as an example for the setup, but it's easily adaptable to any other Unix-like system.
-
In practice, cool URLs can become inaccessible even if they don't change
The idea that "cool URLs don't change" has been an article of faith for a very long time. Of course this is false in practice; decades of experience have shown us that cool URLs do change for all sorts of reasons (for example, forced changes in your domain name). Recently, we've seen at least two examples where cool URLs may not change as such, but they do become broadly inaccessible.
-
The persistence of 'san' names in our environment
We have a bunch of Linux fileservers, which use ZFS pools on ordinary SATA SSDs and export the filesystems from those pools over NFS. To make managing this environment easier, we have a suite of local programs (including our own ZFS spares system). All of these tools have names that start with 'san' (for example 'sanpool' and 'sanspares'). All of the hostnames of the fileservers also start with 'san' (they're mostly but not entirely named after cities, so we have 'santafe' but also 'sanandreas', which is of course the test fileserver). All of this is despite there being no SAN (Storage Area Network) in sight.
-
the details element and in-page search
An important factor in terms of UX and accessibility for deciding whether the <details> element is the right solution for a problem is the find-in-page behaviour.
In Chromium-based browsers, the details element automatically opens when it contains a string the user searches for. If Safari and Firefox, it has to be opened for the find-in-page feature to find the string.
-
[Repeat] How to Set Up a Local DNS Resolver with Unbound on Debian
In this guide, you will learn how to set up Private DNS Server with Unbound on a Debian 11 and Debian 12 server. You'll set up Unbound as a Local DNS Server with some features such as an authoritative DNS Server, enable DNS cache, set up local IP address and Access Control Lists (ACLs), setup local domain names, then set up Unbound as a DNS resolver with DNS-over-TLS (DoT) enabled.
In addition to that, you'll also set up logging for Unbound service via Rsyslog and Logrotate.
-
Clearing Pip Cache
You can built-in cache functionality in pip that plays its role by reducing the time while doing duplicate downloads and builds.
-
How to Install Gitea on AlmaLinux 9
In this tutorial, we are going to explain in step-by-step detail how to install Gitea on AlmaLinux 9 OS.