On Linux, Control-C and Control-V don't work for copying and pasting in terminals. The Control modifier is used for its original purpose of inserting control codes. Instead, terminal apps require an extra Shift modifier, like Control+Shift+C.

But what if there were hidden shortcut combos for copy and paste on Linux that work across most apps without adding any additional software or configuration? By the end of 2025, this will be the case, and many apps already support them. Here's the scoop!

This is meant to be the first part of a 3-part series discussing the space & types of IP addresses, with a particular focus on what has changed between IPv4 and IPv6. In this first post I’ll take the audience through a historical tour of some developments within the IPv4 address space.

In a second part I’ll discuss the properties of different types of addresses from a routing and from a security perspective, both in the IPv4 and in the IPv6 space. In the third part we’ll look at the implications of deploying IPv6 in certain networks based on those differences, e.g. “how to handle ACLs and IP address based log analysis approaches in a dual-stack network where systems have one RFC 1918 IPv4 address and multiple IPv6 GUAs?” (for specific reasons the latter two parts might be published on another medium though). In any case let’s start with a brief history of IPv4. The goal here is to understand how we got to the state that we have today.

Remember the way strings work in C: they consist of a bunch of bytes followed by a null character, which has the value 0. This has two obvious implications:

There is no way to know where the string ends (that is, the string length) without moving through it, looking for the null character at the end.
Your string can’t have any zeros in it. So you can’t store an arbitrary binary blob like a JPEG picture in a C string.

Why do C strings work this way? It’s because the PDP-7 microprocessor, on which UNIX and the C programming language were invented, had an ASCIZ string type. ASCIZ meant “ASCII with a Z (zero) at the end.”

Performance improvement for accessing documents through viewentries

Setting the Update_Fulltext_Thread parameter to 1 allows use of a separate thread to do full text indexing so that long full text indexes don't delay view updates. By default, view updates and full text index updates are driven by the same thread.

someone casually mentioned that there is an undocumented URL command "?OpenField".

What this URL command does, is return the HTML rendering of a specified Rich Text Field, with no head, no body tag etc.

Dieses Dokument beinhaltet die Dokumentenformate, die von Behörden zu
verwenden, anzunehmen bzw. abzulehnen sind.