In September 2025, I attended the annual LibreOffice conference in Budapest, Hungary. This gave me an opportunity to explore the city, which I will cover in this post.
Let s start with the currency. Although Hungary is a part of the European Union (EU), it doesn t use the euro as its currency. Instead, it uses Hungarian forints (denoted by Ft ). During my time in Hungary, 1 Indian rupee was equal to 4 Hungarian forints.
After reaching the Budapest airport, I bought a 15-day public transport pass. The public transport counter is after you pass customs and immigration. The pass allows unlimited use of public transport in the city. I had to show my passport and pay 5950 Ft to get the pass. The pass had my passport number mentioned on it. The public transport passes can also be bought at any of the tram stations as well.
This is the counter from where I bought my public transport pass.
My unlimited public transport pass for Budapest. I have redacted my passport number from it.
An automatic ticket machine at a tram station in Budapest.
Budapest is a union of two cities Buda and Pest lying on opposite sides of the Danube River. My hotel Corvin Hotel was on the Pest side.
Budapest had good public transport. The buses, metros, and trams complemented each other. For example, the airport didn t have metro or tram connectivity, but it was served by the bus. Most of the metro was on the Pest side, with only a couple of stations falling in Buda. However, both sides had an extensive network of trams.
Furthermore, the information about the public transport was easily accessible. For instance, the map of tram stops inside the trams also included the bus routes one could get after alighting at those stops.
From the airport, I took a bus followed by taking a metro on the M3 line to reach within walking distance of my hotel.
An M3 line metro in Budapest.
During the conference I would take the tram to the conference venue. The trams were modern and fast. They also had a smiley face at the front, which gave them a friendly look. It seemed like the trams were happily doing their job. The city also had a good pedestrian infrastructure along with separate cycling tracks.
A tram in Budapest having a smiley face at the front.
Budapest s tap water is officially safe to drink, which was mentioned on a sticker posted on the wall of the bathroom of my hotel room. So, I did not need to buy any water bottles while I was there.
On the 6th of September, I went on a sightseeing tour of Budapest with my Dione. Our friend Attila, who was a local (from Hungary), joined us. We went to the central market from our hotel by metro.
If you read my post on Vienna, I mentioned that the metro stations don t have AFC gates but ticket validators instead. Budapest s metro also has the same system. If you buy individual tickets, you need to validate them using the validators on the station before boarding the metro. If you are using a public transport pass like I was, then you do not need to validate, and you can board the metro directly.
A ticket validator at a metro station in Budapest.
In 10-15 minutes, we reached the central market. Attila showed us around. I bought a fridge magnet and paprika powder as souvenirs. Paprika powder is a signature spice of Hungary. It is mainly available in two forms one is sweet and the other being spicy. I wanted the spicy one, but I didn t get that in that market. Therefore, I had to contend with buying the sweet version. The sweet version isn t sweet though, it is just not spicy. After bringing that paprika powder home, it is mainly used for food coloring. I like it though and use it frequently in my omelets and other dishes.
Central market.
The building right behind the tram is the central market building.
At some point, Atilla had to join the The Document Foundation (TDF) sightseeing group, so we parted ways at the central market. Dione and I continued our sightseeing and decided to start with visiting the Hungarian parliament, which is a tourist attraction. It was because we were on the Pest side and the parliament was also on the same side, while other tourist attractions were on the Buda side.
So, Dione and I hopped on a tram and went to the parliament. We got off at a tram station just outside the parliament. The parliament is the icon of Budapest. The building has a gothic architecture and colored brown and white. One can buy tickets and take an inside tour. However, we didn t have a lot of time, so we stayed outside the building.
Hungarian Parliament building.
After spending some time outside the parliament building, we took a tram to the Chain Bridge. As I mentioned earlier, Budapest has two parts Buda and Pest separated by the Danube River. To go from one of the sides to the other requires crossing a bridge. Although Budapest has many bridges linking the two sides, the main one is the Chain Bridge.
We walked on the chain bridge to get to the other side. The bridge gave a good view of the Danube River. It also had a statue of a lion. The Buda Castle (another major landmark of Budapest) was visible from the bridge.
A shot of Chain Bridge.
The lion statue on the Chain Bridge.
After reaching the other side of the bridge (the Buda side), we sat on a bench for some time and then planned on where to go next. We decided to go to Fisherman s Bastion, which is another tourist attraction.
We used the OSMAnd~ app to figure out which bus to take and hopped on one. Soon we reached Fisherman s Bastion, where we found a flight of stairs that led upwards. Upon climbing the stairs, we got a panoramic view of the city. It also gave us a good view of the Hungarian parliament across the river. Going further upstairs, we found a statue of Stephen I of Hungary. He was the first king of Hungary, getting the crown in the year 1900.
A view of Hungarian parliament from Fisherman s bastion.
I found Fisherman s Bastion to be the best tourist attraction in the city. As mentioned earlier, it offers a panoramic view of the city, which I liked. I liked the arhitecture and open space there. If you find yourself in Budapest, I would highly recommend that you visit Fisherman s Bastion.
Fisherman s Bastion.
Statue of Stephen I of Hungary at Fisherman s Bastion.
Next, we went downstairs and returned to where the bus dropped us. From here on, we walked in random streets to see the residential and non-touristy side of Budapest. It was not so random as we walked towards Batthy ny t r metro station. Upon reaching the metro station, we found a caf where we stopped for a while for some coffee. After injecting some caffeine into our blood, we proceeded to find a place to have lunch.
Batthy ny t r metro station.
For lunch, we decided to go to R k czi t r metro station after reading on the internet about the food options there. Upon exiting the metro station, we found a market inside a building that had a lot of shops, but most of them were closed.
After roaming around inside a bit, we found an Italian place open and decided to eat there. The name of this place was Matteos. We ordered an eggplant parmigiana, a lasagna artichoke, and a classic tiramisu. It wasn t very tasty but filled us up for the day.
A picture of Matteos, where we had our lunch.
Budapest has four metro lines, and we had been to three of them, so we decided to try the remaining line, which was the M1 line. It is the oldest line in the city and has a different vibe than the modern lines. This line was opened in 1896, one of the oldest subway systems in the world.
The coaches were much smaller than the other metro lines, and the seating arrangement was something you would expect from a bus than a typical metro train. We rode all the way to the last stop, Mexik i t. Upon going outside, we found out there wasn t much to do here.
At this point, I checked the map and realized that Heroes Square is just a couple of metro stations away. Heroes Square is a tourist attraction in Budapest. It is located in Zugl a and is a historically significant place in Budapest. It has a monument which features the Seven chieftains of the Magyars.
M1 line station and tracks. It is the oldest metro transit of Budapest and one of the oldest in the world. It started operations in 1896.
Here, our unlimited public transport pass was handy because if it was paid per trip, we would think of the stop as a wasted one because we would have to buy a ticket again, but in this case we could just hop on again without any regrets.
An M1 line metro train entering the station.
So we took the M1 line again and deboarded at H s k tere station, followed by walking to the square. After roaming around for a while, we saw a trolleybus and decided to ride on that.
Heroes Square.
This is the trolleybus we took in Budapest.
A trolleybus is an electric bus that is powered by overhead electric cables. It is like a tram but runs on roads instead of tracks. We got down at D zsa Gy rgy t metro station. Then we took a metro to our hotel.
Before going to the hotel, we went to a place to eat something. We had coffee and l ngos. L ngos is a deep-fried Hungarian dish, which looks exactly like the Indian flatbread bhatura. I found it tasty, but since it was deep-fried, that was almost a given.
L ngos a dish which looks like the Indian flatbread bhatura.
The next day we went to Vienna the capital of Austria which I have already posted about. Check it out here.
I had a good time in Budapest, and it is a beautiful city with good public transport and some amazing sites to visit.
That s it for now, and see you next time!
Credits: Thanks Dione and Badri for proofreading.
Zswap vs Zram
Last year I blogged about using Zram for VMs [1]. That setup is still working well for VMs and for phones and laptops with no swap device.
I have just read Chris Down s insightful blog post about Zswap vs Zram [2] which convinced me to setup Zswap on some systems. I have had some of the problems that were described in his blog post when trying to run Zram on workstation and server systems.
One limitation of zswap is that it doesn t allow specifying the compression level. For zram I can put the following in /etc/systemd/zram-generator.conf to set the zstd compression level (this works well on my Thinkpad X1 Carbon Gen6):
[zram0]
compression-algorithm=zstd(level=10)
For the BTRFS filesystem I can put compress=zstd:13 in the mount options to specify the compression level. They really should support different compression levels in zswap. The ideal compression level depends on the speed of the CPU and new CPUs keep getting faster.
Setup
The documentation says to use something like the following on the kernel command-line to enable zswap:
The max_pool_percent=20 setting is the default which means to use up to 20% of system RAM for compressed data. I ve seen documentation sugesting up to 50% which seems a little excessive.
Note that a lot of documentation says to use zswap.zpool=z3fold, but z3fold is going to be removed and zsmalloc (the default) is recommended [3].
There is documentation about changing the compression algorithm via command line parameters, on Debian only lzo is linked in to the kernel and zstd (my preferred option) is a module so the kernel command line can t be used to set zstd, but the following command works:
The shrinker_enabled option is to allow the kernel to evict cold pages without waiting for memory pressure.
You can enable zswap without rebooting by running commands like the following. You could even put them in /etc/rc.local or something, but I think putting it in the kernel command line is a good idea as it makes it obvious to the next sysadmin what is happening.
This table documents my current understanding of the debug values. The difference between reject_compress_fail and reject_compress_poor isn t clear in a lot of the documentation, even reading the source didn t make it easy to understand.
File
Meaning (LC is lifetime count)
pool_limit_hit
LC pool limit hit and pages are forced to the swap partition
pool_total_size
RAM used for zswap data
reject_alloc_fail
LC can t allocate memory because max_pool_percent has been reached
reject_compress_fail
LC of pages with a compression algorithm failure so go straight to swap partition
reject_compress_poor
LC of pages that can t compress so go straight to swap partition
reject_kmemcache_fail
LC kernel malloc failure (serious problem?)
reject_reclaim_fail
LC failure to move a page from compressed RAM to disk serious problem!
stored_pages
Swapped pages stored by zswap
written_back_pages
LC of pages written back to swap partition from zswap
All of this is not nearly as easy to understand as the following command for zram:
# zramctl
NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 zstd 7.7G 2.1G 375M 386M 4 [SWAP]
Debian Wiki
The Debian Wiki page about Zswap is very brief [4] and needs more description about this, I think a lot of Debian users will use zram instead of zswap because setting up zram is just a single apt command. I m not planning to immediately add to that wiki page because I m not an expert on this, I would appreciate comments on this blog post from others who have got zswap working. I will update the wiki if others report matching experiences to mine.
Conclusion
I m now using zswap on a few systems including my main home workstation which had performed poorly with zram and a swap device in the past. If that goes well I ll put it on other systems.
I wrote the following shell script to display zswap stats, consider it GPL if you want to use it:
#!/bin/bash
if [ ! -f /sys/kernel/debug/zswap/stored_pages ]; then
echo "ZSwap not enabled"
exit 0
fi
PAGES=$(</sys/kernel/debug/zswap/stored_pages)
PAGESIZE=$(getconf PAGESIZE)
RAM=$(echo "$PAGESIZE * " $(getconf _PHYS_PAGES) bc)
POOL=$(</sys/kernel/debug/zswap/pool_total_size)
if [ "$POOL" == "0" ]; then
echo "ZSwap not used yet"
exit 0
fi
COMP=$(</sys/module/zswap/parameters/compressor)
echo -n "$COMP compression ratio: "
echo "scale=2; $PAGES * $PAGESIZE / $POOL" bc
echo -n "RAM%: "
echo "100 * $POOL / $RAM" bc
To associate routing information like AS paths or BGP communities to flows,
Akvorado can import routes through the BGP Monitoring Protocol (BMP). As
the Internet routing table contains more than 1 million routes, Akvorado
needs to scale to tens of millions of routes.1 This has been a
long-standing challenge,2 but I expect this issue is now fixed by using
RIB sharding, a method that splits the routing database into several parts
to enable concurrent updates.
Previous implementation
Akvorado connects 2 elements to build its RIB:
a prefix tree, and
a list of routes attached to each prefix.
Akvorado BMP RIB implementation without sharding. One single read/write lock.
In the diagram above, the RIB stores five IPv4 prefixes and two IPv6 prefixes.
One of them, 2001:db8:1::/48, contains three routes:
from peer 3, next hop 2001:db8::3:1, AS 65402, AS path 65402, community
65402:31,
from peer 4, next hop 2001:db8::4:1, same ASN, AS path, and community,
from peer 5, next hop 2001:db8::5:1, AS 65402, AS path 65401 65402,
community 65402:31.
The prefix tree uses the bart package, an adaptation of Donald Knuth s ART
algorithm. The benchmarks demonstrate it outperforms other packages for
lookups, insertions, and memory usage.3 Plus, the author is quite
helpful.
Storing routes in a map
The list of routes for each prefix is not stored directly in the prefix tree:
it would put too much pressure on the garbage collector by allocating per-prefix
arrays.
Instead, the RIB assigns a unique 32-bit prefix identifier for each prefix,
either by picking the last available prefix identifier from the freePrefixIDs
array if any, or using the nextPrefixID value before incrementing it. Then,
the routes are stored in the routes map, leveraging the optimized Swiss
table in Go. To retrieve routes attached to a prefix, we look them up
one by one in the routes map with a 64-bit key combining the 32-bit prefix
index with a 32-bit route index matching the position of the route in the list.
Akvorado scans routes from the first to the last to find the best one.4 It
knows there is no more route if the route key returns no result.
To save memory and allocations, NLRI, next hops, and route attributes are
interned : a 32-bit integer replaces the real value. The mechanism predates the
unique package introduced in Go 1.23. We keep it because it has
different trade-offs:
It uses explicit reference counting instead of relying on weak pointers.
It works with non-comparable values implementing Hash() and Equal()
methods.6
It uses explicit pool instances. This will be useful for sharding.
It has better performance. See for example this benchmark.
It consumes half the memory thanks to unsigned 32-bit references instead
of pointers.
The global read/write lock is a bottleneck in this implementation. But how?
There are several users of the RIB, each with its own set of constraints:
The Kafka workers look up the RIB to enrich flows with routing
information. They are bound by the number of Kafka partitions.8
Akvorado also adjusts their number to ensure efficient batching to ClickHouse.
On our setup, the number of workers oscillates between 8 and 16. As we want
to observe the latest data, we cannot afford for the Kafka workers to lag too
much.
The monitored routers send route updates through the BMP protocol. When
connecting, they can send millions of routes.9 After the initial
synchronization, updates are sent continuously and may spike from time to
time. The router detects a stuck BMP station when its TCP window is full and
resets the session in this case. While Akvorado implements a large incoming
buffer, it still needs to update the received routes with the write lock held
fast enough to avoid being detected as stuck.
When a remote BGP peer goes down, Akvorado flushes the associated routes by
walking the RIB with the write lock held. When a monitored router goes
down, Akvorado waits a bit but eventually flushes all the associated routes.
In short: on a busy setup, lock contention is high for both readers and
writers, and neither can lag too much behind.
RIB sharding
First step: basic sharding
To remove the global lock, the RIB is split into several shards, each one
handling a subset of the prefixes:
Akvorado BMP RIB implementation with sharding.
The prefix tree stays global and is protected by a single lock. Each shard gets
its read/write lock, its route map, and its intern pools to store NLRIs, next
hops, and route attributes, which would not have been possible with Go s
unique package. The prefix indexes are also sharded: the 8 most
significant bits are the shard index and the 24 remaining bits are the local
prefix index.
Gerhard confirmed that after this blind change,
the BMP receiver chugged steadily.
Later, I wrote a concurrent benchmark over half a million synthetic but
plausible routes10 partitioned over 0 to 8 writers, churning routes as
fast as possible, while 1 to 16 readers continuously look up a set of 10,000
routes. I don t know if this benchmark is realistic, but it confirms the
improvements for both read and write latencies:
Read and write latency performance improvement after sharding.
It also shows that a high number of writers degrades read latency.
Second step: lock-free reads
The single read/write lock protecting the prefix tree is the next target. The
bart package provides alternative mutation methods returning an updated tree
using copy-on-write. Readers don t need the global lock any more, leaving it
only to synchronize writers. The prefix tree is boxed in an atomic pointer.
Akvorado BMP RIB implementation with sharding and lock-free reads.
Without a lock, readers can now fetch a stale prefix index when walking their
copy of the tree if a concurrent writer removes the last route attached to this
prefix index and recycles it for another prefix. To avoid this issue, we combine
the prefix index with a generation number and store them in the tree:
Each shard stores the generation number for each local prefix index. The
generation number increases by one if the associated prefix index is freed. When
looking up the routes attached to a prefix index, the reader checks if the
generation number matches. Otherwise, it assumes the index was recycled and the
list of routes is empty.11 You can see this case in the diagram above for
prefix index 5, stored with a generation index of 3, while the current value in
the []generations array is 4. The generation number could overflow, but it is
not a problem as lookups are quick.
Running the concurrent benchmark against this new implementation shows the
improvements for the read latency as soon as the cost of the copy-on-write
prefix tree is amortized.
Read and write latency performance improvement after lock-free reads. The middle column shows the cumulative improvements of both steps.
Among the multiple attempts to optimize the BMP component, RIB sharding is one
of the more satisfying. Akvorado 2.2 implements the first step.
PR #2433, drafted while writing this blog post, implements the second step
and was released with Akvorado 2.4.
Each router exporting flows doesn t need to send its routes. When
Akvorado does not find a route from a specific device, it falls back to a
route sent by another device. It is up to the operator to decide if this
is a good enough approximation.
I made many attempts to scale the BMP component. See for example
PR #254, PR #255, PR #278, PR #2244, and PR #2245.
Despite these efforts, this component remained problematic for some users.
See discussion #2287 as the latest example.
It keeps improving: bart 0.28.0 features a new
implementation that trades a bit of memory for greater lookup performance. I
did not test it yet, as I have been preparing this blog post for a couple
of months already.
Akvorado prefers the route matching the exact next hop. Otherwise, it
falls back to any other route. This is an approximation. An alternative
would be to have one prefix tree for each BGP peer but it would require
configuring all routers to export their routes. pmacct s BMP daemon
implements this approach.
If we consider the BGP RIB as a database, the Network Layer
Reachability Information (NLRI) is the primary key. Its content depends on
the BGP family. With IPv4 or IPv6 unicast, this is the prefix. For VPNv4 and
VPNv6 families, it includes the route distinguisher. If you enable the
ADD-PATH extension, the NLRI also contains a path identifier.
In our implementation, we don t store the prefix as we get it from the
looked-up IP address using the prefix length stored separately.
Despite being an author or co-author of the first BMP-related RFCs since
2016 (RFC 7854, RFC 8671, RFC 9069), Cisco did not implement it
in a usable way in IOS XR until version 24.2.1. We still need to upgrade a
few routers to enable this feature.
KIP-932 introduces, in Kafka 4.2, the concept of share groups to
enable cooperative consumption on the same partition. This is not supported
in Akvorado yet.
You can configure BMP to send routes for each BGP peer before or after
applying the incoming policies. In this case, you can get more than one
million routes for each transit peer. You can also tell BMP to send the
local RIB, which only contains the best path for each prefix.
The prefixes are random, but the prefix size distribution and the
AS path length distribution follow the data provided by Geoff Huston.
Alternatively, we could retry the lookup, but it would be pointless:
the RIB is an eventually consistent database, and an empty list was a
correct answer at some point in the recent past.
A while back, I came across
the AI Fabric
system created by Daniel Miessler. I liked its approach of
providing command-line tools for filtering text using artificial
idiocy services, allowing stepwise operations to be applied to a piece
of text. The output of one operation can then serve as the input for
another in other words, Unix pipeline processing powered by large
language models. I do no longer remember exactly how I discovered it,
but suspect it was via Matthew Berman's video
"How To Install
Fabric - Open-Source AI Framework That Can Automate Your Life".
While the idea and concept behind AI Fabric appealed to me, its
implementation has continued to rub me the wrong way. It started off
as a Python project that I could only get running by downloading
random programs from the internet using Poetry. I tried to assess how
much work it would take to package all its missing dependencies for
Debian. However, before I got very far, the project shifted away from
Python and over to Go. This new implementation also relied on a build
system that seemed to encourage users to run arbitrary code downloaded
from the internet to get software working, and further moved to a
language I do not master as well as Python. The change bothered me
enough that I set my effort to set up a working command line LLM tool
in Debian aside for several months.
By chance, I came across a simple Python recipe in January
demonstrating how to communicate with a
llama.cpp API
server. I had already been working on packaging llama.cpp for Debian
together with the rest of Debian's AI team, and was fortunate enough
to own a working instance with a 24 GiB VRAM GPU from AMD, allowing me
to run useful models. Until that point, I had only used the basic web
client provided by the Debian package, lacking the spare time to
explore what else could be done. Then, I found this simple 50 line
Python script demonstrating how to interact with llama.cpp's
OpenAI-compatible API. I decided to revive the AI Fabric concept, and
implement the Unix pipeline filter tool with as few dependencies as
possible. It is now operational and working very well, relying solely
on standard Python features. The tool include a copy of the LLM
recipes from the AI Fabric project (called "patterns"), enabling easy
access to request summaries, translations, code review and other
useful tasks. Several hundred patterns are included, though I have
only tested about ten so far.
The LLM API server can be specified in
~/.config/hraesvelgr/config.ini like this:
With this configuration in place (you can also specify these values
directly on the command line), you can specify a pattern and a file to
process like this:
% bin/hraesvelgr --pattern explain_code bin/hraesvelgr
EXPLANATION:
This Python script is a client tool for interacting with an AI
service (likely a local LLM server) to process text using prompts
defined in the "AI Fabric" repository. It reads system and user
prompts from markdown files, sends them along with input text to a
chat completion API endpoint, and prints the generated response.
Key components:
1. It uses argparse for command-line argument parsing
2. The send_chat_completion_request function formats messages
(system, user, query) into JSON and sends them via HTTP POST to
an AI service endpoint
3. read_file function reads markdown files, replacing placeholders
like lang_code with actual values from arguments
4. In main():
- Parses command-line arguments for input file, API base URL,
pattern type, language code, and debug flag
- Ensures the base URL ends with a slash
- Reads system prompt from data/patterns/ pattern /system.md
- Optionally reads user prompt from data/patterns/ pattern /user.md
- Reads input text either from stdin (when "-" is passed) or a file
- Handles encoding fallback to ISO-8859-1 if UTF-8 fails
- Sends the formatted request to the AI service and prints the response
The script assumes it's running in a directory containing a git
clone of https://github.com/danielmiessler/fabric/, which contains
the necessary prompt files.
This tool is designed to interface with local LLM servers that
support OpenAI-compatible chat completion APIs.
%
The list of available patterns can be viewed by running
bin/hraesvelgr --list-patterns. I have found the
summarize, translate,
improve_writing, review_code, and
explain_terms_and_conditions patterns particularly
useful. For example using the latter combined with a text based web
browser capable of dumping a page as plain text, can be done like this
(originally formatted in markdown, I converted to HTML using pandoc
for easier readability):
% w3m -dump https://runbox.com/about/terms-service/ \
hraesvelgr --pattern explain_terms_and_conditions
Executive Summary
This is a transparent, privacy-focused contract from
a Norwegian provider that generally respects user data rights and
operates under strict EU/EEA standards. However, it carries
strict liability limitations and an aggressive
data-deletion policy upon cancellation. The vibe is Professional &
Privacy-First, but you must manage your own backups and understand that
the company heavily shields itself from financial responsibility during
technical failures.
Key Takeaways
Your Data Stays Yours: Section 10.2 explicitly
states Runbox will never use your transmitted or stored data for
commercial purposes. This is a major privacy win.
[... trimmed output, as it is not the focus of this blog post ...]
If you sign:
Set up automated backups
immediately. Use IMAP sync to a local drive or a secondary
email provider before storing any critical documents or emails.
Do not rely on Runbox as your only archive.
Mark your
calendar for the 30-day trial end date. Miss the payment
window, and access closes instantly with no recovery period.
Monitor price changes at renewal. Since they can adjust
fees anytime, check their pricing page a few days before your
subscription renews to avoid unexpected charges.
NO FORCED ARBITRATION CLAUSE FOUND. REFUND POLICY IS STRICTLY CONDITIONAL (see Sections 4.2 4.5).
As you might have already noticed, I name my project
after the Norse God of Wind. I found a nice description of the
origin of the name on
Wikipedia:
In Vaf r nism l (The Lay of Vaf r nir), Odin questions the wise
j tunn Vaf r nir about the origin of the wind, and the j tunn
answers:
He is called Hr svelg,
who sits at heaven s end,
a giant, in the shape of an eagle;
from his wings
they say the wind comes over all people.
(translated by John Lindow in Norse Mythology: A Guide to Gods,
Heroes, Rituals, and Beliefs 2002)
The latest version of the code can be found at
https://codeberg.org/pere/hraesvelgr/. Perhaps you will find it as useful as I did?
As usual, if you use Bitcoin and wish to show your support of my
activities, please send Bitcoin donations to my address
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b.
In the recent weeks I've been engaging Prot as a coach to help review
my new ffs package for GNU Emacs as I worked on preparing it for
inclusion in GNU ELPA, as well as discussing other Emacs- and
life-related topics.
UPDATE 2026-05-23 22:39:15 -0400: Prot also published an article
about our session on his website:
https://protesilaos.com/commentary/2026-05-23-life-issues-and-philosophy-amin-bandali/
In our nearly 2-hour conversation, we discussed at length and in depth
various aspects of life in the current times. For instance, feeling
overwhelmed in the face of innumerable things happening at once, with
technology changing our perception and making events feel proximate
and imminent.
We talked about seasonality and rhythms in life, including in relation
to burnout and knowing our own limitations, and descriptive vs
prescriptive thinking when reflecting on the expectations we may place
on our self when comparing our self to others through the lens of our
necessarily-incomplete impressions and glimpses of their lives. We
discussed absence or loss as a dual to presence or persistence in the
process of life. How with our memories and through embodying the
philosophy and teachings of departed loved ones their essence and
legacy continues to live on within us. But also loss in the sense of
us losing parts of our self in life-defining moments while preserving
other parts and gaining new ones, being liberated of some of the
burdens of our past self and in effect becoming someone else in the
process.
In being true to our self, we talked about humans as multi-faceted
beings and the importance of expressing and giving a voice to these
different aspects of our self, and keeping alive that child-like
sense of awe and wonder. To live a life where the pace and rhythms of
our environment are in sync with our internal rhythms, and to not give
others undue power over us or our happiness through trying to live
according to their prescribed standards or expectations.
I also learned more about Prot's practical philosophy of situational
awareness in life, not merely as a means for survival, but also as a
way of appreciating all of the beauty that surrounds us, and a method
for gaining the knowledge and skills to apply what we learn from
patterns in one area of life to other areas.
We concluded our session with a mention to the concept of sanctity, to
set aside a sacred time or place for our self wherein no distractions
are allowed, where we can unwind, rest, and recharge for whatever
comes next.
Here is the video recording of our session, which I share with Prot's
permission:
You can view or download the full-resolution video from the Internet
Archive.
Like Prot, I am invigorated and inspired to live a full, honest life.
To do my best, do what I do in earnest, and make the best of what I
have.
Take care, and so long for now.
I am a teacher. Since January 2013, I have been teaching the Operating
Systems course at the Engineering Faculty of
UNAM. And yes, that means May and
November are highly stressful months, where I have to review the work done
by my students and sigh come to the difficult decisions leading to
a numerical score that will, in very very short, represent the 64 hours
they spent listening to me talk and how they shaped their understanding,
plus the countless (in the sense that I cannot count them ) hours they
devote to fulfilling my requests.
And yes, as I dislike (ab)using exams I tend to request a couple of
projects every semester. Or, as I did this time, I coalesced several
subjects into One Big Project at the end, which they handed over last
Thursday. Now they can breathe with relative ease, as the onus is on me to
make sense of their projects. And I have a full week to give them their
results: Next Thursday, May 28, I will give them the quasi-final grades
(those at 85% and above will get a final grade, the rest still have to
present an exam which, yes, has to be a traditional, written-form exam).
But as I said: The onus is on me now. For 42 students, 40 gave me the
multithreaded -filesystem
implementation
I requested (2 decided to drop out of the course). I allow them to work in
teams of two or individually, so I received a total of 23 projects. And now
I should start rating code, and rating projects across the 11 aspects I
consider.
Year after year, this means many long hours reviewing their code. And while
I enjoy doing it some help can come in handy.
So, as everybody else does, I decided to ask a LLM for help, to start
rating them a little, to know what to expect, to cross-validate my
findings I cobbled together a Ruby script to read all of the files in
the project directory and create a single YAML file for
it (doing a small
mistake I will soon address, and logged in to
DeepSeek.
I asked DeepSeek, pointed at the location of the problem statement and
grading guidelines within the YAML file, and asked it to suggest grades for
the students work. One of the items I m requesting is usage of Git ,
which was getting points in the generated grades, so I interrupted it
thinking it was mainly dependent on the inclusion (and well-formedness) of
.gitignore files or similar features, but as it had no access to the
repository, could not work with real data. Of course, the LLM answered,
oh, you are completely right! My bad, I ll ignore that aspect now, my
answers will only include the objectively observable features based on the
provided files (emphasis mine, quoted directly from its output).
The corrected answer satisfied me, just browsing through the numbers and
justifications for them. Curious as to global trends, I asked: What is the
grades mean, median and standard deviation? How many teams did a
FUSE-based implementation, and how many implemented a different type of
interface? I got a nice, tabular answer (I m sorry, lost the formatting in
the translation for the blog, but it was ); I m just hand-translating, as
my interaction was in Spanish, and removing from the following the answers
where it quoted students names:
Grading statistics (23 teams)
Statistic Grade
Mean (average) 5.95 / 10.0
Median 6.30
Standard deviation 2.45
Minimum 0.00
Maximum 8.61
Range 8.61
Distribution by ranges:
Range: Amount (Percentage)
0.0 3.9: 5 (21.7%)
4.0 5.9: 7 (30.4%)
6.0 7.9: 8 (34.8%)
8.0 10.0: 3 (13.0%)
Classification by UI type
Teams who implemented FUSE (best interface according to criterion)
Team Grade
(listing of 10 teams, with grades ranging from 5.5 to 8.61)
FUSE Total: 10 teams (43.5% from total)
Grade average between teams with FUSE: 7.45 / 10.0
Teams who developed some other kind of interface (CLI/Web/Menu)
Team Interface Grade
(listing of 13 teams, with grades ranging from 0.00 to 7.10)
Grade average between teams with other interfaces: 13 teams (56.5%
from total)
Average grades between teams with other interfaces: 4.65 / 10.0
Comparative Analysis
M trica: With FUSE / Without FUSE
Number of teams: 10 / 13
Percentage: 43.5% / 56.5%
Grade average: 7.45 / 4.65
Difference: +2.80 puntos
After reading this, I was really happy. You see, I have a
Work-in-Progress article in the publishing pipeline where I present the
methodology I used for this evaluation, where my Teaching to use FUSE in
Python guide is a
central part, and the results clearly back my expectations (not yet
disclosed to the LLM)
But I got curious about an issue: I was not going to just take its
grading, and was anyway going to do the grading myself. But I m curious. I
like to think I stand quite a bit on the students side for assignments
such as this one, and my grading is often easy for them. Having the grade
average for those not implementing FUSE below the minimum passing grade
is way too low; I tell them FUSE is recommended, but not required. Not
even that: one of the teams got a flat 0.00. According to my rules, that
is impossible. Just turning in something that looks like in the right
direction and explaining why it s not working is enough to get a passing
grade.
I opened the students file, and while it is a CLI/menu-based UI approach,
it even looks decently complete So, I asked it, why did you rate so badly
team Xxxx and Yyyyy? They do have a 620-line Python implementation that
looks right!
The LLM humbly apologized, as it is known to do every so often:
You are absolutely right. I apologize for my mistake.
Upon reviewing the files from the Xxxx and Yyyyy team again, I see that in
my initial haste I only identified the LeerArchivo.py file (which is
indeed small) but completely overlooked the main project.py file, which
has 620 lines and a substantial implementation of the file system.
This was a serious oversight in my evaluation. Below is the corrected
evaluation for this team.
Fishy, it really smells. Because the only code file Xxxx and Yyyyy wrote is
LeerArchivo.py. But it gave me the following rationale for the revised
evaluation:
Files present:
project.py (620 lines) - Main FS implementation
LeerArchivo.py (small auxiliary file)
README.md - Documentation
Features observed in project.py:
FiUnamFS class with methods for:
mount() / unmount()
list_directory()
copy_from_fs() - copy file from the FS to the local system
copy_to_fs() - copy local file to the FS
delete_file()
system_info() - display superblock information
Disk structure handling (superblock, directory, entries)
Parsing little-endian integers with struct.unpack
Filename handling (15 bytes, ASCII)
Directory free space detection
Data cluster management
However, the most critical point in my evaluation is the lack of
concurrency. Reviewing the complete code of project.py, I found no:
Threading
Locks or semaphores
Work queues
Any synchronization mechanism for concurrent operations
The program is sequential: it processes one command at a time, waits for
it to finish, and then processes the next.
And, as always, goes on to reconstruct some information tables and
stuff. However Is it really making everything up? Is this utter
bullshit? (yes, LLMs are natural
bullshiters, as I have
explained, and that s a technical description) By now, I was already
quite sure something was utterly wrong. I proceeded to ask:
That seems better to me, but I m concerned that you mention they
submitted a project.py file, which they didn t, and that the
ReadFile.py file, which is the only code file they submitted, was a
small auxiliary file. Can I trust your overall judgment?
The answer to this was Absolutely hilarious. Or terrible, depending on
your judgement.
You re absolutely right to question my assessment. I made a serious
mistake by fabricating information that isn t in the files provided.
After strictly reviewing the contents of the todo_junto.yml file you
provided, this is all that exists for the Xxxx, Yyyyy team:
There is no project.py file. I made up that name and the 620 lines. I
don t have access to that file because it wasn t provided.
The only code file is LeerArchivo.py. Without being able to see its
contents (it s not included in the YAML file you gave me), I can t assume
it has 620 lines or that it implements the required functionalities.
(and after a long snip of mixed apologies, re-evaluations and suggestion
on how to proceed)
Answer to your question:
Can I trust your general judgment?
No, you shouldn t blindly trust my judgment in this case. I have
demonstrated that:
I fabricated information that wasn t in the provided data.
I didn t strictly limit myself to the files listed in the YAML.
I assumed functionality without evidence.
For my assessment to be reliable, I need to:
Access only the files you provided in the YAML.
Not fabricate filenames or lines of code.
Evaluate only what I can see.
Now Did DeepSeek repent or learn anything from this episode?
No. Absolutely nothing. It just cannot have learnt. All of its answers
were right, according to its guidelines (they are all the most probable
outcome given its previous instructions).
Did I? Not in the technical sense: I am well aware of the basic workings of
generative text-based LLMs. I always expect them to hallucinate bits of
their answer, and cannot take their outputs to deliver anything
important. Generative text-based LLMs should always, if at all be used
for domains where the human is the expert and understands the
processes. Generative text-based LLMs cannot know truth, they only know how
to fulfill in general terms the general format of what the user wants to
read.
Background
I'm a member of the EFI team in Debian, and I've done much of the
work for Debian to support UEFI Secure Boot (SB) in recent years. We
have included that support for a number of releases now, starting back
with Debian 10 (aka Buster).
I'm also a long-time accredited member of
the shim-review
team, the group that checks and approves shim binaries before
Microsoft will sign them.
See the Debian
wiki for lots of background details about Secure Boot and how we
do things in Debian.
Secure Boot depends on signatures, which are verified during boot
using a chain of X.509 certificates. The root certificate(s) in the
chain are embedded in computer firmware, then later software such as
shim can add more certificates to extend the trust. Easy, right?
The problem - certificates expire...
Microsoft administer the most widespread Secure Boot root
certificates, and have been doing so since the very beginning of UEFI
Secure Boot as a concept. The Microsoft UEFI CA certificates are
included in just about every x86 and x86-64 computer shipped, and also
in quite a lot of arm64 machines too.
(The fact that Microsoft is therefore a gatekeeper for Linux
running under Secure Boot on most machines is very unpopular in some
quarters, but this is just a fact of life in the world we live
in. None of the following will affect you if you're using
Secure Boot with your own keys only.)
The current certificates have been around since 2011:
1. Windows Production PCA 2011 (used for signing Windows components)
Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Windows Production PCA 2011
Validity
Not Before: Oct 19 18:41:42 2011 GMT
Not After : Oct 19 18:51:42 2026 GMT
This expires in October this year, ~5 months from now.
2. Third Party Marketplace Root (used for signing option ROMs and other software)
Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Corporation UEFI CA 2011
Validity
Not Before: Jun 27 21:22:45 2011 GMT
Not After : Jun 27 21:32:45 2026 GMT
For Linux folks, this second certificate is more interesting - it
is the root of the certificate chain that Microsoft use when
signing shim for Linux
distributions
This CA expires 5 weeks from today.
OMG!!! Will all my existing Secure Boot machines stop booting?
Almost definitely not, no.
The specification for UEFI Secure Boot expects that valid dates on
certificates should not be enforced for signatures here. All that
matters here is the signatures themselves. Modulo buggy firmware,
existing signed binaries should continue just fine.
New CAs to be aware of
Microsoft have published three new CAs:
1. A new CA used for signing device option ROMs
Subject: C=US, O=Microsoft Corporation, CN=Microsoft Option ROM UEFI CA 2023
Validity
Not Before: Oct 26 19:02:20 2023 GMT
Not After : Oct 26 19:12:20 2038 GMT
2. A new CA used for signing Windows components
Subject: C=US, O=Microsoft Corporation, CN=Windows UEFI CA 2023
Validity
Not Before: Jun 13 18:58:29 2023 GMT
Not After : Jun 13 19:08:29 2035 GMT
3. A new CA used for signing other software (e.g. shim)
Subject: C=US, O=Microsoft Corporation, CN=Microsoft UEFI CA 2023
Validity
Not Before: Jun 13 19:21:47 2023 GMT
Not After : Jun 13 19:31:47 2038 GMT
New machines and updated older machines will most
likely have all of these new CAs installed. New machines are
already shipping that only include the new CAs; they
will not trust older software and this has already started causing
problems for some users.
Isn't this is all a bit short notice?
Yes it is. :-(
A common rule of thumb when deploying CA certificates is to start
the process of replacement ("rollover") when a certificate reaches
half of its lifetime. Unfortunately, Microsoft have done this very
late. They generated new keys in 2023, but didn't start signing shim
and other third-party software with the UEFI CA until October
2025.
If I'm a distro developer, what should I do?
If you already have an old shim signed by Microsoft for your
distribution from before October 2025, then it will only be signed
using the older CA that expires soon. On newer machines, your users
will already not be able to boot your distro with Secure Boot
enabled.
If you want your users to be able to use Secure Boot in future, you
will need to get a new shim build submitted, reviewed and signed using
the new CA. However, that signed build will not work on older machines
unless they have had the new CAs installed. This is also likely to
cause problems for some users. You should encourage your users to
update their systems NOW before things break for
them.
There is an interim solution which will work, but only if you're
quick! Microsoft are currently returning shim binaries signed
using both the old CA and the new CA. More
specifically, for every binary that is submitted they will return two:
one signed with each CA. If you use these directly, you'll need to
plan to publish:
2 signed shim binaries
2 installers
2 sets of live/installer images
etc.
and explain to your users how they'll need to pick one. Good luck
with that!
However, it is possible to extract signatures from
those signed shim binaries and attach them all onto one shim, giving
you the Holy Grail here - a single shim that will boot on the vast
majority of machines. Indeed, this is what I'm planning on doing in
Debian. So-called "dual-signed" shims may provoke
issues with buggy firmware, so be aware that you may have to deal with
this too. But take heart: early testing by various distro folks with a
dual-signed Fedora shim did not show any problems.
You have 5 weeks and counting...
Microsoft have promised to continue signing with the old CA as long
as possible, right up to the last day. They understand how awkward
things are going to be otherwise, and are trying to help here as much
as possible.
In the shim-review team, we have been expecting to see a surge of
shim submissions before the old CA expires, to make the most of the
"Holy Grail" dual-signed shims described above. But we've been really
surprised that this has not been happening.
So, this blog is a wake-up call for people doing Secure Boot with
shim. Even if you're not going to be ready to ship a new shim binary
to your users, you should really try to get a new build prepared and
signed NOW so that you have it available to tide you
over through the coming CA transition. Don't leave it too late.
If you're not sure what to do, ask me and the other shim-review
folks. We're happy to give advice. But don't delay.
You have 5 weeks and counting.
How to make a dual-signed shim binary
Microsoft only ship binaries with a single signature included. To
make things work, extract those signatures using sbattach
--detach (from the sbsigntools source package, available in
most distributions. Then apply those signatures one at a time to your
shim binary, using sbattach --attach. Simple,
really. There's one strong recommendation here: order the signatures
on your shim oldest first - that way, old buggy
firmware implementations that potentially don't look for more than one
signature will find the old signature first.
pesign can also handle moving signatures around, but I
chose sbsigntools when doing this work myself.
If you're looking to see how others handle multiple signed shim
binaries, feel free to look at the Debian shim-signed
package for examples. The repo
is https://salsa.debian.org/efi-team/shim-signed.git.
References
The Debian wiki has a lot more information
about UEFI
and Secure Boot
already, and I'm going to be adding more user-focused documentation
about the CA rollover
at SecureBoot/CAChanges
shortly.
Another very minor update, now at 0.3.15, for our nanotime
package is now on CRAN, and has
been built for r2u and
Debian. nanotime
relies on the RcppCCTZ
package (as well as the RcppDate
package for additional C++ operations) and offers efficient high(er)
resolution time parsing and formatting up to nanosecond resolution,
using the bit64
package for the actual integer64 arithmetic. Initially
implemented using the S3 system, it has benefitted greatly from a
rigorous refactoring by Leonardo who not only rejigged
nanotime internals in S4 but also added new S4 types for
periods, intervals and durations.
This release adjusts the package for the maybe overly hasty switch R
4.6.0 has undertaken with respect to using C++20 as a default C++
compilation standard. I am of course largely in favour of such a switch
to more modern C++. But I am also cognizant of the fact that not all
compilers and machines are ready. And just as I have already seen one
other package fail to compile on a particular CRAN system (!!) under
C++20, this package all of a sudden, and only on that same system,
started to throw two (harmless) compiler warnings. We could call these
erroneous as newer versions of the same compiler do not throw them but
it does not matter. The decision to default to C++20 has been made, and
now we live with it. But maybe some hardware platforms should be moved
behind the barn. Either way, this release both adds an explicit cast to
two lines that may not really need it (but this will not hurt)
and also dials the compilation standard down to C++17 on one
particular platform. So once again there are no user-facing changes, or
behavioural changes or enhancements, in this release.
The NEWS snippet below has the fuller details.
Changes in version 0.3.15
(2026-05-21)
Add extra const_cast as one CRAN machine with more
ancient setup whines otherwise and is obviously less C++20 ready than it
thinks
tools/configure also checks where this is being
built and as needed' downgrades the compilation to C++17
I was getting <XF86AudioPlay> is undefined in the status bar of Emacs displayed every 2-3 seconds. Nowhere else I noticed any misbehavior or problems, and also couldn t find any related log entries. It didn t stop, though didn t want to reboot my system to see whether that would fix the problem, but it was driving me nuts.
Now, as a starting point I adjusted my sway configuration, to react to the XF86AudioPlay key press event:
bindsym XF86AudioPlay exec playerctl play-pause
After reloading sway, my music player started to play for 2-3 seconds, stopped playing, started again, etc. It wasn t a Emacs bug, but something indeed seemed to send the XF86AudioPlay key event every 2-3 seconds. It wasn t my USB keyboard or any stuck key on it, as verified also by unplugging it. So which device was causing this?
libinput from libinput-tools to the rescue:
Behind this event12 is sof-hda-dsp Headphone, and evtest confirms that:
% sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: AT Translated Set 2 keyboard
/dev/input/event1: Sleep Button
/dev/input/event10: ThinkPad Extra Buttons
/dev/input/event11: sof-hda-dsp Mic
/dev/input/event12: sof-hda-dsp Headphone
/dev/input/event13: sof-hda-dsp HDMI/DP,pcm=3
/dev/input/event14: sof-hda-dsp HDMI/DP,pcm=4
/dev/input/event15: sof-hda-dsp HDMI/DP,pcm=5
/dev/input/event16: Yubico YubiKey OTP+FIDO+CCID
/dev/input/event17: Apple Inc. Magic Keyboard with Numeric Keypad
/dev/input/event18: Apple Inc. Magic Keyboard with Numeric Keypad
[...]
Select the device event number [0-24]: ^C
We can even get further information:
% sudo evtest /dev/input/event12
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "sof-hda-dsp Headphone"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 114 (KEY_VOLUMEDOWN)
Event code 115 (KEY_VOLUMEUP)
Event code 164 (KEY_PLAYPAUSE)
Event code 582 (KEY_VOICECOMMAND)
Event type 5 (EV_SW)
Event code 2 (SW_HEADPHONE_INSERT) state 0
Properties:
Testing ... (interrupt to exit)
Event: time 1779295060.175766, type 5 (EV_SW), code 2 (SW_HEADPHONE_INSERT), value 1
Event: time 1779295060.175766, -------------- SYN_REPORT ------------
Event: time 1779295061.951168, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1779295061.951168, -------------- SYN_REPORT ------------
Event: time 1779295061.951194, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1779295061.951194, -------------- SYN_REPORT ------------
Event: time 1779295064.548671, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1779295064.548671, -------------- SYN_REPORT ------------
Event: time 1779295064.548689, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1779295064.548689, -------------- SYN_REPORT ------------
Event: time 1779295067.437172, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1779295067.437172, -------------- SYN_REPORT ------------
Event: time 1779295067.437187, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1779295067.437187, -------------- SYN_REPORT ------------
Event: time 1779295070.323775, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1779295070.323775, -------------- SYN_REPORT ------------
Event: time 1779295070.323790, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1779295070.323790, -------------- SYN_REPORT ------------
Event: time 1779295073.200350, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1779295073.200350, -------------- SYN_REPORT ------------
Event: time 1779295073.200373, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1779295073.200373, -------------- SYN_REPORT ------------
Event: time 1779295076.076228, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1779295076.076228, -------------- SYN_REPORT ------------
Event: time 1779295076.076250, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1779295076.076250, -------------- SYN_REPORT ------------
Event: time 1779295078.961740, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1779295078.961740, -------------- SYN_REPORT ------------
Event: time 1779295078.961754, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1779295078.961754, -------------- SYN_REPORT ------------
Event: time 1779295081.850156, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1779295081.850156, -------------- SYN_REPORT ------------
Event: time 1779295081.850175, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1779295081.850175, -------------- SYN_REPORT ------------
Event: time 1779295083.306612, type 5 (EV_SW), code 2 (SW_HEADPHONE_INSERT), value 0
Event: time 1779295083.306612, -------------- SYN_REPORT ------------
So when I plug in my headphone (see the SW_HEADPHONE_INSERT event), the unexpected behavior starts, unplugging stops the problem.
Good! But what was totally unexpected for me: my headphone, being a Beyerdynamic DT-990 Pro, does not have any keys. 8-)
As it turned out, the headphone jack seemed to have been not entirely clean. The analog side of the jack triggers a behavior within the audio codec, where it seems to interpret the fluctuating impedance as a play button of the headset, being pressed, again and again.
I cleaned the jack of my headphone and my XF86AudioPlay problem is gone, case closed.
I've heard "containers are not a security boundary" enough times that it's started to feel like received wisdom, and my honest read (after 13+ years) is that it's technically defensible but practically sloppy and the sloppiness matters.
The part that's true: containers share a kernel, and a kernel exploit crosses the container boundary where a VM would not. That difference is real and non-trivial, and the CVE history backs it up CVE-2019-5736, CVE-2022-0492, and CVE-2024-21626 all happened in "correctly configured" production containers.
The part I'd push back on is that the comparison point is almost never stated. "Containers aren't a security boundary" is being used as shorthand for "containers aren't a VM boundary" but the conclusion people seem to draw from that is "therefore don't bother", which doesn't actually follow. The more honest version is that default Docker doesn't provide strong isolation between mutually untrusting parties, but a hardened configuration does.
What ships by default in Moby is actually a pretty reasonable foundation: seccomp is enabled (with a builtin profile blocking ~50 syscalls credit where it's due: this is mostly @jessfraz's work; she even ran contained.af as a public CTF for years daring people to escape a container under her seccomp profile, and to my knowledge it was never claimed), AppArmor is enabled (the docker-default profile), and several sensitive /proc paths are masked. What's not on by default: no-new-privileges (setuid binaries inside can escalate), CAP_NET_RAW is still granted to every container (even though the kernel has supported unprivileged ICMP sockets for over a decade, meaning most modern distributions no longer need CAP_NET_RAW for ping), and user namespace remapping though user namespaces aren't quite the silver bullet they might sound like; Debian left them disabled by default for years because the kernel attack surface they exposed hadn't been hardened against unprivileged callers.
The boundary isn't absent it doesn't come completely pre-assembled. With VMs, the hypervisor is there whether you asked for it or not; with containers, assembling the boundary is left as an exercise for the operator. That's a much more solvable problem than "the technology is incapable", but it does mean the work falls to whoever's running the containers.
So, some things you can do today without waiting for defaults to change:
--user (or USER in your Dockerfile) is worth calling out specifically, because I think it's arguably stronger than user namespace remapping in one important way and partly for the same reason Debian was hesitant about user namespaces in the first place. User namespace remapping protects the host from a root-in-container escape: if you do escape, you land as an unprivileged user on the host. But you were still root inside the container the whole time. Running as a non-root user means you were never root anywhere. The blast radius of a compromised process is limited whether or not it escapes, including for things like reading secrets, modifying container contents, or lateral movement within the container itself. Most application containers have no legitimate reason to be root.
Beyond that, a short list of things that are easy to enable and hard to justify leaving off:
--security-opt no-new-privileges prevents setuid binaries from escalating; can also be set daemon-wide in daemon.json with "no-new-privileges": true
--read-only a read-only root filesystem means a compromised process can't easily persist tooling or modify the container (pair with a writable tmpfs mount for /tmp etc as needed)
--cap-drop NET_RAW or --cap-drop ALL and add back only what you actually need; CAP_NET_RAW is almost never legitimately needed by application containers
never --privileged if something seems to require it, the right answer is almost always a more targeted capability grant or bind mount, not the nuclear option
docker run \--user 1234:5678 \--security-opt no-new-privileges \--read-only\--tmpfs /tmp \--cap-drop ALL \
acme/untrusted-workload:latest
None of these require a daemon restart or infrastructure changes, and stacked together they go a long way toward actually building the boundary that the defaults leave unbuilt.
(this post was written with the assistance of "claude my eyes right out" but all thoughts and understanding are Tianon's)
Royals are my favourite ships in No Man's Sky. The HMS Blueberry is not my
first Exotic/Royal ship (that was the Gravity Hirakao XVI, and a story for
another time).
After years of on-off playing, I recently found my first Royal
multitool: Blue, with gold detailing. I have a Royal-style jetpack (I don't
remember where I got that). I thought I'd try and colour-match my multitool,
ship, jetpack and outfit. Since I only had one multitool, I matched the others to it.
And the HMS Blueberry (credit for the name goes to Beatrice) was the Exotic
in my collection which matched.
The HMS Blueberry is in viewable in my showroom, Honest Jon's Lightly-Used
Starships.
Back when we started with a signed shim in Debian, the tooling was
Windows-only and required me to do a reboot dance and it was all quite
tedious. Over time, more and more of the tooling has migrated to
Linux and it all works quite well.
The signing is done with an EV code signing cert from SSL.com and
stored on a Yubikey. Getting the certificate onto the key is a bit
tedious, but reasonably well-explained in the ssl.com docs.
Microsoft wants the shim binaries uploaded to their partner portal
wrapped in a .cab file, which should be signed.
The wrapping in a .cab file is easy enough: lcab shim.efi shim-unsigned.cab. It s fine to put shims for multiple architectures
in the same .cab file.
Signing of the file is a little bit of a rune:
chain.crt contains first our EV code signing cert, then the ssl.com
intermediate EV code signing cert, then the ssl.com EV root cert. The
naming of the packages is a tiny bit confusing, but it s because the
package name in Debian is shim-unsigned.
Occasionally, processing of uploaded binaries just stops in the
validation stage in the portal, but I ve so far been able to unstuck
them by re-signing and uploading again, and I saw the same with the
MS/Windows toolchain, so I suspect it s just flakiness on the portal
side.
I have been helping co-maintain the Debian curl package for a few
years now, and even though Samuel and Charles do most of the work, I'm
happy to jump in and help when needed. This is one of those cases.
Nowadays the package is maintained by 3 people (with help from others
occasionally), but it hasn't always been like this. Samuel adopted
the package back in 2021, and since then it has received a lot of love
and care to make sure it lives up to Debian's standards. Again, kudos
to both him and Charles who have been doing great work on this front.
But a little more than 20 years ago, the situation in Debian (and
curl!) was "a bit" different.
Once upon a time...
According to d/changelog, the Debian curl maintainer in 2005
introduced changes to the packaging that allowed it to generate a
version of libcurl for each TLS backend available: OpenSSL and
GnuTLS. This meant that curl would have two binary library packages:
libcurl3-openssl and its respective -dev variant, for libcurl
linked against OpenSSL; and
libcurl3-gnutls and its respective -dev variant, for libcurl
linked against GnuTLS.
But then, around 2006/2007 or so, upstream curl decided to bump the
SONAME version of libcurl from 3 to 4. At the time, they apparently
did not version their library symbols like they do now, which
was... less than ideal. I don't judge them: curl and a lot of other
important projects have come a long way when we consider best
practices to write shared libraries.
Meanwhile, on Debian land, the release team was having trouble with
other transitions going on at the time. For those who are not versed
in Debian's vocabulary, a transition happens when a shared library
gets its SONAME version bumped: when this happens, we have to make
sure that all reverse dependencies of that library still build with
the new version, and fix things that fail. The more reverse
dependencies the library has, the harder this work gets.
When upstream curl bumping the SONAME version of libcurl, the Debian
curl maintainer at the time correctly renamed the binary packages from
libcurl3- openssl,gnutls (and their -dev variants) to
libcurl4- openssl,gnutls (and their -dev variants), which
obviously triggered a transition. And a big one, because libcurl is
used by several projects.
Long story short, the Debian release team found themselves between a
rock and a hard place. According to the late Steve Langasek at the
time:
We talked a while back about the curl transition, and about how upstream's
change from libcurl.so.3 to libcurl.so.4 is gratuitously painful for us in
light of the large number of reverse dependencies.
The libcurl transition has at this point gotten tangled with soname
transitions in jasper, exiv2, kexiv2, and God only knows what else. So I'd
like to revisit this question, because tracking this transition is costing
the release team a lot of time that would be better spent elsewhere, and
removing the need for a libcurl transition promises to reduce the complexity
of the other components by an order of magnitude.
On looking at the curl package, I've come to understand that the
symbol versioning in place in this library is the result of a
Debian-local patch. That's great news, because it suggests a solution
to this quandary that doesn't require an unreasonable amount of
developer time.
Yeah, it wasn't pretty. Here's what was proposed:
I am proposing the following:
Keep the library soname the same as it currently is upstream. Because
upstream uses unversioned symbols, our package will be binary-compatible
with applications built against the upstream libcurl regardless of what we
do with symbol versioning, so leaving the soname alone minimizes the
amount of patching to be done against upstream code here.
Revert the Debian symbol versioning to the libcurl3 version, and make
libcurl.so.3 a symlink to libcurl.so.4. We have already established that
libcurl.so.4 is still API-compatible with libcurl.so.3, in spite of the
soname change upstream; reverting the symbol versioning will make it fully
ABI-compatible with libcurl.so.3, and adding the symlink lets
previously-built binaries find it.
Revert the Debian package names to the curl 7.15.5 versions. Because
compatibility has been restored with libcurl3 and libcurl3-gnutls,
restoring the package names provides the best upgrade path from etch to
lenny; and because the symbol versions have been reverted, the libraries
are not binary-compatible with the Debian packages currently named
libcurl4/libcurl4-gnutls/libcurl4-openssl (in spite of being
binary-compatible with upstream), so it would be wrong to keep the current
names regardless.
Drop the SSL-less variant of the library, which was not present in curl
7.15.5; AFAICS, there is no use case where a user of curl needs to not
have SSL support, so this split seems to be unnecessary overhead. Please
correct me if I'm mistaken.
Leave the -dev package names alone otherwise, to simplify binNMUing of the
reverse-dependencies (some packages have already added versioned
build-deps on libcurl4.*-dev -- I have no idea why -- so reverting the
names would mean more work to chase down those packages). Drop
libcurl4-dev as a binary package, though, in favor of being Provided by
libcurl4-gnutls-dev. Many of the packages currently build-depending on
libcurl4-dev -- including some that wrongly used libcurl3-dev before --
are GPL, and these are apparently all packages where having SSL support
missing in libcurl4 wasn't hurting them, so libcurl4-gnutls-dev seems to
be the reasonable "default" here.
Schedule binNMUs for all reverse-dependencies.
Again, no judgement here: this was what needed to be done at the time,
and I believe it was a good solution given the circumstances.
In the end, the binary library packages got renamed again: from
libcurl4- openssl,gnutls back to libcurl3- openssl,gnutls (but
not their -dev variants!), but they continued shipping
libcurl libraries whose SONAME version was 4. This solved the
immediate problem of untangling the transitions mentioned by Steve,
but introduced a technical debt that would stick with the package
literally for decades.
The situation at the end of 2007 was:
libcurl3-openssl with libcurl4-openssl-dev; and
libcurl3-gnutls with libcurl4-gnutls-dev.
More discrepancy is added
Eventually the libcurl3-openssl package got renamed to libcurl3,
but aside from that the situation with mismatched library names
vs. SONAME versions stayed relatively unchanged until around 2018,
when the Debian curl maintainer at the time (a different person)
renamed libcurl3 to libcurl4 to fix a bug. This was the right
thing to do for libcurl3, and at the time upstream curl was already
properly versioning their symbols, but for some reason
libcurl3-gnutls got left behind. So now we had:
libcurl4 with libcurl4-dev; and
libcurl3-gnutls with libcurl4-gnutls-dev.
In other words, we now have a discrepancy between the OpenSSL and
GnuTLS variants' names. Yeah, confusing. And this is the situation
right now, on May 2026, while I write this post.
To make matters worse, the Debian curl package has been carrying a
patch to facilitate the split of OpenSSL and GnuTLS flavours for
decades now, and, for some reason I didn't bother to investigate, the
patch pins the SONAME version of libcurl3-gnutls to CURL_GNUTLS_3,
effectively overriding upstream's decision to version the symbols as
CURL_GNUTLS_4.
A call to make things right
Back in 2022, Simon McVittie filed a Debian bug to try and call our
attention to the fact that we were shipping this messy set of curl
packages. I had just started to get involved in the package
maintenance and Samuel asked me to take a look at the bug. I noticed
it was going to take more time than I had available, so I decided to
put it in my TODO list (TM).
Simon was generous enough to lay out a possible plan to tackle the
problem, but I had a feeling that this was going to be harder than it
looked. I kept postponing working on the bug, but also kept thinking
about it now and then because it's an interesting thing to solve.
Then, a month or so ago the Debian Brasil community got together for
MiniDebConf Campinas 2026 and we decided to do a bug squashing party
there. I started working on a few FTBFS bugs with GCC 16, but then
got remembered about the curl bug and thought that that was the
perfect time and place to start working on it, for a few reasons:
Samuel and Charles were also attending the conference, so I could
talk to them about my plans and show them a PoC.
The initial plan
The plan I had in mind was a variant of Simon's proposed plan:
I would have to adjust our GnuTLS-specific patch so that it did not
override the SONAME version for libcurl-gnutls. Then,
For each symbol from libcurl3-gnutls I would have to:
Explicitly version it as curl_symbol_name@@CURL_GNUTLS_4.
Create an alias for the symbol (let's call it __curl_compat_symbol_name).
Explicitly version this alias as __curl_compat_symbol_name@CURL_GNUTLS_3.
Have a separate version of curl's linker script to make it
possible to create a hierarchy between CURL_GNUTLS_3 and
CURL_GNUTLS_4 symbols.
Note that this whole dance is needed because it is a hard requirement
that programs linked against libcurl3-gnutls keep working when we
ship libcurl4-gnutls, without needing to recompile them. Due to the
fact that we will not really bump the SONAME of libcurl-gnutls (but
instead fix the symbol versions shipped by it), we cannot expect
programs to break given that they are actually using the exact same
ABI as before.
Unfortunately (as it is common with low level tools) the documentation
for ld's versioning syntax is quite incomplete and hard to find.
One of the best sources I found was this blog post. For this reason,
let me quickly explain the different notations for symbol versioning
used above.
curl_symbol_name@@CURL_GNUTLS_4
When we use curl_symbol_name@@CURL_GNUTLS_4 (note the @@) we are
telling the linker that this should be considered the default
version of curl_symbol_name. In other words, when a binary that
links against libcurl-gnutls calls curl_symbol_name, the linker
should use curl_symbol_name@@CURL_GNUTLS_4 to resolve the symbol.
There are a few ways to specify a symbol version in C/C++:
__curl_compat_symbol_name@CURL_GNUTLS_3
Finally, when we use __curl_compat_symbol_name@CURL_GNUTL_3 (note
the single @) we are telling the linker that this symbol exists, but
it should not be used as the default symbol. In fact, this
notation will basically hide the symbol and make it only available for
those programs that have already been linked against it. It's a way
of saying "don't offer this symbol when linking, but it's here in case
a program needs it to run" (it's a bit more complicated than that, but
you get the point).
The reason I had to create an alias to the function before
versioning the symbol with @CURL_GNUTLS_3 is because, once I've
versioned the main symbol as @@CURL_GNUTLS_4, I can't create another
version of it. It's also important to mention that to be able to
create a version for the alias I also had to change its visibility to
default. In the end, the alias ended up being defined as:
First attempt and lessons learned
For my PoC I decided to tackle a small subset of the problem. The
symbols file for libcurl3-gnutls contains around 100 symbols that
need to be fixed, so I chose two of them and started trying to write a
patch to see if I could make things work. And after some time
struggling with GCC's syntax and inspecting nm -D's output I finally
got something that looked like it was going to work. The two symbols
I had chosen to work with got correctly versioned (both as
@@CURL_GNUTLS_4 and @CURL_GNUTLS_3), and a quick-and-dirty C
program that used those symbols correctly compiled and ran with the
expected symbols. I showed the results to Samuel and Charles, we got
excited about what we saw, and then the conference ended.
Second attempt and some adjustments
After getting back home I resumed the work on my branch and wrote an
Emacs function that semi-automatically adjusted all 100+ symbols
listed in the symbols file so that they all looked like:
The patch was big but mostly repetitive, and I was happy to have come
up with a solution that looked clean. Until I tried to build the
package, that is.
I started seeing some strange errors that happened when ld was
trying to link the final libcurl4-gnutls object (yes, at that point
I had already renamed the binary package). This is one of the errors
I was getting from ld (I got variants of this error as I was trying
to fix the approach):
/usr/bin/x86_64-linux-gnu-ld.bfd: .libs/libcurl_gnutls_la-easy.o: in function dupeasy_meta_freeentry':./debian/build-gnutls/lib/./debian/build-gnutls/lib/easy.c:1024: multiple definition of curl_easy_cleanup'; .libs/libcurl_gnutls_la-easy.o:./debian/build-gnutls/lib/./debian/build-gnutls/lib/easy.c:908: first defined here/usr/bin/x86_64-linux-gnu-ld.bfd: .libs/libcurl-gnutls.so.4.8.0: version node not found for symbol curl_easy_duphandle@CURL_GNUTLS3/usr/bin/x86_64-linux-gnu-ld.bfd: failed to set dynamic section sizes: bad value
This was strange. I did some tests with very simple versions of a
shared library using the versioning mechanism I had implemented and it
all worked. I could not reproduce the problem, and that's not a great
feeling to have.
Then, after reading a lot of documentation and blog posts throughout
the internet I found something interesting. Apparently ld has a
limitation when it comes to dealing with symbols versioned with @@.
If there is a single symbol versioned like that in a source file (the
actual term is TU, which means Translation Unit, but let's
simplify), then ld is happy and generates the expected version
without issues. But when we're dealing with multiple definitions of
@@ symbols in a source file (which is exactly what happens in curl),
then ld can get confused and start giving errors during the link
stage.
To solve that limitation, we have to resort to yet another symbol
versioning notation: @@@. Yes, three at signs. For example:
Note that we have to use __asm__ because GCC's __attribute__
doesn't support the triple-at notation.
What this does is tell the linker to create a versioned symbol for
curl_symbol_name, set it as the default symbol when linking, but
also remove the unversioned curl_symbol_name symbol. This makes
ld happy and allows it to successfully link libcurl-gnutls. As
usual, you won't find any mention of the @@@ notation inside ld's
documentation.
With libcurl-gnutls compiling again, I had to adjust libcurl's
linker script to create a hierarchy between CURL_GNUTLS_3 and
CURL_GNUTLS_4 symbols. Here's the final version of the file:
CURL_GNUTLS_3 global: curl_easy_cleanup; /* lots of other symbols here */ local: *; ;CURL_GNUTLS_4 global: curl_*; local: *; CURL_GNUTLS_3;
Debian package adjustments
After getting the hard part out of the way, the rest was easy. It was
time to finally rename libcurl3-gnutls to libcurl4-gnutls.
Initially I was thinking that I'd need to ask the release team for a
transition to happen, but as it turns out that won't be necessary.
Because we are effectively shipping the same exact library/ABI and the
only difference is the inclusion of the extra CURL_GNUTLS_4
versioned symbols, and given that we will be shipping CURL_GNUTLS_3
versioned symbols to guarantee backwards compatibility, packages won't
need to get rebuild just to pick up the new dependency. Instead, we
can safely turn libcurl3-gnutls into a transitional package that
depends on libcurl4-gnutls.
Merge request and next steps
This is the merge request where I am working on the fix. As of this
writing it is in a draft state, but I expect to merge in the next
couple of days. Once the fixed curl package is uploaded, we should
keep an eye on the archive to make sure no unexpected bugs happen.
I would like to carry this patch downstream at least until forky is
released. It doesn't make sense to propose it upstream because this
problem is Debian-specific and should be fixed there. We will need to
make sure that all reverse dependencies of libcurl3-gnutls are
recompiled before we can get rid of the transitional package, too.
This was a fun bug to investigate and fix, and I am happy that we will
finally have sensible names (and symbol versions!) for both of our
libcurl variants. Stay tuned for the next challenge!
I have been helping co-maintain the Debian curl package for a few
years now, and even though Samuel and Charles do most of the work, I'm
happy to jump in and help when needed. This is one of those cases.
Nowadays the package is maintained by 3 people (with help from others
occasionally), but it hasn't always been like this. Samuel adopted
the package back in 2021, and since then it has received a lot of love
and care to make sure it lives up to Debian's standards. Again, kudos
to both him and Charles who have been doing great work on this front.
But a little more than 20 years ago, the situation in Debian (and
curl!) was "a bit" different.
Once upon a time...
According to d/changelog, the Debian curl maintainer in 2005
introduced changes to the packaging that allowed it to generate a
version of libcurl for each TLS backend available: OpenSSL and
GnuTLS. This meant that curl would have two binary library packages:
libcurl3-openssl and its respective -dev variant, for libcurl
linked against OpenSSL; and
libcurl3-gnutls and its respective -dev variant, for libcurl
linked against GnuTLS.
But then, around 2006/2007 or so, upstream curl decided to bump the
SONAME version of libcurl from 3 to 4. At the time, they apparently
did not version their library symbols like they do now, which
was... less than ideal. I don't judge them: curl and a lot of other
important projects have come a long way when we consider best
practices to write shared libraries.
Meanwhile, on Debian land, the release team was having trouble with
other transitions going on at the time. For those who are not versed
in Debian's vocabulary, a transition happens when a shared library
gets its SONAME version bumped: when this happens, we have to make
sure that all reverse dependencies of that library still build with
the new version, and fix things that fail. The more reverse
dependencies the library has, the harder this work gets.
When upstream curl bumping the SONAME version of libcurl, the Debian
curl maintainer at the time correctly renamed the binary packages from
libcurl3- openssl,gnutls (and their -dev variants) to
libcurl4- openssl,gnutls (and their -dev variants), which
obviously triggered a transition. And a big one, because libcurl is
used by several projects.
Long story short, the Debian release team found themselves between a
rock and a hard place. According to the late Steve Langasek at the
time:
We talked a while back about the curl transition, and about how upstream's
change from libcurl.so.3 to libcurl.so.4 is gratuitously painful for us in
light of the large number of reverse dependencies.
The libcurl transition has at this point gotten tangled with soname
transitions in jasper, exiv2, kexiv2, and God only knows what else. So I'd
like to revisit this question, because tracking this transition is costing
the release team a lot of time that would be better spent elsewhere, and
removing the need for a libcurl transition promises to reduce the complexity
of the other components by an order of magnitude.
On looking at the curl package, I've come to understand that the
symbol versioning in place in this library is the result of a
Debian-local patch. That's great news, because it suggests a solution
to this quandary that doesn't require an unreasonable amount of
developer time.
Yeah, it wasn't pretty. Here's what was proposed:
I am proposing the following:
Keep the library soname the same as it currently is upstream. Because
upstream uses unversioned symbols, our package will be binary-compatible
with applications built against the upstream libcurl regardless of what we
do with symbol versioning, so leaving the soname alone minimizes the
amount of patching to be done against upstream code here.
Revert the Debian symbol versioning to the libcurl3 version, and make
libcurl.so.3 a symlink to libcurl.so.4. We have already established that
libcurl.so.4 is still API-compatible with libcurl.so.3, in spite of the
soname change upstream; reverting the symbol versioning will make it fully
ABI-compatible with libcurl.so.3, and adding the symlink lets
previously-built binaries find it.
Revert the Debian package names to the curl 7.15.5 versions. Because
compatibility has been restored with libcurl3 and libcurl3-gnutls,
restoring the package names provides the best upgrade path from etch to
lenny; and because the symbol versions have been reverted, the libraries
are not binary-compatible with the Debian packages currently named
libcurl4/libcurl4-gnutls/libcurl4-openssl (in spite of being
binary-compatible with upstream), so it would be wrong to keep the current
names regardless.
Drop the SSL-less variant of the library, which was not present in curl
7.15.5; AFAICS, there is no use case where a user of curl needs to not
have SSL support, so this split seems to be unnecessary overhead. Please
correct me if I'm mistaken.
Leave the -dev package names alone otherwise, to simplify binNMUing of the
reverse-dependencies (some packages have already added versioned
build-deps on libcurl4.*-dev -- I have no idea why -- so reverting the
names would mean more work to chase down those packages). Drop
libcurl4-dev as a binary package, though, in favor of being Provided by
libcurl4-gnutls-dev. Many of the packages currently build-depending on
libcurl4-dev -- including some that wrongly used libcurl3-dev before --
are GPL, and these are apparently all packages where having SSL support
missing in libcurl4 wasn't hurting them, so libcurl4-gnutls-dev seems to
be the reasonable "default" here.
Schedule binNMUs for all reverse-dependencies.
Again, no judgement here: this was what needed to be done at the time,
and I believe it was a good solution given the circumstances.
In the end, the binary library packages got renamed again: from
libcurl4- openssl,gnutls back to libcurl3- openssl,gnutls (but
not their -dev variants!), but they continued shipping
libcurl libraries whose SONAME version was 4. This solved the
immediate problem of untangling the transitions mentioned by Steve,
but introduced a technical debt that would stick with the package
literally for decades.
The situation at the end of 2007 was:
libcurl3-openssl with libcurl4-openssl-dev; and
libcurl3-gnutls with libcurl4-gnutls-dev.
More discrepancy is added
Eventually the libcurl3-openssl package got renamed to libcurl3,
but aside from that the situation with mismatched library names
vs. SONAME versions stayed relatively unchanged until around 2018,
when the Debian curl maintainer at the time (a different person)
renamed libcurl3 to libcurl4 to fix a bug. This was the right
thing to do for libcurl3, and at the time upstream curl was already
properly versioning their symbols, but for some reason
libcurl3-gnutls got left behind. So now we had:
libcurl4 with libcurl4-dev; and
libcurl3-gnutls with libcurl4-gnutls-dev.
In other words, we now have a discrepancy between the OpenSSL and
GnuTLS variants' names. Yeah, confusing. And this is the situation
right now, on May 2026, while I write this post.
To make matters worse, the Debian curl package has been carrying a
patch to facilitate the split of OpenSSL and GnuTLS flavours for
decades now, and, for some reason I didn't bother to investigate, the
patch pins the SONAME version of libcurl3-gnutls to CURL_GNUTLS_3,
effectively overriding upstream's decision to version the symbols as
CURL_GNUTLS_4.
A call to make things right
Back in 2022, Simon McVittie filed a Debian bug to try and call our
attention to the fact that we were shipping this messy set of curl
packages. I had just started to get involved in the package
maintenance and Samuel asked me to take a look at the bug. I noticed
it was going to take more time than I had available, so I decided to
put it in my TODO list (TM).
Simon was generous enough to lay out a possible plan to tackle the
problem, but I had a feeling that this was going to be harder than it
looked. I kept postponing working on the bug, but also kept thinking
about it now and then because it's an interesting thing to solve.
Then, a month or so ago the Debian Brasil community got together for
MiniDebConf Campinas 2026 and we decided to do a bug squashing party
there. I started working on a few FTBFS bugs with GCC 16, but then
got remembered about the curl bug and thought that that was the
perfect time and place to start working on it, for a few reasons:
Samuel and Charles were also attending the conference, so I could
talk to them about my plans and show them a PoC.
The initial plan
The plan I had in mind was a variant of Simon's proposed plan:
I would have to adjust our GnuTLS-specific patch so that it did not
override the SONAME version for libcurl-gnutls. Then,
For each symbol from libcurl3-gnutls I would have to:
Explicitly version it as curl_symbol_name@@CURL_GNUTLS_4.
Create an alias for the symbol (let's call it __curl_compat_symbol_name).
Explicitly version this alias as __curl_compat_symbol_name@CURL_GNUTLS_3.
Have a separate version of curl's linker script to make it
possible to create a hierarchy between CURL_GNUTLS_3 and
CURL_GNUTLS_4 symbols.
Note that this whole dance is needed because it is a hard requirement
that programs linked against libcurl3-gnutls keep working when we
ship libcurl4-gnutls, without needing to recompile them. Due to the
fact that we will not really bump the SONAME of libcurl-gnutls (but
instead fix the symbol versions shipped by it), we cannot expect
programs to break given that they are actually using the exact same
ABI as before.
Unfortunately (as it is common with low level tools) the documentation
for ld's versioning syntax is quite incomplete and hard to find.
One of the best sources I found was this blog post. For this reason,
let me quickly explain the different notations for symbol versioning
used above.
curl_symbol_name@@CURL_GNUTLS_4
When we use curl_symbol_name@@CURL_GNUTLS_4 (note the @@) we are
telling the linker that this should be considered the default
version of curl_symbol_name. In other words, when a binary that
links against libcurl-gnutls calls curl_symbol_name, the linker
should use curl_symbol_name@@CURL_GNUTLS_4 to resolve the symbol.
There are a few ways to specify a symbol version in C/C++:
__curl_compat_symbol_name@CURL_GNUTLS_3
Finally, when we use __curl_compat_symbol_name@CURL_GNUTL_3 (note
the single @) we are telling the linker that this symbol exists, but
it should not be used as the default symbol. In fact, this
notation will basically hide the symbol and make it only available for
those programs that have already been linked against it. It's a way
of saying "don't offer this symbol when linking, but it's here in case
a program needs it to run" (it's a bit more complicated than that, but
you get the point).
The reason I had to create an alias to the function before
versioning the symbol with @CURL_GNUTLS_3 is because, once I've
versioned the main symbol as @@CURL_GNUTLS_4, I can't create another
version of it. It's also important to mention that to be able to
create a version for the alias I also had to change its visibility to
default. In the end, the alias ended up being defined as:
First attempt and lessons learned
For my PoC I decided to tackle a small subset of the problem. The
symbols file for libcurl3-gnutls contains around 100 symbols that
need to be fixed, so I chose two of them and started trying to write a
patch to see if I could make things work. And after some time
struggling with GCC's syntax and inspecting nm -D's output I finally
got something that looked like it was going to work. The two symbols
I had chosen to work with got correctly versioned (both as
@@CURL_GNUTLS_4 and @CURL_GNUTLS_3), and a quick-and-dirty C
program that used those symbols correctly compiled and ran with the
expected symbols. I showed the results to Samuel and Charles, we got
excited about what we saw, and then the conference ended.
Second attempt and some adjustments
After getting back home I resumed the work on my branch and wrote an
Emacs function that semi-automatically adjusted all 100+ symbols
listed in the symbols file so that they all looked like:
The patch was big but mostly repetitive, and I was happy to have come
up with a solution that looked clean. Until I tried to build the
package, that is.
I started seeing some strange errors that happened when ld was
trying to link the final libcurl4-gnutls object (yes, at that point
I had already renamed the binary package). This is one of the errors
I was getting from ld (I got variants of this error as I was trying
to fix the approach):
/usr/bin/x86_64-linux-gnu-ld.bfd: .libs/libcurl_gnutls_la-easy.o: in function dupeasy_meta_freeentry':./debian/build-gnutls/lib/./debian/build-gnutls/lib/easy.c:1024: multiple definition of curl_easy_cleanup'; .libs/libcurl_gnutls_la-easy.o:./debian/build-gnutls/lib/./debian/build-gnutls/lib/easy.c:908: first defined here/usr/bin/x86_64-linux-gnu-ld.bfd: .libs/libcurl-gnutls.so.4.8.0: version node not found for symbol curl_easy_duphandle@CURL_GNUTLS3/usr/bin/x86_64-linux-gnu-ld.bfd: failed to set dynamic section sizes: bad value
This was strange. I did some tests with very simple versions of a
shared library using the versioning mechanism I had implemented and it
all worked. I could not reproduce the problem, and that's not a great
feeling to have.
Then, after reading a lot of documentation and blog posts throughout
the internet I found something interesting. Apparently ld has a
limitation when it comes to dealing with symbols versioned with @@.
If there is a single symbol versioned like that in a source file (the
actual term is TU, which means Translation Unit, but let's
simplify), then ld is happy and generates the expected version
without issues. But when we're dealing with multiple definitions of
@@ symbols in a source file (which is exactly what happens in curl),
then ld can get confused and start giving errors during the link
stage.
To solve that limitation, we have to resort to yet another symbol
versioning notation: @@@. Yes, three at signs. For example:
Note that we have to use __asm__ because GCC's __attribute__
doesn't support the triple-at notation.
What this does is tell the linker to create a versioned symbol for
curl_symbol_name, set it as the default symbol when linking, but
also remove the unversioned curl_symbol_name symbol. This makes
ld happy and allows it to successfully link libcurl-gnutls. As
usual, you won't find any mention of the @@@ notation inside ld's
documentation.
With libcurl-gnutls compiling again, I had to adjust libcurl's
linker script to create a hierarchy between CURL_GNUTLS_3 and
CURL_GNUTLS_4 symbols. Here's the final version of the file:
CURL_GNUTLS_3 global: curl_easy_cleanup; /* lots of other symbols here */ local: *; ;CURL_GNUTLS_4 global: curl_*; local: *; CURL_GNUTLS_3;
Debian package adjustments
After getting the hard part out of the way, the rest was easy. It was
time to finally rename libcurl3-gnutls to libcurl4-gnutls.
Initially I was thinking that I'd need to ask the release team for a
transition to happen, but as it turns out that won't be necessary.
Because we are effectively shipping the same exact library/ABI and the
only difference is the inclusion of the extra CURL_GNUTLS_4
versioned symbols, and given that we will be shipping CURL_GNUTLS_3
versioned symbols to guarantee backwards compatibility, packages won't
need to get rebuild just to pick up the new dependency. Instead, we
can safely turn libcurl3-gnutls into a transitional package that
depends on libcurl4-gnutls.
Merge request and next steps
This is the merge request where I am working on the fix. As of this
writing it is in a draft state, but I expect to merge in the next
couple of days. Once the fixed curl package is uploaded, we should
keep an eye on the archive to make sure no unexpected bugs happen.
I would like to carry this patch downstream at least until forky is
released. It doesn't make sense to propose it upstream because this
problem is Debian-specific and should be fixed there. We will need to
make sure that all reverse dependencies of libcurl3-gnutls are
recompiled before we can get rid of the transitional package, too.
This was a fun bug to investigate and fix, and I am happy that we will
finally have sensible names (and symbol versions!) for both of our
libcurl variants. Stay tuned for the next challenge!
Unwinding Anxiety is a non-fiction self-help book about how to
reduce anxiety. The author is a board-certified psychiatrist specializing
in addiction and substance abuse, who has subsequently done clinical and
research (and commercial, more on that later) work in anxiety. His
previous book, The Craving Mind, was a pop science treatment of
addiction research. This book is more deliberately structured as a
self-help guide.
(The cover will assure you that he has an M.D. and a Ph.D. I don't include
honorifics and degrees in author listings as a small protest against the
weird social rules about which degrees count and which don't.)
There are a lot of self-help books out there about anxiety. There are a
lot fewer that say something relatively original. I think this is one of
the latter, but I certainly have not done a survey of the subgenre, and
it's possible the ideas here are only new to me. Brewer makes three basic
claims in this book, all of which I found personally useful:
Anxiety can be usefully analyzed as a habit. The rumination loop and
other related anxiety behaviors such as excessive analysis,
reassurance-seeking, and negative anticipation take the form of deeply
ingrained habits triggered by stimuli.
Raw willpower is not a useful way to break habits in general and
anxiety habits in particular. In order to displace the habit, you have
to retrain the part of your brain that runs habits on autopilot.
Attempting to override it with willful effort is exhausting and likely
to fail.
Habit loops in general, and anxiety loops in particular, can be
defused and replaced using mindfulness techniques.
This is not the way Brewer lays out the book. He goes to some effort to
lead the reader slowly through three techniques for handling anxiety (for
which he uses the metaphor of "gears," like for a bicycle or car) by
introducing them one at a time and encouraging the reader to become
thoroughly familiar with each one before moving on to the next. Since this
is a book review, I'm going to give you the whole argument at once so that
you know where this book is going. This may be less helpful in practice;
if you're trying to use this technique on your own anxiety, you may want
to read the book instead and not jump ahead.
Brewer's three gears are:
Identify your habit loops and recognize when they're happening. (This
part felt the most similar to traditional cognitive behavioral therapy
to me.)
Focus on how those habit loops make you feel. Rather than trying to
force the habit loop to stop, let it happen but pay very close
attention to the outcome and its effects on you.
Find and focus on a different reaction that provides better rewards
than the anxiety habit loop. Brewer suggests curiosity.
For me, the point where I thought "okay, you have my attention" is when
Brewer described the way many people, particularly people without anxiety,
tell people with anxiety to "just stop thinking about it" or "just do the
thing you're anxious about anyway and you'll see it will be fine" and then
described in detail why he believes that doesn't work. This is one of the
few discussions of anxiety I've read where the author goes out of his way
to stress that you cannot simply think your way out of anxiety and that
repeatedly trying to do so and failing is exhausting and demoralizing.
Everyone is different and I know some people find cognitive behavioral
therapy very helpful, but I find the constant effort to challenge
cognitive distortions more draining and demoralizing than useful. His
second gear, of not directly confronting the habit loop but instead
watching its effect and thinking about its outcome, feels so much more
approachable to me. Assuming, of course, it works.
Brewer's approach is essentially just mindfulness, although he mostly
avoids the (to me at least) somewhat off-putting typical introduction to
mindfulness via religious practice or general well-being and instead ties
it to a theorized model of how habits work in the human brain. His
contention is that habits, including anxiety, exist because at some point
they provided a reward that was sufficiently compelling to make the
habit-following part of your brain seek that reward. You were getting some
benefit (a sense of control, a sense of being prepared, temporary
reassurance, etc.) out of the anxiety reaction, which is why the anxiety
habit formed in the first place. Once that habit is in place, it can
continue without the reward. (Although in my experience there is probably
still some short-term reward.)
Rather than trying to force yourself to stop following the habit, Brewer
instead suggests letting the habit happen but then focusing (via
mindfulness) on how following the habit makes you feel, whether it
improves your sense of well-being or worsens it, and whether other actions
produce different feelings. The goal, in other words, is to undermine the
assumption of reward and to challenge any short-term reward with the
long-term discomfort that made you want to stop being anxious.
This avoids using your conscious brain to exert direct willpower, which is
exhausting and usually unsuccessful since the habit-following part of your
brain is stronger (for various evolutionary psychology reasons he explains
and that I found at least partly credible). Instead, you are using its
strengths of observation and classification. You pay close attention to
the ways in which the habit loop makes you feel bad, which in theory
provides feedback to the habit-following part of your brain that can
dislodge the habit. If the habit is recognized as no longer rewarding, it
will weaken.
Brewer's background is in addiction treatment, so he is predisposed to see
addiction in everything and one should probably be a bit cautious about
his enthusiasm. He claims a great deal of success with this approach in
clinical settings, mostly with addiction but also with anxiety, but this
is always hard to verify. (Few doctors who write self-help books
rigorously document their failures.) He apparently also has a company that
produces various phone apps that assist with this technique. I'm rather
cynical about anyone who talks about products their company has produced
in self-help books of this type, and I'm also rather cynical about anyone
who calls himself "Dr. Jud," but the book doesn't seem to be a sales pitch
and there's no direct information in it about how to get the apps.
For me, the first two parts of the book were the most useful and the
conception of anxiety reactions as habits made a surprising amount of
intuitive sense. I thought the third part of the book, where he tries to
describe a better in-the-moment reaction that you can try to build into a
more beneficial habit, to be the weakest. It's mostly stock mindfulness
advice that I've seen in other places, and you will be entirely
unsurprised to learn that Brewer meditates and has studied meditation. I
think it's clear that, for him, a feeling of curiosity works as an anxiety
replacement; I'm not sure that's universal and I'm not sure it works for
me.
That core idea that anxiety reactions are a type of addictive habit that
have outlived their useful rewards but continue because habits are hard to
change felt both useful and at least a little bit true, though. Your
mileage may, of course, vary, but I've been trying out various ideas from
this book since I first started reading it, and I think it's helping. If
any of this clicks with you and you're also prone to anxiety, it might be
worth a read.
One warning, though: Brewer's previous work on addiction includes binge
eating, and while it's not a primary focus, he uses several weight loss
and disordered eating examples and has a very traditional medical attitude
towards weight. I'm somewhat dubious of the addiction model of weight gain
in general, but more to the point, it's rather off-putting in a book
supposedly about anxiety. It's something I was able to skim over, but be
aware going in if you're likely to find this obnoxious.
I do think this book is a case of an addiction researcher seeing
everything through the lens of addiction, and I'm a little dubious this is
the right model for everyone's anxiety. But this is one of the good
reasons why there are a lot of books about anxiety: Different approaches
suit different people. This one made more sense to me than most; maybe you
are similar.
I can't really recommend or not recommend a book like this, since I think
so much will depend on whether you are one of the people for whom this
specific explanation will click, but I'm glad that I read it and I think
it's good to know that this model of anxiety exists.
Rating: 8 out of 10
Being persistent, sticking to a plan and showing up to work every day is generally valued highly across all cultures as virtuous behavior. It is obvious that anything of value and worth achieving is also not easy, but requires significant and recurring effort. Learning a new language, winning a sports competition or building a successful business are all typical scenarios where grit plays a central role above everything else. However, sometimes the virtue of tenacity can result in just a waste of energy.
The question is then: how does one recognize that true progress is being blocked by stubbornness and a pivot would be the correct decision, as opposed to being close to breakthrough where doing more of the same would actually be the right choice?
What is persistence actually?
To think clearly about this topic, one must first grasp the concept of grit and what it looks like in practice. Research by psychologist Angela Duckworth on grit shows that sustained effort in the face of setbacks separates high achievers from those who quit too soon. Entrepreneurs who iterated through dozens of failed prototypes or writers who revised manuscripts for years understand this truth. Persistence builds resilience, deep expertise, and the kind of compounding results that shortcuts cannot deliver. It also protects against the distraction of shiny new ideas that pull focus from what actually works.
Persistence is about:
Believing in an outcome and working towards it despite people around you not sharing the belief, and despite your own work and experiments not being successful.
Continuing to hold the belief and sticking to the decision despite other ideas, solutions and competing alternatives surfacing.
The more time passes, the firmer the conviction becomes. Time, money, and emotional energy invested in a failing direction create psychological pressure to continue (sunk-cost fallacy).
Simply following through on a plan or upholding a contract is not true persistence. Grit is a personal trait one can cultivate to actually become more energized to do something precisely because it turns out to be harder than expected.
Pivoting: a calculated choice
The opposite of being persistent is giving up. Pivoting is not about giving up, but about redirecting the energy and momentum towards a new goal. Pivoting requires coming to the realization that you were wrong, and going through the painful process of discovering a new truth.
Ideas tend to be abundant, and doing something new isn t hard as such. The hard part is to abandon a previously held belief and adopt a new one with equal conviction. To have that conviction you need to have data and metrics. This is also the key to how to decide between persisting vs pivoting at any moment in time.
Key metrics of success
Any decision is only as good as the information available at the time it was made. To be set up for success one needs to start by deciding on what the actual goal is, what one values and how progress is measured.
Key metrics are usually easiest to discover by working backwards from the goal. If you want to build an electric car, you might decide that the goal is to have a car that costs 30,000 euros and can drive 300 km on one charge. From that goal you can break down what the cost structure should be, what volume of production is needed to break even, what raw materials are needed and what the battery chemistry needs to achieve to meet the goal. That can further be broken down into a rate of progress. Suppose the plan requires battery energy density to reach 150 Wh/kg to be viable. If the state of the art starts at 100 Wh/kg and funding lasts a maximum of five years, the team needs at least an 8% improvement every year (1.08^5 100 Wh/kg 150 Wh/kg). This can then be used as a guideline. Sometimes progress is not steady, but happens in jumps. Even in those cases there should be a trajectory to benchmark the jumps against.
In an online business, the key metric could, for example, be one of these:
7- or 30-day retention rate: Do new users who try the service actually like it?
Weekly or monthly active users: Is usage trending up?
Feature adoption rate: In an existing service, how many users are using the new feature?
Product-Market Fit Score (from Sean Ellis test): Percentage of users who say they would be very disappointed if the product disappeared. Above 40% is a strong early indicator. A number below that (after multiple iterations) is a good data point to pivot.
Revenue run rate or burn rate: The most generic metric everything eventually boils down to. Healthy markets reward good products.
Weekly metrics are better than monthly, as they make the feedback loop faster and allow you to get validation quickly and do minor course corrections along the way. A complete pivot should, however, be based on long-term data, driven by the key metric and supported by additional data points.
Metrics are also needed because they can t be bribed or convinced to be anything other than what they are. Listening to other people is good, but just relying on the opinion of others is extremely dangerous because people are biased either for you or against you depending on whether they see you as a trusted leader or an outcast.
Key metrics are of course domain-specific and everyone needs to come up with their own. However, you must have some key metric. You can t have the excuse that what you are doing can t be measured. If you are part of a larger organization and you need to advocate for a difficult decision for example, to kill your darlings when facing a pivot you need to have the metrics to back up your views, and those metrics need to have been established way before as something the organization values, and not cherry-picked just for this one decision.
It does not matter if you are on a personal improvement journey, running a political campaign, inventing a new product, or growing a business you need to have some metric you can check at any given time to see if things are improving fast enough to predict success. Metrics can and should also be used in daily work to validate that you are on the correct path, and to optimize execution.
Famous examples of persistence and pivoting that led to breakthroughs
In all of the cases below it is of course in hindsight easy to say they made the right decision. However, take a minute to try to imagine yourself in their shoes at the time of the decision. What metrics might they have had available to support their decision? What would you have wanted to measure or find out if you were in the same situation?
Frustrated that his vacuum lost suction, James Dyson spent five years and built thousands of failed prototypes in a backyard shed. He remortgaged his home, lived on savings, and faced rejection from every major manufacturer who wanted to protect their bag-replacement business. The 5,127th prototype based on an idea from a sawmill with a cyclone finally worked. Launched in 1993, the Dyson DC01 became Britain s best-selling vacuum within two years.
As a single mother on welfare in the mid-1990s, J.K. Rowling finished her manuscript for Harry Potter and the Philosopher s Stone while battling depression and poverty. She hand-typed copies and mailed them to publishers. Twelve rejected it outright, with comments like children s books about magic don t sell. She nearly quit multiple times but kept revising and submitting. Bloomsbury finally accepted it after the CEO s eight-year-old daughter read the first chapter and demanded the rest. The series has since sold hundreds of millions of copies worldwide.
Founded in 1997 as a mail-order DVD rental service, Netflix added unlimited subscriptions in 1999 to compete with Blockbuster. By 2007, broadband growth and declining DVD sales signaled a shift. CEO Reed Hastings pivoted aggressively toward streaming, investing in bandwidth deals and original content while de-emphasizing physical media. The move faced skepticism, but eventually changed the whole culture of how entertainment is consumed.
YouTube launched in 2005 as a video-dating site. Founders offered money to women who uploaded dating videos, but almost no one did. Meanwhile, users uploaded random clips. The team recognized the mismatch and pivoted within months to a general-purpose video-sharing platform with easy uploading. Google bought it just 18 months later.
Instagram began in 2010 as Burbn, a location-based check-in app that let users post plans, earn points, and share photos. Co-founders Kevin Systrom and Mike Krieger quickly noticed users ignored most features and mainly used it for photo-sharing. They made the tough call: scrap everything else. Within weeks, they rebuilt the app around clean, simple photography with filters. The pivot launched as Instagram in October 2010. It gained 1 million users in two months and was acquired by Facebook just 18 months later.
Insanity or conviction?
English has several proverbs that warn against excessive persistence, such as banging your head against the wall . Insanity is commonly defined as Doing the same thing over and over again and expecting different results.
In Finland, the national identity is practically built on the concept of sisu . It means much more than just grit . The word is derived from the word for inside or guts and represents an unexplained, almost superhuman force that makes one stoically take action despite seemingly impossible odds and somehow succeed anyway. It became a defining national mythos during the Winter War (1939 1940), where a force 10 times larger than the Finnish army tried to invade the country but was stopped and Finland just barely managed to keep its independence. The word sisu transitioned from a character trait to a pillar of national survival.
I think Finns survived because the more you believe in persistence, the more likely you are to persist. I view persistence as a religion that requires faith, while pivoting is a science where you derive the truth from the numbers.
When in doubt, I would always choose persistence over pivoting. Perhaps it is because of my genetic tendency towards having sisu , but I would also rather keep on going a bit more and try one more time before giving up and pivoting in order to get more data, so that when I pivot, I know it is absolutely the right thing to do at that point.
Depending on the situation, the costs of postponing the pivot vary. Of course, if the main metric is the burn rate and a company is running out of money, a pivot must be done early enough that the remaining runway is enough to execute the pivot, and then some more.
In some situations a business idea might simply be ahead of its time. If that is the conviction and the key metrics support it, the best way to navigate the situation is to cut down on costs and wait for competitors to appear, help build general awareness, and then ramp up again to ride the wave. Remember that success does not come from grit alone there is always an element of timing and luck as well. But if you are not persistent and stop showing up every day, you won t be able to seize the opportunities if and when they arise.
Failure is the likely outcome you have to avoid it at any cost
One must also realize that most attempts end in failure. Failure is the baseline, and success is the exception. To reach a breakthrough, one must be stubbornly persistent. In particular, if you are a leader, you need to be so high in conviction that it almost becomes an aura that radiates to those around you.
Postponing the decision to pivot allows you to get a bit more data for the decision, so that once you pivot, you have full belief in the new direction. Once you pivot, there is no looking back, otherwise you will undermine morale and most certainly fail with the new thing as people will execute it with hesitation.
Failure is statistically always the more likely outcome. Most things end in failure and we never hear about them. If someone on your team does not believe in what you are doing, it is very easy for them to prove that something is a failure by spreading negativity, putting in less effort (perhaps unconsciously due to lack of conviction) and thus actually contributing to a self-fulfilling failure.
In most areas of life, ideas are cheap and the only thing that matters is execution. To be good at executing, you need to be good at making decisions. When drafting plans it is good to have alternatives and a lot of consideration. However, when execution starts, there is no room for doubt, otherwise the chances of success decrease.
Therefore, the best way of balancing persistence vs pivoting is to
plan well ahead,
establish the key metrics,
have thresholds established for what would trigger a pivot, and
do everything you can to move the metrics in the direction you want them to go.
Finally, if you decide to pivot, you must do so only with very high conviction, as you can t undo a pivot, and you should not be doing multiple pivots in a row either. If you are fully convinced yourself about the pivot, you will also be able to convince others about it, and carry the momentum.
I have been battling Large Language Models (LLM1) for the past
couple of weeks and have struggled to think about what it means and
how to deal with its fallout.
Because the fight has come from many fronts, I've come to articulate
this in terms of the Four Horsemen of the Apocalypse.
War: bot armies
Let's start with War. We've been battling bot armies for control of
our GitLab server for a while. Bots crawl virtually infinite
endpoints on our Git repositories (as opposed to downloading an
archive or shallow clone), including our fork of Firefox, Tor Browser,
a massive repository.
At first, we've tried various methods: robots.txt, blocking user
agents, and finally blocking entire networks. I wrote
asncounter. It worked for a while.
But now, blocking entire networks doesn't work: they come back some
other way, typically through shady proxy networks, which is kind
of ironic considering we're essentially running the largest proxy
network of the world.
Out of desperation, we've forced users to use cookies when
visiting our site. We haven't deployed Anubis yet, as we worry
that bots have broken Anubis anyways and that it does not really
defend against a well-funded attacker, something which Pretix
warned against in 2025 already.
(We have a whole discussion regarding those tools here.)
But even that, predictably, has failed. I suspect what we consider
bots are now really agents. They run full web browsers, JavaScript
included, so a feeble cookie is no match for the massive bot armies.
Side note on LLM "order of battle"
We often underestimate the size of that army. The cloud was huge even
before LLMs, serving about two thirds of the web. Even larger swaths of
clients like government and corporate databases have all moved to the
cloud, in shared, but private infrastructure with massive spare
capacity that is readily available to anyone who pays.
LLMs have made the problem worse by dramatically expanding the
capacity of the "cloud". We now have data centers that defy
imagination with millions of cores, petabytes of memory, exabytes
of storage.
I thought that 25 gigabit residential internet in Switzerland
could bring balance, but this is nothing compared to the scale of
those data centers.
Those companies can launch thousands, if not millions of fully
functional web browsers at our servers. Computing power or bandwidth
are not a limitation for them, our primitive infrastructure is. No one
but hyperscalers can deal with this kind of load, and I suspect that
they are also struggling, as even Google is deploying extreme
mechanisms in reCAPTCHA.
This is the largest attack on the internet since the Morris
worm but while Robert Tappan Morris went to jail on a felony,
LLM companies are celebrated as innovators and will soon be too big to
fail.2
Which brings us to the second horsemen, famine.
Famine: shortages
All that computing power doesn't come out of thin air: it needs
massive amounts of hardware, power, and cooling.
Earlier this year, I've heard from a colleague that their Dell
supplier refused to even provide a quote before August. Dell!
In February, Western Digital's hard drive production for 2026 was
already sold out. Hard drives essentially doubled in price within
a year, and some have now tripled. A server quote we had in
November has now quadrupled, going from 10 thousand to FORTY
thousand dollars for a single server.
But regular folks are facing real-life shortages as well, as
city-size data centers are being built at neck-breaking speed,
stealing fresh water and energy from human beings to feed the war
machine.
We've been scared of losing our jobs, but it seems that Apocalypse has
yet to fully materialize. Regardless for engineers, the market feels
tighter than it was a couple years ago, and everyone feels on edge
that they will just have to learn to operate LLMs to keep their jobs.
Update: it turns out I was clearly too optimistic. Cisco is laying
off 4,000 or 5% of its staff in a jolly announcement celebrating
a record $15.8 billion revenue, and Meta will lay off 8,000 or
10% of its workforce, in horrifying conditions. See also the
jobloss.ai tracker which counts 125,000 jobs lost since January
2025, as of May 2026.
Which brings us, of course, to Death.
Death: security and copyright
Our third horseman is one I did not expect a couple of months
ago. Back at FOSDEM, curl's maintainer Daniel Stenberg famously
complained about the poor quality of LLM-generated reports but
then, a few months later, everyone is scrambling to deal with floods
of good reports.
In the past two weeks, this culminated in a significant number of
critical security issues across multiple projects. Chained
together, remote code execution vulnerabilities in Nginx and
Apache and two local privilege escalations in the Linux kernel
(dirtyfrag and fragnesia) essentially gave anyone root access to any unpatched server to the web.
As I write this, another vulnerability dropped, which gives read
access to any file to a local user, compromising TLS and SSH private
keys.
All those vulnerabilities were released without any significant
coordination while people scrambled to mitigate.
Many people including Linus Torvalds are now considering issues
discovered through LLMs to be essentially public. This puts some
debates about disclosure processes in perspective, to say the
least.
But this is not merely the death of the traditional coordinated disclosure
process, the C programming language, or the Linux kernel: remember
that those bots are trained on a large corpus of copyrighted
material. Facebook has trained their models on pirated books and
Nvidia has done deals with Anna's Archive to secure access to
large swaths of copyrighted material. The US Congress seems to think
LLM outputs are not copyrightable, like any other machine outputs.
With many people now vibe coding their way out of learning or
remembering how computers work, is this the Death of Copyright?
And that, of course, brings us to the final horseman: Pestilence.
Pestilence: slop
There is a growing meme that programming is essentially over as we
know it. That you can simply vibe-code applications from scratch and
it's pretty good.
Maybe that's true.
So far, most of my attempts at resolving any complex problem with a
LLM have often failed with bizarre failures. Some worked surprisingly
well. Maybe, of course, I am holding it wrong.
I personally don't believe LLMs will ever be good enough to produce
and maintain software at scale. They're surprisingly good at finding
security flaws right now. But what I see is also a lot of
Bullshit, with a capital B. It's not lying: it does not "know"
anything, so it can't lie. It's misleadingly cohesive and
deliberate, but it lacks meaning, intent, will.
I have not been confronted with much slop, apart from the lobster
Jesus or the yellow man atrocities, and particularly not in my
work. But I see what it is doing to my profession: beyond
vibe-coding, people are now token-maxxing, and
land-grabbing their colleagues.
I don't like what LLMs do to our communities, or the fabric of
software we live with.
Software does not evolve in a void. It is a team effort, be it free
software or a corporate product. Generations of humans have carefully
built the scaffolding of technology required for modern networks and
software to operate, in a convoluted contraption that no single human
fully understands anymore.
The idea of simply giving up on that understanding entirely and
delegating it to an unproven model is not only chilling, it feels just
plain stupid. Not stupid as in Skynet, stupid as in "I can't get
inside the data center because the authentication system is
down". Except we're in a "the power plant doesn't reboot" or "their
LLM found an 0day in our slop" kind of stupid.
The fifth horsemen
Researching for this article, I looked up the four horsemen and found
out they original seems to have been:
Famine
War
Death
Conquest (??)
I was surprised. I grew up thinking about the horsemen being Famine,
War, Pestilence, and Death. So I went back to my original source
which actually claims the horsemen are:
Time has taken its toll on you, the lines that crack your face.
Famine, your body, it has torn through, withered in every place.
Pestilence for what you've had to endure, and what you have put others through
Death, deliverance for you, for sure, now there's nothing you can do
So I guess that makes no sense either, which, fair enough, I shouldn't
rely on Metallica for theological references. Especially since that
song was originally called Mechanix and was "about having sex at
a gas station".
Anyways.
The point is, there are actually five horsemen, and the fifth one is,
in my opinion, Conquest.
Those companies (and not "AI", mind you) are taking over the
world. I sense a strong connection with the "post-truth" world imposed
on us by fascists like Trump and Putin. It's not an accident, it's a
power grab part of the Californian Ideology3. Just like Airbnb
broke housing, Uber destroyed the transportation and Amazon is taking
over retail and server hosting, LLM companies are essentially trying
to take over if not everything, at least Cognition as a whole.
But the capitalization of those companies (OpenAI and Nvidia in particular)
are so far beyond reason that their inevitable collapse will likely
lead to a global financial collapse of biblical proportions.
Because they will inevitably fail like previous bubbles they are built
on. And when they fail, I hope it zips all the way back through the
blockchain scam, the ad surveillance system, and the dot com then git
me back my internet.
The Tower of Babel
While I'm off in the woods hallucinating (ha!) on biblical allegories,
I feel there's another sign that the apocalypse is coming.
The Tower of Babel myth says that humans tried to create a big
tower up to heaven and become god. God confounds their speech and
scatters the human race. End of utopia.
This is what is happening to our human translators now. LLMs being,
after all, Language Models, they are excellent at translation work. So
much that the only translators not replaced by LLMs right now are
interpreters, who translate vocally in real time. But
interpreters are worried about their jobs as well.
This concretely means we will lose the human capacity, as a
civilization, to translate between each other. It is still an open
question whether the remaining revision work will be enough for
translators to avoid deskilling, but other research has shown that LLM
use leads to cognitive decline, impacts critical thinking,
and generally, that deskilling is a common outcome.
Ultimately, I think this is where LLMs bring us. Towards collapse.
So this is a call to arms. Fight back!
Poison bots. Build local real-world communities.
Go low tech. Moore's law is dead, make use of it.
Patch your shit. Go weird.
Refuse slop. Train your brain. Refuse distillation.
The horsemen will collapse, but let's not go down with them.
Butlerian Jihad!
This article was written without the use of a large language model
and should not be used to train one.
Updates
A paragraph was added about the job apocalypse, which was of course
under-estimate.
Why Timnit Gebru was fired is extremely important and
interesting. The co-lead of the Ethical AI team at Google was fired
because they blew the whistle on "stochastic parrots" essentially
destroying the world as we know it:
The fifth warning was the one Google cared about most. [...]
The internet would become a place where the dominant voice was a
statistical average of dominant voices, presented as a neutral
assistant.
The warnings from the paper are eerily similar to my horsemen:
predicted the hallucination (pestilence)
bias amplification (war?)
environmental cost (famine)
un-auditable training corpus (death?)
"centralize linguistic and cultural power in the hands of the
small number of companies" (conquest)
I prefer "LLM" to Artificial Intelligence, as I don't consider
models to have "Intelligence" which goes far beyond the analytical
traits we train models for. Intelligence requires embodiment
and social interaction; machines lack the innate human skills of
empathy, feeling and care, which explains a lot of the evils
behind the current trends.
It should be noted that Morris also happened to be one of the
founder of Y Combinator where he is in good company with
other techno-fascists like Peter Thiel, Sam Altman, and so
on. Crime, after all, pays.
In the recent weeks I've been engaging Prot as an Emacs coach to help
with doing review passes over my upcoming ffs package as I work on
polishing and documenting it in preparation for offering it for
inclusion in GNU ELPA.
UPDATE 2026-05-15 08:50:10 -0400: Prot also published an article
about our session on his website:
https://protesilaos.com/codelog/2026-05-15-emacs-amin-bandali-ffs-display-buffer-org-capture/
Today we had our third session where we started by reviewing and
talking about my recent changes to ffs, then ventured to other
Emacs-related topics with the overarching theme of the flexibility
and extensibility of GNU Emacs, including display-buffer-alist,
keyboard macros, defining a custom ox-bhtml Org export backend
derived from Org's ox-html for ultimate flexibility when exporting
my site's pages from Org to HTML, Org capture, plain text files and
Emacs's diary and how it compares to org-agenda, and keeping a
journal with the help of Emacs.
Here is the video recording of our session, which I share with Prot's
permission:
You can view or download the full-resolution video from the Internet
Archive.
Lastly, here is the snippet Prot shared for having Isearch treat space
as a wildcard, helpful for more easily matching multiple parts of a
line:
Undeclared file conflicts, by Helmut Grohne
The duplication checker, the
Multi-Arch hinter, and the
/usr-move analyzer share significant
parts of their code. While the /usr-move transition is
complete, the other tools needed a
bit of love. Helmut added Python type annotations, slightly improved the
performance of the duplication website and shared more code between these tools.
Building upon this Helmut looked into file conflicts of various kinds such as
unrelated packages installing overlapping files, file type conflicts,
mismatching directory metadata and shared files of Multi-Arch: same packages
with varying content. Implementing reliable detection proved to be difficult due
to the amount of corner cases. So Helmut semi-manually
filedbugs.
In that process, it became apparent that binNMUs
do not reproduce SOURCE_DATE_EPOCH across architectures and therefore some
shared files embedding the build date would vary in content. Additionally, a
significant number of reports required further correspondence.
contributors.debian.org mini-sprint, by Enrico Zini
Enrico Zini met with Mattia Rizzolo to continue the work started at DebConf 25
on crediting contributions done via salsa, and to catch up with accumulated site
issues.
Building on the same kind of infrastructure used to notify tag2upload,
salsa.debian.org triggers a webping on pushes and merge
request activity, which causes a small JSON payload to be queued in a private
directory on contributors.debian.org.
We worked on processing, filtering and aggregating the files in the queue into a
private, staging database table. When configuring a
data source on the site, it is now
possible to configure automated submission of contributions from information in
the staging table. This makes it significantly simpler to credit contributors
for all teams that use Salsa as their code repository and coordination tool, as
the site can take care of the data mining for you.
See more details in the sprint report
posted to debian-devel-announce.
MiniDebConf Campinas, by Lucas Kanashiro, Santiago Ruano Rinc n and Antonio Terceiro
MiniDebConf Campinas was held between April 23rd and 25th, at the State
University of Campinas, and was preceded by a MiniDebcamp between April 20th
and 22nd. Freexian was Gold sponsor for the event, and Freexian collaborators
were active contributors to the conference success.
Lucas and Santiago delivered a talk about Debian LTS
during MiniDebConf Campinas 2026, where they described how the LTS project
benefits Debian users and developers, while strengthening Debian itself.
Lucas and Antonio delivered a talk about internship programs
in Debian during MiniDebConf Campinas 2026, with the goal of getting students
interested in working in and with Debian.
Lucas took part in the MiniDebConf Campinas content team, reviewing/accepting
talks and building the schedule.
Antonio led a session where he invited the audience to weigh in on current
controversies in Debian. The session presented playful elements as colored signs
to denote agree/disagree, and was not recorded, to help people feel more
comfortable about speaking up. He might be convinced to lead a similar session
at the next DebConf.
Antonio also organized a debate to discuss the consequences of new Brazilian
regulation for the protection of children and adolescents in digital spaces for
Debian and other free operating systems, but also for the free software
community in general. This session was very fruitful and will lead into further
actions, as one of the main outcomes was the realization that the free software
community must follow the discussion leading up to similar regulations more
closely to avoid being caught by surprise when they come into effect.
security-tracker performance, by Helmut Grohne and Emilio Pozuelo Monfort
Prompted by spontaneous influx of web requests on Freexian s security-tracker
back in February, we considered the options for managing that demand. One of our
mitigations was making it faster. To that end, Helmut sent
twoMRs
towards improving the situation. There are four notable improvements. The use of
Python s str.translate
generally speeds up rendering of larger templates.
Indexing
the CVE names avoids a costly sequential table scan.
Avoiding FFI calls while sorting
and reducing the queryset
speeds up the source package view. Emilio reviewed and deployed the changes on
to the Debian instance. Together these changes provide a twofold speedup on both
Freexian s and
Debian s instance on average.
dput-ng data loss bug, by Colin Watson
Ian Jackson (not affiliated with Freexian) reported that dput-ng could
lose data when using the local install
method, which could cause misleading results in tests of other packages; they
also filed an initial merge request
to fix it. Colin improved this to isolate its tests properly, and uploaded it.
Miscellaneous contributions
Lucas coordinated the src:valkey update to version 9 in unstable with a
potential co-maintainer.
Lucas provided a security update for src:valkey targeting trixie .
Thorsten did two uploads of foo2zjs, one to fix a bug and one to improve
packaging. As there have been several CVEs published for cups he also did an
upload of a new upstream version. Unfortunately this introduces a regression
and another upload was needed to take care of a crash. The patch for one CVE
also broke a test script, which is used by lots of printing packages in Debian.
As a result some autopkgtest runs failed. This could be fixed as well and the
only remaining issue that needs some more investigation is related to
cups-pdf. It is also worth mentioning that some issues related to the apparmor
configuration of cups could be resolved.
Helmut sent patches for 11 cross build failures.
Helmut sent a MR for enabling the new mainline YT6801 ethernet Linux driver
and it is now working fine with Debian s 7.x kernels.
Carles did further code developments for check-relations:
steps towards making it production ready when the initial round of reports are
analyzed. New show-package (information) command, improvements for
report_missing cases, added support for ignoring packages for specific
reasons, added unit tests, added CI. Used it to open 39 new bugs. Also followed
up different open bugs
Rapha l completed the French translation of Zulip for the
release of version 12.0.
Zulip is a nice 100% free software threaded communication platform for
distributed teams.
Stefano did routine uploads of python-pipx, python-mitogen,
platformdirs, python-authlib, python-discovery, distro-info-data,
python-virtualenv, python-certifi, python-wheel, pypy3.
Stefano uploaded distro-info-data updates to stable and oldstable proposed
updates, with the latest Ubuntu release.
Stefano took part in DebConf 26 preparation meetings.
Stefano prepared DebConf s online video streaming infrastructure for
MiniDebConf Campinas, and configured the
Debian reimbursement system to handle their travel bursary claims.
Stefano helped MiniDebConf Hamburg prepare their website for 2027.
Stefano did some sysadmin work on debian.social infrastructure.
Stefano reviewed Matthias python3.15 packaging and rebased his work on top
of it.
Antonio debugged a general slowness in salsa, caused by loss of IPv6
connectivity between the salsa host and the remote object storage in the cloud ,
which is a problem due to an open upstream bug in gitlab.
Santiago reviewed different changes to the Salsa CI pipeline, including the
new uscan test job,
prepared by Tha s Rebou as Araujo, and the final review to introduce
faketime testing, made by quila Macedo.
Santiago continued helping the DebConf 26 local team to prepare the conference.
Emilio updated libxpm to address a security issue.
Colin finished upgrading groff to 1.24.1; 1.24.0 and 1.24.1 were the first
upstream releases since 2023 and had extensive changes, so this took some time
to get right.
Colin released bookworm and trixie fixes for CVE-2026-3497
in openssh, and issued the corresponding BSA-130
for trixie-backports.
Colin upgraded openssh to 10.3p1.
Anupa worked on the accounting tasks for MiniDebConf Kanpur and prepared and
submitted a report to the fiscal host.
In or around 2014 I bought an iPad Mini (2), and following the normal
lifecycle of iOS devices, a major OS update eventually killed it as
a useful, general-purpose device: operating it was just too sluggish.
It remained useful as a streaming media player for a little while
longer until eventually the big streamers (BBC iPlayer, Netflix, etc.)
stopped supporting the version of their app which the iPad could
install: the last officially supported iOS was 12.4.8 in July 2020,
and by November it was officially dead.
Old 32bit games
During its useful life, the iPad Mini witnessed Apple's transition
from 32 to 64 bit apps. In the 32 bit days, there was a little cottage
industry of app developers, and in particular, game developers. There
were even several independent websites (App Shopper, Pod Gamer, Free-App Hero), which aided in sorting through
the morass of apps to find the good ones (then as now, the App Store
itself was almost impossible to effectively browse). This all went
away during the 32/64 transition, as many small-scale developers
weren't actively developing their applications or games any more, and
weren't prepared to pay the time or apple tax to rebuild and publish
them as 64 bit.
The last version of iOS that supported 32 bit apps on this device was
10.3.3, and by luck, there are some methods available to install this
old version of iOS on the Mini 2 Today. A couple of years ago I did so,
and I kept no notes so sadly I can't report on which method I used. But
it worked, and I was able to install a bunch of old 32 bit games that I
had no access to on more modern devices.
Prior to John Carmack's1 departure from iD Software, he'd been
responsible for publishing several experimental iD software games on iOS. These
mostly disappeared in the 64 bit transition. Amongst them are ports of
Wolfenstein 3D, classic Doom, some RAGE tie-ins, but perhaps most
interestingly. at least two original games, designed for the phone form factor:
Doom 2 RPG and Wolfenstein RPG.
Reading magazine-style things
Another notable game that disappeared was "Civilisation Revolution", a
cut-down Civ game that for a while I was obsessed with. Rather than port
it to 64 bit, the publisher withdrew it, and then published a "new" game
"Civilisation Revolution 2", requiring a separate purchase. Sadly, it is
rubbish, nowhere near as good as the first one.
Anyway, having managed to downgrade it to the 32 bit iOS and install these old
lost games, I then, of course, never played them and the device continued to
gather dust. I should make clear that, running such an old unpatched iOS version
means it's not safe at all to put any kind of sensitive information on this,
including entering passwords. I don't recommend even opening the web browser.
However, this 12 year old device does have some use as an e-reader, especially
for certain types of ebook or magazine, that I've struggled to engage with
on other devices. That's a topic for another blog post.
Carmack reportedly also had a pivotal role in convincing Steve
Jobs to permit native apps and provide an App Store on iOS:
the plan had been to solely support web apps, at least for 3rd
parties.