mirror of
https://github.com/kamranahmedse/developer-roadmap.git
synced 2026-09-24 15:00:31 +08:00
chore: cleanup orphaned content files (#9931)
Co-authored-by: jcanalesluna <56018501+jcanalesluna@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
co-authored by
jcanalesluna
jcanalesluna
parent
039c24d6c1
commit
d02783e024
@@ -1,27 +0,0 @@
|
||||
# Archiving
|
||||
|
||||
Linux offers powerful utilities for archiving, where multiple files and directories are combined into a single file, primarily for backup and simplification of distribution. The main tools used for this purpose are `tar`, `gzip`, and `bzip2`.
|
||||
|
||||
The `tar` command, originally for tape archiving, is a versatile tool that can manage and organize files into one archive. Meanwhile, `gzip` and `bzip2` are used for file compression, reducing the file size and making data transmission easier.
|
||||
|
||||
Take a look at the following commands in use:
|
||||
|
||||
```bash
|
||||
# To create a tar archive:
|
||||
tar cvf archive_name.tar directory_to_archive/
|
||||
|
||||
# To extract a tar archive:
|
||||
tar xvf archive_name.tar
|
||||
|
||||
# To create a gzip compressed tar archive:
|
||||
tar cvzf archive_name.tar.gz directory_to_archive/
|
||||
|
||||
#To create a bzip2 compressed tar archive:
|
||||
tar cvjf archive_name.tar.bz2 directory_to_archive/
|
||||
```
|
||||
|
||||
Remember, in Linux, archiving and compression are separate processes, hence `tar` to archive and `gzip`/`bzip2` to compress. Although they're commonly used together, they can very much be used separately as per the requirements.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@Linux File Packaging and Compression](https://labex.io/tutorials/linux-file-packaging-and-compression-385413)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Authentication Logs
|
||||
|
||||
Authentication logs record system login events, password changes, and sudo commands, located in `/var/log/auth.log` (Debian) or `/var/log/secure` (Red Hat/CentOS). Essential for monitoring server security, detecting brute force attacks and unauthorized access attempts. Use `tail /var/log/auth.log` to view recent entries. Regular analysis ensures server security and data integrity.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Monitoring Linux Authentication Logs](https://betterstack.com/community/guides/logging/monitoring-linux-auth-logs/)
|
||||
- [@article@How to Check Linux Login History - Linux Handbook](https://linuxhandbook.com/linux-login-history/)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Available Memory
|
||||
|
||||
Evaluating available memory is crucial for Linux system health monitoring. Use command-line tools like `free`, `vmstat`, and `top` to track memory usage and performance metrics. The `free -h` command shows total, used, free, shared, buffer/cache, and available memory in human-readable format. Essential for maintaining optimal server performance and troubleshooting resource issues.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@5 Best Ways To Check Available Memory In Linux](https://itslinuxfoss.com/5-ways-check-available-memory-linux/)
|
||||
- [@article@Free vs. Available Memory in Linux](https://linuxblog.io/free-vs-available-memory-in-linux/)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Background and Foreground Processes
|
||||
|
||||
Linux processes run in foreground (taking direct user input) or background (running independently). Send processes to background with `&` or `bg` command. Bring to foreground with `fg`. Use Ctrl+Z to pause, then `bg` to resume in background. Part of job control for managing multiple tasks simultaneously from single terminal.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Understanding Foreground and Background Processes](https://linuxconfig.org/understanding-foreground-and-background-linux-processes)
|
||||
- [@article@Running Linux Commands in Background and Foreground](https://linuxhandbook.com/run-process-background/)
|
||||
- [@article@Foreground and Background Processes - LinuxOPsys](https://linuxopsys.com/foreground-and-background-processes-co11/)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Checking Logs
|
||||
|
||||
Linux system logs provide chronological records of events for debugging and troubleshooting, stored in `/var/log` directory. Use `dmesg` for kernel messages and `journalctl` for systemd logs. `journalctl -u service_name` shows logs for specific services. Essential skill for system administration, monitoring, and effective troubleshooting in Linux environments.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@How to Check System Logs on Linux](https://www.fosslinux.com/8984/how-to-check-system-logs-on-linux-complete-usage-guide.htm)
|
||||
- [@article@Linux Log Files Location & How To View Logs Files](https://www.cyberciti.biz/faq/linux-log-files-location-and-how-do-i-view-logs-files/)
|
||||
- [@article@System Logging - Linuxjourney](https://linuxjourney.com/lesson/system-logging)
|
||||
@@ -1,10 +0,0 @@
|
||||
# Copying and Renaming Files
|
||||
|
||||
Essential Linux file operations use `cp` to copy files and `mv` to move/rename them. The `cp` command copies files from source to destination, while `mv` moves or renames files/directories. Both commands use the syntax `command source destination`. These case-sensitive commands are fundamental for daily file management tasks in Linux systems.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@mv and cp - Linux.org](https://www.linux.org/threads/mv-and-cp.54793/)
|
||||
- [@article@Mastering cp and mv Commands in Linux](https://dev.to/ldwit/mastering-cp-and-mv-commands-in-linux-plus-related-cmds-5cc9)
|
||||
- [@article@Linux cp Command: File Copying](https://labex.io/tutorials/linux-linux-cp-command-file-copying-209744)
|
||||
- [@article@Linux mv Command: File Moving and Renaming](https://labex.io/tutorials/linux-linux-mv-command-file-moving-and-renaming-209743)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Create, Update, and Delete Users
|
||||
|
||||
Linux user management involves creating, updating, and deleting user accounts for system security and resource utilization. Key commands: `useradd`/`adduser` (create users), `usermod` (update user details like home directory/shell), `userdel` (delete users). Essential for maintaining secure, organized multi-user system environments and efficient resource allocation.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Creating, Modifying, and Deleting User Accounts](https://serveracademy.com/courses/linux-server-administration/creating-modifying-and-deleting-user-accounts/)
|
||||
- [@article@How to create, update, and delete users account on Linux](https://linuxconfig.org/how-to-create-modify-and-delete-users-account-on-linux)
|
||||
- [@article@User Management in Linux: A Beginner's Guide](https://dev.to/austinozor/user-management-in-linux-a-beginners-guide-to-creating-modifying-and-deleting-users-fhf)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Creating Files
|
||||
|
||||
Linux file creation uses `touch` for empty files, `echo "text" > filename` for text files, or `cat > filename` for interactive input. Commands like `mkdir` create directories. File creation is immediate and permanent. Essential for organizing data, scripts, and configuration files in Linux systems.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@What is the Difference Between Cat and Touch Command](https://linuxways.net/centos/what-is-the-difference-between-cat-and-touch-command/)
|
||||
- [@article@Creating and Deleting Files / Directories in Linux](https://useful.codes/creating-and-deleting-files-directories-in-linux/)
|
||||
- [@article@Creating, Moving, and Deleting Files and Folders](https://dev.to/alkesh009/linux-basics-part-4-creating-moving-and-deleting-files-and-folders-5hip)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Creating Services
|
||||
|
||||
Creating Linux services involves setting up background applications using systemd service files. Services run continuously performing essential tasks like web servers, databases, and mail servers. Create `.service` files in `/etc/systemd/system/` with Unit, Service, and Install sections. Control services using `systemctl` commands. Best practice: avoid running services as root for security.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@How to Create a systemd Service in Linux](https://linuxhandbook.com/create-systemd-services/)
|
||||
- [@article@A Beginner's Guide to Creating Linux Services](https://www.fosslinux.com/111815/a-guide-to-creating-linux-services-with-systemd.htm)
|
||||
@@ -1,20 +0,0 @@
|
||||
# Understanding Directory Hierarchy
|
||||
|
||||
In Linux, understanding the directory hierarchy is crucial for efficient navigation and file management. A Linux system's directory structure, also known as the Filesystem Hierarchy Standard (FHS), is a defined tree structure that helps to prevent files from being scattered all over the system and instead organise them in a logical and easy-to-navigate manner.
|
||||
|
||||
- `/`: Root directory, the top level of the file system.
|
||||
- `/home`: User home directories.
|
||||
- `/bin`: Essential binary executables.
|
||||
- `/sbin`: System administration binaries.
|
||||
- `/etc`: Configuration files.
|
||||
- `/var`: Variable data (logs, spool files).
|
||||
- `/usr`: User programs and data.
|
||||
- `/lib`: Shared libraries.
|
||||
- `/tmp`: Temporary files.
|
||||
- `/opt`: Third-party applications.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Linux Directory Structure Explained for Beginners](https://linuxhandbook.com/linux-directory-structure/)
|
||||
- [@article@Overview of File System Hierarchy Standard (FHS)](https://access.redhat.com/documentation/ru-ru/red_hat_enterprise_linux/4/html/reference_guide/s1-filesystem-fhs#s3-filesystem-usr)
|
||||
- [@video@The Linux File System Explained in 1,233 Seconds](https://youtu.be/A3G-3hp88mo?si=sTJTSzubdb0Vizjr)
|
||||
@@ -1,10 +0,0 @@
|
||||
# Disks and Filesystems
|
||||
|
||||
Linux uses various filesystems to organize, store, and retrieve data from storage devices. Popular filesystems include EXT4 (robust for Linux volumes), FAT32 (compatible with all OS for removable media), NTFS, and Btrfs. Each has specific advantages and use cases. Use `df -T` command to display filesystem types, disk space usage, and mounted device information.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Filesystems in the Linux Kernel](https://www.kernel.org/doc/html/v6.16-rc2/filesystems/index.html)
|
||||
- [@article@Partitions And Filesystems In Linux - Introduction](https://www.linuxfordevices.com/tutorials/linux/partitions-and-filesystems)
|
||||
- [@article@Overview of File System Hierarchy Standard (FHS)](https://access.redhat.com/documentation/ru-ru/red_hat_enterprise_linux/4/html/reference_guide/s1-filesystem-fhs#s3-filesystem-usr)
|
||||
- [@article@Understanding Linux Filesystems: Inodes, Block Sizes, and Data](https://www.linuxjournal.com/content/understanding-linux-filesystems-inodes-block-sizes-and-data-structures)
|
||||
@@ -1,10 +0,0 @@
|
||||
# Ethernet, ARP and RARP
|
||||
|
||||
Three crucial Linux networking components: Ethernet enables LAN device communication, ARP (Address Resolution Protocol) translates IP addresses to MAC addresses for direct network communication, and RARP (Reverse ARP) converts MAC addresses to IP addresses when devices know their MAC but need their IP. Essential for diagnosing and managing Linux networking issues.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@A Comprehensive guide to Linux Networking](https://centlinux.com/linux-networking/)
|
||||
- [@article@A Beginner's Guide to Linux Networking Fundamentals](https://dev.to/iaadidev/a-beginners-guide-to-linux-networking-fundamentals-dev-ops-prerequisite-7-434o)
|
||||
- [@video@ARP Explained - Address Resolution Protocol](https://www.youtube.com/watch?v=cn8Zxh9bPio)
|
||||
- [@video@What is Ethernet?](https://www.youtube.com/watch?v=HLziLmaYsO0)
|
||||
@@ -1,11 +0,0 @@
|
||||
# Finding and Installing Packages
|
||||
|
||||
Linux package managers like `apt`, `yum`, and `dnf` automate software installation, upgrading, configuring, and removal. Debian-based systems: `sudo apt-get update && sudo apt-get install package-name`. Fedora/CentOS: `sudo dnf update && sudo dnf install package-name`. Package management eliminates manual compilation from source code. Root permissions required for installation.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@APT Package Manager](https://www.debian.org/doc/manuals/apt-guide/index.en.html)
|
||||
- [@official@Yum Package Manager](http://yum.baseurl.org/)
|
||||
- [@official@Using the DNF Software Package Manager](https://docs.fedoraproject.org/en-US/quick-docs/dnf/)
|
||||
- [@article@Linux Package Manager Explained](https://geekflare.com/dev/linux-package-manager-explained/)
|
||||
- [@article@8 Best Package Manager for Linux](https://linuxsimply.com/linux-basics/package-management/best-package-manager/)
|
||||
-4
@@ -1,4 +0,0 @@
|
||||
# Install, Remove, and Upgrade Packages
|
||||
|
||||
Linux package management handles installing, removing, and upgrading pre-compiled software modules. Different distributions use specific package managers: `apt` (Debian/Ubuntu), `yum`/`dnf` (Fedora/RHEL/CentOS), `zypper` (SUSE). Example installation: `sudo apt-get install packagename`. Each manager has specific commands for removal and upgrades. Critical skill for effective Linux system administration.
|
||||
|
||||
@@ -1,8 +0,0 @@
|
||||
# Kill Processes
|
||||
|
||||
The `kill` command terminates processes manually by sending specific signals to Process IDs (PIDs). Used when processes behave unexpectedly due to system bugs or accidental initiation. Syntax: `kill [signal or option] PID(s)`. Essential for Linux process management, allowing administrators to stop, pause, or terminate problematic processes and maintain system stability.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@Using Kill Command in Linux](https://linuxhandbook.com/kill-command/)
|
||||
- [@article@Kill Command in Linux](https://linuxize.com/post/kill-command-in-linux/)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Listing and Finding Processes
|
||||
|
||||
Linux processes can be monitored using the `proc` virtual filesystem and commands like `ps`, `top`, and `htop`. Use `ps -ef` for process snapshots, `top`/`htop` for real-time views. The `/proc` directory contains detailed process information. View specific process details with `cat /proc/{PID}/status`. Essential for system performance monitoring and troubleshooting.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@The /proc File System](https://www.kernel.org/doc/html/latest/filesystems/proc.html)
|
||||
- [@article@What is a Process in Linux/Unix?](https://www.scaler.com/topics/linux-process/)
|
||||
- [@article@Exploring the Linux /proc Filesystem](https://www.redhat.com/en/blog/linux-proc-filesystem)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Moving Files
|
||||
|
||||
In Linux, moving files is an essential task that you will need to perform quite frequently. The `mv` command, short for move, is used to move files and directories from one location to another. The `mv` command can also be used for renaming files in Linux.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@mv command](https://linuxhandbook.com/mv-command/)
|
||||
- [@article@mv Cheat Sheet](https://www.commandinline.com/cheat-sheet/mv/)
|
||||
- [@article@Linux mv Command: File Moving and Renaming](https://labex.io/tutorials/linux-linux-mv-command-file-moving-and-renaming-209743)
|
||||
@@ -1,10 +0,0 @@
|
||||
# Permissions
|
||||
|
||||
Linux permissions control file and directory access for users, groups, and others with read, write, and execute types. Commands include `chmod` (change permissions), `chown` (change owner), and `chgrp` (change group). Proper permission management is crucial for system security and organization. Essential for maintaining controlled access to system resources.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Understanding Linux File Permissions](https://linuxize.com/post/understanding-linux-file-permissions/)
|
||||
- [@article@Linux File Permissions](https://linuxhandbook.com/linux-file-permissions/)
|
||||
- [@article@Linux Permissions of Files](https://labex.io/tutorials/linux-permissions-of-files-270252)
|
||||
- [@video@Linux File Permissions in 5 Minutes](https://www.youtube.com/watch?v=LnKoncbQBsM)
|
||||
@@ -1,23 +0,0 @@
|
||||
# Linux File Permissions
|
||||
|
||||
In Linux systems, rights and privileges are assigned to files and directories in the form of permissions. These permissions indicate who can read, write, or execute (run) them. In Linux, there are three types of users: owners, groups, and others who can have a different set of permissions.
|
||||
|
||||
In fact, permissions on the system are there for a reason: to prevent unprivileged users from making changes on the system that would ultimately affect other users. With inadequate permissions, unprivileged users are able to make changes that would be beneficial or harmless to the Linux system.
|
||||
|
||||
Let's have a look at an example:
|
||||
|
||||
```bash
|
||||
-rwxr--r-- 1 root root 4096 Jan 1 12:00 filename
|
||||
```
|
||||
|
||||
From the above example, the first character `-` indicates if it is a regular file(`-`) or directory(`d`). The following group of three characters(`rwx`) represents the permissions for the file owner. The next three characters(`r--`) represent permissions for the group and the last set of three characters(`r--`) represents permissions for others.
|
||||
|
||||
The `r` indicates that the file can be read, `w` indicates that the file can be written to, and `x` indicates that the file can be executed.
|
||||
|
||||
The permissions can be changed using the `chmod`, `chown`, and `chgrp` commands.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@Linux File Permissions](https://linuxhandbook.com/linux-file-permissions/)
|
||||
- [@video@Linux File Permissions in 5 Minutes](https://www.youtube.com/watch?v=LnKoncbQBsM)
|
||||
- [@article@Linux Permissions of Files](https://labex.io/tutorials/linux-permissions-of-files-270252)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Process Forking
|
||||
|
||||
Process forking uses the `fork()` system call to create child processes from parent processes, enabling concurrent execution. Child processes are nearly perfect copies of parents with different PIDs. Changes in child processes don't affect parents. Essential for understanding Linux process creation and control in multi-processing environments.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@fork — Linux manual page](https://www.man7.org/linux/man-pages/man2/fork.2.html)
|
||||
- [@article@Understanding the fork() System Call in Linux](https://thelinuxcode.com/fork-system-call-linux/)
|
||||
- [@article@Linux Process calls: Creating process using fork](https://medium.com/@joshuaudayagiri/linux-process-calls-creating-process-using-fork-52a1eac7de8b)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Process Priorities
|
||||
|
||||
Linux assigns priority levels to processes for efficient resource utilization and execution timing. Priority values ("nice" values) range from -20 (highest) to +19 (lowest priority). View priorities with `ps -eo pid,pri,user,comm`. Change priorities using `renice -5 -p [PID]`. Essential for system performance optimization and CPU resource management.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Understanding Process Thread Priorities in Linux](https://blogs.oracle.com/linux/post/task-priority)
|
||||
- [@article@How To Manipulate Process Priority In Linux](https://www.itsmarttricks.com/how-to-manipulate-process-priority-in-linux-using-nice-and-renice-commands/)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Process Signals
|
||||
|
||||
Process signals are communication mechanisms in Linux that notify processes of synchronous or asynchronous events. Common signals include SIGINT, SIGSTOP, SIGKILL for interrupting, pausing, or terminating processes. Example: `kill -SIGSTOP 12345` suspends process with PID 12345 until `SIGCONT` is received. Essential for comprehensive process management and resource allocation.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Understanding Linux Process Signals](https://www.ceos3c.com/linux/understanding-linux-process-signals-a-complete/)
|
||||
- [@article@Linux Process Signals and their meaning](https://linux-audit.com/processes/linux-process-signals/)
|
||||
@@ -1,10 +0,0 @@
|
||||
# Repositories
|
||||
|
||||
Repositories are storage locations containing collections of software packages for Linux distributions. They store thousands of compiled packages specific to each distribution (.deb for Debian/Ubuntu, .rpm for Fedora/CentOS). Repositories ensure secure, tested software with proper dependencies. Update commands: `sudo apt update` (Ubuntu), `sudo yum update` (CentOS/Fedora). Essential for secure software management.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@APT Package Manager](https://www.debian.org/doc/manuals/apt-guide/index.en.html)
|
||||
- [@article@What is Repository in Linux?](https://linuxsimply.com/what-is-repository-in-linux/)
|
||||
- [@article@Official Repositories - ArchWiki](https://wiki.archlinux.org/title/Official_repositories)
|
||||
- [@article@Understanding Linux Repositories](https://blogs.maalavs.com/linux/understanding-linux-repositories/)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Service Management
|
||||
|
||||
Service management controls Linux services (daemons) during boot and shutdown processes. Common systemctl commands include start, stop, restart, reload, status, enable/disable. Modern Linux uses systemd while older systems use SystemV or Upstart. Example: `sudo systemctl start sshd` starts SSH service. Essential skill for Linux system administration and maintaining secure, stable systems.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@How to Master Linux Service Management with Systemctl](https://labex.io/tutorials/linux-how-to-master-linux-service-management-with-systemctl-392864)
|
||||
- [@article@Service Management in Linux: A Comprehensive Guide](https://medium.com/@thesureshvadde/service-management-in-linux-a-comprehensive-guide-cb4c7e81dfa9)
|
||||
- [@article@How to Manage Services in Linux: systemd and SysVinit](https://dev.to/iaadidev/how-to-manage-services-in-linux-systemd-and-sysvinit-essentials-devops-prerequisite-8-1jop)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Service Status
|
||||
|
||||
Service status shows the current state of Linux services including network processes, backend servers, and background applications. Use `systemctl status service_name` to check service states through systemd manager. Example: `systemctl status apache2.service` shows Apache web server status. Essential for diagnosing problems, maintaining performance, and preventing service downtimes.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@Service Management in Linux: A Comprehensive Guide](https://medium.com/@thesureshvadde/service-management-in-linux-a-comprehensive-guide-cb4c7e81dfa9)
|
||||
- [@article@Use Systemctl Status Command to Check Service Status](https://linuxhandbook.com/systemctl-check-service-status/)
|
||||
- [@article@How to Check All Running Services in Linux](https://www.2daygeek.com/how-to-check-all-running-services-in-linux/)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Shell Basics
|
||||
|
||||
The Linux shell is a command-line interface that acts as an intermediary between users and the system kernel. Common shells include Bash, sh, and csh. Basic operations involve navigating directories, creating/deleting files, and executing commands. Shell knowledge is fundamental for Linux administration, scripting, and automation tasks.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@Learning The Shell](https://www.linuxcommand.org/lc3_lts0010.php)
|
||||
- [@article@What is a Shell in Linux](https://linuxsimply.com/what-is-a-shell-linux/)
|
||||
- [@article@Learn Linux Easily](https://linuxjourney.com)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Soft and Hard Links
|
||||
|
||||
Linux supports two types of file links. Hard links share the same inode and data as the original file - if the original is deleted, data remains accessible. Soft links (symbolic links) are shortcuts pointing to the original file path - they break if the original is removed. Create with `ln` for hard links and `ln -s` for soft links.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Hard links and Soft links in Linux Explained](https://www.redhat.com/en/blog/linking-linux-explained)
|
||||
- [@article@Difference between hard link and soft link](https://kerneltalks.com/commands/difference-between-hard-link-and-soft-link/)
|
||||
- [@article@How to Understand the Difference between Hard and Symbolic Links in Linux](https://labex.io/tutorials/linux-how-to-understand-the-difference-between-hard-and-symbolic-links-in-linux-409929)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Start and Stop Services
|
||||
|
||||
Linux service management controls system services like firewall, network, and database using `systemctl` commands. Basic operations: `sudo systemctl start service_name` (start), `sudo systemctl stop service_name` (stop), `sudo systemctl restart service_name` (restart). Root permissions required. Essential for system administrators managing updates and configuration changes.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@Service Management in Linux: A Comprehensive Guide](https://medium.com/@thesureshvadde/service-management-in-linux-a-comprehensive-guide-cb4c7e81dfa9)
|
||||
- [@article@How to Master Linux Service Management with Systemctl](https://labex.io/tutorials/linux-how-to-master-linux-service-management-with-systemctl-392864)
|
||||
- [@article@How to Manage Services in Linux: systemd and SysVinit](https://dev.to/iaadidev/how-to-manage-services-in-linux-systemd-and-sysvinit-essentials-devops-prerequisite-8-1jop)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Stdout, Stdin, and Stderr
|
||||
|
||||
Linux processes use three standard data streams: STDIN (input), STDOUT (output), and STDERR (error messages). STDOUT handles normal command output while STDERR specifically handles error messages. You can redirect these streams using operators like `>` for stdout and `2>` for stderr, allowing separate handling of normal output and errors for better scripting and debugging.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@Linux Fundamentals - I/O, Standard Streams, and Redirection](https://www.putorius.net/linux-io-file-descriptors-and-redirection.html)
|
||||
- [@article@Understanding 'stdin', 'stdout' and 'stderr' in Linux](https://www.slingacademy.com/article/understanding-stdin-stdout-and-stderr-in-linux/)
|
||||
- [@article@Working with data streams on the Linux command line](https://opensource.com/article/18/10/linux-data-streams)
|
||||
@@ -1,9 +0,0 @@
|
||||
# TCP/IP
|
||||
|
||||
TCP/IP (Transmission Control Protocol/Internet Protocol) forms the backbone of internet communication, allowing computers to connect and transfer data. It comprises four layers: Network Interface, Internet, Transport, and Application. Essential for Linux networking, enabling hosts to interact across networks. Use `netstat -at` to view active TCP/IP connections. Crucial for network management and troubleshooting.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@TCP/IP Commands for Linux](https://whatismyipaddress.com/tcp-ip-commands-linux)
|
||||
- [@article@Netstat Command in Linux](https://phoenixnap.com/kb/netstat-command)
|
||||
- [@article@Netstat Command in Linux: 13 Practical Examples](https://linuxhandbook.com/netstat-command/)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Uptime and Load
|
||||
|
||||
The `uptime` command shows system running time and load averages for 1, 5, and 15-minute intervals. Load average indicates computational work and processes waiting for CPU time. High load suggests insufficient resources or misconfigurations. Example: `uptime` shows "2 days, 20 min" uptime and "0.00, 0.01, 0.05" load averages. Essential for performance monitoring and capacity planning.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@Linux Uptime Command With Usage Examples](https://www.tecmint.com/linux-uptime-command-examples/)
|
||||
- [@article@How to Check Uptime in Linux Command Line](https://linuxhandbook.com/uptime-command/)
|
||||
- [@article@Linux Load Average: What is Load Average in Linux?](https://www.digitalocean.com/community/tutorials/load-average-in-linux)
|
||||
@@ -1,10 +0,0 @@
|
||||
# Users and Groups
|
||||
|
||||
Linux user groups simplify system administration by managing collections of users with shared access rights to files and directories. Each user belongs to one or more groups, enabling privilege management without full superuser access. Management commands: `groupadd`, `groupdel`, `groupmod`, `usermod`, `gpasswd`. Essential for secure and organized system environments.
|
||||
|
||||
Learn more from the following resources:
|
||||
|
||||
- [@article@How to create, delete, and modify groups in Linux](https://www.redhat.com/sysadmin/linux-groups)
|
||||
- [@article@How to manage groups on Linux](https://linuxconfig.org/how-to-manage-groups-on-linux)
|
||||
- [@article@Creating, Modifying, and Deleting User Accounts](https://serveracademy.com/courses/linux-server-administration/creating-modifying-and-deleting-user-accounts/)
|
||||
- [@article@User Management in Linux: A Beginner's Guide](https://dev.to/austinozor/user-management-in-linux-a-beginners-guide-to-creating-modifying-and-deleting-users-fhf)
|
||||
Reference in New Issue
Block a user