La BBC tiene una página donde puedes ver cómo se van armando los cruces del Mundial 2026 conforme avanzan los partidos. Sin drama, sin "última hora". Solo el cuadro, actualizado, con el camino posible de cada selección. Parece un detalle menor. No lo es.
En un torneo con 48 equipos y 12 grupos, como aficionados, además de saber quién ganó, queremos imaginar contra quién podrían jugar nuestras selecciones, qué tan difícil se pone el camino, qué escenarios son posibles. Esa página responde exactamente eso, sin obligarte a calcular nada.
Y eso es lo que hace bien, convierte la información compleja en algo fácil de entender, en el momento exacto en que la gente lo necesita.
Les comparto la página por si quieren seguir los cruces: https://t.co/xo3HWSuTp3 ⚽
#Comunicación #Mundial2026 #ComunicaciónDigital
@sercaslo@MovistarCo@CRCCol@OyentesW O de servicios que nunca cortan, yo me pase 1 día de la fecha de pago, no suspendieron el servicio pero el siguiente recibo llegó con cobro de reconexión
Full disk encryption on Linux scrambles most of the bytes on your partition, including the filesystem metadata.
Most because it encrypts everything except for the LUKS header itself, which stores encryption metadata.
If you look at the raw disk, you won't see file headers, directory structures, or even what type of filesystem is installed. You just see encrypted noise.
This happens because LUKS sits at the block layer.
It creates a virtual device (via the device mapper) that sits on top of your physical disk.
Write: The kernel sends data to the virtual device -> LUKS encrypts it -> writes encrypted bytes to the physical disk.
Read: You read from the virtual device -> LUKS fetches encrypted bytes -> decrypts it on the fly.
This architecture provides flexibility.
Because the decrypted virtual device looks exactly like a standard hard drive to the kernel, you can format it with anything.
You can put ext4, XFS, or something else inside a LUKS container. The filesystem doesn't even know it's being encrypted.
It’s a perfect example of the Unix philosophy: do one thing (encryption) and do it well, then pipe it to the next tool.
The most powerful feature in your Linux shell isn't a command.
It's a single character: |
ls -l | grep .txt | wc -l chains three simple tools into a powerful one-liner. This elegant design is powered by one of the oldest and most important syscalls: pipe() (#22 on x86_64).
Let's break down how it works. 🧵👇
> created the Linux kernel at 21
> built Git because no existing tool was good enough
> accidentally became the backbone of servers, Android, cloud, supercomputers
> never chased fame, money, titles or hype
> stayed private, consistent, and brutally honest for decades
> still reviews code, still improves Linux, still avoids drama
Is Linus Torvalds the most underappreciated legend of the tech industry?
🚨 Hackers Actively Exploiting 7-Zip RCE Vulnerability in the Wild
Source: https://t.co/cBwD6zCeXR
Hackers have begun actively exploiting a critical remote code execution (RCE) vulnerability in the popular file archiver 7-Zip, putting millions of users at risk of malware infection and system compromise.
The flaw, tracked as CVE-2025-11001, stems from improper handling of symbolic links in ZIP archives, allowing attackers to traverse directories and execute arbitrary code on vulnerable systems.
The U.K.'s NHS England Digital issued an urgent advisory on November 18, 2025, confirming active exploitation of CVE-2025-11001, urging immediate updates to mitigate risks.
#cybersecuritynews #cyberattacknews
From its inception in 1991, the Linux kernel has been developed in tandem with the GNU toolchain, specifically the GNU Compiler Collection (GCC) and GNU Binutils. Linus Torvalds wrote early kernel code relying on features unavailable in the ISO C standard or in other compilers. Over time, GCC wasn’t just the compiler used for Linux; it effectively defined the C dialect of the Linux kernel. The kernel’s Makefiles, header macros, and inline assembly conventions all assumed GCC semantics, and the kernel’s source is filled with GCC extensions such as:
__attribute__((...)) – custom attributes for alignment, sections, packing, etc.
Statement expressions (({ ... })) – used for inline, expression-like macros.
typeof – used to infer types in macros safely.
Inline assembly (asm volatile) – critical for low-level hardware control.
Builtins (__builtin_expect, __builtin_constant_p, etc.) – for branch prediction and optimisation.
These are not part of the C standard, rather, they’re part of GNU C. In other words, the Linux kernel source cannot be compiled by a compiler that implements the ISO C standard only (e.g., C99 or C11) without the GNU extensions. The Linux kernel doesn’t compile with “standard C”—it compiles with GNU C.
Even when Clang/LLVM was introduced as an alternative compiler in the 2010s, the LLVM project had to re-implement GCC behaviour. In practice, Clang’s “GNU compatibility mode” exists largely because of Linux.
RAID combines multiple drives into one logical unit to boost speed, reliability, or both. Each RAID level strikes a different balance between performance, fault tolerance & capacity 😎👇
Find pdf books with all my #Linux related infographics from https://t.co/3t6LHw8TIY