<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Natano Ledger</title>
    <description>The latest articles on DEV Community by Natano Ledger (@_frozen_infinity_).</description>
    <link>https://dev.to/_frozen_infinity_</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3387590%2F3fdf608e-5a08-4151-8dc6-733e985df2da.jpg</url>
      <title>DEV Community: Natano Ledger</title>
      <link>https://dev.to/_frozen_infinity_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/_frozen_infinity_"/>
    <language>en</language>
    <item>
      <title>How to get started with ricing on Linux?</title>
      <dc:creator>Natano Ledger</dc:creator>
      <pubDate>Sat, 26 Jul 2025 13:29:58 +0000</pubDate>
      <link>https://dev.to/_frozen_infinity_/how-to-get-started-with-ricing-on-linux-1l9d</link>
      <guid>https://dev.to/_frozen_infinity_/how-to-get-started-with-ricing-on-linux-1l9d</guid>
      <description>&lt;p&gt;First, let's understand what &lt;em&gt;is&lt;/em&gt; ricing. Ricing is the process of customizing your WM(windows manager) or DE(desktop environment). Usually you do this by editing the config of your window manager or compositor. In this article you will learn some basics about ricing and window managers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's the difference between a window manager and a desktop environment?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A window manager is a program that manages windows: how they look like, their behavior and keyboard shortcuts. A desktop environment is a set of utilities for graphical experience. Usually it includes a window manager, a file program, a photo viewer, etc. An example of a window manager could be Hyprland or i3, when GNOME and KDE are desktop environments.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's the difference between different window managers?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;All window managers are divided into 3 groups: tiling window managers, stacking and mixed(can be both stacking and tiling)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;A tiling window manager organizes windows so that each one is a some part of your screen, and the screen get divided into several rectangles, and each rectangle corresponds to one window. You can edit the size of the tiles(rectangles) with keyboard bindings that you configured in the config. &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;In stacking window manager windows are organized like, say, in Microsoft Windows. Each window floats and can overlay other windows, and some space of the screen can remain unused.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A mixed window manager can be either a tiling wm either a stacking wm, depending on the configuration.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;How do you use a tiling window manager?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Nowadays quite a few people know about tiling window managers, because they are not used neither in Windows, neither in macOS. But that doesn't make them worse that stacking window managers. In a tiling window manager you open an application by pressing a keyboard bind that you can configure in the config. An application launcher pops up. Usually it is something like rofi or wofi. In the launcher you select the desired application and a new tile is being created for it, shrinking some other tiles. You resize, close and drag windows using keyboard bindings. Some multi-layout wms offer different layouts. A layout is a preset of tiles for windows. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to write configs?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This question fully depends on the wm you are running. You need to locate the config file. Usually it is located in ~/.config/WMname, where WMname is the name of your wm. Every config has it's own syntax, which you can learn in the wm's docs. Usually in the config you can set keybindings for opening specific applications that you use often like terminal, browser, etc., for closing, resizing, dragging windows and actions with the wm itself, such as exiting a session. Also you can create some decorations for windows. The most common ones are rounded corners, outline(stroke), shadow, animations and blur. The possible options are available in the wm docs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What are the pros of a custom config?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In a custom config you can set absolutely anything as you like, it takes only your time. It is possible to set keybindings for tons of different actions, like changing volume. brightness and so on. When one has a config that one has written for oneself, the system is completely optimized for one. Also you can show off with your system on different communities.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Wayland? X11? XWayland? What is it?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;There are several different protocols for window managers. Basically they state which operations are allowed to be done with windows, and which aren't. Also, some applications run better in specific protocols, as they have been coded to fit this specific protocol. For example, Spotify is pixelated on Hyprland.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where to get inspiration and show off?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;There are very many different rices on &lt;a href="https://www.reddit.com/r/unixporn/" rel="noopener noreferrer"&gt;this reddit community&lt;/a&gt;. There you can publish your own rices and like/comment others. Also there are Discord servers of, say, Arch Linux, and there is a thread devoted to theming, you could post there too. There are many, many more communities, perhaps, not as big as the reddit community I mentioned, but the size doesn't matter. What matters is the people in the community.&lt;/p&gt;

