Видео

The issue started because the partition (nvme1n1p1) had a corrupted superblock. When the superblock is corrupted, the system can't correctly recognize the partition's file system. In this case, instead of recognizing it as an XFS file system (which it was supposed to be), it mistakenly showed up as swap. This misidentification happened because the corruption made the file system unreadable or caused the system to fall back on a default assumption, which was swap in this case. When I ran xfs_repair, it scanned the partition, found the corrupted superblock, and fixed it. Once the superblock was repaired, the system could correctly identify the partition as XFS again, just like it was supposed to be. So, the partition wasn't actually meant to be swap it was just showing up that way because of the corruption. Running xfs_repair fixed the corruption and restored the partition to XFS, which is why everything worked after the repair.

@@ProfessorLinux thank you for the detailed explanation. It surely helped me understand better the intricate works of lsblk and xfs_repair. If you don't mind another question: let's say you didn't know it was supposed to be XFS, how would you do you find out it was supposed to be XFS and not SWAP? Thank you again.

@@NoskPur If I didn’t know the partition was supposed to be XFS, there are a few things I would do to figure it out. First, I would check the /etc/fstab file. This file lists what each partition should be mounted as, so if it says XFS in there, then the system expects the partition to be XFS, not swap. Another step is to use the file command to identify the file system type. Running this on the partition would tell you if it’s actually formatted as XFS, swap, or something else. Additionally, I’d check the partition table using tools like gdisk or fdisk. These tools show the original partition type, which could provide another clue about what the partition was meant to be. That said, if the disk is corrupted, it’s important to keep in mind that things can be misleading, and the file system might not show up correctly due to the corruption. To be completely sure, I would look at any external company documentation that describes how the partition should have been set up. If it’s an environment you didn’t configure yourself, you might need to consult whoever initially set it up. This way, you can be confident you’re restoring the partition to its correct state, especially in cases where the corruption might mislead tools like lsblk.

I planned to recreate it. Is there a specific part you need help with so I can upload a video for you.

@@ProfessorLinux Hi Prof, if possible cover all please. This video is very informative as it goes straight to the answer but will need your guidance on some explanation voice over to understand it better. Thanks Prof!

@@jesusblanca3246 I will work on it

Yes which one would you like?

You're welcome!

unix.stackexchange.com/questions/128953/how-to-display-top-results-sorted-by-memory-usage-in-real-time

You can try to manually delete it , after install dig . sudo yum remove bind-libs-lite

Yes , I will be working on one.

Linux takes 15 seconds

Not exactly but based on the RH342 exam.

1. CTRL-C to Exit Programs: - Pressing CTRL-C in a terminal interrupts the currently running process. It sends a SIGINT (Interrupt) signal to the program, prompting it to terminate gracefully. This is a common way to stop a process or program in a terminal. 2. Exiting top with Q: - In the top command, pressing the Q key allows you to exit the program and return to the command prompt. It stops the real-time monitoring of system processes. 3. Clearing the Screen: - To clear the terminal screen, you can use either of the following methods: - Press CTRL-L. - Type the clear command and press Enter. - Both methods achieve the same result, providing you with a clean terminal screen for better visibility.

INE LABS - SETUID EXPLOIT

It's a command-line tool used in Unix-based systems (like Linux) for querying DNS (Domain Name System) servers. Essentially, dig helps retrieve information about domain names, such as IP addresses associated with specific domains, DNS record types, name servers, and other domain-related information. It's commonly utilized to troubleshoot networking issues, check DNS configurations, and gather details about domain setups.

Thank you!

Will work on a video. For Buildah

Sure, here are some of the main commands for Podman and Buildah with explanations: PODMAN: podman run - Starts a new container and runs the specified command. podman ps - Lists all running containers. podman images - Lists all images on the host. podman pull - Pulls an image from a registry. podman push - Pushes an image to a registry. podman build - Builds an image from a Dockerfile or a Podmanfile. podman commit - Creates a new image from a running container. podman export - Exports a container's filesystem as a tar archive. podman import - Imports an image from a tar archive. podman save - Saves one or more images to a tar archive. podman load - Loads one or more images from a tar archive. podman exec - Runs a command in a running container. BUILDAN: buildah bud - Builds an image from a Dockerfile or a Buildah format file. buildah from - Starts a new container and prepares it for building an image. buildah images - Lists all images on the host. buildah inspect - Displays detailed information about an image or container. buildah commit - Creates a new image from a running container. buildah push - Pushes an image to a registry. buildah tag - Tags an image with a new name and/or registry. buildah rmi - Removes one or more images. buildah containers - Lists all containers on the host. buildah rm - Removes one or more containers. buildah mount - Mounts the filesystem of a container. buildah unmount - Unmounts the filesystem of a container. Each of these commands has various options and flags that can be used to customize their behavior.

Will be working on this

That's awesome! I need to try mint with xfce soon. Haha.

Thank you for your feedback ! I will be working on a video that will include important modules/parameters on how to use them.

Try to use sudo dmidecode

I'm working on a series for rhcsa. I will make sure to fix it.

yes will do

By trying to run a rootless container as root, you have entered the condition where root is trying to access another user's container." So if one logs into root and then tries to su to another user, one is still root. Use the logname command to see which user you are. If you are root then ssh into the user that will run the rootless container. It should work that way

thank you