<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hack the Way on Aleskandro</title><link>https://aleskandro.com/categories/hack-the-way/</link><description>Recent content in Hack the Way on Aleskandro</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>&lt;p xmlns:cc="http://creativecommons.org/ns#" style="margin:0;padding:0">
The content in this blog is licensed under
&lt;a href="https://creativecommons.org/licenses/by-nc-sa/4.0/?ref=chooser-v1" target="_blank" rel="license noopener noreferrer" style="display:inline-block;">
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International&lt;/a>
&lt;/p>
&lt;p style="margin:0;padding:0;margin-top:5px">
&lt;img style="border:none;display:inline-block;padding:0;margin:0" height=40 src="https://aleskandro.com/img/by-nc-sa.png" alt="">
&lt;/p></copyright><lastBuildDate>Sat, 13 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://aleskandro.com/categories/hack-the-way/index.xml" rel="self" type="application/rss+xml"/><item><title>Workaround for Fedora CoreOS boot partition space errors during upgrades</title><link>https://aleskandro.com/posts/workaround-no-space-left-on-device-boot-partition-fedora-coreos/</link><pubDate>Sat, 13 Dec 2025 00:00:00 +0000</pubDate><guid>https://aleskandro.com/posts/workaround-no-space-left-on-device-boot-partition-fedora-coreos/</guid><description>&lt;p>The default boot partition size for Fedora CoreOS installations is 384MB. This default size is likely not enough&lt;sup id="fnref:1">&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref">1&lt;/a>&lt;/sup> today for hosting new deployments and accommodating new kernels and initrd images in the boot partition&amp;rsquo;s /ostree folder. &lt;sup id="fnref:2">&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref">2&lt;/a>&lt;/sup>&lt;/p>
&lt;p>Eventually, some systems can start to fail when two kernels and initrd images cannot fit into the boot partition, and you may find &lt;code>rpm-ostree status&lt;/code> reporting:&lt;/p>
&lt;blockquote>
&lt;p>error: Installing kernel: regfile copy: No space left on device&lt;/p></description></item><item><title>Use overlayfs to compose /lib/modules for loading custom Kernel Modules on Fedora CoreOS</title><link>https://aleskandro.com/posts/custom-kernel-modules-autoload-overlayfs-fedora-coreos/</link><pubDate>Sat, 12 Apr 2025 00:00:00 +0000</pubDate><guid>https://aleskandro.com/posts/custom-kernel-modules-autoload-overlayfs-fedora-coreos/</guid><description>&lt;p>&lt;a href="https://fedoraproject.org/coreos/">Fedora CoreOS&lt;/a> is designed to be an &lt;strong>immutable operating system&lt;/strong>, meaning many critical system directories—like &lt;code>/lib/modules&lt;/code>—are &lt;strong>read-only&lt;/strong>. This poses a challenge when you need to &lt;strong>load custom kernel modules&lt;/strong> that aren&amp;rsquo;t shipped with the default kernel package.&lt;/p>
&lt;p>In this post, you&amp;rsquo;ll learn how to use &lt;strong>OverlayFS&lt;/strong> to compose a writable version of &lt;code>/lib/modules&lt;/code>, allowing custom modules to be loaded at boot without modifying the underlying system.&lt;/p>
&lt;h3 id="why-overlayfs">Why OverlayFS?&lt;/h3>
&lt;p>&lt;a href="https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html">&lt;strong>OverlayFS&lt;/strong>&lt;/a> is a union filesystem that lets you layer a writable directory over a read-only one. While it&amp;rsquo;s common in container environments, it also works great for CoreOS when you want to &amp;ldquo;extend&amp;rdquo; immutable paths like &lt;code>/lib/modules&lt;/code>.&lt;/p></description></item><item><title>Download O'Reilly Media EPUB books with SSO Login</title><link>https://aleskandro.com/posts/download-oreilly-media-epub-pdf/</link><pubDate>Wed, 01 Jan 2025 00:19:02 +0200</pubDate><guid>https://aleskandro.com/posts/download-oreilly-media-epub-pdf/</guid><description>&lt;p>If you have an O&amp;rsquo;Reilly Media Account, you may have noticed that - unfortunately - the platform doesn&amp;rsquo;t provide an easy way to download EPUB files for offline reading on your e-reader. While O&amp;rsquo;Reilly offers a web-based reader and mobile apps, sometimes you just want to read your books offline or on a dedicated e-reader, like a Kindle or Kobo.&lt;/p>
&lt;p>&lt;a href="https://github.com/kirinnee/oreilly-downloader/tree/main">This project&lt;/a> on GitHub provides a simple Python script on a Docker container that allows you to download your O&amp;rsquo;Reilly Media EPUB books with a single sign-on (SSO) login. This way, you can easily transfer your books to your e-reader or mobile device for offline reading.&lt;/p></description></item><item><title>Resizing the boot partition on Fedora CoreOS</title><link>https://aleskandro.com/posts/resize-boot-partition-fedora-coreos/</link><pubDate>Sun, 03 Nov 2024 00:19:02 +0200</pubDate><guid>https://aleskandro.com/posts/resize-boot-partition-fedora-coreos/</guid><description>&lt;p>This covers the issue at installation time.
After the coreos installer runs, the layout of the partitions will include something like:&lt;/p>
&lt;pre tabindex="0">&lt;code>└ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1000215216 sectors, 476.9 GiB
Model: HUGWORLD SSD 512
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 9E151132-C6B9-4E44-92FD-60DB86CCB8BE
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 1000215182
Partitions will be aligned on 16-sector boundaries
Total free space is 2669 sectors (1.3 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 BIOS-BOOT
2 4096 264191 127.0 MiB EF00 EFI-SYSTEM
3 264192 786432 384.4 MiB 8300 boot
4 786833 9717247 2.4 GiB 8300 root
&lt;/code>&lt;/pre>&lt;p>The root partition will be resized to its maximum size, after the reboot. This is the best time to shift it to the right and resize the boot partition.&lt;/p></description></item><item><title>Configuration of a Samba share on Fedora CoreOS based systems to allow public and browseable shares</title><link>https://aleskandro.com/posts/samba-fedora-coreos-kinoite-silverblue-home-public-browseable-share/</link><pubDate>Fri, 01 Nov 2024 00:19:02 +0200</pubDate><guid>https://aleskandro.com/posts/samba-fedora-coreos-kinoite-silverblue-home-public-browseable-share/</guid><description>&lt;p>Configuring samba on a Fedora CoreOS based system like Fedora Kinoite or Fedora Silverblue is not so different from
the traditional, non-atomic, OS configurations, including Fedora Workstation.
The main package to install is &lt;code>samba&lt;/code>, that you can achieve with the following command:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-shell" data-lang="shell">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># rpm-ostree install samba&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># systemctl enable smb nmb --now&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If you are using CoreOS-native layering, you might want to add this package and enable the unit in your &lt;code>Containerfile&lt;/code>.&lt;/p></description></item><item><title>Derivate Fedora CoreOS. Integrate MicroShift. Lightweight Kubernetes for lightweight travelling</title><link>https://aleskandro.com/posts/fedora-coreos-microshift/</link><pubDate>Tue, 02 Jan 2024 00:19:02 +0200</pubDate><guid>https://aleskandro.com/posts/fedora-coreos-microshift/</guid><description>&lt;p>As I prepare to move from Italy to the United Kingdom, I&amp;rsquo;ve started reassessing not just the physical belongings I&amp;rsquo;ll bring along, but also my personal infrastructure. My goal is to travel light, so reducing both physical and digital baggage has become a priority.&lt;/p>
&lt;p>As an OpenShift contributor and enthusiast of the Kubernetes and CoreOS ecosystem, I began exploring if MicroShift—a lightweight Kubernetes distribution built from OpenShift and optimized for small form factors and edge computing—could fulfill my needs.&lt;/p></description></item><item><title>Hack the Great Firewall</title><link>https://aleskandro.com/posts/hack-the-great-firewall/</link><pubDate>Sun, 22 Oct 2023 00:19:02 +0200</pubDate><guid>https://aleskandro.com/posts/hack-the-great-firewall/</guid><description>&lt;p>Shadowsocks is a versatile open-source proxy tool designed to bypass internet censorship and provide users with secure
and private access to the internet. It works by creating an encrypted tunnel between the user&amp;rsquo;s device and a remote
server, allowing them to circumvent firewalls and access blocked content. With its lightweight and efficient design,
Shadowsocks has become a popular choice for individuals seeking to maintain anonymity and freedom while browsing the
web, particularly in regions with strict online censorship policies.&lt;/p></description></item></channel></rss>