</description>
      <category>ricing</category>
      <category>archlinux</category>
      <category>linux</category>
      <category>wm</category>
    </item>
    <item>
      <title>Hackintosh guide - install macOS on non-apple PC!</title>
      <dc:creator>Natano Ledger</dc:creator>
      <pubDate>Fri, 25 Jul 2025 11:43:34 +0000</pubDate>
      <link>https://dev.to/_frozen_infinity_/how-to-install-macos-on-a-non-apple-pc-2aoa</link>
      <guid>https://dev.to/_frozen_infinity_/how-to-install-macos-on-a-non-apple-pc-2aoa</guid>
      <description>&lt;p&gt;I think, everyone has seen macOS at least once in their lives. It is a very beautiful, easy to use and pleasant operating system. Although Apple Macs are very expensive and are not so functional, as many of them have only USB Type-C ports.&lt;/p&gt;

&lt;p&gt;So in this guide I will show you how to install OpenCore Hackintosh on your PC. Please note, that in this guide I am just showing my experience of installing and fixing post-install issues, and if something goes wrong with your machine, I am not responsible in any way for any damage or data loss. And now, let’s roll!&lt;/p&gt;

&lt;p&gt;Step #1:&lt;br&gt;
In this guide it will be crucial to know your CPU codename, as you will need to download or create EFI for yourself, and usually different EFIs are classified by the CPU codename they are oriented to.&lt;/p&gt;

&lt;p&gt;Now, to know your CPU codename, if you’re on Windows, you can download a free tool called CPU-Z, that shows you the processor codename. After obtaining the information, head to &lt;a href="https://olarila.com/forum/96-hackintosh-efi-folder-collection/" rel="noopener noreferrer"&gt;this website&lt;/a&gt; and download EFI with accordance to your system specs. Here I would like to say big &lt;strong&gt;THANKS&lt;/strong&gt; to the Olarila team for the EFI folders, as sometimes it is rather difficult to collect them. If you CAN’T see the EFI folder for your system, you can also visit &lt;a href="https://olarila.com/topic/5676-hackintosh-efi-folder-with-clover-and-opencore/" rel="noopener noreferrer"&gt;https://olarila.com/topic/5676-hackintosh-efi-folder-with-clover-and-opencore/&lt;/a&gt; with EFI for Intel PCs. Also you can use your own EFI if you have one.&lt;/p&gt;

&lt;p&gt;Step #2: &lt;br&gt;
    Now we need a recovery image for macOS. To get this, visit &lt;a href="https://github.com/acidanthera/OpenCorePkg" rel="noopener noreferrer"&gt;https://github.com/acidanthera/OpenCorePkg&lt;/a&gt;, and download the latest release from the releases page. After downloading, extract the files, and head to &lt;code&gt;Utilities/macrecovery&lt;/code&gt;. There, if you don’t have Python installed, then this is a perfect time to install it. Open the file named &lt;code&gt;recovery_urls.txt&lt;/code&gt; and copy the first line under latest, or copy the line under a specific version. If you’re on Windows, open Command Prompt as admin and paste the command you just copied and add &lt;code&gt;download&lt;/code&gt; on the very end. This would download a folder named &lt;code&gt;com.apple.recovery.boot&lt;/code&gt;. Now, if you’re on Windows, install Rufus and open it. (If you can’t install Rufus, then skip everything until the :), then just you will have to format the flash drive as FAT32 manually.). Then insert a flash drive with a minimum of 1GB and configure Rufus as shown:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fg1rez7hm9889mu65l15v.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fg1rez7hm9889mu65l15v.jpeg" alt="Rufus configuration" width="581" height="707"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Now click create, this would create a bootable USB. When the flash in complete, close Rufus, open File Explorer, navigate to the flash drive and delete the two files now located in it :) Now, copy the &lt;code&gt;com.apple.recovery.boot&lt;/code&gt; folder we downloaded earlier to the flash drive. Now copy the EFI folder to the flash drive and rename it to &lt;code&gt;EFI&lt;/code&gt;. The flash drive is ready.&lt;/p&gt;

&lt;p&gt;Step #3:&lt;br&gt;
    Now we need to boot to the installer. To do this, if you created the flash drive with Rufus, then just open boot menu and select the flash drive. Otherwise, in boot menu select boot from EFI file and then select the flash drive, and go to &lt;code&gt;/EFI/BOOT/BOOTx64.efi&lt;/code&gt;. In the boot loader select macOS recovery, it should be selected automatically.&lt;/p&gt;

