<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adefemi Oluwaseun (whoami) on Medium]]></title>
        <description><![CDATA[Stories by Adefemi Oluwaseun (whoami) on Medium]]></description>
        <link>https://medium.com/@a__whoami?source=rss-208812ea704c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lChQ_KBqMN4AcLsj3lE8xg@2x.jpeg</url>
            <title>Stories by Adefemi Oluwaseun (whoami) on Medium</title>
            <link>https://medium.com/@a__whoami?source=rss-208812ea704c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:49:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@a__whoami/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Ubuntu Freezes During Boot? How to Troubleshoot the piix4_smbus Error in VMware]]></title>
            <link>https://medium.com/@a__whoami/ubuntu-freezes-during-boot-how-to-troubleshoot-the-piix4-smbus-error-in-vmware-a487f8f423c5?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a487f8f423c5</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[vmware]]></category>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 10:06:16 GMT</pubDate>
            <atom:updated>2026-11-16T10:06:16.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*-1EfWXqLC5CcsX3uDqkAqQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*xK5dBvB7xSoNPHM0fH5hTw.png" /><figcaption>piix4_smbus</figcaption></figure><p>Ever booted your Ubuntu VM and got stuck staring at this message?</p><p>piix4_smbus 0000:00:07.3: SMBus Host Controller not enabled!</p><p>Don’t panic! 🔐</p><p><strong>What’s happening?</strong></p><p>This message indicates that the Linux i2c_piix4 driver detected an SMBus controller that isn&#39;t enabled or fully supported by the virtual hardware.</p><p>In VMware or other virtualized environments, this warning is often harmless. However, if booting genuinely gets stuck, you can try the following workaround.</p><p><strong>🛠️ How to fix it:</strong></p><p>1️⃣ Boot into Ubuntu Recovery Mode or access a terminal.</p><p>2️⃣ Edit the GRUB configuration:</p><pre>sudo nano /etc/default/grub</pre><p>3️⃣ Locate:</p><pre>GRUB_CMDLINE_LINUX_DEFAULT=&quot;quiet splash&quot;</pre><p>4️⃣ Change it to:</p><pre>GRUB_CMDLINE_LINUX_DEFAULT=&quot;quiet splash modprobe.blacklist=i2c_piix4&quot;</pre><p>5️⃣ Update GRUB:</p><pre>sudo update-grub</pre><p>6️⃣ Reboot:</p><pre>sudo reboot</pre><p><strong>💡 Important Lesson:</strong></p><p>The last error displayed on your screen isn’t necessarily the actual cause of a frozen boot. Always investigate before changing kernel parameters.</p><p>Linux troubleshooting is about understanding the problem, testing a solution, and validating the result.</p><p>🐧 <strong>Learn by Doing. Build → Break → Analyze → Fix.</strong></p><p>What’s the most confusing Linux boot error you’ve encountered?</p><p>#Linux #Ubuntu #LinuxTroubleshooting #SystemAdministration #VMware #LinuxKernel #DevOps</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a487f8f423c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux service vs systemctl: Understanding Old and Modern Service Management]]></title>
            <link>https://medium.com/@a__whoami/linux-service-vs-systemctl-understanding-old-and-modern-service-management-8cdaab30fb26?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cdaab30fb26</guid>
            <category><![CDATA[linux-kernel]]></category>
            <category><![CDATA[systemctl]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Tue, 20 Oct 2026 03:10:18 GMT</pubDate>
            <atom:updated>2026-10-20T03:10:18.173Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A practical guide to managing Linux services, troubleshooting legacy systems, and understanding what happens under the hood.</strong></p><h3>Introduction: Why Does Linux Have Two Commands for the Same Job?</h3><p>Imagine you’re learning Linux and encounter this command:</p><pre>service apache2 status</pre><p>Then, in another tutorial, you see:</p><pre>systemctl status apache2</pre><p>Both commands appear to perform the same task: checking whether Apache is running.</p><p>So, what’s the difference?</p><p>Is service deprecated? Is systemctl its replacement? And what happens when you&#39;re working with an older Linux distribution like Metasploitable 2, where systemctl might not even exist?</p><p>These questions are more important than they seem.</p><p>Understanding Linux service management isn’t just about memorizing commands. It’s about understanding how Linux starts, manages, monitors, and controls background processes.</p><p>In this article, we’ll explore both commands, their historical differences, practical applications, and how to troubleshoot services when traditional management tools fail.</p><h3>1. What Is a Linux Service?</h3><p>A Linux service is a program that runs in the background to provide functionality to the operating system or other applications.</p><p>Unlike a regular application that you launch and interact with directly, a service typically operates without requiring continuous user interaction.</p><p><strong>Examples include:</strong></p><pre>Service                                 Function<br>Apache                                  Hosts websites and web applications<br>SSH                                     Provides remote system access<br>MySQL                                   Database management<br>Cron                                    Executes scheduled tasks<br>Docker                                  Manages containers<br>NetworkManager                          Manages network connections</pre><p>Think of a service like a generator.</p><p>You need to start it, stop it, restart it, or check whether it’s running.</p><p>Linux provides commands to perform these operations.</p><h3>2. The Traditional Approach: service</h3><p>Before systemd became widely adopted, Linux distributions commonly used SysV init for system initialization and service management.</p><p>The traditional service command follows this syntax:</p><pre>service &lt;service-name&gt; &lt;action&gt;</pre><p>For example:</p><pre>service apache2 status</pre><p>This checks Apache’s status.</p><p>Other operations include:</p><pre>service apache2 start<br>service apache2 stop<br>service apache2 restart<br>service apache2 reload</pre><h3>Understanding the commands</h3><ul><li>start — Starts the service.</li><li>stop — Stops the service.</li><li>restart — Stops and starts the service again.</li><li>reload — Requests that the service reload its configuration.</li><li>status — Displays the service&#39;s current state.</li></ul><p>The service command is considered a legacy interface, but it has not disappeared. Many modern distributions retain it for compatibility.</p><h3>3. The Modern Approach: <em>systemctl</em></h3><p>Enter systemctl, the command-line utility used to interact with systemd.</p><p>Systemd is an init system and service manager used by many modern Linux distributions, including Ubuntu, Debian, Fedora, and Kali Linux.</p><p>Its general syntax is:</p><pre>systemctl &lt;action&gt; &lt;unit&gt;</pre><p><strong>For example:</strong></p><pre>systemctl status apache2</pre><p><strong>Notice the difference:</strong></p><pre>service apache2 status</pre><p><strong>Compared with:</strong></p><pre>systemctl status apache2</pre><p>The command structure changes, but the objective is similar.</p><h3>Common systemctl commands</h3><pre>sudo systemctl start apache2<br>sudo systemctl stop apache2<br>sudo systemctl restart apache2<br>sudo systemctl reload apache2<br>sudo systemctl status apache2</pre><p><strong>When checking the status, you might encounter:</strong></p><pre>● apache2.service - The Apache HTTP Server<br>     Loaded: loaded<br>     Active: active (running)</pre><p><strong>The most important line is:</strong></p><pre>Active: active (running)</pre><p>This indicates that systemd considers the Apache service active.</p><p>Other possible states include:</p><ul><li>inactive (dead) — The service is not currently active.</li><li>failed — The service encountered a failure.</li><li>activating — The service is in the process of starting.</li></ul><h3>4. The Difference Between start and enable</h3><p>This is one of the most misunderstood concepts in Linux service management.</p><p>Consider:</p><pre>sudo systemctl start apache2</pre><p>This starts Apache immediately.</p><p>However, it does not necessarily configure Apache to start automatically after a system reboot.</p><p>For that, we use:</p><pre>sudo systemctl enable apache2</pre><p>This configures the service to start automatically during boot, according to its systemd configuration.</p><p>We can combine both operations:</p><pre>sudo systemctl enable --now apache2</pre><p>This enables Apache at boot and starts it immediately.</p><h3>What about disable and stop?</h3><p>These commands are also different:</p><pre>sudo systemctl stop apache2</pre><p>Stops Apache now.</p><pre>sudo systemctl disable apache2</pre><p>Removes its automatic startup configuration.</p><p>Disabling a service does not necessarily stop an already-running instance.</p><p>CommandPurposestartStart nowstopStop nowrestartStop and start againreloadReload configurationenableEnable automatic startupdisableDisable automatic startupenable --nowEnable and start immediately</p><h3>5. Reload vs Restart: Are They the Same?</h3><p>No.</p><p>Suppose you modify Apache’s configuration file.</p><p>You have two common options:</p><pre>sudo systemctl restart apache2</pre><p><strong>Or:</strong></p><pre>sudo systemctl reload apache2</pre><p>A restart stops and starts the service again.</p><p>A reload asks the running service to reread its configuration without a full service restart, if supported.</p><pre>RESTART</pre><pre>Apache<br>   ↓<br>Stop<br>   ↓<br>Start again</pre><pre>RELOAD</pre><pre>Apache continues running<br>   ↓<br>Reads updated configuration<br>   ↓<br>Continues operating</pre><p>For configuration changes, reload can reduce interruption, but always confirm that the service supports it and that the configuration is valid.</p><h3>6. Why Did Linux Move From SysV Init to systemd?</h3><p>Historically, Linux distributions used different initialization systems.</p><p>One traditional approach was SysV init.</p><p>Service scripts were commonly stored in:</p><pre>/etc/init.d/</pre><p>For example:</p><pre>/etc/init.d/<br>├── apache2<br>├── ssh<br>├── mysql<br>└── networking</pre><p>These scripts were used to start, stop, and manage services.</p><p>As Linux systems evolved, systemd gained widespread adoption.</p><p>Modern systemd-based systems manage units such as:</p><pre>apache2.service<br>ssh.service<br>cron.service<br>NetworkManager.service</pre><p>The systemctl command provides an interface for managing these units.</p><p>Importantly, systemd does more than manage services. It also handles other unit types, including:</p><pre>Unit                                           Purpose<br>.service                                       Services<br>.socket                                        Socket activation<br>.timer                                         Scheduled activation<br>.mount                                         Filesystem mount points<br>.target                                        Groups of units</pre><p>This is why systemctl is more than a simple replacement for service.</p><h3>7. Is the service Command Deprecated?</h3><p>The accurate explanation is:</p><p><strong>service is an older service-management interface, while </strong><strong>systemctl is the modern, generally preferred interface on systemd-based Linux systems.</strong></p><p>However, saying that service is completely deprecated everywhere would be inaccurate.</p><p>On many modern Debian-based distributions, service remains available for backward compatibility and may delegate operations to systemd.</p><p>Conceptually:</p><pre>service apache2 status<br>          |<br>          v<br>Compatibility interface<br>          |<br>          v<br>systemd<br>          |<br>          v<br>apache2.service</pre><p><strong>Whereas:</strong></p><pre>systemctl status apache2<br>          |<br>          v<br>systemd<br>          |<br>          v<br>apache2.service</pre><p>For modern Linux administration, learn systemctl first, but understand service because it remains relevant when working with older systems and scripts.</p><h3>8. Practical Linux Lab: Managing Apache</h3><p>Let’s apply what we’ve learned.</p><p>First, install Apache on a Debian-based system:</p><pre>sudo apt update<br>sudo apt install apache2</pre><p>Check its status:</p><pre>systemctl status apache2</pre><p>Stop it:</p><pre>sudo systemctl stop apache2</pre><p>Check its status again:</p><pre>systemctl status apache2</pre><p>Start it:</p><pre>sudo systemctl start apache2</pre><p>Enable automatic startup:</p><pre>sudo systemctl enable apache2</pre><p>Check whether it’s enabled:</p><pre>systemctl is-enabled apache2</pre><p>Check whether it’s currently active:</p><pre>systemctl is-active apache2</pre><p>Remember:</p><pre>is-enabled<br>     |<br>     v<br>Is it configured to start at boot?</pre><pre>is-active<br>     |<br>     v<br>Is it currently active?</pre><p>These are two different questions.</p><h3>9. What Happens When You’re Working With Metasploitable 2?</h3><p>Here’s where Linux history becomes particularly useful for cybersecurity learners.</p><p>Metasploitable 2 is an intentionally vulnerable Linux virtual machine used for penetration testing education.</p><p>Because it is based on an older Ubuntu environment, it uses the traditional SysV init architecture rather than systemd.</p><p>If you run:</p><pre>systemctl status apache2</pre><p>You may receive:</p><pre>systemctl: command not found</pre><p>This doesn’t automatically mean something is wrong with your installation.</p><p>It means the system may not have systemd or its command-line utility.</p><p>Try:</p><pre>service apache2 status</pre><p>If necessary, use the traditional init script directly:</p><pre>/etc/init.d/apache2 status</pre><p>To view available service scripts:</p><pre>ls /etc/init.d/</pre><p>This is one reason cybersecurity professionals should understand both modern and legacy Linux environments.</p><h3>10. What If Both service and systemctl Fail?</h3><p>Sometimes, you need to investigate beyond the service manager.</p><p>Instead of immediately concluding that a service is down, check the actual process.</p><h3>Method 1: ps</h3><pre>ps aux | grep &#39;[a]pache2&#39;</pre><p>This searches for Apache processes.</p><h3>Method 2: pidof</h3><pre>pidof apache2</pre><p>If Apache is running, this may return one or more process IDs (PIDs).</p><h3>Method 3: pgrep</h3><pre>pgrep -a apache2</pre><p>This displays matching process IDs and command lines.</p><h3>Method 4: netstat</h3><p>On older Linux systems:</p><pre>netstat -tulpn</pre><p>To check HTTP port 80:</p><pre>netstat -tulpn | grep &#39;:80&#39;</pre><p>On modern systems, you can use:</p><pre>ss -tulpn</pre><p>For SSH:</p><pre>ss -tulpn | grep &#39;:22&#39;</pre><p>For MySQL:</p><pre>ss -tulpn | grep &#39;:3306&#39;</pre><p>A listening port provides evidence that a process is accepting connections on that port. However, a listening port alone doesn’t prove that the application is healthy or functioning correctly.</p><h3>11. My Linux Service Troubleshooting Cheat Sheet</h3><p>When checking a service, use this general approach:</p><pre>CHECK SERVICE<br>                      |<br>           +----------+----------+<br>           |                     |<br>       Modern OS             Legacy OS<br>           |                     |<br>       systemctl              service<br>           |                     |<br>           |                 /etc/init.d/<br>           |                     |<br>           +----------+----------+<br>                      |<br>               Check process<br>                      |<br>             +--------+--------+<br>             |        |        |<br>             ps      pgrep    pidof<br>                      |<br>                Check port<br>                      |<br>                 ss / netstat</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OMlPJ4XTYYeOAdz9LIkIxw.png" /><figcaption>Check Service on Linux</figcaption></figure><p>This approach is useful when troubleshooting Linux servers, cybersecurity labs, CTF environments, and older virtual machines.</p><h3>Final Thoughts</h3><p>Linux service management is a perfect example of why understanding the underlying technology matters more than memorizing commands.</p><p>The key differences are:</p><ul><li>service — Traditional/legacy service-management interface.</li><li>systemctl — Modern command-line interface for systemd.</li><li>/etc/init.d/ — Traditional SysV init service scripts.</li><li>ps, pgrep, and pidof — Tools for checking processes.</li><li>ss and netstat — Tools for inspecting network sockets and listening ports.</li></ul><p>For modern Linux systems that use systemd, make systemctl your primary tool.</p><p>But when working with older systems like Metasploitable 2, knowing the legacy approach can save you considerable troubleshooting time.</p><p><strong>Don’t just memorize commands. Understand what is happening underneath them.</strong></p><p>That is how you move from being someone who uses Linux commands to someone who understands Linux.</p><h3>Continue Learning</h3><p>If you’re learning Linux for cybersecurity, practice these commands in Kali Linux, Ubuntu, and Metasploitable 2.</p><p>Build your understanding through hands-on exercises:</p><p><strong>Learn → Practice → Troubleshoot → Document → Repeat.</strong></p><p>Follow me for more practical Linux, cybersecurity, ethical hacking, and security research tutorials.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cdaab30fb26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Privilege Escalation Explained: su, sudo su, su -, sudo -s, sudo -i and More]]></title>
            <link>https://medium.com/@a__whoami/linux-privilege-escalation-explained-su-sudo-su-su-sudo-s-sudo-i-and-more-cc87e46665aa?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc87e46665aa</guid>
            <category><![CDATA[linux-kernel]]></category>
            <category><![CDATA[roots]]></category>
            <category><![CDATA[sudo]]></category>
            <category><![CDATA[privilege-escalation]]></category>
            <category><![CDATA[linux-tutorial]]></category>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Sun, 18 Oct 2026 21:30:35 GMT</pubDate>
            <atom:updated>2026-10-18T21:30:35.523Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aQ3IqFGw9JtbM_eZmu4C0w.jpeg" /></figure><p><strong>Understanding the difference between switching users, becoming root, and starting a login shell in Linux.</strong></p><p>If you are learning Linux administration, cybersecurity, or Linux kernel engineering, you will eventually encounter commands such as su, sudo, sudo su, sudo -s, and sudo -i.</p><p>At first glance, they appear to do the same thing: give you access to the root account.</p><p><strong>But they are not exactly the same.</strong></p><p>Some commands switch your identity. Others execute commands with elevated privileges.</p><p>Some create a new shell, while others create a login environment that loads the target user’s configuration.</p><p>In this article, we will break down these commands in simple English, explain what happens behind the scenes in Linux, and troubleshoot a real error encountered in a Kali Linux virtual machine.</p><h3>1. First, understand the Linux root user</h3><p>Think of Linux as a building with different access levels.</p><p>A regular user is like an employee who can access their own workspace and perform permitted tasks.</p><p>The root user is like the system administrator who has almost unrestricted control over the entire building.</p><p>In Linux, the root account has a User ID (UID) of 0.</p><p>You can check your current identity with:</p><pre>whoami</pre><p>Example output:</p><pre>kali</pre><p>Check your numeric user ID and group memberships:</p><pre>id</pre><p>Example output:</p><pre>uid=1000(kali) gid=1000(kali) groups=1000(kali),27(sudo)</pre><p>Now become root using:</p><pre>sudo -s</pre><p>Then run:</p><pre>whoami</pre><p>Expected output:</p><pre>root</pre><p>You are now running a shell with root privileges.</p><p><strong>Important Linux concept:</strong> Your username, UID, group memberships, shell, and environment variables are different pieces of information. Understanding these differences will help you troubleshoot privilege-related problems.</p><h3>2. What is su?</h3><p>The su command means <strong>substitute user</strong>. It allows you to switch to another user account.</p><p>In simple English, imagine leaving your own desk and sitting at another user’s desk, using that person’s account identity.</p><h3>Step 1: Switch to root</h3><pre>su</pre><p>On a typical Linux system, this attempts to switch to root.</p><p>You may be prompted for the root password.</p><p>If authentication succeeds, you become root. If the root account has no usable password or your system is configured differently, the command may fail.</p><p>Verify your identity:</p><pre>whoami</pre><p>Expected output:</p><pre>root</pre><h3>Step 2: Switch to a specific user</h3><pre>su username</pre><p>Replace username with an actual account name.</p><p>For example:</p><pre>su kali</pre><p>This switches to the kali account, generally retaining much of the calling environment rather than creating a complete login environment.</p><h3>Step 3: Understand the limitation</h3><p>Switching users does not necessarily give you a clean login environment. Environment variables and the working directory may differ from what you would get when logging in normally.</p><p>That is why Linux provides the - option.</p><h3>3. What is su -?</h3><p>The command:</p><pre>su -</pre><p>switches to root and starts a <strong>login shell</strong>.</p><p>Think of su as entering another user&#39;s workspace, while su - is more like leaving your workspace and logging in afresh as that user.</p><p>A login shell typically initializes the target user’s environment, changes to their home directory, and reads the applicable login startup files.</p><h3>Step-by-step example</h3><p>First, check your current location:</p><pre>pwd</pre><p>You might see:</p><pre>/home/kali</pre><p>Now run:</p><pre>su -</pre><p>After authenticating, check:</p><pre>whoami<br>pwd<br>echo &quot;$HOME&quot;</pre><p>Typical output:</p><pre>root<br>/root<br>/root</pre><p>The exact output depends on your system configuration, but the important point is that su - establishes a root login environment.</p><h3>When should you use su -?</h3><p>Use it when you need to switch accounts and want the target user’s login environment.</p><p>For example, when administering a Linux system directly as root.</p><p>On Kali Linux, however, the root account may not have a password configured for direct authentication. In that case, if your account has sudo privileges, sudo -i is often the more convenient option.</p><h3>4. What is sudo su?</h3><p>Let’s break the command into two parts:</p><pre>sudo su</pre><ul><li>sudo authorizes the command to run with elevated privileges according to the system&#39;s sudo policy.</li><li>su then attempts to switch to the root account.</li></ul><p>In simple English, you are using your authorized administrator privileges to launch the program that switches users.</p><h3>What happens behind the scenes?</h3><p>The general process is:</p><ol><li>You enter sudo su.</li><li>sudo checks whether your account is authorized.</li><li>If permitted, sudo launches su with elevated privileges.</li><li>su attempts to establish the root session.</li></ol><p>On many systems, this works without asking for the root password because sudo has already launched su with root privileges.</p><h3>Is sudo su the same as su -?</h3><p>No.</p><p>sudo su does not explicitly request a login shell. The environment and shell behavior depend on the su implementation and configuration.</p><p>If you want to request a root login shell using su, the corresponding command is:</p><pre>sudo su -</pre><p>Nevertheless, sudo -i is usually the cleaner and more direct option when you have sudo access.</p><h3>5. What is sudo -s?</h3><p>The command:</p><pre>sudo -s</pre><p>starts a shell with elevated privileges.</p><p>Think of it as being given administrator access inside a command-line workspace, without necessarily recreating a full root login session.</p><h3>Step-by-step example</h3><p>Run:</p><pre>sudo -s</pre><p>Then check:</p><pre>whoami<br>id<br>pwd<br>echo &quot;$HOME&quot;<br>echo &quot;$SHELL&quot;</pre><p>You should generally see that your effective identity is root, but some environment details may still reflect the calling user or the shell configuration.</p><p>The exact environment depends on your sudo settings and the shell being selected.</p><h3>Why is sudo -s useful?</h3><p>It is convenient when you need to execute several administrative commands in succession.</p><p>For example:</p><pre>sudo -s<br>apt update<br>apt upgrade<br>exit</pre><p>Here, exit leaves the privileged shell and returns you to your previous shell.</p><p><strong>Security tip:</strong> Do not remain in a root shell longer than necessary. A typo in a privileged command can damage the operating system.</p><h3>6. What is sudo -i?</h3><p>The command:</p><pre>sudo -i</pre><p>starts a root login shell.</p><p>The -i option tells sudo to simulate an initial login for the target user. With the default target user, that is root.</p><h3>Step-by-step example</h3><pre>sudo -i</pre><p>Now run:</p><pre>whoami<br>pwd<br>echo &quot;$HOME&quot;</pre><p>Typical output:</p><pre>root<br>/root<br>/root</pre><p>The shell is running with root privileges and a login-style environment.</p><h3>Why use sudo -i instead of sudo su -?</h3><p>Both commonly produce a root login shell, but they reach that result differently.</p><ul><li>sudo -i directly asks sudo to start the target user&#39;s login shell.</li><li>sudo su - asks sudo to run su, which then performs the user switch.</li></ul><p>For routine administration when sudo access is available, sudo -i is generally the more straightforward choice.</p><h3>7. Other useful commands: sudo command, sudo -u and sudo -l</h3><p>You do not always need to open a root shell.</p><h3>Run one command as root</h3><pre>sudo apt update</pre><p>This runs that particular command with elevated privileges.</p><p>Once it finishes, you return to your normal shell.</p><h3>Run a command as another user</h3><pre>sudo -u username command</pre><p>For example:</p><pre>sudo -u nobody whoami</pre><p>If permitted and the account is available, this runs whoami under the nobody account.</p><h3>See what you are allowed to run</h3><pre>sudo -l</pre><p>This displays the sudo privileges available to your account.</p><h3>Return to your regular user</h3><p>When you are inside a root shell:</p><pre>exit</pre><p>You can also press Ctrl+D to end the shell.</p><h3>8. Comparison table: Which command should you use?</h3><p>su Switch to root by default or another user &gt; Not normally a login shell</p><p>su -Switch to root by default with a login shellYes</p><p>sudo suUse sudo to launch</p><p>suNot explicitly requested</p><p>sudo su -Use sudo to launch a root login shell through suYes</p><p>sudo -sStart a privileged shellNot necessarily</p><p>sudo -iStart a privileged login shellYes</p><p>sudo commandRun one command with elevated privilegesNo new persistent shell</p><p>sudo -u user commandRun a command as another userDepends on the command and options</p><p>sudo -lList available sudo privilegesNot applicable</p><p>The key distinction is that <strong>privilege level and login environment are separate concepts</strong>. A root shell does not automatically mean you have a fresh root login environment.</p><h3>9. Real-world troubleshooting: Why does sudo su fail while sudo -s works?</h3><p>Consider this error from a Kali Linux virtual machine:</p><pre>$ sudo su<br>su: failed to execute whoami: No such file or directory</pre><p>Yet this command works:</p><pre>sudo -s</pre><p>Why might this happen?</p><p>The error indicates that su attempted to execute whoami as a shell or executable, but could not find it in the expected location.</p><p>One possibility is that the root account’s configured login shell is incorrectly set to whoami. Other possibilities include a missing executable or a configuration issue.</p><p>The fact that sudo -s works does not prove that the root account&#39;s shell is configured correctly. It may be using a different shell-selection path.</p><h3>Step 1: Inspect the root account</h3><p>Enter a privileged shell:</p><pre>sudo -s</pre><p>Then run:</p><pre>getent passwd root</pre><p>A typical healthy result is:</p><pre>root:x:0:0:root:/root:/bin/bash</pre><p>The last field identifies the configured login shell.</p><p>If it ends in whoami, that is suspicious.</p><h3>Step 2: Inspect the executable</h3><p>Run:</p><pre>command -v whoami<br>ls -l /bin/bash /usr/bin/whoami</pre><p>On a typical Kali installation, Bash and the whoami executable should be present at these paths.</p><h3>Step 3: Correct the shell only if it is wrong</h3><p>If the root account is confirmed to have whoami configured as its login shell, correct it with:</p><pre>usermod -s /bin/bash root</pre><p>Then verify:</p><pre>getent passwd root</pre><p>Do not change the root shell blindly if the output already shows a valid shell.</p><h3>Step 4: Test again</h3><p>Exit the privileged shell:</p><pre>exit</pre><p>Then try:</p><pre>sudo su<br>sudo -i</pre><p>If sudo su still fails, inspect the shell configuration and executable paths before making additional changes.</p><p>This is an important Linux troubleshooting lesson: <strong>do not assume two commands that provide root access follow the same execution path.</strong></p><h3>10. A practical lab to reinforce your understanding</h3><p>Run these commands in your Kali Linux VM, one at a time.</p><p><strong>Lab A: Establish your baseline</strong></p><pre>whoami<br>id<br>pwd<br>echo &quot;$HOME&quot;</pre><p><strong>Lab B: Compare privileged shells</strong></p><pre>sudo -s<br>whoami<br>pwd<br>echo &quot;$HOME&quot;<br>exit</pre><p>Then:</p><pre>sudo -i<br>whoami<br>pwd<br>echo &quot;$HOME&quot;<br>exit</pre><p><strong>Lab C: Inspect root configuration</strong></p><pre>getent passwd root</pre><p><strong>Lab D: Compare single-command privilege escalation with an interactive shell</strong></p><pre>sudo whoami<br>whoami</pre><p>The first command should report root, while the second should report your regular user if you have returned to your normal shell.</p><p>Observe the results instead of memorizing the commands. This is how you build practical Linux administration skills.</p><h3>Conclusion</h3><p>Understanding su, sudo su, su -, sudo -s, and sudo -i is not just about memorizing syntax. It is about understanding Linux identity, privileges, shell selection, and environment initialization.</p><p>For everyday administration, use sudo command for individual tasks and sudo -i when you need a root login shell. Use sudo -s when you need an interactive privileged shell without necessarily requiring a login environment.</p><p>Most importantly, when a command fails, investigate the configuration rather than assuming the entire privilege-escalation system is broken.</p><p>The more you practice these commands in a virtual machine, the more confidently you will troubleshoot Linux systems in system administration, cybersecurity, and kernel engineering.</p><p><strong>Keep learning. Keep testing. Understand what Linux is doing under the hood.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc87e46665aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Fix APT Repository Duplication in Kali Linux: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@a__whoami/how-to-fix-apt-repository-duplication-in-kali-linux-a-step-by-step-guide-1a41ec25df14?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a41ec25df14</guid>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[system-administration]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 09:15:49 GMT</pubDate>
            <atom:updated>2026-10-10T09:15:49.617Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Learn how to identify duplicate APT repositories, understand the warning, and fix the configuration safely.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UEQ8SUEgWtFqrQUds_nOVA.jpeg" /><figcaption><strong>Duplicate APT repositories</strong></figcaption></figure><h3>Introduction</h3><p>Have you ever run sudo apt update on Kali Linux and encountered this warning?</p><pre>Warning: Target Packages (main/binary-amd64/Packages)<br>is configured multiple times.</pre><pre>Warning: Target Packages (main/binary-i386/Packages)<br>is configured multiple times.</pre><p>I encountered this issue while troubleshooting my Kali Linux environment.</p><p>At first, it may look like an internet connectivity problem or a broken package manager. However, this warning often means that the same package index target has been defined more than once in your APT repository configuration.</p><p>In this tutorial, we’ll fix it, and verify the result.</p><p>The goal is simple: <strong>don’t just copy commands; understand what you’re fixing and why.</strong></p><h3>1. Understand the Problem</h3><p>APT stands for Advanced Package Tool. It manages software installation, package dependencies, and updates on Debian-based distributions such as Kali Linux.</p><p>When you run:</p><pre>sudo apt update</pre><p>OR</p><pre>sudo apt full-upgrade -y</pre><p>APT downloads package indexes from your configured repositories. These indexes contain information about available software and package versions.</p><p>Think of a repository as a software catalogue. If the same catalogue is registered twice, APT may warn that certain package targets are configured multiple times.</p><p>For example, a Kali repository might be configured in:</p><pre>/etc/apt/sources.list</pre><p>and again in:</p><pre>/etc/apt/sources.list.d/kali.sources</pre><p>If both definitions point to the same repository suite and generate overlapping package targets, APT can report duplication.</p><p><strong>Important:</strong> Having both files does not automatically mean your configuration is wrong. Their active entries must actually overlap.</p><h3>2. Understand the Warning</h3><p>Let’s break down the message.</p><ul><li>Target Packages: The package index APT is attempting to retrieve.</li><li>binary-amd64: Package index for the 64-bit x86 architecture</li><li>binary-i386: Package index for the 32-bit x86 architecture.</li><li>configured multiple times: APT has encountered the same target through multiple configuration entries.</li></ul><p>Seeing i386 does not necessarily mean your Kali installation is 32-bit.</p><p>You can check your primary architecture using:</p><pre>dpkg --print-architecture</pre><p>To see additional architectures:</p><pre>dpkg --print-foreign-architectures</pre><p>The main issue is the overlapping repository configuration, not necessarily your system architecture.</p><h3>3. Step One: Inspect Your Repository Configuration</h3><p>Before editing anything, identify which repositories are configured.</p><p>Run:</p><pre>cat /etc/apt/sources.list</pre><p>Then inspect the additional repository directory:</p><pre>ls -la /etc/apt/sources.list.d/</pre><p>If the following file exists, inspect it too:</p><pre>cat /etc/apt/sources.list.d/kali.sources</pre><p>A traditional repository entry may look like this:</p><pre>deb http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware</pre><p>A modern deb822-style configuration may look like this:</p><pre>Types: deb<br>URIs: http://http.kali.org/kali/<br>Suites: kali-rolling<br>Components: main contrib non-free non-free-firmware<br>Signed-By: /usr/share/keyrings/kali-archive-keyring.gpg</pre><p>These examples describe the same general repository configuration in two different formats.</p><p>Kali’s official documentation explains the supported configuration:</p><p><a href="https://www.kali.org/docs/general-use/kali-apt-sources/">https://www.kali.org/docs/general-use/kali-apt-sources/</a></p><h3>4. Step Two: Search for Duplicate Entries</h3><p>Instead of checking every file manually, use grep to search for Kali repository references.</p><pre>grep -RniE &#39;http.kali.org/kali|kali-rolling&#39; \<br>/etc/apt/sources.list /etc/apt/sources.list.d/ 2&gt;/dev/null</pre><p>You might see output similar to:</p><pre>/etc/apt/sources.list:1:deb http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware<br>/etc/apt/sources.list.d/kali.sources:2:URIs: http://http.kali.org/kali/<br>/etc/apt/sources.list.d/kali.sources:3:Suites: kali-rolling</pre><p>This is a clue that you should investigate further.</p><p>However, <strong>matching URLs alone do not prove duplication</strong>. Check the suite, components, architecture restrictions, and other options to confirm whether the package targets overlap.</p><p>For example, kali-rolling and kali-last-snapshot are different suites. Do not assume that two entries using the same server URL are duplicates if their suite definitions differ.</p><h3>5. Step Three: Back Up Before Making Changes</h3><p>Once you identify a redundant entry, create a backup of the file you intend to edit.</p><p>For example:</p><pre>sudo cp /etc/apt/sources.list \<br>/etc/apt/sources.list.backup</pre><p>This allows you to recover the original configuration if necessary.</p><p>Never delete repository files randomly. Some may contain repositories required by other applications.</p><h3>6. Step Four: Disable the Confirmed Duplicate</h3><p>Suppose your investigation confirms that /etc/apt/sources.list contains a redundant Kali Rolling entry while your intended configuration is maintained in kali.sources.</p><p>Open the legacy file:</p><pre>sudo nano /etc/apt/sources.list</pre><p>Find the confirmed duplicate:</p><pre>deb http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware</pre><p>Add # at the beginning:</p><pre># deb http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware</pre><p>This comments out the entry, preventing APT from processing it.</p><p>Save the file using:</p><ol><li>Ctrl + O</li><li>Press Enter</li><li>Ctrl + X</li></ol><p>This example applies only if the entry is genuinely redundant and you intend to retain the other configuration. If the duplicate is in another file, edit that file instead.</p><h3>7. Step Five: Refresh APT and Verify the Fix</h3><p>Run:</p><pre>sudo apt update</pre><pre>OR </pre><pre>sudo apt full-upgrade -y</pre><p>APT should refresh its package indexes without the duplicate-target warnings caused by the entry you disabled.</p><p>If the warnings remain, another overlapping definition may still exist. Return to the diagnostic steps rather than deleting additional files without evidence.</p><p>You can also inspect APT’s package index targets using:</p><pre>apt-get indextargets</pre><p>This can help you understand which package-index targets APT recognizes.</p><h3>8. Step Six: Check for Available Upgrades</h3><p>Once the repository configuration is correct, check which packages have newer versions available:</p><pre>apt list --upgradable</pre><p>If you are maintaining a Kali Rolling installation, you can then run:</p><pre>sudo apt full-upgrade</pre><p>Unlike apt upgrade, apt full-upgrade can install or remove packages to resolve dependency changes.</p><p><strong>Safety tip:</strong> Review the proposed changes before accepting them. If APT proposes removing a large number of important packages, stop and investigate first.</p><p>Also, do not confuse repository duplication with packages being held back. These are separate problems and may require different troubleshooting steps.</p><h3>9. Key Lessons</h3><p>This troubleshooting exercise reinforces several Linux administration principles:</p><ul><li><strong>Read error messages carefully.</strong> They often identify the class of problem.</li><li><strong>Inspect before editing.</strong> Establish which entries overlap before disabling anything.</li><li><strong>Understand repository suites.</strong> The same URL can serve different Kali branches.</li><li><strong>Back up configuration files.</strong> Make changes that can be reversed.</li><li><strong>Verify after every fix.</strong> Run apt update again to confirm the warning has disappeared.</li><li><strong>Keep repositories compatible.</strong> Avoid casually mixing Ubuntu or unrelated Debian repositories into Kali Linux.</li></ul><h3>Conclusion</h3><p>APT repository duplication is a useful Linux troubleshooting exercise because it teaches you to investigate configuration files, understand package indexes, and make controlled changes.</p><p>The solution is not to delete every repository file or repeatedly run upgrade commands. It is to identify the overlapping package targets, correct the redundant definition, and verify that APT can refresh its indexes cleanly.</p><p>As you develop your Linux skills, remember this workflow:</p><p><strong>Inspect → Diagnose → Back up → Fix → Verify → Document.</strong></p><p>Have you encountered the Target Packages ... is configured multiple times warning on Kali Linux or another Debian-based distribution? Share your experience and troubleshooting approach in the comments.</p><p>Let’s learn Linux by doing, testing safely, and documenting every step.</p><p><strong>References</strong></p><ul><li><a href="https://www.kali.org/docs/general-use/kali-apt-sources/">Kali Linux — APT Sources</a></li><li><a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834629">Debian Bug Tracking System — APT duplicate target warning example</a></li></ul><p>#Linux #KaliLinux #LinuxTroubleshooting #SystemAdministration #Cybersecurity #LinuxForBeginners</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a41ec25df14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Ever had your mouse cursor disappear inside Kali Linux running on VMware? ️]]></title>
            <link>https://medium.com/@a__whoami/ever-had-your-mouse-cursor-disappear-inside-kali-linux-running-on-vmware-%EF%B8%8F-8edc264b2e09?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8edc264b2e09</guid>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 21:33:59 GMT</pubDate>
            <atom:updated>2026-10-08T21:33:59.073Z</atom:updated>
            <content:encoded><![CDATA[<p>The strange part?</p><p>👉 The mouse still works.<br>👉 Keyboard input works.<br>👉 Mouse clicks may even work.<br>👉 But the cursor itself is completely invisible inside the VM.</p><p>And once you move the mouse back to your Windows host, the cursor magically appears again.</p><p>I recently experienced this while running <strong>Kali Linux 2026.2 on VMware</strong> after a <strong>kernel update</strong>.</p><h3>🔎 THE PROBLEM</h3><p>My environment:</p><p>• Guest OS: Kali Linux 2026.2<br>• Host OS: Windows 10 / Windows 11<br>• Virtualization: VMware Workstation / VMware Player<br>• Desktop: Xfce / GNOME</p><p>The cursor was invisible inside the Kali VM, even though the mouse and keyboard were still responding.</p><h3>🧠 THE EXPLANATION</h3><p>After searching for a solution, I came across a fix shared on the <strong>Kali Linux forums</strong>.</p><p>In simple terms:</p><p><em>Normally, the cursor can be rendered using the graphics hardware or the virtual GPU presented by VMware.</em></p><p>If the graphics stack has a problem after an update, the system may still receive mouse input but fail to <strong>display the cursor</strong>.</p><p>So instead of relying on the hardware cursor, we can tell <strong>Xorg</strong> to render the cursor using software.</p><p>Think of it like saying:</p><blockquote><strong><em>“If the graphics hardware isn’t displaying my cursor correctly, let the operating system draw it instead.”</em></strong></blockquote><p>Technically, the modesetting driver is being configured with:</p><p>SWcursor</p><p>This forces Xorg to use a <strong>software-rendered cursor</strong> instead of the hardware cursor path.</p><h3>🛠️ THE DEMONSTRATION</h3><p>I created the Xorg configuration file:</p><pre>sudo nano /etc/X11/xorg.conf.d/20-modesetting.conf</pre><p>Then added:</p><pre>Section &quot;Device&quot;<br>    Identifier &quot;Card0&quot;<br>    Driver &quot;modesetting&quot;<br>    Option &quot;SWcursor&quot; &quot;true&quot;<br>EndSection</pre><p>I saved the file and <strong>rebooted the Kali VM</strong>.</p><p>✅ After the reboot, the mouse cursor was visible again.</p><p>🎥 <strong>I also recorded a step-by-step video showing how I applied the fix and restored the cursor:</strong></p><p>👉 <a href="https://www.tiktok.com/@whoami__a/video/7694094069600881928">Tiktok Video</a></p><p>👉 <a href="https://www.youtube.com/watch?v=2CW20ynAYQ4">Youtube Video</a></p><h3>💡 THE LESSON</h3><p>This was a good reminder that troubleshooting isn’t always about replacing hardware or reinstalling the operating system.</p><p>Sometimes the problem is somewhere between:</p><p><strong>Kernel → Graphics stack → Display server → Virtual GPU → Desktop environment</strong></p><p>Understanding how these layers interact makes troubleshooting much easier.</p><p>And as someone learning Linux and cybersecurity, this is exactly the kind of problem I enjoy documenting:</p><p><strong>Build → Break → Troubleshoot → Understand → Document.</strong></p><h3>💬 YOUR TURN</h3><p>Have you experienced the <strong>Kali Linux + VMware disappearing cursor issue</strong>?</p><p>If you have, what solution worked for you?</p><p>Drop it in the comments. Your solution might help someone else troubleshooting the same problem. 👇</p><p>#KaliLinux #VMware #Linux #CyberSecurity #LinuxTroubleshooting</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8edc264b2e09" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Helped a Friend Recover His Windows 11 System After a BIOS/UEFI Configuration Reset]]></title>
            <link>https://medium.com/@a__whoami/how-i-helped-a-friend-recover-his-windows-11-system-after-a-bios-uefi-configuration-reset-a3a9d2de0a60?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3a9d2de0a60</guid>
            <category><![CDATA[computer-hardware]]></category>
            <category><![CDATA[helpdesk]]></category>
            <category><![CDATA[technical-support]]></category>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 14:48:42 GMT</pubDate>
            <atom:updated>2026-10-05T15:13:19.150Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Sometimes, fixing a computer doesn’t require reinstalling Windows. It requires understanding what changed.</em></p><p>A few minutes ago, a friend reached out to me because his laptop was displaying an unexpected boot error instead of loading Windows 11.</p><p>He was worried that something had gone wrong with his operating system, and like many users, his first thought was that Windows might have become corrupted.</p><p>But before suggesting a Windows reinstallation or any complicated troubleshooting, I decided to investigate the problem from the firmware level.</p><p>And what I discovered was a simple but important lesson in computer troubleshooting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*LsHM1ZeAHFgM8Hcog3JFvA@2x.jpeg" /></figure><h3>The Problem: Windows 11 Refused to Boot</h3><p>My friend explained that his system was no longer booting into Windows 11.</p><p>Based on the symptoms, I suspected that the issue might not be Windows corruption but a change in the system’s BIOS/UEFI configuration.</p><p>I asked him to navigate into the BIOS/UEFI setup to inspect the boot configuration.</p><p>My suspicion was that the BIOS settings might have reverted to their defaults, possibly due to a CMOS battery issue or a loss of stored firmware settings.</p><p>One important setting caught my attention:</p><p><strong>The boot mode had reverted to Legacy instead of UEFI.</strong></p><h3>Understanding What Happened</h3><p>Before going further, let’s understand two important boot modes.</p><h3>1. Legacy BIOS (Legacy Boot)</h3><p>Legacy boot is associated with the traditional BIOS boot process.</p><p>It commonly works with MBR (Master Boot Record) partitioning.</p><h3>2. UEFI (Unified Extensible Firmware Interface)</h3><p>UEFI is the modern firmware interface used by most contemporary computers.</p><p>It commonly works with GPT (GUID Partition Table) and supports modern boot features, including Secure Boot.</p><p>Windows 11 is designed for UEFI-based booting, and its standard installation requirements include UEFI firmware and Secure Boot capability.</p><p>This was the key to understanding my friend’s problem.</p><p>His Windows 11 installation had been configured to boot using UEFI, but the firmware was now attempting to boot using Legacy mode.</p><p>As a result, the system could not locate or load the Windows Boot Manager through the expected boot configuration.</p><h3>My Troubleshooting Approach</h3><p>Rather than rushing into reinstalling Windows, I guided him through the following steps:</p><p><strong>Step 1: Enter BIOS/UEFI Setup</strong></p><p>I instructed him to restart the computer and press the appropriate BIOS setup key, depending on the laptop manufacturer.</p><p><strong>Common keys include:</strong></p><ul><li>F2</li><li>F10</li><li>F12</li><li>DEL</li><li>ESC</li></ul><p><strong>Step 2: Locate the Boot Configuration</strong></p><p>Inside the firmware setup, I asked him to navigate to the Boot section.</p><p>We checked the available boot mode options and discovered that Legacy mode was enabled.</p><p><strong>Step 3: Change Legacy to UEFI</strong></p><p>I instructed him to switch the boot mode back to UEFI.</p><p>We also ensured that Windows Boot Manager was selected as the primary boot option, where available.</p><p><strong>Step 4: Save and Exit</strong></p><p>After making the changes, I guided him to select:</p><p><em>Save Changes and Exit</em></p><p>The system restarted automatically.</p><p>And then came the moment we were waiting for.</p><h3>The Result: Windows 11 Booted Successfully! 🎉</h3><p>The laptop successfully loaded Windows 11 again.</p><p>No Windows reinstallation.</p><p>No formatting.</p><p>No unnecessary data loss.</p><p>Just a proper diagnosis and correction of the firmware boot configuration.</p><p>What initially appeared to be a serious operating system problem turned out to be a boot-mode mismatch.</p><h3>What About the CMOS Battery?</h3><p>A CMOS battery helps maintain certain firmware settings, including the system clock and configuration information, when the computer is powered off.</p><p>If the battery is weak or depleted, some systems may lose their stored settings and revert to defaults.</p><p>However, a Legacy-to-UEFI change alone does not confirm that the CMOS battery is faulty.</p><p>If the BIOS repeatedly resets after shutdown, the CMOS battery should be checked.</p><h3>Lessons From This Experience</h3><p>This troubleshooting experience reminded me of several important principles:</p><ol><li><strong>Not every boot failure is an operating system problem.</strong> Sometimes, the issue exists at the firmware level.</li><li><strong>Understand BIOS and UEFI.</strong> Knowing the difference can save hours of unnecessary troubleshooting.</li><li><strong>Check boot mode before reinstalling Windows.</strong> A mismatch between the installed operating system’s boot configuration and firmware settings can prevent startup.</li><li><strong>Always investigate before formatting.</strong> Reinstalling an operating system should not be the first response to every boot issue.</li><li><strong>Troubleshooting is about understanding the root cause, not just applying random fixes.</strong></li></ol><h3>Final Thoughts</h3><p>As someone passionate about IT support, Linux, networking, and cybersecurity, experiences like this reinforce one principle I strongly believe in:</p><p><strong>Don’t just fix the problem. Understand why it happened.</strong></p><p>A simple BIOS configuration change can be the difference between a computer that appears completely dead and one that boots normally.</p><p>Sometimes, the solution is not to reinstall Windows.</p><p>Sometimes, all you need is to enter BIOS, correct the configuration, save, and exit.</p><h3>Key Technical Concepts</h3><p>BIOS | UEFI | Legacy Boot | GPT | MBR | Windows 11 | CMOS Battery | Boot Manager | IT Troubleshooting</p><p>#Windows11 #BIOS #UEFI #ITSupport #TechnicalSupport #ComputerTroubleshooting #Windows #HardwareTroubleshooting #Cybersecurity #LearnByDoing</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3a9d2de0a60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making a Kali Bootable USB drive on Windows Operating System]]></title>
            <link>https://medium.com/@a__whoami/making-a-kali-bootable-usb-drive-on-windows-operating-system-b53f75e641df?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b53f75e641df</guid>
            <category><![CDATA[bootable-usb]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[kali-linux]]></category>
            <category><![CDATA[windows]]></category>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 16:09:08 GMT</pubDate>
            <atom:updated>2026-09-25T16:09:08.713Z</atom:updated>
            <content:encoded><![CDATA[<p>📌 <strong>Introduction</strong></p><p>A <strong>Bootable USB Drive</strong> is a USB flash drive that contains special files which allow a computer to start (boot) from it instead of the hard disk.</p><p><strong>In very simple terms:</strong></p><p>👉 It’s a USB that can <strong>start your computer and load an operating system or tool</strong>.</p><p><strong>Why it’s called “bootable”</strong></p><ul><li><strong>Boot</strong> = the process of starting a computer</li><li>A <strong>boot able USB</strong> tells the computer:<br> “Start using what’s on this USB first.”</li></ul><p><strong>What it’s used for</strong></p><p>A bootable USB is commonly used to:</p><ul><li>💻 <strong>Install an operating system</strong> (Windows, Linux, Kali Linux, Ubuntu)</li><li>🛠️ <strong>Repair or recover a broken system</strong></li><li>🔐 <strong>Run security tools</strong> (pentesting, forensics, antivirus)</li></ul><p>✅ <strong>Prerequisites</strong></p><p>✔️ 8GB USB drive- maximum<br> ✔️ <strong>Windows 10/11</strong> as the OS to Run tools <br> ✔️ Download <a href="https://etcher.balena.io/">balenaEtcher — Flash OS images to SD cards &amp; USB drives</a></p><p>✔️ Download <a href="https://www.kali.org/get-kali/#kali-platforms">Kali linux ISO</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aAO0LJ4gXbiKPujBZuc61w.png" /><figcaption>Kali Linux ISO to download</figcaption></figure><p><strong>Step 1</strong> Plug your USB drive into an available USB port on your Windows PC, note which drive designator (e.g. “G:\”) it uses once it mounts, and launch <strong>Etcher</strong>.</p><p><strong>Step 2 </strong>Click <strong>Flash from file</strong>, and locate the Kali Linux ISO file to be imaged with.</p><p><strong>Step 3</strong> Click <strong>Select target</strong> and choose the USB drive you want to make bootable.</p><p><strong>Step 4:</strong> Click the <strong>Flash!</strong> button once ready.</p><p><em>Note: You may get a UAC prompt asking for administrator privileges that you will need to accept.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/0*zFxMGKw9hwOekiDz.png" /><figcaption><strong>Using Etcher for Bootable Kali Linux</strong></figcaption></figure><p><strong>Step 5 </strong>Once Etcher alerts you that the image has been flashed, you can safely remove the USB drive and proceed to boot into Kali with it.</p><p>Thanks for reading 😃 and if you’ve a question, kindly drop in the comment box</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b53f75e641df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Install pfSense on VMware: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@a__whoami/how-to-install-pfsense-on-vmware-a-step-by-step-guide-62086573c1c3?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/62086573c1c3</guid>
            <category><![CDATA[firewall]]></category>
            <category><![CDATA[vmware]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[firewall-security]]></category>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Sat, 25 Jul 2026 19:30:13 GMT</pubDate>
            <atom:updated>2026-07-25T19:30:13.964Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Install pfSense on VMware (Step-by-Step Guide for Beginners)</h3><h3>Introduction</h3><p><strong>Most people think learning firewalls requires expensive hardware.</strong></p><p><strong>It doesn’t.</strong></p><p>In less than 30 minutes, you can build your own enterprise firewall lab on your laptop using VMware and pfSense — for free.</p><p>If you’re learning <strong>Cybersecurity, Networking, SOC Analysis, or Ethical Hacking</strong>, setting up a pfSense lab is one of the best hands-on projects you can do.</p><p>In this guide, I’ll show you how to install <strong>pfSense Community Edition (CE)</strong> on VMware Workstation or ESXi.</p><h3>Why Learn pfSense?</h3><p>Many beginners understand networking but have never configured a real firewall.</p><p>With <strong>pfSense</strong>, you can practice enterprise-level networking concepts like:</p><ul><li>Firewall Rules</li><li>NAT</li><li>DHCP</li><li>VPNs</li><li>Routing</li><li>Network Security</li></ul><p>The best part? It’s completely free.</p><h3>📌 Prerequisites</h3><p>Before we begin, make sure you have:</p><p>✅ VMware Workstation or ESXi installed<br> ✅ A pfSense ISO file (Download from here)<br> ✅ At least <strong>2GB RAM</strong> and <strong>10GB storage</strong> allocated for pfSense</p><h3>Step 1: Download pfSense ISO</h3><ol><li>Visit the official <strong>pfSense download page</strong> → <a href="https://www.pfsense.org/download/">https://www.pfsense.org/download/</a></li></ol><p>OR</p><p>Download from <a href="https://repo.ialab.dsu.edu/pfsense/">https://repo.ialab.dsu.edu/pfsense/</a> (For Free)</p><ol><li>Select the <strong>Architecture</strong>: AMD64 (64-bit)</li><li>Select the <strong>Installer Type</strong>: ISO Installer (ISO.gz)</li><li>Choose file with name pfSense-CE-2.7.2-RELEASE-amd64.iso.gz (https://repo.ialab.dsu.edu/pfsense/).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/879/1*s3DbGOEry2uo4zI9kZFayw.png" /><figcaption><a href="https://repo.ialab.dsu.edu/pfsense/">pfSense-CE-2.7.2-RELEASE-amd64.iso.gz</a></figcaption></figure><blockquote><em>💡 </em><strong><em>Tip:</em></strong><em> Ensure you download the correct version compatible with your VMware setup.</em></blockquote><h3>Step 2: Create a New Virtual Machine in VMware</h3><h3>In VMware Workstation</h3><ol><li>Open <strong>VMware Workstation</strong> → Click <strong>Create a New Virtual Machine (Ctrl + N )</strong></li><li>Choose <strong>Other &gt; FreeBSD 14 or FreeBSD 13 (64-bit)</strong> → Click <strong>Next</strong></li><li>Set <strong>Virtual Machine Name</strong> (e.g., pfSense_VM)</li><li>Allocate at least <strong>10GB disk space</strong></li><li>Choose <strong>Split virtual disk into multiple files</strong> → Click <strong>Next</strong></li><li>Click <strong>Customize Hardware</strong>:</li></ol><ul><li>Set <strong>Memory</strong>: 2GB (2048 MB)</li><li>Set <strong>Processor</strong>: 2 cores (or more)</li><li>Add <strong>Two Network Adapters</strong>:</li><li><strong>Adapter 1</strong> → Set to <strong>Bridged (WAN)</strong></li><li><strong>Adapter 2</strong> → Set to <strong>Host-Only (LAN)</strong></li><li>Attach the <strong>pfSense ISO</strong>:</li><li>Click <strong>CD/DVD (IDE)</strong> → Select <strong>Use ISO Image File</strong></li><li>Browse and select the downloaded <strong>pfSense ISO</strong></li><li>Click <strong>Close</strong> → Click <strong>Finish</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R5lpQfUGwBEJTnmgvAYWEw.png" /><figcaption>Creating New Virtual Machine</figcaption></figure><p>2. Select <strong>Custom (advanced)</strong> → Click <strong>Next</strong></p><p>3. Select <strong>Installer disc image file (iso)</strong> → Click <strong>Next</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*UzSAKBgtCedKqVDLF3o5hg.png" /></figure><h3>Step 3: Install pfSense</h3><ol><li>Start the <strong>pfSense Virtual Machine</strong></li><li>When prompted, press Enter to <strong>Boot Multi-user</strong></li><li>The installer will load. Choose <strong>Install pfSense</strong> and press Enter</li><li>Select <strong>Auto (UFS)</strong> as the partition mode</li><li>Confirm the disk formatting → Click <strong>OK</strong></li><li>The installation will begin. Once done, select <strong>Reboot</strong></li><li>Remove the ISO file from the virtual machine</li></ol><h3>Step 4: Basic Configuration</h3><ol><li>Once pfSense boots, you will see the interface assignment screen.</li><li>Assign the <strong>WAN (e.g., vmx0)</strong> and <strong>LAN (e.g., vmx1)</strong> interfaces.</li><li>Note the <strong>LAN IP Address</strong> (default: 192.168.1.1)</li></ol><h3>Step 5: Access pfSense Web Interface</h3><ol><li>Open a browser and go to <a href="http://192.168.1.1/"><strong>http://192.168.1.1</strong></a></li><li>Login with:</li></ol><ul><li><strong>Username:</strong> admin</li><li><strong>Password:</strong> pfsense</li></ul><p>3. Follow the <strong>pfSense setup wizard</strong> to configure the firewall</p><h3>What You’ve Learned</h3><p>By completing this lab, you’ve built a real firewall environment that can be used to practice:</p><ul><li>Firewall configuration</li><li>Routing</li><li>NAT</li><li>VPN setup</li><li>Network security</li></ul><p>These are practical skills used by Network Engineers, SOC Analysts, and Cybersecurity Professionals.</p><h3>Final Thoughts</h3><p>Reading about firewalls is helpful, but building one yourself is where real learning begins.</p><p>Start with pfSense, experiment with different configurations, and gradually expand your home lab with tools like <strong>Kali Linux</strong>, <strong>Windows Server</strong>, and <strong>Wazuh</strong>.</p><p><strong>If this guide helped you, leave a comment, share it with someone learning cybersecurity, and follow me for more hands-on tutorials on Linux, Networking, Cybersecurity, and AI Security.</strong></p><p>💬 <strong>Got questions? Drop a comment below!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62086573c1c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IT ROLES & RESPONSIBILITES]]></title>
            <link>https://medium.com/@a__whoami/it-roles-responsibilites-c4f17897f4ad?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4f17897f4ad</guid>
            <category><![CDATA[it-security]]></category>
            <category><![CDATA[helpdesk]]></category>
            <category><![CDATA[system-administration]]></category>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Sat, 11 Jul 2026 22:40:04 GMT</pubDate>
            <atom:updated>2026-07-11T22:40:04.463Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*QDxPzuLpdvsGtRE6" /></figure><p>🖥️ Do you know the difference between IT roles?</p><p>Many people think “IT” is just one job — but there’s a whole career ladder behind the scenes keeping everything running! 🚀</p><p>Here’s a breakdown of key IT roles and what they actually do:</p><p>✅ IT Help Desk (L1) — Your first line of support. Password resets, basic troubleshooting, and ticket management.</p><p>✅ IT Support Engineer (L2) — Handles escalated, complex issues. Digs deeper into OS, networks, and hardware.</p><p>✅ System Administrator (L3) — Manages servers, Active Directory, DNS, DHCP, backups, and security patches.</p><p>✅ IT Infrastructure Engineer — The big picture person. Designs, builds, and secures the entire IT environment — cloud, virtualization, disaster recovery, and more.</p><p>💡 Whether you’re just starting out at the Help Desk or scaling up to Infrastructure Engineering — every level matters. Each role builds the skills for the next!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4f17897f4ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ What if your “new” SIM card isn’t really new?]]></title>
            <link>https://medium.com/@a__whoami/what-if-your-new-sim-card-isnt-really-new-601a6f0057aa?source=rss-208812ea704c------2</link>
            <guid isPermaLink="false">https://medium.com/p/601a6f0057aa</guid>
            <dc:creator><![CDATA[Adefemi Oluwaseun (whoami)]]></dc:creator>
            <pubDate>Mon, 06 Jul 2026 18:55:58 GMT</pubDate>
            <atom:updated>2026-07-11T22:38:37.608Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine buying a brand-new phone number from your telecom provider…</p><p>A few weeks later, you start receiving messages meant for someone else.</p><p>Or worse…</p><p>The previous owner is still using that same number on WhatsApp.</p><p>This is not a hypothetical scenario.</p><p>It recently happened to me.</p><h3>The Problem</h3><p>Many telecom providers recycle inactive phone numbers after a period of inactivity.</p><p>While recycling numbers is a common industry practice, the real concern is what happens <strong>before</strong> that number is reassigned.</p><p>If the previous owner never removed the number from their digital accounts — or if services don’t properly verify continued ownership — the newly assigned subscriber may inherit someone else’s digital footprint.</p><p>That could include:</p><p>📱 WhatsApp</p><p>📧 Gmail recovery</p><p>🏦 Banking notifications</p><p>🔐 Two-Factor Authentication (2FA)</p><p>🌐 Social media accounts</p><p>💼 Business applications</p><p>The consequences can range from privacy issues to account recovery complications.</p><h3>My Experience</h3><p>I recently discovered that a new phone number, which is registered under my NIN, had been actively used on WhatsApp by someone else for months.</p><p>I only became aware after receiving calls and messages intended for me.</p><p>When I checked the number, I found that another person had already established an active WhatsApp account using it.</p><p>As a Security Researcher, this immediately raised several questions about telecom number reassignment, identity verification, and digital account lifecycle management.</p><h3>Why This Matters</h3><p>Now imagine a different scenario.</p><p>Someone purchases a recycled SIM card that was previously associated with online fraud or cybercrime.</p><p>Although investigators rely on multiple pieces of evidence — not just a phone number — a reassigned number could initially create confusion during an investigation if historical ownership is not properly distinguished.</p><p>Likewise, if online services continue trusting an old phone number, sensitive information may unintentionally reach the wrong person.</p><p>A phone number is no longer just a way to make calls.</p><p>Today, it is a digital identity.</p><h3>The Lesson</h3><p>Whether you’re an individual, business, or telecom provider, this is a reminder to strengthen your digital hygiene.</p><p>Before abandoning a phone number:</p><p>✅ Remove it from WhatsApp.</p><p>✅ Update your Gmail recovery information.</p><p>✅ Change your banking and financial accounts.</p><p>✅ Update all MFA/2FA settings.</p><p>✅ Remove it from social media and business platforms.</p><p>And if you activate a recycled number, check whether it appears to be linked to someone else’s digital accounts.</p><p>Cybersecurity isn’t always about sophisticated attacks.</p><p>Sometimes, it’s about understanding the hidden risks in everyday technology we trust.</p><h3>Let’s Discuss</h3><p>Have you ever received a recycled phone number that still belonged to someone else’s digital life?</p><p>Or have you experienced calls, verification codes, or messages intended for a previous owner?</p><p>I’d love to hear your experience.</p><p>The more we discuss these issues, the better we can improve awareness around telecom security, digital identity, and cyber resilience.</p><p>#CyberSecurity #SecurityResearch #ThreatIntelligence #DigitalIdentity #TelecomSecurity #Privacy #WhatsApp #NIN #InformationSecurity #CyberAwareness #Nigeria #DataProtection</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=601a6f0057aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>