<?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 Hyunjae on Medium]]></title>
        <description><![CDATA[Stories by Hyunjae on Medium]]></description>
        <link>https://medium.com/@hjkim6321?source=rss-4bffd1fb69a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*B2hy9tPWFCsQeQjc</url>
            <title>Stories by Hyunjae on Medium</title>
            <link>https://medium.com/@hjkim6321?source=rss-4bffd1fb69a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:11:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hjkim6321/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[Linux Administration: Umask and Special Permissions (SetUID, SetGID, Sticky Bit)]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-umask-and-special-permissions-setuid-setgid-sticky-bit-3ee87ad04eca?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ee87ad04eca</guid>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Thu, 20 Aug 2026 17:13:29 GMT</pubDate>
            <atom:updated>2026-08-20T17:13:29.623Z</atom:updated>
            <content:encoded><![CDATA[<p>In this guide, we will cover <strong>umask</strong>, which manages default file and directory creation permissions. We will also explore three special permissions that can be applied to files and directories: <strong>SetUID</strong> (4000), <strong>SetGID</strong> (2000), and <strong>Sticky Bit</strong> (1000).</p><h3>Checking and Setting Umask</h3><p>umask controls default permissions applied when creating new files and directories.</p><p>Checking the current umask setting using the umask command shows a default value of 0022. This means new files inherit permissions of 644 (calculated as 666 base permission minus 022 umask), and new directories inherit 755 (calculated as 777 base permission minus 022 umask).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/0*aWBySwMbXFsDxP0A" /><figcaption>Checking umask and default file/directory permissions</figcaption></figure><p>Now, set the umask using umask 0424 so that newly created files default to 242 and directories to 353. Creating new files and directories confirms that the updated permissions are applied.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/0*a5PX8MoYgYMDrcPg" /><figcaption>Setting umask and testing creation</figcaption></figure><h3>Configuring SetUID Special Permission</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/0*ctITApjUy1tiKX9f" /><figcaption>Installing GCC compiler package</figcaption></figure><p>The <strong>SetUID</strong> (4000) special permission allows an executable file to run with the privileges of the file owner rather than the user executing it.</p><p><strong>Note:</strong> While SetUID can technically be applied to directories, Linux ignores it because creator ownership enforcement prevents users from creating files on behalf of others.</p><p>First, as the root user, write a C program file named suid_test.c and compile it using gcc suid_test.c -o suid_test. If gcc is not installed, install it using dnf -y install gcc before compiling.</p><p><strong>Note:</strong> Linux ignores SetUID permissions on Bash scripts, so a compiled C executable is used here instead.</p><p>Switch to the centos user and run the executable. Both the real UID and effective UID show as centos (1000).</p><p>Now, grant SetUID permission using chmod u+s suid_test (or chmod 4xxx suid_test) and run the file again as the centos user. While the real user remains centos (1000), the effective user changes to root (0).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9sVb0Azm0NOl1hW92MkU3A.png" /><figcaption>Creating and compiling C program file</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/491/0*7hQBhzs6RvYQ_itQ" /><figcaption>Executing as centos user</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yoyx9-R2WkE4T8qT0Ha1lg.png" /><figcaption>Setting SETUID permission and testing execution</figcaption></figure><h3>Configuring SetGID Special Permission</h3><p>The <strong>SetGID</strong> special permission executes a file with the privileges of the owning group rather than the running user’s primary group.</p><p>Create a C file named sgid_test.c in /usr/local/bin and compile it with gcc sgid_test.c -o sgid_test. Switch to the centos user and run the program; both the real GID and effective GID match as centos (1000).</p><p>Now, apply SetGID permission using chmod g+s sgid_test (or chmod 2xxx sgid_test) and execute the file again as the centos user. The effective group ID changes to the root (0) group.</p><p><strong>Note:</strong> Unlike SetUID, when SetGID is applied to a directory, any new files or subdirectories created inside it inherit the group ownership of the directory rather than the primary group of the user creating them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FM9WJYFVPyczaXzcLT0Rsg.png" /><figcaption>Creating and compiling C program file</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/0*UD7xE0W2v30TLfYG" /><figcaption>Executing as centos user</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yRQ3Q15c9btZJoPhgj7rXQ.png" /><figcaption>Setting SetGID permission and testing execution</figcaption></figure><h3>Configuring Sticky Bit Special Permission</h3><p>The <strong>Sticky Bit</strong> special permission prevents users from deleting or renaming files within a directory unless they are the file owner, directory owner, or root user.</p><p>First, create a directory named /sticky_dir and a file named sticky_file inside it. Grant write permissions to others so external users can modify, rename, or delete files inside. Switch to the centos user and delete sticky_file to confirm that deletion works as expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dWxweb-o3t5m3M4S8f3fRg.png" /><figcaption>Creating directory and file, granting others write permissions, and deleting file</figcaption></figure><p>Now, grant Sticky Bit permission to /sticky_dir using chmod +t sticky_dir (or chmod 1xxx sticky_dir). Switch back to the centos user and attempt to delete the file again; the deletion attempt is denied.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iah2SINP4jPM8-vLPr_puw.png" /><figcaption>Applying Sticky Bit permission and testing deletion</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ee87ad04eca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: wget and curl Commands]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-wget-and-curl-commands-5a6c4ec7b1bf?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a6c4ec7b1bf</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[curl]]></category>
            <category><![CDATA[sysadmin]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Wed, 19 Aug 2026 15:29:52 GMT</pubDate>
            <atom:updated>2026-08-19T15:30:23.970Z</atom:updated>
            <content:encoded><![CDATA[<p>In this guide, we will cover wget and curl, two command-line utilities used for downloading data from the web.</p><p>The difference between the two lies in their core capabilities: wget is a non-interactive, one-way downloader capable of recursive downloads, making it ideal for retrieving large files or downloading entire websites. On the other hand, curl supports bidirectional data transfer, making it better suited for uploading data or testing APIs like REST services, while offering more flexible functionality.</p><h3>Downloading Files with wget</h3><p>First, check whether the wget package is installed using the rpm -q wget command. If it is not installed, install it with dnf -y install wget.</p><p>Next, navigate to https://www.gimp.org/downloads, right-click the <strong>Download directly</strong> button, and click <strong>Copy Link</strong> to copy the download URL for GIMP, an open-source image editor.</p><p>Now, download the installation file using the wget -O GIMP-3.0.8.AppImage &lt;download_link&gt; command, and verify that the file has been downloaded successfully using the ls -l command.</p><p><strong>Note:</strong> Here, the -O option renames the downloaded file to GIMP-3.0.8.AppImage. There are various other options available, which you can check using the wget --help command. To highlight a few:</p><ul><li>-c: Resumes an interrupted download (If the server supports this capability).</li><li>-i: Reads URLs from an input file to perform downloads.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*4Ymg-dxhbdj5E1-P0XEI_g.png" /><figcaption>GIMP Image Editor</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y73hfve43yXzUBcB" /><figcaption>Using wget command</figcaption></figure><h3>Using the curl Command</h3><p>Next, let’s download the website https://kernel.org as an index.html file using the curl -o index.html https://kernel.org command.</p><p>Move the file to the Apache web server directory using the mv index.html /var/www/html command, and modify the SELinux file context using the semanage fcontext -a -t httpd_sys_content_t index.html and restorecon index.html commands.</p><p>Finally, restart the Apache service using the systemctl restart httpd command and test it in a browser to confirm that the website loads properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/0*bGI-KU1fw7Z9RYdh" /><figcaption>Using curl command</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/0*ANYs0iKVnU8hH6AH" /><figcaption>Configuring Apache web server and changing SELinux file context</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uQPetz0KH44h5PBu6XoSbw.png" /><figcaption>Restarting service and testing access</figcaption></figure><h3>Testing REST APIs with curl</h3><p>As mentioned earlier, curl supports bidirectional communication, making it well-suited for testing APIs. Since testing an actual API requires setting up an API server, we will use a hypothetical REST API endpoint at https://school.com/api/students for reference examples only.</p><p>The examples below demonstrate how to test the four core functions of a REST API — <strong>GET</strong> (Read), <strong>POST</strong> (Create), <strong>PUT</strong> (Update), and <strong>DELETE</strong> (Delete) — using the curl command.</p><pre># GET(Read)<br># Multiple<br>curl https://school.com/api/students<br><br># Single<br>curl https://school.com/api/students/1<br><br># POST(Create)<br>curl -X POST https://school.com/api/students/create \<br>     -d &#39;{ &quot;name&quot; : &quot;Ryan&quot;, &quot;age&quot; : &quot;15&quot; }&#39; \<br>     -H &quot;Content-Type: application/json&quot;<br><br># PUT(Update)<br>curl -X PUT https://school.com/api/students/update/25 \<br>     -d &#39;{ &quot;name&quot; : &quot;James&quot;, &quot;age&quot; : &quot;17&quot; }&#39; \<br>     -H &quot;Content-Type: application/json&quot;<br><br># DELETE(Delete)<br>curl -X DELETE https://school.com/api/students/delete/25</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a6c4ec7b1bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: IP Forwarding and Port Forwarding]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-ip-forwarding-and-port-forwarding-36d049889c84?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/36d049889c84</guid>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Mon, 10 Aug 2026 09:07:02 GMT</pubDate>
            <atom:updated>2026-08-10T09:07:02.059Z</atom:updated>
            <content:encoded><![CDATA[<p>While <strong>IP Forwarding</strong> and <strong>Port Forwarding</strong> sound similar, they represent distinct networking concepts.</p><p>IP Forwarding refers to the process of transmitting traffic between different networks, typically performed by network devices such as routers. In contrast, Port Forwarding utilizes Network Address Translation (NAT) technology to map external traffic coming into a router or host to a specific device on a private network.</p><p>In this guide, we will cover how to enable IPv4 and IPv6 forwarding (which is disabled by default in Linux) and walk through a practical Port Forwarding setup using a virtual machine environment.</p><h3>Enabling IP Forwarding</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/0*n57Blm-EJgxtl4IY" /><figcaption>IP Forwarding</figcaption></figure><p>By default, IP forwarding is disabled in Linux, so you must explicitly enable it to route packets between interfaces.</p><p>The configuration for IP forwarding resides in /etc/sysctl.conf. Open this file and add the required settings to permit routing across different networks for both IPv4 and IPv6.</p><p>After editing, apply the changes immediately using sysctl -p to activate IP forwarding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mjCor7HqAv1CI8M1JlopBg.png" /><figcaption>Enabling IP forwarding</figcaption></figure><h3>Configuring Port Forwarding</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/0*v4re3Ode6WrYtu0h" /><figcaption>Port Forwarding</figcaption></figure><p>To test Port Forwarding, first set up a simple web server and allow the HTTP service through firewalld.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d_25QPk6o0gesMKlf5TI1A.png" /><figcaption>Web server and firewall configuration</figcaption></figure><p>For this demonstration, we will configure Port Forwarding using <strong>VMware Workstation Pro</strong>:</p><p>Open VMware Workstation Pro, navigate to <strong>Edit &gt; Virtual Network Editor</strong>, and click <strong>Change Settings</strong> to grant administrative privileges. Select the active virtual network, then click <strong>NAT Settings &gt; Add</strong>. Map an external port (e.g., 8080) to the private IP address and port (80) of the web server created earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ldFllrW-6GhTecMI" /><figcaption>Port forwarding configuration</figcaption></figure><p>Next, allow external traffic through the host machine’s firewall. On the Windows host system, open <strong>Control Panel &gt; System and Security &gt; Windows Defender Firewall</strong> and click <strong>Advanced Settings</strong>.</p><p>Create a new <strong>Inbound Rule</strong>, select <strong>Port</strong>, enter port number 8080, leave the remaining options at their defaults, and assign a rule name to complete the configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIhwAIwPedhk2nMxyp2E6w.png" /><figcaption>External PC firewall configuration</figcaption></figure><p>Now, entering the host PC’s IP address along with the designated external port number (8080) in a browser allows access to the internal web server running inside the virtual machine.</p><p><strong>Note:</strong> In a production environment, you would connect via the router’s public IP address. In this setup, since the virtual machine runs locally on the same host, requests are directed to the host PC’s local IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/0*xQCor-y93eEfvvLk" /><figcaption>Accessing the web server</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36d049889c84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: LVM Thin Provisioning]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-lvm-thin-provisioning-e43c677d8f6d?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e43c677d8f6d</guid>
            <category><![CDATA[lvm]]></category>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Sun, 09 Aug 2026 11:01:37 GMT</pubDate>
            <atom:updated>2026-08-09T11:01:37.489Z</atom:updated>
            <content:encoded><![CDATA[<p>In this guide, we will cover <strong>Thin Provisioning</strong>, a method in LVM that dynamically allocates disk space on demand through a thin pool rather than statically reserving storage space directly from a volume group. This approach prevents storage waste caused by over-allocation and improves overall disk utilization efficiency.</p><h3>Configuring Thin Provisioned Volumes</h3><p>First, add a new hard drive to the system. Create an LVM partition using fdisk /dev/sdb, and then build a physical volume on top of it using pvcreate /dev/sdb1. Next, create a volume group named new_vg using vgcreate new_vg /dev/sdb1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MQMtvHs14N9XqxJBJ58nzA.png" /><figcaption>Creating partition and LVM physical volume</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/0*O9MRsMlJVzKOW7wf" /><figcaption>Creating volume group</figcaption></figure><p>Now, create a 2GB thin pool named thin_pool using lvcreate --type thin-pool -L 2G -n thin_pool new_vg.</p><p>Then, create a thin provisioned volume named new_lv using the newly created thin pool with lvcreate -V 500M new_vg/thin_pool -n new_lv.</p><p><strong>Note:</strong> Notice that while the new_lv logical volume shows a virtual size of 500MB, the data usage indicator inside thin_pool remains at 0%. This demonstrates that storage is not pre-allocated immediately to the logical volume, but is instead provisioned dynamically as data is written.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/0*uoicOeRPIHm0rNJv" /><figcaption>Creating Thin Pool and Thin Provisioned Volume</figcaption></figure><p>Finally, create an ext4 file system on the thin volume, create a mount point directory named /thin_data, and mount the volume. Add the file system entry to /etc/fstab for persistent mounting upon boot, and verify the mount status using df -h.</p><p><strong>Note:</strong> If you are interested in an alternative tool, you can also look into <strong>Stratis</strong>, which allows you to set up thin provisioned volumes even more easily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/0*xMBzcKOhuVz0ee0Y" /><figcaption>Creating file system and mount point</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/0*agLcKocGLT-3I7oy" /><figcaption>Mounting file system</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/0*u_XefjhRS3rc0O3B" /><figcaption>/etc/fstab configuration</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e43c677d8f6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: RAID Configuration (RAID 1, RAID 5)]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-raid-configuration-raid-1-raid-5-de9bee531eb1?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/de9bee531eb1</guid>
            <category><![CDATA[raid]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Sat, 08 Aug 2026 15:01:10 GMT</pubDate>
            <atom:updated>2026-08-08T15:01:10.281Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/477/0*4IHLV0oTKQfAxfFi" /><figcaption>VMWARE Workstation</figcaption></figure><p>In this guide, we will cover how to configure RAID (Redundant Array of Independent Disks), which combines multiple physical hard drives into a single logical storage unit. RAID can be configured in various ways depending on your needs. Here, we will walk through setting up the commonly used RAID 1 and RAID 5 configurations.</p><h3>Installing RAID Management Package (mdadm)</h3><p>First, install the mdadm package, which is required for configuring and managing RAID arrays, by running dnf -y install mdadm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1xY7fkoORgnKbJzk" /><figcaption>Installing mdadm package</figcaption></figure><h3>Configuring RAID 1</h3><p>RAID 1 mirrors identical data across different disks. Because the same data is saved across multiple drives, data remains preserved even if one disk fails. However, since data is duplicated, available storage space is reduced to 50% of the total capacity, making it less space-efficient.</p><p>First, add two hard drives to the system and create a partition of type raid on each drive as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xkYUK_9_j9zSFSKNR_d-ng.png" /><figcaption>Creating RAID partitions</figcaption></figure><p>Next, build the RAID 1 array using the created partitions with mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdb1 /dev/sdc1. Once created, inspect the active RAID array using mdadm --detail --scan.</p><p>Create an ext4 file system on the array using mkfs.ext4 /dev/md1, create a mount point directory /raid1, and mount the device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/0*QUbNK5Zw7Th5ndfe" /><figcaption>Configuring and verifying RAID 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/0*zRYiLA1HH_tPsFTQ" /><figcaption>Creating file system and mounting</figcaption></figure><p>Finally, register the RAID array in /etc/fstab so that it mounts automatically on boot. For RAID arrays, registering by device name can cause mount failures if device identifiers change during boot. Therefore, use the device&#39;s UUID (Universally Unique Identifier) instead.</p><p>Check the UUID of /dev/md1 using blkid /dev/md1. Open /etc/fstab, add the entry as shown below, and save the file. After rebooting the system, verify that the file system is properly mounted using df -h.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/0*eeD08eoT48VZGu-p" /><figcaption>Checking UUID</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/0*9xJ6EElME-pQOy_5" /><figcaption>/etc/fstab configuration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/0*HXwyCpSRRxHgJGSP" /><figcaption>Verifying mount status</figcaption></figure><h4>Configuring RAID 5</h4><p>RAID 5 requires three or more disks and distributes parity information across all drives in a round-robin fashion, allowing data recovery if a single disk fails. Because parity is distributed alongside data, usable storage efficiency is calculated as (N — 1) / N, where N is the number of disks. Adding more disks increases overall space efficiency while maintaining fault tolerance against single-disk failures.</p><p>First, add three hard drives to the system and create a partition of type raid on each drive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SKsRx52LAlhv_uZ1bYgbvg.png" /><figcaption>Creating RAID partitions</figcaption></figure><p>Build the RAID 5 array using mdadm --create /dev/md5 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1, and verify the configuration using mdadm --detail --scan.</p><p>Create an ext4 file system using mkfs.ext4 /dev/md5 and mount it to the /raid5 mount point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/0*DoAmAPyBsdxXtARz" /><figcaption>Configuring and verifying RAID 5</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/0*pj5qLQ5jQcqQ-IS0" /><figcaption>Creating file system and mounting</figcaption></figure><p>Finally, check the UUID of the RAID device and add it to /etc/fstab as shown below for persistent mounting on boot. After rebooting, run df -h to confirm the array mounts automatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/0*Wqi4JmdDV8G6f9Q4" /><figcaption>Checking UUID</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*YXqHW6QgmUVYcQXH" /><figcaption>/etc/fstab configuration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/0*o4nEumD6_L05cZb2" /><figcaption>Verifying mount status</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de9bee531eb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: Managing SELinux Contexts, Port Labels, and Restoring File Contexts]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-managing-selinux-contexts-port-labels-and-restoring-file-contexts-11749d0b8f56?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/11749d0b8f56</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[selinux]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Wed, 05 Aug 2026 14:26:00 GMT</pubDate>
            <atom:updated>2026-08-05T14:26:00.829Z</atom:updated>
            <content:encoded><![CDATA[<p>In this guide, we will cover how to inspect SELinux security contexts — labels applied to files and processes that enable SELinux to make access control decisions. In addition, We will also look at how to manage SELinux port labels and how to restore file contexts back to their default values.</p><h3>Inspecting File and Process Contexts</h3><p>File and process contexts are labels added to files, directories, and processes so that SELinux can make security-related decisions. A context consists of four components: <strong>user</strong>, <strong>role</strong>, <strong>type</strong>, and <strong>level</strong>, among which the third component, <strong>type</strong>, is considered the most critical.</p><p>First, as shown in the example below, checking the type of the index.html file context using the ls -Z /var/www/html/index.html command shows httpd_sys_content_t. This means it is web content used by the Apache web server.</p><p><strong>Note:</strong> If you want to check the file context policies applied to each file and directory, you can use the semanage fcontext -l command.</p><p>Next, using the ps -eZ command allows you to view the process context for all processes. Additionally, if you want to check the context of a specific process, you can use the ps -Zp &lt;PID&gt; command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AJxugSHCGPMqQbqOTOc95A.png" /><figcaption>Checking file context</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FhnHbd8WqinPLeQoAtQKNQ.png" /><figcaption>Checking process context</figcaption></figure><h3>Managing Port Labels</h3><p>Port labels are security contexts assigned to network port numbers, specifying which services are permitted to bind to specific ports. For example, inspecting the ssh_port_t type using semanage port -l shows that the SSH service is configured to use port 22.</p><p>If you edit /etc/ssh/sshd_config to change the SSH port from 22 to 2222 and attempt to restart the service with systemctl restart sshd, an error occurs and the service fails to start. This happens because port 2222 has not been added to the SSH port label.</p><p>To resolve this, add port 2222 to the ssh_port_t label using semanage port -a -t ssh_port_t -p tcp 2222, then restart the service with systemctl restart sshd. The SSH service will now start without any issues.</p><p><strong>Note:</strong> To allow external traffic through the new SSH port, you must also allow port 2222 in FirewallD using firewall-cmd --permanent --add-port=2222/tcp and apply the changes with firewall-cmd --reload.</p><p>Additionally, if you remove port 2222 from the port label using semanage port -d -p tcp 2222 and restart sshd once again, the service will fail to start as expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/0*1NfPAuTQguNXJoWq" /><figcaption>Checking port labels</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4EnLFz1cmRfbZs2m5xSfaA.png" /><figcaption>Changing SSH service port configuration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sT4vHkRgz7oHt5FSlHpdaQ.png" /><figcaption>Modifying port label, restarting service and updating firewall</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/0*NogN_QnOXpu6KgFE" /><figcaption>Deleting port from port label</figcaption></figure><h3>Restoring File Contexts</h3><p>When modifying file contexts, custom policy settings may sometimes cause issues, requiring you to revert changes back to their default state. In such cases, delete the newly added custom policy using semanage fcontext -d &lt;file_or_directory&gt;, and then restore the default context values using restorecon -v &lt;file_or_directory&gt;.</p><p><strong>Note:</strong> The -v flag displays the restoration process on the screen. For directories, include the -R option (restorecon -vR &lt;directory&gt;) to recursively restore contexts for all files and subdirectories within that directory.</p><p>If you wish to restore the context of all files and directories across the entire system to their defaults, remove any added context configurations, create a hidden flag file with touch /.autorelabel, and reboot the system.</p><p>While you could manually restore all contexts using restorecon -v -R /, this method is not recommended as it takes a significant amount of time and can adversely affect services currently running on the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*esHjCkUTPcET34davD1O4w.png" /><figcaption>Modifying and restoring file contexts</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/0*M_Cn8uyjva9U1KcU" /><figcaption>Restoring full-system file contexts via autorelabel</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11749d0b8f56" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: Changing SELinux Modes and Configuring Booleans]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-changing-selinux-modes-and-configuring-booleans-b886c37a9f79?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b886c37a9f79</guid>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[selinux]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Sun, 02 Aug 2026 01:21:05 GMT</pubDate>
            <atom:updated>2026-08-02T01:21:05.694Z</atom:updated>
            <content:encoded><![CDATA[<p>In this guide, we will cover how to switch SELinux mode from <strong>Enforcing</strong> (which blocks actions that violate security policies) to <strong>Permissive</strong> (which allows policy violations while logging them). Additionally, we will explore how to manage SELinux <strong>Booleans</strong>, which allow dynamically turning security policy rules on or off like a toggle switch.</p><h3>Changing SELinux Mode (Enforcing -&gt; Permissive)</h3><p>By default, SELinux runs in <strong>Enforcing</strong> mode, denying access when a security policy is violated. However, when troubleshooting system issues, switching to <strong>Permissive</strong> mode helps determine whether SELinux is causing the problem without actually blocking operations.</p><p><strong>Note:</strong> Permissive mode still logs policy violations. If you wish to completely deactivate SELinux, set the mode to disabled.</p><p>First, check the current SELinux status using sestatus. It should indicate Current mode: enforcing.</p><p>Next, open /etc/selinux/config and update the setting to SELINUX=permissive.</p><p>Because modifying the config file does not change the active mode immediately, execute setenforce 0 to apply Permissive mode instantly.</p><p><strong>Note:</strong> To switch back to Enforcing mode at runtime, run setenforce 1.</p><p>Finally, run sestatus again to confirm that the current mode has changed to permissive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/0*J3Qva609Dyn2hh5h" /><figcaption>Checking SELinux status</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UnhJnEBnJZFAzw1U_FTHcA.png" /><figcaption>Changing SELinux mode</figcaption></figure><h3>Configuring SELinux Booleans</h3><p>SELinux Booleans allow you to dynamically alter security policy behavior at runtime without modifying policy files.</p><p>To inspect available Booleans and their current states, run getsebool -a.</p><p>For instance, notice that httpd_use_nfs is set to off by default, preventing the Apache HTTP Server (httpd) from accessing files stored on an NFS mount. Let&#39;s demonstrate this behavior with a hands-on setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/0*ILO0Gud-gxNja3pZ" /><figcaption>Checking SELinux Booleans</figcaption></figure><p><strong>1. NFS Server Configuration</strong></p><p>Install the NFS utilities package using dnf -y install nfs-utils, then start and enable the service with systemctl start nfs-server and systemctl enable nfs-server.</p><p>Create a directory named /nfs_share and update its permissions to 755. Add the directory export configuration to /etc/exports, then apply it using exportfs -rv.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RC2M7llZHIN5wO2BC0WafQ.png" /><figcaption>Installing NFS packages and starting service</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/461/0*-J_j8vYxXGTwObs4" /><figcaption>Creating NFS share directory</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2fTimmLJGwiCHzeHM0ab3w.png" /><figcaption>Configuring NFS file system export</figcaption></figure><p><strong>2. Apache Web Server Configuration</strong></p><p>Install the Apache Web Server using dnf -y install httpd, then start and enable the service using systemctl start httpd and systemctl enable httpd.</p><p>Mount the NFS share onto the web root using mount -t nfs 127.0.0.1:/nfs_share /var/www/html, and create a simple index.html file inside /var/www/html.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TU8X3l2okCY_C1ai_TZlaA.png" /><figcaption>Installing httpd package and starting service</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hsZ5NUdHVBuiyxvz4z7QLA.png" /><figcaption>Mounting NFS directory and setting up web server</figcaption></figure><p><strong>3. Enabling </strong><strong>httpd_use_nfs Boolean</strong></p><p>Attempting to access the web server via http://localhost in a browser will fail because the SELinux policy blocks httpd from accessing NFS mounts.</p><p>To grant access, enable the Boolean persistently using setsebool -P httpd_use_nfs on.</p><p><strong>Note:</strong> The -P flag applies the setting permanently across system reboots.</p><p>After enabling the Boolean, refreshing the page demonstrates that the web server can now successfully render the page from the NFS share.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/0*8zgr5A2fmHLt5yhi" /><figcaption>Access before enabling Boolean</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*azjURwIyncFE0a2mWVJEGA.png" /><figcaption>Access after enabling Boolean</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b886c37a9f79" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: Flatpak Setup, Package Installation, and Uninstallation.]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-flatpak-setup-package-installation-and-uninstallation-7b81feed96a3?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b81feed96a3</guid>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[flatpak]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Sat, 01 Aug 2026 14:27:52 GMT</pubDate>
            <atom:updated>2026-08-01T14:27:52.421Z</atom:updated>
            <content:encoded><![CDATA[<p>In Linux, package installation traditionally relies on distribution-specific package managers — such as apt on Debian-based systems or yum/dnf on Fedora-based distributions. However, using Flatpak allows you to install and manage applications across different Linux distributions using a single unified workflow.</p><p>In this guide, we will cover how to install Flatpak (a universal package manager), add the Flathub repository, and search, install, launch, and uninstall applications using Flatpak commands.</p><h4>Flatpak Configuration</h4><p>First, install the Flatpak package by executing dnf -y install flatpak.</p><p>Next, add the Flathub remote repository to enable downloading packages using flatpak remote-add — if-not-exists flathub <a href="https://dl.flathub.org/repo/flathub.flatpakrepo">https://flathub.org/repo/flathub.flatpakrepo</a> command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*e0KASbL9oF2b5P7x" /><figcaption>Installing Flatpak</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*7AoF2U7lBLjmvnbK" /><figcaption>Adding Flathub repository</figcaption></figure><h4>Managing Packages (Search, Install, Run, Uninstall)</h4><p>First, search for an application (e.g., Slack) in the Flathub repository using flatpak search slack.</p><p><strong>Note:</strong> Flatpak supports both <strong>system mode</strong> (accessible by all users, which is the default) and <strong>user mode</strong> (accessible only by the installing user). To install or remove packages in user mode, append the --user flag to your command.</p><p>To install Slack, run flatpak install flathub com.slack.Slack.</p><p>Once the installation completes, launch the application to verify it functions properly. Afterwards, you can remove it using flatpak uninstall com.slack.Slack.</p><p><strong>Note:</strong> If you wish to clear application configuration and user data during uninstallation, append the --delete-data option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bRYrcbf1fqSYWNJI_PsrIA.png" /><figcaption>Searching, installing and running Flatpak packages</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/0*rFtf_kgXYWN7Pbxm" /><figcaption>Uninstalling Flatpak packages</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b81feed96a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: NFS (Network File System) and Autofs Configuration]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-nfs-network-file-system-and-autofs-configuration-a1cb034592ab?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1cb034592ab</guid>
            <category><![CDATA[fn]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 17:28:38 GMT</pubDate>
            <atom:updated>2026-07-31T17:28:38.588Z</atom:updated>
            <content:encoded><![CDATA[<p>In this guide, we will look at how to set up and use an NFS (Network File System) server to share directories across systems over a network. Additionally, we will cover how to configure autofs on an NFS client to automatically mount and unmount shared directories on demand.</p><h3>NFS (Network File System) Server Setup</h3><p>First, install the nfs-utils package, which contains the configuration tools for NFS, by executing dnf -y install nfs-utils. Then, start and enable the NFS service so that it runs automatically on boot using systemctl start nfs-server and systemctl enable nfs-server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UbDbJPdKnmkes5pbNWf8ig.png" /><figcaption>Installing, starting and enabling NFS</figcaption></figure><p>Next, create a directory to share externally using mkdir /exports, and create a sample file inside it using touch /exports/test_file.</p><p>Open the NFS configuration file at /etc/exports and add the entry as shown in the example below to export the /exports directory.</p><p><strong>Note:</strong> Using * for the IP address allows access from any host. The rw option grants read and write permissions, sync ensures changes are written to disk immediately, and no_root_squash preserves root privileges for the client&#39;s root user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZdZofYOWAiS7qocStVUejw.png" /><figcaption>Creating share directory and configuring NFS server</figcaption></figure><p>Finally, export the shared directory using exportfs -rv, and allow NFS traffic through the firewall.</p><p><strong>Note:</strong> Allowing rpc-bind and mountd services in the firewall is necessary for clients to inspect available NFS shares using the showmount command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tXFcvG8zKDO2TiHJxoszFQ.png" /><figcaption>Exporting NFS share and firewall setup</figcaption></figure><h4>NFS Client Configuration</h4><p>On the client machine, install the NFS client package using dnf -y install nfs-utils. Next, inspect the exported shares available on the NFS server by running showmount -e &lt;NFS_SERVER_IP&gt;. You should see the /exports directory configured earlier.</p><p>Now, create a mount point directory using mkdir /mnt/nfs, and mount the NFS share using mount &lt;NFS_SERVER_IP&gt;:/exports /mnt/nfs. Additionally, add the entry to /etc/fstab as shown below to ensure persistent mounting on boot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rf0XfS-QmnNHL1hjOigPbQ.png" /><figcaption>Inspecting and mounting NFS share</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/0*w4LQzJ0wZIdWaVGc" /><figcaption>Configuring persistent mount on boot</figcaption></figure><p>Navigate to the /mnt/nfs directory and execute ls -l to verify that test_file created on the server is visible. You can also test write access by creating a new file with touch new_file and checking if it appears on the NFS server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tbeCfpQOIxiFdrjFUH5Q-Q.png" /><figcaption>Verifying and creating files</figcaption></figure><h3>Autofs Configuration</h3><p>autofs is an automounting service that dynamically mounts NFS shares on the client when accessed and unmounts them after a period of inactivity.</p><p>First, unmount the existing NFS directory using umount /mnt/nfs, and install the package using dnf -y install autofs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*JleOVAhsA3BamR5qEepYbQ.png" /><figcaption>Unmounting NFS share and installing autofs</figcaption></figure><p>Open /etc/auto.master and add /mnt/nfs /etc/auto.nfs --ghost --timeout=60 at the end of the file to direct autofs to map shares defined in /etc/auto.nfs under /mnt/nfs.</p><p><strong>Note:</strong> The --ghost option creates empty placeholder directories so users can see mount points even when unmounted. The --timeout=60 option automatically unmounts the NFS share after 60 seconds of inactivity.</p><p>Next, create /etc/auto.nfs and add the map configuration so the client mounts the NFS share on demand, then restart the service using systemctl restart autofs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*Z4BjcO2-Wh929ILV4HqDSA.png" /><figcaption>/etc/auto.master and /etc/auto.nfs configuration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/0*Z5-txS-GyyCbpddZ" /><figcaption>Restarting autofs service</figcaption></figure><p>Now, access the mount point using ls -l /mnt/nfs/exports, and verify with df -h to see that the NFS directory has been mounted automatically. Because the timeout was set to 60 seconds, running df -h again after one minute will confirm that the share has automatically unmounted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uBZ3nk4oyWAHhdpbsWp1tg.png" /><figcaption>Autofs automatic mounting and unmounting</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1cb034592ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration: Configuring and Using an FTP Server]]></title>
            <link>https://medium.com/@hjkim6321/linux-administration-configuring-and-using-an-ftp-server-af066fbc9b54?source=rss-4bffd1fb69a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/af066fbc9b54</guid>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[red-hat]]></category>
            <category><![CDATA[ftp]]></category>
            <dc:creator><![CDATA[Hyunjae]]></dc:creator>
            <pubDate>Sun, 26 Jul 2026 02:24:54 GMT</pubDate>
            <atom:updated>2026-07-26T02:24:54.082Z</atom:updated>
            <content:encoded><![CDATA[<p>In this guide, we will cover how to install and configure vsftpd, an FTP (File Transfer Protocol) server package in Linux. We will also install the ftp client package on a client machine to test downloading and uploading files.</p><h3>FTP (File Transfer Protocol) Server Configuration</h3><p>First, let’s install the FTP server package by executing dnf -y install vsftpd.</p><p>The primary configuration file for vsftpd is located at /etc/vsftpd/vsftpd.conf. For this setup, leave anonymous login disabled while keeping local user access enabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4rTJUTFbM4ygahtu" /><figcaption>Installing vsftpd</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/0*Xh-LgSaGIDy1D1y2" /><figcaption>/etc/vsftpd/fsftpd.conf</figcaption></figure><p>Next, start and enable the service so it automatically runs on boot using systemctl start vsftpd and systemctl enable vsftpd.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/0*D3Tg51n40AjMzcFS" /><figcaption>Starting and enabling vsftpd service</figcaption></figure><p>Then, allow external FTP connections through the firewall using firewall-cmd --permanent --add-service=ftp followed by firewall-cmd --reload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/0*gzdq7YK8npbRkZM6" /><figcaption>Firewall configuration</figcaption></figure><h3>Client Connection and File Transfer Testing</h3><p>Now, on a separate Linux client machine, install the FTP client package using dnf -y install ftp and verify the connection with ftp &lt;SERVER_IP&gt;.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*agswNX3hFxvFEvN9" /><figcaption>[Client] Installing ftp package</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/0*kizNlBmq4S6NP9SB" /><figcaption>[Client] Connecting to FTP server</figcaption></figure><p>Once logged in via FTP, download a file named test_file from the rhel user&#39;s home directory to the client using the get test_file command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*poJ7NpYMM8rVC7A8BJIimQ.png" /><figcaption>[Client] Downloading a file</figcaption></figure><p>Next, create a new file locally using touch upload_file. Upload this file to the rhel user&#39;s home directory on the server using put upload_file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gcE_eX6Y5PGbFIK0c7c5Vw.png" /><figcaption>[Client] Uploading a file</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af066fbc9b54" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>