&lt;p&gt;After you have booted in the installer, in the menu select Disk Utility and format the partition you want to install macOS on as APFS. When the format is completed, close Disk Utility and click reinstall macOS . At this step you will need a working Ethernet connection. Now the install process has started. Your computer will reboot several times, and each time you need to boot to the installer. If you booted accidentally not to the installer, but to something else, just shutdown and boot back to the installer.&lt;br&gt;
    When the installation is completed, you will be introduced to a quick setup guide. you might not be able to sign in to Apple ID. To fix this, click skip, and when the setup is complete, open App Store and login to Apple ID from the App Store.&lt;/p&gt;

&lt;h2&gt;
  
  
  Post-Install
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Fixing WiFi:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Open &lt;a href="https://github.com/OpenIntelWireless/itlwm/releases" rel="noopener noreferrer"&gt;https://github.com/OpenIntelWireless/itlwm/releases&lt;/a&gt; and choose the latest release. Them choose the AirportItlwm.kext for your macOS version. If there is no AirportItlwm.kext for your version, download itlwm.kext. Now download OpenCoreConfigurator (you could do this by clicking on this link &lt;a href="https://mackie100projects.altervista.org/download-opencore-configurator/" rel="noopener noreferrer"&gt;https://mackie100projects.altervista.org/download-opencore-configurator/&lt;/a&gt;). Now head to the &lt;code&gt;EFI/OC/Kexts&lt;/code&gt; and copy the itlwm.kext or AirportItlwm.kext to the folder, renaming them to itlwm.kext or AirportItlwm.kext respectively.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;WARNING!!! DON’T USE ITLWM AND AIRPORTITLWM AT THE SAME TIME!!!!&lt;/strong&gt; &lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Now open &lt;code&gt;config.plist&lt;/code&gt; under &lt;code&gt;EFI/OC&lt;/code&gt; with OpenCoreConfigurator and head to Kernel tab. Drag the copied kext from the Kexts folder to the list. If it fails to drag, just click on the + button and select the kext. Now save the changes. If you are using itlwm.kext, download HeliPort from &lt;a href="https://github.com/OpenIntelWireless/HeliPort/releases" rel="noopener noreferrer"&gt;https://github.com/OpenIntelWireless/HeliPort/releases&lt;/a&gt; and install it. Set HeliPort as a login item in Settings/General/Login items. Reboot and enjoy. If you are using itlwm.kext, the wifi logo will appear on the very left of the right tab on the upper menu. If using AirportItlwm.kext, then it will still be where it was.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fixing sound:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Download Hackintool from &lt;a href="https://github.com/benbaker76/Hackintool" rel="noopener noreferrer"&gt;https://github.com/benbaker76/Hackintool&lt;/a&gt; and install it. Open Hackintool and head to the sound tab and in the lowest tab scroll down to ALC Layout ID and click on the number on the right to see possible numbers for your audio. Now open &lt;code&gt;config.plist&lt;/code&gt; with OpenCoreConfigurator and head to the NVRAM tab and under the last entry (the third one) in the boot args set alcid to one of the possible entries from Hackintool. Save changes and reboot. If the sound still doesn’t work, change the value under alcid again and reboot. Repeat this until succeeded. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Booting without USB:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you want to boot macOS without a USB flash drive always sticking out, open OCC(OpenCoreConfigurator) and on the icon in the upper menu click on mount partition. Now open Finder, click on NO NAME and if you want only OpenCore as boot loader, delete everything. If not, it will be more tricky and will not be covered in the guide. For more info you can visit Dortania’s guide. Now copy all files from the flash drive to the EFI partition and you’re good to go!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Who to thank:&lt;/strong&gt;&lt;br&gt;
Apple for macOS&lt;br&gt;
Acidanthera for OpenCore&lt;br&gt;
Olarila for EFI folders&lt;br&gt;
OpenIntelWireless for itlwm.kext, HeliPort and  AirportItlwm.kext&lt;br&gt;
BenBaker76 for Hackintool&lt;/p&gt;

&lt;p&gt;.....and many, many more!!!&lt;/p&gt;

</description>
      <category>hackintosh</category>
      <category>opencore</category>
    </item>
  </channel>
</rss>
