mirror of
https://github.com/Snigdha-OS/documentation.git
synced 2025-09-05 19:06:37 +02:00
📝 docs: getting ready for Ukrainian translation
This commit is contained in:
@@ -0,0 +1,143 @@
|
||||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
# Download Snigdha OS
|
||||
|
||||
Here’s the updated **Markdown file** with Ventoy instructions added for creating bootable media:
|
||||
|
||||
|
||||
### 🌟 **Guide to Download Snigdha OS**
|
||||
|
||||
Snigdha OS is a beautiful Arch-based distribution that provides an intuitive and user-friendly experience, complete with eye-catching themes, performance enhancements, and pre-configured software. Here's a simple guide to help you download Snigdha OS and start using it on your system.
|
||||
|
||||
|
||||
|
||||
## 🔽 **Step 1: Visit the Official Snigdha OS Website**
|
||||
|
||||
1. **Go to the Official Snigdha OS Website**:
|
||||
Open your browser and visit the official Snigdha OS website to download the ISO. The website is:
|
||||
- [Download Snigdha OS](https://snigdhaos.org/downloads.html)
|
||||
|
||||
2. **Choose Your Preferred Edition**:
|
||||
Snigdha OS offers several editions based on desktop environments and use cases. Some of the most popular editions include:
|
||||
- **Snigdha OS KDE** (KDE Plasma desktop with customizations)
|
||||
- **Snigdha OS XFCE** (A lighter desktop environment)
|
||||
- **Snigdha OS GNOME** (GNOME desktop environment)
|
||||
- **Snigdha OS LXQt** (A very lightweight desktop environment)
|
||||
- **Snigdha OS i3WM** (A minimalist tiling window manager)
|
||||
|
||||
Select the edition that best fits your preferences.
|
||||
|
||||
|
||||
|
||||
## 💻 **Step 2: Download the ISO File**
|
||||
|
||||
1. **Click on the Desired Edition**:
|
||||
Once on the Snigdha OS download page, select the edition you want to install. The page will provide a direct download link or a mirror list for the ISO.
|
||||
|
||||
2. **Start the Download**:
|
||||
After selecting your edition, click on the **Download** button. The file will typically be named something like:
|
||||
- `snigdhaos-YYYY.MM.DD-x86_64.iso`
|
||||
- Example: `snigdhaos-2024.12.01-x86_64.iso`
|
||||
|
||||
Wait for the download to complete. The size is typically around 2-3 GB, depending on the edition.
|
||||
|
||||
|
||||
|
||||
## 🔍 **Step 3: Verify the Download (Optional)**
|
||||
|
||||
1. **Verify the Integrity of the ISO**:
|
||||
To ensure that the ISO file has not been corrupted during download, it’s a good idea to verify its checksum (SHA256 or SHA1) to compare it with the official value.
|
||||
|
||||
- **Check the provided checksum** on the Snigdha OS website.
|
||||
- **Run the following command** in the terminal (replace the filename with your downloaded ISO file):
|
||||
|
||||
```bash
|
||||
sha256sum snigdhaos-YYYY.MM.DD-x86_64.iso
|
||||
```
|
||||
|
||||
- Compare the output checksum with the one on the Snigdha OS website. If they match, your download is intact.
|
||||
|
||||
|
||||
|
||||
## 💿 **Step 4: Create Bootable Media (USB or DVD)**
|
||||
|
||||
### Option 1: Using Ventoy 🛠️
|
||||
|
||||
Ventoy is an excellent tool for creating multi-boot USB drives with minimal effort.
|
||||
|
||||
1. **Download Ventoy**:
|
||||
- Visit the [Ventoy website](https://www.ventoy.net/) and download the latest version for your operating system.
|
||||
|
||||
2. **Install Ventoy on Your USB Drive**:
|
||||
- Extract the Ventoy zip file and run the installation script (e.g., `Ventoy2Disk.exe` for Windows or `./Ventoy2Disk.sh` for Linux).
|
||||
- Select your USB drive and click **Install**.
|
||||
|
||||
3. **Copy the Snigdha OS ISO**:
|
||||
- Once Ventoy is installed on the USB drive, copy the downloaded Snigdha OS ISO file directly to the USB drive.
|
||||
|
||||
4. **Boot with Ventoy**:
|
||||
- Restart your system and boot from the Ventoy USB drive. Select the Snigdha OS ISO from the Ventoy menu.
|
||||
|
||||
|
||||
|
||||
### Option 2: Using dd (Linux)
|
||||
|
||||
1. **Insert your USB Drive** and check its device name using the `lsblk` command:
|
||||
```bash
|
||||
lsblk
|
||||
```
|
||||
|
||||
2. **Write the ISO to the USB**:
|
||||
```bash
|
||||
sudo dd if=snigdhaos-YYYY.MM.DD-x86_64.iso of=/dev/sdX bs=4M status=progress oflag=sync
|
||||
```
|
||||
Replace `/dev/sdX` with your USB drive's actual device (e.g., `/dev/sdb`).
|
||||
|
||||
|
||||
|
||||
### Option 3: Using Rufus (Windows)
|
||||
|
||||
1. **Download Rufus**:
|
||||
Download and install **Rufus** from [Rufus website](https://rufus.ie/).
|
||||
|
||||
2. **Create a Bootable USB Drive**:
|
||||
- Insert your USB drive and launch Rufus.
|
||||
- Select the Snigdha OS ISO and choose the USB drive.
|
||||
- Click **Start** to create the bootable USB drive.
|
||||
|
||||
|
||||
|
||||
### Option 4: Burn to a DVD (Optional)
|
||||
|
||||
1. **Download ImgBurn or Brasero**:
|
||||
- Windows: Use [ImgBurn](https://www.imgburn.com/).
|
||||
- Linux: Use Brasero.
|
||||
|
||||
2. **Burn the ISO to a DVD**:
|
||||
Follow the application instructions to burn the ISO file to a blank DVD.
|
||||
|
||||
|
||||
|
||||
## 🚀 **Step 5: Boot from USB or DVD**
|
||||
|
||||
1. **Insert the Bootable USB or DVD** into the system where you want to install Snigdha OS.
|
||||
|
||||
2. **Enter BIOS/UEFI**:
|
||||
- Restart the computer and press the key to enter BIOS/UEFI (e.g., `F2`, `DEL`, or `ESC`).
|
||||
|
||||
3. **Set USB/DVD as Primary Boot Device**:
|
||||
- In BIOS/UEFI settings, set the USB drive or DVD as the primary boot device.
|
||||
|
||||
4. **Save and Reboot**:
|
||||
- Save the settings and reboot. Your system should boot into the Snigdha OS live environment.
|
||||
|
||||
|
||||
|
||||
## 🏁 **Conclusion**
|
||||
|
||||
Now that you’ve successfully downloaded and created bootable media for Snigdha OS, you’re ready to move forward with installation. You can use the **Calamares graphical installer** for a smooth installation experience or proceed with manual partitioning if you're an advanced user.
|
||||
|
||||
For more detailed installation instructions, visit the [Snigdha OS Wiki](https://wiki.snigdhaos.org/).
|
||||
|
||||
Enjoy the performance and beauty of Snigdha OS! 😎🚀
|
@@ -0,0 +1,69 @@
|
||||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
# Important Note
|
||||
|
||||
Installing Snigdha OS is an exciting step toward a customized and high-performance Linux experience. However, before you proceed, it's crucial to be fully prepared. Please read this guide carefully to ensure a smooth and secure installation process. 💡
|
||||
|
||||
|
||||
|
||||
## 🔒 Backup Your Data
|
||||
|
||||
- 🗂️ **Backup is essential!** Before making any changes to your system, ensure you have securely backed up all critical files and data to an external drive or cloud storage.
|
||||
- 💾 **Why?** The installation process involves disk partitioning, which can result in data loss if done incorrectly.
|
||||
|
||||
|
||||
|
||||
## ⚠️ Know Your System
|
||||
|
||||
- 🖥️ Ensure you are familiar with your system's hardware, including disk configuration, BIOS/UEFI settings, and boot order.
|
||||
- 🛠️ Check system compatibility with Snigdha OS requirements:
|
||||
- **Processor:** x86_64 architecture
|
||||
- **RAM:** Minimum 2 GB (4 GB recommended)
|
||||
- **Storage:** Minimum 20 GB free space
|
||||
|
||||
|
||||
|
||||
## 🌐 Stable Internet Connection Required(Online Installation)
|
||||
|
||||
- 📶 **Internet is a must if you are going for online installation!** The installation process downloads essential packages in real-time. Ensure you have a stable and reliable internet connection throughout the setup.
|
||||
|
||||
|
||||
|
||||
## 📜 Read the Documentation
|
||||
|
||||
- 📖 **Thoroughly review the installation documentation** to understand each step. Jumping into the process without preparation can lead to errors or an incomplete setup.
|
||||
- 🧭 Follow the official [Snigdha OS Documentation](https://snigdha-os.github.io/documentation/) for detailed guidance.
|
||||
|
||||
|
||||
|
||||
## 🛑 Dual Boot Warning
|
||||
|
||||
- 💡 If you are installing Snigdha OS alongside another operating system (dual boot), be cautious when partitioning the disk.
|
||||
- 🔧 Misconfiguring the bootloader or partition scheme can render other operating systems unbootable.
|
||||
- 🛡️ Use tools like `GParted` to prepare your disk safely.
|
||||
|
||||
|
||||
|
||||
## 🏗️ Installation Checklist
|
||||
|
||||
Before you begin, ensure you have:
|
||||
- ✅ A **bootable USB drive** with the Snigdha OS ISO.
|
||||
- ✅ Backed up all critical data.
|
||||
- ✅ A stable internet connection.**(Optional)**
|
||||
- ✅ A system that meets the hardware requirements.
|
||||
- ✅ Read and understood the installation guide.
|
||||
|
||||
|
||||
|
||||
## 🧑💻 Need Help?
|
||||
|
||||
If you encounter any issues during installation:
|
||||
- Visit our [community forums](https://forum.snigdhaos.org) for support.
|
||||
- Check out the troubleshooting section in the [Snigdha OS documentation](https://snigdha-os.github.io/documentation/).
|
||||
- Reach out to the active developers or contributors for assistance.
|
||||
|
||||
|
||||
|
||||
Installing Snigdha OS is a journey into the world of minimalistic and powerful Linux. 🌟 With proper preparation, you're just a few steps away from an amazing experience. Good luck! 🚀
|
@@ -0,0 +1,99 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
# Live Environment
|
||||
|
||||
### 🌟 **Snigdha OS Live Environment: An Overview**
|
||||
|
||||
The **Snigdha OS Live Environment** is the initial mode you boot into when running Snigdha OS from a USB drive or DVD without installing it. It provides an opportunity to test and experience Snigdha OS before committing to the installation. The live environment allows you to explore the user interface, test hardware compatibility, and even run applications without modifying your system.
|
||||
|
||||
Here's everything you need to know about the **Snigdha OS Live Environment**.
|
||||
|
||||
|
||||
|
||||
### 🖥️ **What Is the Snigdha OS Live Environment?**
|
||||
|
||||
The **Live Environment** in Snigdha OS is a fully functional, bootable environment that runs directly from your USB drive or DVD without needing installation. It's a great way to:
|
||||
|
||||
- **Try Snigdha OS**: Get a feel for the operating system without installing it.
|
||||
- **Test Hardware Compatibility**: Check if your system's hardware works well with Snigdha OS.
|
||||
- **Access Tools**: Use the pre-installed tools and utilities to diagnose or repair your system.
|
||||
|
||||
In the live environment, you can explore Snigdha OS's features, such as the **KDE Plasma** desktop (in the default edition), graphical tools, system settings, and much more.
|
||||
|
||||
|
||||
|
||||
### 🌍 **Features of the Snigdha OS Live Environment**
|
||||
|
||||
#### 1. **Beautiful KDE Plasma Desktop**
|
||||
Snigdha OS comes with a highly customized version of **KDE Plasma** as its default desktop environment. In the live environment, you can experience:
|
||||
- **Eye-catching themes**: Custom themes with vibrant colors and transparent effects.
|
||||
- **Pre-configured widgets**: Useful widgets like system monitoring, weather, and calendar.
|
||||
- **Snigdha OS Assistant**: A tool for managing your system easily, offering options for updates, tweaks, and more.
|
||||
|
||||
#### 2. **Performance Optimizations**
|
||||
Snigdha OS is known for its performance enhancements, and these are present in the live environment too:
|
||||
- **Preconfigured optimizations** for better responsiveness and speed.
|
||||
- **ZFS support**: Built-in support for advanced filesystem options like ZFS (available after installation).
|
||||
- **Btrfs snapshots**: You can test out Btrfs-based snapshots and rollback features in the live environment.
|
||||
|
||||
#### 3. **Pre-installed Software**
|
||||
The live environment comes with a wide range of pre-installed software to explore:
|
||||
- **Web browser**: Typically **Firefox** or **Chromium** for web browsing.
|
||||
- **Office suite**: LibreOffice or other office applications.
|
||||
- **Media players**: VLC and other multimedia tools.
|
||||
- **System monitoring tools**: Tools like **KSysGuard** to check system resources, and **GParted** for partitioning.
|
||||
|
||||
#### 4. **Hardware Compatibility Testing**
|
||||
The live environment helps you test hardware compatibility before installation:
|
||||
- **Graphics**: See if your graphics card works well with Snigdha OS (NVIDIA, AMD, or Intel).
|
||||
- **Wi-Fi**: Test if your wireless card connects without issues.
|
||||
- **Sound**: Check if your speakers or headphones work correctly.
|
||||
|
||||
#### 5. **Snigdha OS Welcome App**
|
||||
The Snigdha OS Welcome app provides an easy-to-navigate introduction to the system, offering quick access to:
|
||||
- **Installation**: Start the installation process if you're ready to install Snigdha OS.
|
||||
- **Settings**: Customize settings and tweak the system.
|
||||
- **Updates**: Quickly check for and apply system updates.
|
||||
- **Documentation**: Access official documentation and guides to help you along the way.
|
||||
|
||||
#### 6. **Persistence (Optional)**
|
||||
In some cases, you can configure persistence in the Snigdha OS live environment. This allows you to save changes and data across reboots, making it a more persistent experience. It is not enabled by default, but it can be set up using specific tools or settings.
|
||||
|
||||
|
||||
|
||||
### 🚀 **Using the Snigdha OS Live Environment**
|
||||
|
||||
#### 1. **Testing and Exploring**
|
||||
You can explore the system freely. Here are a few things you can do:
|
||||
- **Try out the desktop**: Navigate the KDE Plasma desktop, try out its features, and experience the customization that Snigdha OS provides.
|
||||
- **Check out system settings**: Explore various pre-configured system settings like appearance, keyboard layout, and more.
|
||||
- **Use pre-installed apps**: Open apps like Firefox, VLC, and LibreOffice to get a feel of the system’s performance.
|
||||
|
||||
#### 2. **Launching the Installer**
|
||||
If you decide to install Snigdha OS, the live environment offers an easy-to-use graphical installer. Here's how to launch it:
|
||||
- **Click the Snigdha OS Installer** icon on the desktop or in the menu.
|
||||
- The installer will guide you through the process of partitioning your hard drive and setting up Snigdha OS.
|
||||
- You can choose between **Btrfs**, **ext4**, or **other file systems** during installation.
|
||||
|
||||
#### 3. **Running Diagnostics**
|
||||
If you encounter hardware issues or need to run diagnostic tests, the live environment has a range of useful tools like:
|
||||
- **GParted** for managing partitions.
|
||||
- **Timeshift** for system snapshots (you can install it for more advanced setups).
|
||||
- **Snigdha OS Assistant** for managing system tweaks.
|
||||
|
||||
|
||||
|
||||
### 🏁 **When to Use Snigdha OS Live Environment**
|
||||
|
||||
- **Before Installing**: If you're unsure about how Snigdha OS will perform on your hardware, the live environment lets you test it out first.
|
||||
- **For Repairs**: If you need to troubleshoot or repair a system, you can boot into the live environment to access system recovery tools.
|
||||
- **For Exploration**: Snigdha OS's live environment is a great way to get to know the system, whether you're considering a switch from another distro or just want to see how it works.
|
||||
|
||||
|
||||
|
||||
### 🎉 **Conclusion**
|
||||
|
||||
The **Snigdha OS Live Environment** is a powerful and feature-packed way to experience Snigdha OS without committing to an installation. It offers a fully functional system with performance optimizations, a beautiful KDE Plasma desktop, pre-installed software, and various tools for hardware testing and system diagnostics.
|
||||
|
||||
You can use it to explore Snigdha OS, try out the desktop, check compatibility, or even install it if you're ready to make the switch. Whether you want to test, troubleshoot, or simply explore, the live environment is the perfect starting point. 😎🚀
|
@@ -0,0 +1,154 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Offline Installation
|
||||
|
||||
### 🖥️ **How to Install Snigdha OS in Offline Mode**
|
||||
|
||||
Installing Snigdha OS in **offline mode** means performing the installation without an active internet connection. While Snigdha OS's installation typically requires an internet connection to fetch updates and additional packages, it’s still possible to install it offline using the installation ISO and pre-downloaded packages. This method is especially useful if you're in an environment with limited or no internet access.
|
||||
|
||||
Here's a step-by-step guide to install Snigdha OS in **offline mode**:
|
||||
|
||||
|
||||
|
||||
### 📥 **Step 1: Download Snigdha OS ISO**
|
||||
|
||||
1. **Go to the Official Snigdha OS Website**:
|
||||
Visit the Snigdha OS download page:
|
||||
- [Snigdha OS Downloads](https://snigdhaos.org/downloads.html)
|
||||
|
||||
2. **Download the ISO File**:
|
||||
Select your preferred edition (KDE, GNOME, etc.) and download the ISO file. This will be used to create the bootable USB.
|
||||
|
||||
3. **Optionally Download Extra Packages**:
|
||||
If you know you will need additional packages (like drivers or software that may not be included in the ISO), it’s a good idea to download them beforehand using another system that has internet access. You can use a tool like **Pacman** to download packages:
|
||||
```bash
|
||||
sudo pacman -Sw package_name
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 💾 **Step 2: Create a Bootable USB Drive**
|
||||
|
||||
You need a **bootable USB** to install Snigdha OS. Use **Ventoy** or **Rufus** (for Windows) or the `dd` command (for Linux) to create a bootable USB drive.
|
||||
|
||||
#### **For Linux Users (Using `dd`)**
|
||||
|
||||
1. **Insert USB Drive**:
|
||||
Plug in a USB drive (at least 4 GB).
|
||||
|
||||
2. **Find USB Drive Location**:
|
||||
Use the `lsblk` command to identify your USB drive:
|
||||
```bash
|
||||
lsblk
|
||||
```
|
||||
|
||||
3. **Create Bootable USB**:
|
||||
Run the `dd` command to copy the Snigdha OS ISO to your USB drive (replace `/dev/sdX` with your USB device path):
|
||||
```bash
|
||||
sudo dd if=snigdhaos-YYYY.MM.DD-x86_64.iso of=/dev/sdX bs=4M status=progress oflag=sync
|
||||
```
|
||||
|
||||
4. **Eject USB**:
|
||||
After the process finishes, safely eject the USB:
|
||||
```bash
|
||||
sudo eject /dev/sdX
|
||||
```
|
||||
|
||||
#### **For Windows Users (Using Rufus)**
|
||||
|
||||
1. **Download and Install Rufus**:
|
||||
Download **Rufus** from [https://rufus.ie/](https://rufus.ie/) and install it.
|
||||
|
||||
2. **Open Rufus** and Select the USB Drive.
|
||||
|
||||
3. **Choose the Snigdha OS ISO** and select the appropriate **Partition Scheme** (usually **GPT** for modern systems).
|
||||
|
||||
4. **Start the Process**:
|
||||
Click **Start** to create a bootable USB. Wait for it to complete.
|
||||
|
||||
|
||||
|
||||
### 🔌 **Step 3: Boot into Snigdha OS Live Environment**
|
||||
|
||||
1. **Insert the Bootable USB** into the target system.
|
||||
|
||||
2. **Enter BIOS/UEFI**:
|
||||
Restart the system and press the appropriate key (often `F2`, `DEL`, or `ESC`) to enter BIOS/UEFI.
|
||||
|
||||
3. **Set USB as Primary Boot Device**:
|
||||
In the BIOS/UEFI settings, set the USB drive as the first boot device.
|
||||
|
||||
4. **Save and Reboot**:
|
||||
Save the changes and reboot the system. It will boot into the Snigdha OS live environment.
|
||||
|
||||
|
||||
|
||||
### ⚙️ **Step 4: Install Snigdha OS Offline**
|
||||
|
||||
1. **Launch the Installer**:
|
||||
In the live environment, click on the **Snigdha OS Installer** icon on the desktop or in the application menu.
|
||||
|
||||
2. **Select Language and Region**:
|
||||
Follow the prompts to select your language, region, and keyboard layout.
|
||||
|
||||
3. **Partitioning**:
|
||||
Choose the disk where you want to install Snigdha OS. You can either let the installer automatically partition your disk or choose manual partitioning for more control.
|
||||
|
||||
- **Btrfs** is the default filesystem used by Snigdha OS.
|
||||
- You can set up **LVM** or **ZFS** if you want advanced features.
|
||||
|
||||
4. **Offline Mode Warning**:
|
||||
The installer will ask for an internet connection to fetch updates and additional software. **Ignore this step** since you are installing in offline mode. Proceed without an internet connection.
|
||||
|
||||
5. **User Configuration**:
|
||||
- Set up your **username** and **password**.
|
||||
- Configure **root password** if required.
|
||||
|
||||
6. **Installation Location**:
|
||||
Confirm the partition where you want to install Snigdha OS. Double-check the partitions to avoid data loss.
|
||||
|
||||
7. **Begin Installation**:
|
||||
Click on the **Install** button to start the installation. The system will copy files from the ISO to the target disk.
|
||||
|
||||
|
||||
|
||||
### 🔄 **Step 5: Install Pre-Downloaded Packages (Optional)**
|
||||
|
||||
If you have pre-downloaded additional packages or software (like drivers, codecs, or essential tools), you can install them during or after the installation process:
|
||||
|
||||
1. **Mount the USB with Packages**:
|
||||
If the packages are on another USB or disk, you can mount it to the system during installation using the terminal.
|
||||
|
||||
2. **Use Pacman to Install Packages**:
|
||||
Once Snigdha OS is installed and you’ve booted into the system, use the `pacman` package manager to install any pre-downloaded packages:
|
||||
```bash
|
||||
sudo pacman -U /path/to/package_file.pkg.tar.zst
|
||||
```
|
||||
|
||||
Replace `/path/to/package_file.pkg.tar.zst` with the actual path to the downloaded package.
|
||||
|
||||
|
||||
|
||||
### ⚙️ **Step 6: Final Steps and Reboot**
|
||||
|
||||
1. **Configure Your System**:
|
||||
Once the installation is complete, you may need to configure your system settings, such as display resolution, Wi-Fi (if available), and user preferences.
|
||||
|
||||
2. **Reboot the System**:
|
||||
After installation, **reboot** your system and remove the USB drive.
|
||||
|
||||
3. **Boot into Snigdha OS**:
|
||||
Your system should boot into Snigdha OS. If you set up a **dual-boot** with other operating systems, you’ll see the bootloader menu to choose the OS.
|
||||
|
||||
4. **Offline Setup**:
|
||||
If you have any additional software or updates that need to be installed, you can use the **offline package manager** to install them later when you have an internet connection.
|
||||
|
||||
|
||||
|
||||
### 🎉 **Conclusion**
|
||||
|
||||
You’ve now installed Snigdha OS in **offline mode**! While some post-installation updates and software installation may require an internet connection, this method allows you to set up and use Snigdha OS in environments with no or limited internet access. This installation method is ideal for areas with poor connectivity, or for advanced users who want to configure their system fully offline.
|
||||
|
||||
Enjoy your new Snigdha OS setup! 😎🚀
|
@@ -0,0 +1,205 @@
|
||||
---
|
||||
sidebar_position: 6
|
||||
---
|
||||
# VirtualBox Installation
|
||||
|
||||
### 🖥️ **How to Install Snigdha OS in VirtualBox**
|
||||
|
||||
Installing **Snigdha OS** in **VirtualBox** is a great way to test or use Snigdha OS in a virtual environment without affecting your main system. Here's a detailed step-by-step guide to help you get Snigdha OS running in VirtualBox.
|
||||
|
||||
|
||||
|
||||
### 📥 **Step 1: Download Snigdha OS ISO**
|
||||
|
||||
1. **Go to the Official Snigdha OS Website**:
|
||||
Visit the official Snigdha OS download page:
|
||||
- [Snigdha OS Downloads](https://snigdhaos.org/downloads.html)
|
||||
|
||||
2. **Download the ISO File**:
|
||||
Choose the edition (KDE, GNOME, XFCE, etc.) and download the ISO file. The file will be something like:
|
||||
- `snigdhaos-YYYY.MM.DD-x86_64.iso`
|
||||
|
||||
|
||||
|
||||
### 💾 **Step 2: Install and Set Up VirtualBox**
|
||||
|
||||
1. **Download and Install VirtualBox**:
|
||||
- **For Windows**: Download from [VirtualBox Website](https://www.virtualbox.org/).
|
||||
- **For macOS**: Download from [VirtualBox Website](https://www.virtualbox.org/).
|
||||
- **For Linux**: You can install it via your package manager:
|
||||
```bash
|
||||
sudo pacman -S virtualbox # For Arch Linux and derivatives
|
||||
sudo apt install virtualbox # For Ubuntu/Debian
|
||||
sudo dnf install virtualbox # For Fedora
|
||||
```
|
||||
|
||||
2. **Launch VirtualBox**:
|
||||
After installation, launch **VirtualBox** from your applications menu.
|
||||
|
||||
|
||||
|
||||
### ⚙️ **Step 3: Create a New Virtual Machine**
|
||||
|
||||
1. **Click on "New"**:
|
||||
Open VirtualBox and click on the **New** button to create a new virtual machine.
|
||||
|
||||
2. **Set the Name and Type**:
|
||||
- **Name**: Choose a name for your virtual machine (e.g., "Snigdha OS").
|
||||
- **Type**: Select **Linux**.
|
||||
- **Version**: Select **Linux 2.6 / 3.x / 4.x (64-bit)** (or a similar option depending on the version of Snigdha OS).
|
||||
|
||||
3. **Allocate Memory**:
|
||||
- Assign **at least 2 GB of RAM** (more is recommended if your system can handle it). The default setting is usually fine, but you can increase it if you want better performance.
|
||||
|
||||
4. **Create a Virtual Hard Disk**:
|
||||
- **Virtual Hard Disk Type**: Choose **VDI** (VirtualBox Disk Image).
|
||||
- **Storage on Physical Hard Disk**: Choose **Dynamically allocated** (this will allow the virtual disk to grow as needed).
|
||||
- **Size**: Allocate **at least 20 GB** of disk space (the more the better, depending on your needs).
|
||||
|
||||
|
||||
|
||||
### 💿 **Step 4: Mount the Snigdha OS ISO**
|
||||
|
||||
1. **Go to Settings**:
|
||||
After creating the virtual machine, click on the **Settings** button.
|
||||
|
||||
2. **Mount the ISO**:
|
||||
- Go to the **Storage** tab.
|
||||
- Under **Controller: IDE**, click the empty **disk icon** and then click **Choose a disk file**.
|
||||
- Select the Snigdha OS ISO file you downloaded earlier.
|
||||
|
||||
|
||||
|
||||
### 🔄 **Step 5: Configure Virtual Machine Settings (Optional)**
|
||||
|
||||
1. **Adjust Display Settings**:
|
||||
- Go to the **Display** tab in the settings and increase the **Video Memory** to at least 64 MB to ensure smooth graphics.
|
||||
- Enable **3D Acceleration** (if your hardware supports it) for better performance.
|
||||
|
||||
2. **Network Settings**:
|
||||
- In the **Network** tab, ensure that the adapter is set to **Attached to NAT** (this allows the virtual machine to access the internet).
|
||||
|
||||
|
||||
|
||||
### 🔌 **Step 6: Start the Virtual Machine and Install Snigdha OS**
|
||||
|
||||
1. **Start the Virtual Machine**:
|
||||
Click the **Start** button in VirtualBox.
|
||||
|
||||
2. **Boot from the ISO**:
|
||||
The virtual machine will boot from the Snigdha OS ISO. You’ll see the Snigdha OS **Live Session** screen. If it doesn't boot, make sure the ISO is properly mounted in the **Storage** section.
|
||||
|
||||
3. **Launch the Installer**:
|
||||
Once in the live environment, click on the **Garuda Installer** icon on the desktop to start the installation process.
|
||||
|
||||
|
||||
|
||||
### ⚙️ **Step 7: Install Snigdha OS**
|
||||
|
||||
1. **Select Language and Region**:
|
||||
Choose your **language**, **keyboard layout**, and **timezone**.
|
||||
|
||||
2. **Partitioning**:
|
||||
- If you're using a single disk, you can choose **Erase disk and install Garuda** for automatic partitioning.
|
||||
- Alternatively, select **Manual Partitioning** if you need to create custom partitions.
|
||||
|
||||
3. **User Configuration**:
|
||||
- Set your **username**, **password**, and **root password**.
|
||||
- Choose **Btrfs** as the default filesystem for Garuda (or ext4 if preferred).
|
||||
|
||||
4. **Start the Installation**:
|
||||
After configuring your settings, click **Install** to begin the installation process. The installer will copy files, install packages, and set up your system.
|
||||
|
||||
|
||||
|
||||
### 🔄 **Step 8: Complete the Installation and Reboot**
|
||||
|
||||
1. **Wait for Installation to Finish**:
|
||||
The installation may take a while, depending on the speed of your system and the amount of software being installed. The progress will be shown in the installer.
|
||||
|
||||
2. **Reboot the Virtual Machine**:
|
||||
Once the installation is complete, the installer will prompt you to reboot the system. Click **Reboot Now** and remove the ISO file from the virtual drive in VirtualBox.
|
||||
|
||||
|
||||
|
||||
### 🖥️ **Step 9: Boot into Snigdha OS**
|
||||
|
||||
1. **Reboot**:
|
||||
After the installation, reboot the virtual machine. It will boot into your new **Snigdha OS** installation.
|
||||
|
||||
2. **Login**:
|
||||
Enter the **username** and **password** you set during the installation to log into Snigdha OS.
|
||||
|
||||
|
||||
|
||||
### 🎉 **Step 10: Post-Installation Steps**
|
||||
|
||||
1. **Update the System**:
|
||||
After logging in, open a terminal and update your system:
|
||||
```bash
|
||||
sudo pacman -Syu
|
||||
```
|
||||
|
||||
2. **Install Additional Software**:
|
||||
You can install additional software using the **Garuda Assistant** or the **Pacman** package manager.
|
||||
|
||||
3. **Enjoy Snigdha OS**:
|
||||
Now that your Snigdha OS is installed and running in VirtualBox, you can explore the KDE Plasma desktop or the desktop environment you chose during the installation.
|
||||
|
||||
|
||||
|
||||
### 🎉 **Conclusion**
|
||||
|
||||
You’ve successfully installed **Snigdha OS** in **VirtualBox**! This method allows you to run Snigdha OS on your system without affecting your main operating system. VirtualBox provides an isolated environment where you can experiment with Snigdha OS, install software, and test configurations.
|
||||
|
||||
Enjoy exploring Snigdha OS! 😎🚀
|
||||
|
||||
|
||||
|
||||
# VMware and GNOME Boxes Installation
|
||||
|
||||
### VMware
|
||||
|
||||
1. **Download and Install VMware**:
|
||||
- **For Windows/Mac**: Download VMware Workstation Player from [VMware's website](https://www.vmware.com/products/workstation-player.html).
|
||||
- **For Linux**: Install VMware Workstation using your package manager or download the .bundle file from VMware's site and run it in the terminal.
|
||||
|
||||
2. **Create a New Virtual Machine**:
|
||||
- Open VMware and click **Create a New Virtual Machine**.
|
||||
- Choose **Typical** installation.
|
||||
- Select **Installer disc image file (iso)** and browse for the Snigdha OS ISO.
|
||||
- Follow the on-screen instructions to set the VM's resources (RAM, disk size, etc.).
|
||||
|
||||
3. **Install Snigdha OS**:
|
||||
- After setting up the virtual machine, click **Power on** to start the VM.
|
||||
- The VM will boot from the Snigdha OS ISO, and you can proceed with the installation as described earlier.
|
||||
|
||||
4. **Finish Installation**:
|
||||
- Once installation is complete, reboot the VM and remove the ISO from the virtual drive to boot into the newly installed Snigdha OS.
|
||||
|
||||
|
||||
|
||||
### GNOME Boxes
|
||||
|
||||
1. **Install GNOME Boxes**:
|
||||
- **For Linux**: Install via your package manager.
|
||||
```bash
|
||||
sudo apt install gnome-boxes # For Ubuntu/Debian
|
||||
sudo pacman -S gnome-boxes # For Arch Linux
|
||||
```
|
||||
|
||||
2. **Create a New Virtual Machine**:
|
||||
- Launch **GNOME Boxes**.
|
||||
- Click **+** to create a new virtual machine.
|
||||
- Select the **Snigdha OS ISO** you downloaded.
|
||||
|
||||
3. **Install Snigdha OS**:
|
||||
- Follow the on-screen instructions to configure resources (like RAM and disk space).
|
||||
- Once configured, start the VM, and it will boot from the ISO to begin the installation.
|
||||
|
||||
4. **Complete Installation**:
|
||||
- Follow the installation steps and reboot after installation to boot into your new Snigdha OS installation.
|
||||
|
||||
|
||||
|
||||
Enjoy using Snigdha OS in any of these virtual environments! 😄
|
@@ -0,0 +1,175 @@
|
||||
---
|
||||
sidebar_position: 5
|
||||
---
|
||||
|
||||
# Online Installation
|
||||
|
||||
### 🌐 **How to Install Snigdha OS Online (With Internet Connection)**
|
||||
|
||||
Snigdha OS is a powerful and feature-packed distribution, and the **online installation** method provides the easiest and most efficient way to install Snigdha OS. This method requires an active internet connection to download the latest updates, packages, and additional software during the installation process.
|
||||
|
||||
Here's a detailed step-by-step guide to install **Snigdha OS** using the **online installation** method:
|
||||
|
||||
|
||||
|
||||
### 📥 **Step 1: Download Snigdha OS ISO**
|
||||
|
||||
1. **Go to the Official Snigdha OS Website**:
|
||||
Visit the Snigdha OS download page:
|
||||
- [Snigdha OS Downloads](https://snigdhaos.org/downloads.html)
|
||||
|
||||
2. **Select Your Preferred Edition**:
|
||||
Snigdha OS offers various desktop environments like KDE, GNOME, XFCE, and more. Choose the one that suits your preference.
|
||||
|
||||
3. **Download the ISO File**:
|
||||
Click on the link for the desired edition to download the ISO file. The file will typically be named:
|
||||
- `snigdhaos-linux-YYYY.MM.DD-x86_64.iso`
|
||||
|
||||
|
||||
|
||||
### 💾 **Step 2: Create a Bootable USB Drive**
|
||||
|
||||
You’ll need to create a bootable USB to install Snigdha OS. You can use **Ventoy**, **Rufus** (for Windows), or **dd** (for Linux) to create the bootable USB.
|
||||
|
||||
#### **For Linux Users (Using `dd`)**
|
||||
|
||||
1. **Insert USB Drive**:
|
||||
Plug in a USB drive with at least 4 GB capacity.
|
||||
|
||||
2. **Identify USB Drive**:
|
||||
Use the `lsblk` command to identify the device (e.g., `/dev/sdX`):
|
||||
```bash
|
||||
lsblk
|
||||
```
|
||||
|
||||
3. **Create Bootable USB**:
|
||||
Run the following `dd` command to copy the Snigdha OS ISO to your USB (replace `/dev/sdX` with your USB device path):
|
||||
```bash
|
||||
sudo dd if=snigdhaos-linux-YYYY.MM.DD-x86_64.iso of=/dev/sdX bs=4M status=progress oflag=sync
|
||||
```
|
||||
|
||||
4. **Eject USB**:
|
||||
After the process is complete, safely eject the USB:
|
||||
```bash
|
||||
sudo eject /dev/sdX
|
||||
```
|
||||
|
||||
#### **For Windows Users (Using Rufus)**
|
||||
|
||||
1. **Download and Install Rufus**:
|
||||
Download **Rufus** from [https://rufus.ie/](https://rufus.ie/) and install it.
|
||||
|
||||
2. **Open Rufus** and Select the USB Drive.
|
||||
|
||||
3. **Choose Snigdha OS ISO** and Select the Partition Scheme:
|
||||
Choose **GPT** for UEFI-based systems and **MBR** for legacy BIOS systems.
|
||||
|
||||
4. **Start the Process**:
|
||||
Click **Start** to create the bootable USB. Wait until it’s done.
|
||||
|
||||
|
||||
|
||||
### 🔌 **Step 3: Boot Into Snigdha OS Live Environment**
|
||||
|
||||
1. **Insert the Bootable USB** into the computer where you want to install Snigdha OS.
|
||||
|
||||
2. **Enter BIOS/UEFI**:
|
||||
Restart the system and enter the BIOS/UEFI settings (usually by pressing a key like `F2`, `DEL`, or `ESC`).
|
||||
|
||||
3. **Set USB as the First Boot Device**:
|
||||
In the BIOS/UEFI settings, set the USB drive as the first boot device.
|
||||
|
||||
4. **Save and Reboot**:
|
||||
Save your settings and reboot the computer. It will boot into the Snigdha OS live environment.
|
||||
|
||||
|
||||
|
||||
### ⚙️ **Step 4: Start the Online Installation Process**
|
||||
|
||||
1. **Launch the Installer**:
|
||||
Once the system boots into the Snigdha OS live environment, you’ll see a **Snigdha OS Installer** icon on the desktop. Click it to begin the installation.
|
||||
|
||||
2. **Select Language and Region**:
|
||||
Choose your preferred language, region, and keyboard layout.
|
||||
|
||||
3. **Connect to the Internet**:
|
||||
- **Wi-Fi**: Click on the network icon in the system tray and select your Wi-Fi network.
|
||||
- **Wired Connection**: If you’re using a wired connection, the system should automatically connect to the internet.
|
||||
|
||||
4. **Choose Installation Type**:
|
||||
You’ll have two main options:
|
||||
- **Erase disk and install Snigdha OS**: Automatically partitions and installs Snigdha OS (use this if you want a clean install).
|
||||
- **Manual partitioning**: If you want more control over your partitions, select this option to manually create and set partitions.
|
||||
|
||||
|
||||
|
||||
### 💻 **Step 5: Partitioning and Disk Setup**
|
||||
|
||||
1. **Select the Disk**:
|
||||
Choose the disk where you want to install Snigdha OS.
|
||||
|
||||
2. **Automatic Partitioning (Recommended)**:
|
||||
- **Erase and Install**: Select this if you want to overwrite the entire disk with Snigdha OS.
|
||||
- **Manual Partitioning**: Select this if you want to set up partitions manually, allowing you to configure the disk layout.
|
||||
|
||||
3. **Filesystem Choices**:
|
||||
- Snigdha OS uses **Btrfs** by default. You can also select **ext4** or **LVM** if preferred.
|
||||
|
||||
4. **Confirm and Continue**:
|
||||
Confirm your partition settings and proceed. The installer will format the disk and prepare it for the installation.
|
||||
|
||||
|
||||
|
||||
### 🧑💻 **Step 6: User Configuration**
|
||||
|
||||
1. **Create Your User**:
|
||||
Set up your **username** and **password**. You’ll also need to set the **root password**.
|
||||
|
||||
2. **Timezone and Locale**:
|
||||
Choose your **timezone** and **locale**. The installer should detect your location automatically, but you can adjust it if needed.
|
||||
|
||||
|
||||
|
||||
### 🌐 **Step 7: Installing Snigdha OS**
|
||||
|
||||
1. **Download Updates and Packages**:
|
||||
Since you’re installing online, the installer will fetch the latest updates and packages during the process. This requires an active internet connection. The installer will download:
|
||||
- **System updates**
|
||||
- **Additional packages** (drivers, codecs, utilities, etc.)
|
||||
|
||||
2. **Begin Installation**:
|
||||
Click the **Install** button to start the installation process. Snigdha OS will now be installed on your disk. This process may take some time, depending on your internet speed and disk performance.
|
||||
|
||||
|
||||
|
||||
### 🔄 **Step 8: Finalize the Installation**
|
||||
|
||||
1. **Wait for Installation to Complete**:
|
||||
The installation process will copy files, install software, and configure the system. This may take 15-30 minutes or more, depending on your system and internet speed.
|
||||
|
||||
2. **Reboot the System**:
|
||||
Once the installation is complete, you’ll be prompted to reboot the system. Remove the installation USB stick and reboot into Snigdha OS.
|
||||
|
||||
3. **Boot into Snigdha OS**:
|
||||
Your computer will now boot into Snigdha OS. If you installed it alongside another operating system, you will see the **GRUB bootloader** to select your OS.
|
||||
|
||||
|
||||
|
||||
### 🎉 **Step 9: Post-Installation Setup**
|
||||
|
||||
1. **Set Up Your System**:
|
||||
After booting into Snigdha OS, you may need to:
|
||||
- **Install additional software** using the **Snigdha OS Assistant** or **Pacman**.
|
||||
- **Update the system** if needed:
|
||||
```bash
|
||||
sudo pacman -Syu
|
||||
```
|
||||
|
||||
2. **Enjoy Your New Snigdha OS System**:
|
||||
Once everything is set up, you can start using Snigdha OS, explore the KDE Plasma desktop, install apps, and customize your system!
|
||||
|
||||
|
||||
|
||||
### 🎉 **Conclusion**
|
||||
|
||||
You’ve now successfully installed **Snigdha OS** using the **online installation** method! The online installation ensures you get the latest updates and packages during the installation process, making the system up-to-date as soon as it’s ready. Enjoy using Snigdha OS and all its powerful features! 😎🚀
|
@@ -0,0 +1,28 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
# System Requirements
|
||||
|
||||
### 🌟 **System Requirements for Snigdha OS**
|
||||
|
||||
To ensure a smooth experience with Snigdha OS, here are the minimum and recommended hardware specifications:
|
||||
|
||||
|
||||
|
||||
### 🔹 **Minimum Requirements**
|
||||
These are the bare minimum specifications needed to install and run Snigdha OS:
|
||||
- 🖥 **Processor**: Any x86_64 processor
|
||||
- 💾 **Disk Space**: 10 GB
|
||||
- 🐏 **RAM**: 1 GB
|
||||
|
||||
|
||||
|
||||
### 🔹 **Recommended Requirements**
|
||||
For better performance and to fully utilize the features of Snigdha OS, the following specifications are recommended:
|
||||
- 🖥 **Processor**: Core 2 Duo or higher
|
||||
- 💾 **Storage**: 30 GB HDD/SSD or more
|
||||
- 🐏 **RAM**: 2 GB or higher
|
||||
|
||||
|
||||
|
||||
Snigdha OS is designed to be lightweight and efficient, making it suitable for a wide range of hardware configurations. Whether you're using an older machine or a modern system, Snigdha OS can adapt and deliver a seamless user experience. ✨
|
@@ -0,0 +1,96 @@
|
||||
---
|
||||
sidebar_position: 6
|
||||
---
|
||||
# Contribution Guidelines
|
||||
|
||||
### ✨ **Contribution Guidelines for Snigdha OS**
|
||||
|
||||
Thank you for your interest in contributing to **Snigdha OS**! We’re excited to have you join our community. Contributions from users like you make Snigdha OS better, stronger, and more impactful. 💻💙
|
||||
|
||||
|
||||
|
||||
### 🚀 **Getting Started**
|
||||
|
||||
Before contributing, please make sure to:
|
||||
|
||||
📜 **Read Our Code of Conduct**: By participating, you agree to uphold our Code of Conduct, ensuring a welcoming and respectful environment for everyone.
|
||||
|
||||
|
||||
|
||||
### 🌟 **How Can You Contribute?**
|
||||
|
||||
There are many ways to make a difference! Choose what suits you best:
|
||||
|
||||
#### 🐞 **Reporting Bugs**
|
||||
Encountered a bug? Let us know by opening an issue on our **issue tracker**!
|
||||
- **Option 1**: If you're unsure about the repository causing the bug, raise the issue on our [universal issue tracker](https://github.com/SnigdhaOS/Issues).
|
||||
- **Option 2**: If you know the specific repository, raise the issue there.
|
||||
|
||||
👉 Be sure to include:
|
||||
- Steps to reproduce the bug.
|
||||
- Expected behavior vs. actual behavior.
|
||||
- Screenshots, logs, or any additional information that might help us debug the issue.
|
||||
|
||||
#### 🌟 **Requesting Features**
|
||||
Got an idea to make Snigdha OS even better? Open a feature request issue on our **issue tracker** and let us know your vision! Your feedback is invaluable to shaping the future of Snigdha OS.
|
||||
|
||||
#### 👩💻 **Code Contributions**
|
||||
Want to contribute code? Follow these steps:
|
||||
1️⃣ **Fork** the repository to your GitHub account. Learn [how to fork a GitHub repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo).
|
||||
2️⃣ **Clone** the forked repository to your local machine. Learn [how to clone a GitHub repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository).
|
||||
3️⃣ **Create a New Branch** for your changes. Learn [how to create branches](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging).
|
||||
4️⃣ Make your changes and ensure they align with our coding standards.
|
||||
5️⃣ Write tests to cover your changes (if applicable).
|
||||
6️⃣ Run existing tests to ensure they still pass.
|
||||
7️⃣ **Commit** your changes with clear, descriptive commit messages. Follow [Conventional Commits](https://www.conventionalcommits.org/).
|
||||
8️⃣ **Push** your changes to your forked repository.
|
||||
9️⃣ Open a **pull request (PR)** against the `master` branch of our repository. Learn [how to open a PR](https://docs.github.com/en/pull-requests).
|
||||
🔟 Provide a clear description in your PR, explaining your changes and any context the reviewers should know.
|
||||
|
||||
#### 📚 **Improving Documentation**
|
||||
Clear documentation is key! If you find areas for improvement in our docs (typos, errors, missing details), submit a pull request with your suggested edits.
|
||||
|
||||
|
||||
|
||||
### 🎨 **Code Standards**
|
||||
|
||||
To maintain a high-quality codebase, please:
|
||||
- Follow the coding style guide for the project's language.
|
||||
- Write **clear, concise comments** to explain your code.
|
||||
- Add **tests** for new functionality.
|
||||
- Ensure commits are **atomic** and focused on single logical changes.
|
||||
- Use descriptive commit messages following the [Conventional Commits format](https://www.conventionalcommits.org/).
|
||||
- Update documentation if your changes affect functionality.
|
||||
|
||||
|
||||
|
||||
### 🛠️ **Code Review Process**
|
||||
|
||||
All contributions go through a review process to ensure quality and consistency:
|
||||
1️⃣ Your pull request will be assigned to one or more reviewers.
|
||||
2️⃣ Reviewers will provide feedback and may suggest changes.
|
||||
3️⃣ You’ll need to address any feedback by updating your code.
|
||||
4️⃣ Once your changes meet all standards, your PR will be merged into the main branch.
|
||||
|
||||
|
||||
|
||||
### 📜 **Code of Conduct**
|
||||
|
||||
By contributing, you agree to abide by our **Code of Conduct**. This ensures that Snigdha OS remains a welcoming and inclusive space. Violations may result in rejection of contributions or removal from the project. Be kind, respectful, and supportive! 💕
|
||||
|
||||
|
||||
|
||||
### 💬 **Need Help?**
|
||||
|
||||
We’re here to help you get started and make meaningful contributions! Reach out to us:
|
||||
📧 **Email**: hello@snigdhaos.org
|
||||
|
||||
|
||||
|
||||
### ❤️ **Join Us in Building Snigdha OS**
|
||||
|
||||
Your contributions—whether code, documentation, or ideas—are essential to our success. Together, let’s make Snigdha OS the best it can be. Thank you for being part of our journey! 🌟
|
||||
|
||||
> "Alone, we can do so little; together, we can do so much." – Helen Keller
|
||||
|
||||
Let’s create something amazing! 🚀✨
|
@@ -0,0 +1,45 @@
|
||||
---
|
||||
sidebar_position: 8
|
||||
---
|
||||
# Frequently Asked
|
||||
Here are some frequently asked questions (FAQs) about Snigdha OS (penetration distribution):
|
||||
|
||||
**📌 What is penetration distribution?**
|
||||
|
||||
Penetration distribution refers to the process of distributing penetration testing tools and techniques across different areas of a network or system to identify vulnerabilities and potential entry points for attackers.
|
||||
|
||||
**📌 Why is penetration distribution important?**
|
||||
|
||||
Penetration distribution is important because it helps security professionals identify and address vulnerabilities before attackers can exploit them. By thoroughly testing various aspects of a network or system, organizations can better protect their assets and data from cyber threats.
|
||||
|
||||
**📌 What are some common penetration distribution techniques?**
|
||||
|
||||
Common penetration distribution techniques include network scanning, vulnerability assessment, exploitation of known vulnerabilities, social engineering, phishing attacks, and physical security testing. These techniques aim to identify weaknesses in different layers of a network or system.
|
||||
|
||||
**📌 How does penetration distribution differ from traditional security testing?**
|
||||
|
||||
Penetration distribution goes beyond traditional security testing by employing a broader range of techniques and tools to assess the security posture of an organization's infrastructure. It involves simulating real-world attack scenarios to uncover vulnerabilities that may not be detected by standard security measures.
|
||||
|
||||
**📌 What are the benefits of using penetration distribution services?**
|
||||
|
||||
The benefits of penetration distribution services include improved security posture, reduced risk of data breaches, compliance with regulatory requirements, enhanced incident response capabilities, and increased confidence in the effectiveness of security controls.
|
||||
|
||||
**📌 How often should penetration distribution be conducted?**
|
||||
|
||||
Penetration distribution should be conducted regularly, ideally as part of a comprehensive security testing program. The frequency of testing may vary depending on factors such as the organization's risk profile, industry regulations, and changes to the IT environment.
|
||||
|
||||
**📌 What are some best practices for conducting penetration distribution?**
|
||||
|
||||
Best practices for conducting penetration distribution include defining clear objectives and scope, obtaining appropriate permissions and approvals, using the latest tools and techniques, documenting findings thoroughly, prioritizing remediation efforts based on risk, and conducting post-test debriefings to identify lessons learned.
|
||||
|
||||
**📌 How can organizations ensure the confidentiality and integrity of penetration distribution results?**
|
||||
|
||||
Organizations can ensure the confidentiality and integrity of penetration distribution results by restricting access to sensitive information, encrypting data in transit and at rest, using secure communication channels, and implementing proper access controls and authentication mechanisms.
|
||||
|
||||
**📌 What are the limitations of penetration distribution?**
|
||||
|
||||
Limitations of penetration distribution include the inability to guarantee the absence of all vulnerabilities, the potential for disruption to normal business operations, the reliance on assumptions and estimations, and the need for ongoing monitoring and maintenance to address emerging threats.
|
||||
|
||||
**📌 How can organizations measure the effectiveness of penetration distribution efforts?**
|
||||
|
||||
Organizations can measure the effectiveness of penetration distribution efforts by tracking key performance indicators (KPIs) such as the number of vulnerabilities identified and remediated, the time to detect and respond to incidents, the cost-effectiveness of security controls, and improvements in overall security posture over time.
|
@@ -0,0 +1,68 @@
|
||||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Aim & Motivation
|
||||
|
||||
|
||||
### ✨ **Aim & Motivation of Snigdha OS**
|
||||
|
||||
Snigdha OS is not just another Linux distribution; it’s a carefully crafted platform built with purpose, efficiency, and innovation in mind. Here’s a detailed breakdown of its aim and motivation:
|
||||
|
||||
|
||||
|
||||
### 🎯 **Aim**
|
||||
**Snigdha OS** aims to provide:
|
||||
1️⃣ A **lightweight and efficient** Linux distribution for diverse hardware, from older machines to mobile devices and virtual environments.
|
||||
2️⃣ A **customizable platform** tailored to specific use cases, particularly **penetration testing** and **ethical hacking**.
|
||||
3️⃣ An operating system that bridges the gap between **professional cybersecurity practitioners** and **enthusiasts or learners**, ensuring accessibility and ease of use.
|
||||
4️⃣ A **secure and innovative ecosystem** that fosters experimentation, collaboration, and advancements in cybersecurity.
|
||||
|
||||
|
||||
|
||||
### 💡 **Motivation**
|
||||
|
||||
#### **1️⃣ Resource Efficiency & Versatility**
|
||||
Snigdha OS is motivated by the need for an operating system that runs efficiently on a wide range of hardware. Whether it's an older PC, a virtual environment, or a low-power device, Snigdha OS ensures optimal performance without compromising functionality.
|
||||
|
||||
|
||||
|
||||
#### **2️⃣ Minimalism & Customization**
|
||||
Inspired by the philosophy of minimalism, Snigdha OS provides users with a clean slate—a base system that can be customized to meet individual needs.
|
||||
- Users can build their environment from scratch, tailoring it with tools and features for **penetration testing** and **ethical hacking**.
|
||||
- This approach minimizes bloat and maximizes usability.
|
||||
|
||||
|
||||
|
||||
#### **3️⃣ Security-Centric Design**
|
||||
Security is at the heart of Snigdha OS:
|
||||
- It is **hardened and optimized** for ethical hacking tasks, ensuring that users have a reliable platform for vulnerability assessments and cybersecurity practices.
|
||||
- Pre-installed tools and configurations streamline ethical hacking workflows, saving time and reducing setup complexity.
|
||||
|
||||
|
||||
|
||||
#### **4️⃣ Empowering Learning & Professional Growth**
|
||||
Snigdha OS supports both:
|
||||
- **Experienced professionals** who need a dependable penetration testing platform.
|
||||
- **Learners and enthusiasts** who want to explore cybersecurity in a structured, user-friendly environment.
|
||||
|
||||
Educational resources, documentation, and community support provide a nurturing space for users to grow and contribute.
|
||||
|
||||
|
||||
#### **5️⃣ Fostering Innovation**
|
||||
Snigdha OS encourages:
|
||||
- Experimentation with **new tools, techniques, and methodologies** in the cybersecurity domain.
|
||||
- A community-driven approach where users and developers collaborate, exchange ideas, and contribute improvements.
|
||||
- Transparency and accessibility through its **open-source** model, ensuring that anyone can participate, learn, and innovate.
|
||||
|
||||
|
||||
### 🌍 **Community-Driven Vision**
|
||||
At its core, Snigdha OS is more than just software; it’s a platform for collaboration, growth, and exploration in cybersecurity. The community plays a crucial role in shaping its evolution by:
|
||||
- Contributing code and tools.
|
||||
- Sharing insights and expertise.
|
||||
- Creating documentation and educational content.
|
||||
|
||||
Snigdha OS thrives on this collective effort, enabling innovation while upholding the principles of **open-source freedom**.
|
||||
|
||||
|
||||
Snigdha OS is motivated by a vision of empowering users with a lightweight, secure, and customizable platform that not only meets current cybersecurity challenges but also inspires future advancements. 🚀🌟
|
@@ -0,0 +1,29 @@
|
||||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
# Story & Name
|
||||
|
||||
### 🌟 **The Story and Name Behind Snigdha OS**
|
||||
|
||||
#### 💡 **The Name**
|
||||
The name **Snigdha OS** carries a deeply personal significance to its creator, **Eshan Roy**, widely known as **eshanized**. As the **founder, lead maintainer, and developer** of Snigdha OS, Eshan drew inspiration for the name from **Mubasshira Snigdha**, a figure of immense importance in his life.
|
||||
|
||||
Initially, the project was known by its codename **"Project N"** during the early development phase. However, when the first official release was launched on **December 31, 2023**, Eshan chose to rebrand it as **Snigdha OS** to honor Mubasshira Snigdha’s memory.
|
||||
|
||||
Eshan, the **former CEO of Tonmoy Infrastructure**, continues to receive unwavering support from the company. Tonmoy Infrastructure remains a key backer of Snigdha OS, ensuring its development thrives. 🚀
|
||||
|
||||
|
||||
#### 💔 **The Story**
|
||||
Behind the name lies a heartfelt and poignant story. **Mubasshira Snigdha**, Eshan Roy’s late girlfriend, tragically passed away in **18th June, 2023**. Her untimely departure left a profound impact on Eshan, inspiring him to immortalize her memory through his work.
|
||||
|
||||
Naming the project **Snigdha OS** was Eshan’s way of creating a **living tribute** to her—a meaningful endeavor that would preserve her name and legacy. Through this operating system, her memory continues to inspire users and developers worldwide. 💻💙
|
||||
|
||||
Snigdha OS is not just a technological creation—it’s a testament to love, loss, and the enduring power of remembrance. The operating system embodies a vision for innovation while standing as a beautiful memorial to Mubasshira Snigdha’s impact on Eshan's life.
|
||||
|
||||
|
||||
### ✨ **A Legacy Beyond Code**
|
||||
Snigdha OS represents more than an open-source Linux distribution; it is a bridge between technology and human connection. It’s a project fueled by passion, personal meaning, and the unwavering determination to turn loss into inspiration.
|
||||
|
||||
Through **Snigdha OS**, Mubasshira Snigdha’s name will continue to resonate, not only in Eshan's heart but also in the global community of users who benefit from his work. 🌍
|
||||
|
||||
Let Snigdha OS inspire you, not only as a powerful tool but also as a reminder that the stories we carry can shape the world in profound ways. ❤️✨
|
@@ -0,0 +1,101 @@
|
||||
---
|
||||
sidebar_position: 9
|
||||
---
|
||||
|
||||
# Privacy Policy for Snigdha OS
|
||||
|
||||
**Effective Date:** 09 January, 2025
|
||||
**Last Updated:** 09 January, 2025
|
||||
|
||||
Welcome to Snigdha OS! 🌟 Your privacy is our top priority. This Privacy Policy explains how we handle your information while you use Snigdha OS. By installing or using Snigdha OS, you agree to the practices described below.
|
||||
|
||||
|
||||
|
||||
## 1. 📋 **Information We Collect**
|
||||
|
||||
Snigdha OS is designed to respect your privacy. By default, we do not collect any personal data. However, certain features, applications, or third-party services may collect limited data. Here's what might be collected:
|
||||
|
||||
### a. 📊 **System Diagnostics and Usage Data**
|
||||
- Logs to debug and improve performance.
|
||||
- Crash reports that may include anonymous system details (e.g., device type, error logs).
|
||||
|
||||
### b. ✍️ **User-Provided Data**
|
||||
- Information you enter while using Snigdha OS features, such as preferences and configurations.
|
||||
|
||||
### c. 🌐 **Third-Party Services**
|
||||
- Apps or repositories integrated into Snigdha OS may collect data as per their own privacy policies. We recommend reviewing them before use.
|
||||
|
||||
|
||||
|
||||
## 2. 🎯 **How We Use Your Information**
|
||||
|
||||
Any data collected is used solely for the following purposes:
|
||||
- 💡 Enhancing your experience by diagnosing and fixing technical issues.
|
||||
- 🔐 Ensuring system security and stability.
|
||||
- 📥 Delivering updates and new features.
|
||||
|
||||
Snigdha OS **does not** use your data for advertising or sell it to third parties. 🚫
|
||||
|
||||
|
||||
|
||||
## 3. 🤝 **Sharing Your Data**
|
||||
|
||||
We do not share your data with others, except in these rare situations:
|
||||
- **📜 Legal Requirements:** When we’re legally obligated to comply with a valid legal request.
|
||||
- **🌐 Third-Party Apps:** If you choose to use third-party software, their privacy policies will apply.
|
||||
|
||||
|
||||
|
||||
## 4. 🔒 **How We Protect Your Data**
|
||||
|
||||
Your security is our responsibility. We implement advanced measures to safeguard your information, including:
|
||||
- 🔑 Encryption for sensitive data stored on your device.
|
||||
- 🛡️ Secure update mechanisms to prevent unauthorized changes.
|
||||
- 🛠️ Regular patches and vulnerability fixes.
|
||||
|
||||
Despite our best efforts, no system is completely invulnerable. We recommend adopting good security practices like enabling firewalls and updating software regularly. 🛠️
|
||||
|
||||
|
||||
|
||||
## 5. 🙌 **Your Rights**
|
||||
|
||||
As a user of Snigdha OS, you have full control over your data. Your rights include:
|
||||
- **🔍 Access:** View or download any collected data (if applicable).
|
||||
- **✏️ Control:** Enable or disable data collection features in the system settings.
|
||||
- **🗑️ Erasure:** Request deletion of identifiable data, where possible.
|
||||
|
||||
To exercise these rights, please contact us at 📧 [Insert Email Address].
|
||||
|
||||
|
||||
|
||||
## 6. 🧩 **Third-Party Applications**
|
||||
|
||||
Some apps or repositories in Snigdha OS are provided by third parties. Each of these apps is governed by its own privacy policy. 📝
|
||||
|
||||
**Pro Tip:** Review the privacy settings of any third-party software you install for complete transparency.
|
||||
|
||||
|
||||
|
||||
## 7. 🍪 **Cookies and Tracking**
|
||||
|
||||
Snigdha OS does not use cookies or trackers by default. However, certain apps or web-based features may use cookies to function. For more control, check the privacy settings within those applications. 🔍
|
||||
|
||||
|
||||
|
||||
## 8. 🔄 **Policy Updates**
|
||||
|
||||
We may update this Privacy Policy from time to time to reflect new features, services, or legal requirements. 📢 If significant changes are made, we’ll notify you through official channels.
|
||||
|
||||
|
||||
|
||||
## 9. 📬 **Contact Us**
|
||||
|
||||
We value your feedback! If you have any questions, concerns, or requests, feel free to reach out:
|
||||
|
||||
📧 **Email:** privacy@snigdhaos.org
|
||||
📍 **Address:** N/A
|
||||
📞 **Phone:** N/A
|
||||
|
||||
|
||||
|
||||
**By using Snigdha OS, you acknowledge that you have read and understood this Privacy Policy.** 🛡️💙
|
@@ -0,0 +1,53 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
# Code of Conduct
|
||||
|
||||
### Snigdha OS Code Of Conduct
|
||||
A code of conduct outlines expected behavior and guidelines for individuals within a specific community, organization, or group.
|
||||
|
||||
:::info
|
||||
It is mandatory to follow our **Code of Conduct**.
|
||||
:::
|
||||
|
||||
**Introduction:**
|
||||
[Snigdha OS Forum](https://forum.snigdhaos.org/) is dedicated to providing a respectful, inclusive, and safe environment for all members, regardless of race, ethnicity, gender, sexual orientation, disability, age, religion, or any other characteristic. This Code of Conduct outlines the principles and guidelines that all members are expected to follow to maintain a positive and welcoming atmosphere.
|
||||
|
||||
**📌 Respect and Inclusivity:**
|
||||
- Treat all members with respect, kindness, and empathy.
|
||||
- Value diverse perspectives and experiences, and avoid discriminatory or offensive language and behavior.
|
||||
- Be mindful of the impact your words and actions may have on others, and strive to create an environment where everyone feels valued and included.
|
||||
|
||||
**📌 Professionalism:**
|
||||
- Conduct yourself in a professional manner at all times, both online and offline.
|
||||
- Refrain from engaging in personal attacks, harassment, or bullying of any kind.
|
||||
- Resolve disagreements and conflicts constructively and respectfully, focusing on finding solutions rather than assigning blame.
|
||||
|
||||
**📌 Integrity and Honesty:**
|
||||
- Be honest and transparent in your interactions with fellow members and stakeholders.
|
||||
- Avoid spreading false information or engaging in deceptive practices.
|
||||
- Respect the confidentiality of sensitive information shared within the organization/community.
|
||||
|
||||
**📌 Collaboration and Cooperation:**
|
||||
- Foster a culture of collaboration, cooperation, and teamwork.
|
||||
- Support and encourage fellow members, and be willing to offer assistance and guidance when needed.
|
||||
- Value constructive feedback and use it as an opportunity for growth and improvement.
|
||||
|
||||
**📌 Accountability:**
|
||||
- Take responsibility for your words and actions, and acknowledge and learn from mistakes.
|
||||
- Hold yourself and others accountable for upholding the principles and guidelines outlined in this Code of Conduct.
|
||||
- Report any violations of the Code of Conduct to the appropriate authorities or designated individuals within the organization/community.
|
||||
|
||||
**📌 Safety and Well-being:**
|
||||
- Prioritize the safety and well-being of all members, both physically and emotionally.
|
||||
- Refrain from engaging in behavior that may endanger or harm others.
|
||||
- Report any concerns or incidents related to safety or well-being to the appropriate authorities or designated individuals promptly.
|
||||
|
||||
**📌 Compliance and Enforcement:**
|
||||
- Comply with all applicable laws, regulations, and policies, both within and outside the organization/community.
|
||||
- Violations of this Code of Conduct may result in disciplinary action, up to and including suspension or expulsion from the organization/community.
|
||||
- The enforcement of this Code of Conduct will be administered fairly and impartially, with due process and consideration for all parties involved.
|
||||
|
||||
|
||||
>**Conclusion:**
|
||||
By adhering to this Code of Conduct, we can create a supportive and inclusive community where all members can thrive and contribute positively to our shared goals and objectives. Thank you for your commitment to upholding these principles and for helping to maintain a respectful and welcoming environment for everyone.
|
@@ -0,0 +1,158 @@
|
||||
---
|
||||
sidebar_position: 5
|
||||
---
|
||||
# Coding Standard
|
||||
|
||||
### ✨ **Coding Standards for Snigdha OS Development**
|
||||
|
||||
To ensure that Snigdha OS maintains a high-quality codebase, it’s essential to follow these coding standards. These guidelines promote readability, maintainability, and collaboration while ensuring the code remains efficient and secure. 🚀
|
||||
|
||||
|
||||
|
||||
### 1️⃣ **Consistent Naming Conventions**
|
||||
✅ Use meaningful and descriptive names for variables, functions, and classes.
|
||||
✅ Stick to a consistent naming convention across the codebase:
|
||||
- **camelCase** for variables and functions.
|
||||
- **PascalCase** for classes and constructors.
|
||||
- **snake_case** for constants and configuration keys.
|
||||
|
||||
|
||||
|
||||
### 2️⃣ **Indentation and Formatting**
|
||||
✅ Use consistent indentation (2 or 4 spaces preferred). Avoid using tabs.
|
||||
✅ Follow a consistent formatting style (e.g., braces alignment, spacing).
|
||||
✅ Limit line length to 80-100 characters for better readability.
|
||||
✅ Remove unnecessary whitespaces and trailing spaces.
|
||||
|
||||
|
||||
|
||||
### 3️⃣ **Comments**
|
||||
✅ Add comments to explain complex logic, algorithms, or unusual decisions.
|
||||
✅ Keep comments concise, relevant, and synchronized with code changes.
|
||||
✅ Avoid obvious comments like `// Incrementing i by 1`.
|
||||
|
||||
```javascript
|
||||
// Good Example:
|
||||
function calculateTax(income) {
|
||||
// Calculates tax based on progressive slabs.
|
||||
...
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 4️⃣ **Modularity and Code Reusability**
|
||||
✅ Break down code into small, reusable functions or modules.
|
||||
✅ Group related functionalities into classes or namespaces for better organization.
|
||||
|
||||
|
||||
|
||||
### 5️⃣ **Error Handling**
|
||||
✅ Use proper error-handling mechanisms like `try-catch` blocks or error codes.
|
||||
✅ Avoid exposing internal logic in error messages.
|
||||
|
||||
```python
|
||||
try:
|
||||
result = perform_operation()
|
||||
except ValueError as e:
|
||||
print("Invalid input. Please try again.") # Avoid exposing "ValueError: details"
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 6️⃣ **Code Readability**
|
||||
✅ Write simple and clear code. Avoid unnecessary complexity.
|
||||
✅ Use descriptive variable and function names instead of single-letter identifiers.
|
||||
✅ Favor clarity over cleverness.
|
||||
|
||||
|
||||
|
||||
### 7️⃣ **Consistent Code Style**
|
||||
✅ Follow the style guide for the programming language used (e.g., PEP 8 for Python, ESLint for JavaScript).
|
||||
✅ Adopt consistent practices for spacing, indentation, and braces placement.
|
||||
|
||||
|
||||
|
||||
### 8️⃣ **Documentation**
|
||||
✅ Document every function, class, and module with clear descriptions.
|
||||
✅ Include parameter details, return values, and potential exceptions in documentation.
|
||||
|
||||
```python
|
||||
def calculate_area(radius):
|
||||
"""
|
||||
Calculates the area of a circle.
|
||||
|
||||
Args:
|
||||
radius (float): The radius of the circle.
|
||||
|
||||
Returns:
|
||||
float: The area of the circle.
|
||||
"""
|
||||
return 3.14 * radius ** 2
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 9️⃣ **Testing**
|
||||
✅ Write unit tests for all critical functionality.
|
||||
✅ Aim for at least 80% code coverage.
|
||||
✅ Automate tests where possible with frameworks like `pytest`, `Jest`, or `JUnit`.
|
||||
|
||||
|
||||
|
||||
### 🔟 **Version Control**
|
||||
✅ Use Git for version control. Follow branching strategies like **Git Flow**.
|
||||
✅ Write clear, descriptive commit messages in the [Conventional Commits](https://www.conventionalcommits.org) format:
|
||||
|
||||
```
|
||||
feat: add feature for user authentication
|
||||
fix: resolve bug in payment gateway integration
|
||||
docs: update README with installation steps
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 1️⃣1️⃣ **Performance Considerations**
|
||||
✅ Write efficient algorithms with optimal time and space complexity.
|
||||
✅ Avoid unnecessary loops, nested loops, or redundant operations.
|
||||
✅ Use lazy loading or caching for heavy computations or data fetching.
|
||||
|
||||
|
||||
|
||||
### 1️⃣2️⃣ **Security**
|
||||
✅ Sanitize and validate all user inputs.
|
||||
✅ Use parameterized queries for database operations to avoid SQL injection.
|
||||
✅ Regularly audit code for vulnerabilities like XSS, CSRF, or buffer overflows.
|
||||
|
||||
|
||||
|
||||
### 1️⃣3️⃣ **Dependencies and Third-party Libraries**
|
||||
✅ Use only necessary and trusted libraries.
|
||||
✅ Keep dependencies updated to ensure compatibility and fix vulnerabilities.
|
||||
|
||||
|
||||
|
||||
### 1️⃣4️⃣ **Internationalization (i18n) and Localization (l10n)**
|
||||
✅ Design code to support multiple languages and locales.
|
||||
✅ Externalize strings into resource files for easy translation.
|
||||
|
||||
|
||||
|
||||
### 1️⃣5️⃣ **Accessibility**
|
||||
✅ Ensure UI components follow accessibility standards (e.g., WCAG).
|
||||
✅ Provide alternative text for images and ensure keyboard navigation.
|
||||
|
||||
|
||||
|
||||
### 1️⃣6️⃣ **Concurrency and Thread Safety**
|
||||
✅ For concurrent operations, write thread-safe code to avoid race conditions.
|
||||
✅ Use synchronization mechanisms like locks or semaphores.
|
||||
|
||||
|
||||
|
||||
### 🔑 **Key Principles**
|
||||
1️⃣ **Readability**: Write code as if the next person maintaining it is you in six months.
|
||||
2️⃣ **Modularity**: Make changes easier by keeping code decoupled and modular.
|
||||
3️⃣ **Consistency**: Adopt a uniform style to avoid confusion and ensure maintainability.
|
||||
|
||||
Following these standards will not only improve code quality but also foster a collaborative and professional environment. Happy coding! 🎉👩💻👨💻
|
@@ -0,0 +1,159 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
slug: /
|
||||
---
|
||||
|
||||
# Overview
|
||||
### 🌟 **Overview of Snigdha OS**
|
||||
|
||||
Snigdha OS is a 🌟 **lightweight** and 🛠️ **highly customizable** Linux distribution built on ⚙️ Arch Linux and powered by the 🚀 **Linux Zen Kernel**. Crafted with a focus on 🎯 **minimalism** and 🌈 **user-centric design**, it offers a smooth and seamless experience for both 🖥️ **general usage** and 🔒 **penetration testing**.
|
||||
|
||||
The ecosystem features a dedicated 🛡️ **penetration testing distribution** and **Blackbox** 🧰, a custom framework for efficiently managing security tools.
|
||||
|
||||
**Powered by:** 💡 TONMOY INFRASTRUCTURE.
|
||||
|
||||
|
||||
|
||||
🚀 **Features of Snigdha OS**
|
||||
As a **penetration testing distribution**, Snigdha OS offers a robust suite of features designed to empower security professionals. Here's what makes it stand out:
|
||||
|
||||
|
||||
|
||||
📌 **Tailored Toolset**
|
||||
Snigdha OS comes with a pre-installed arsenal of penetration testing tools for tasks like network scanning, vulnerability assessment, and exploitation. 🛠️ Everything you need, ready to go!
|
||||
|
||||
💡 *Tip:* Expand your toolkit using the **Online Installation** method during setup or via **Blackbox** post-installation.
|
||||
|
||||
|
||||
|
||||
📌 **Customization and Optimization**
|
||||
Fine-tune the OS to maximize performance, minimize resource usage, and streamline workflows—perfect for efficient and focused penetration testing.
|
||||
|
||||
|
||||
|
||||
📌 **Security-Focused**
|
||||
Built with security as a priority:
|
||||
- 🛡️ Features like **SELinux** or **AppArmor**
|
||||
- 🔥 Strict firewall rules
|
||||
- ❌ Disables unnecessary services to reduce the attack surface
|
||||
|
||||
|
||||
|
||||
📌 **Documentation and Support**
|
||||
Comprehensive **documentation** and an active **community** make Snigdha OS beginner-friendly. From tool usage to troubleshooting, you'll have guidance every step of the way.
|
||||
|
||||
🛠️ *Contribute:* Help us improve our documentation!
|
||||
|
||||
|
||||
|
||||
📌 **Learning Opportunities**
|
||||
Perfect for education and training, Snigdha OS offers a controlled environment to explore penetration testing tools and techniques—great for workshops, certifications, and aspiring security pros. 📚
|
||||
|
||||
|
||||
|
||||
📌 **Consistency and Reproducibility**
|
||||
Standardized tools and configurations ensure **consistent results** across different testing environments—essential for compliance audits and routine security assessments. ✅
|
||||
|
||||
|
||||
|
||||
📌 **Portability and Accessibility**
|
||||
Designed to work seamlessly on:
|
||||
- 🖥️ **Physical hardware**
|
||||
- 📦 **Virtual machines**
|
||||
- ☁️ **Cloud instances**
|
||||
|
||||
|
||||
|
||||
📌 **Legal and Ethical Compliance**
|
||||
Snigdha OS includes clear licenses and guidelines to promote ethical penetration testing, helping users stay aligned with industry standards. ⚖️
|
||||
|
||||
|
||||
|
||||
📌 **Innovation and Experimentation**
|
||||
Be part of the **future of cybersecurity**! Contribute to creating cutting-edge tools, techniques, and methodologies that redefine possibilities in penetration testing. ✨
|
||||
|
||||
|
||||
|
||||
**Snigdha OS**: Your ultimate ally in penetration testing and cybersecurity exploration. 🌐
|
||||
|
||||
🎯 **Purposes of Snigdha OS**
|
||||
Snigdha OS embraces the core values of **open-source development**: **transparency**, **collaboration**, and **innovation**. Here's how it aligns with these principles:
|
||||
|
||||
|
||||
|
||||
📌 **Transparency**
|
||||
🔍 The source code is fully open and accessible, fostering trust by allowing anyone to inspect, verify, and enhance the system's security.
|
||||
|
||||
|
||||
|
||||
📌 **Community Collaboration**
|
||||
🌍 Contributions from a global community ensure continuous improvement, the addition of innovative features, and robust, peer-reviewed development practices.
|
||||
|
||||
|
||||
|
||||
📌 **Accessibility**
|
||||
📖 Freely available to all, Snigdha OS promotes inclusivity and adaptability, ensuring it meets diverse user needs.
|
||||
|
||||
|
||||
|
||||
📌 **Innovation**
|
||||
💡 Snigdha OS inspires creativity, encouraging developers to experiment and design groundbreaking features and solutions that benefit everyone.
|
||||
|
||||
|
||||
|
||||
📌 **Freedom**
|
||||
🛠️ No vendor lock-in! Users have the freedom to modify, customize, and share the OS according to their preferences.
|
||||
|
||||
|
||||
|
||||
📌 **Security**
|
||||
🔒 A vigilant community promptly identifies and patches vulnerabilities, delivering a secure and reliable computing experience.
|
||||
|
||||
|
||||
|
||||
📌 **Stability and Reliability**
|
||||
⚙️ Rigorously tested for consistent performance, Snigdha OS provides a dependable platform for various use cases.
|
||||
|
||||
|
||||
|
||||
📌 **Education and Learning**
|
||||
🎓 Ideal for learning Linux systems, programming, and cybersecurity techniques through hands-on exploration—perfect for both beginners and experts.
|
||||
|
||||
|
||||
|
||||
Snigdha OS: Empowering a collaborative, innovative, and secure future in open-source computing. 🚀
|
||||
|
||||
|
||||
### ❤️ **How You Can Help Snigdha OS**
|
||||
|
||||
Snigdha OS thrives on community contributions. Here’s how you can support us:
|
||||
|
||||
#### 📌 **For Developers**
|
||||
- Contribute to the Snigdha OS codebase or packages.
|
||||
- Create new tools and features that benefit the community.
|
||||
|
||||
#### 📌 **For Writers**
|
||||
- Improve our documentation for better user onboarding.
|
||||
- Write blogs, articles, or guides to help others understand Snigdha OS better.
|
||||
|
||||
#### 📌 **For Translators**
|
||||
- Help translate Snigdha OS into multiple languages, making it accessible to a broader audience.
|
||||
|
||||
#### 📌 **Financial Support**
|
||||
- Donations via **GitHub Sponsors** or **OpenCollective** help cover operational costs.
|
||||
- Financial support has enabled us to fund core developers in the past.
|
||||
|
||||
#### 📌 **For Users**
|
||||
- Report bugs or suggest features through **GitHub Issues**.
|
||||
- Engage with the Snigdha OS community to share your experience and help newcomers.
|
||||
|
||||
#### 📌 **Spread the Word**
|
||||
- Blog, tweet, or talk about Snigdha OS! Increased awareness brings more contributors and accelerates development.
|
||||
|
||||
> **Community matters!** Join us to build, improve, and make Snigdha OS better together.
|
||||
|
||||
|
||||
|
||||
### 🌟 **Conclusion**
|
||||
|
||||
Snigdha OS is more than just an operating system—it’s a community-driven project aimed at empowering users through transparency, security, and innovation. Whether you're a developer, learner, or enthusiast, there’s a place for you in the Snigdha OS ecosystem. Together, let’s create a better, more secure future in computing! 💻✨
|
@@ -0,0 +1,45 @@
|
||||
---
|
||||
sidebar_position: 7
|
||||
---
|
||||
# Release Notes
|
||||
|
||||
### 🥳 **Snigdha OS Release ARCTIC V** 🎉
|
||||
|
||||
**Release Date:** December 21, 2024
|
||||
|
||||
We are excited to announce the release of **Snigdha OS ARCTIC V**! This release brings a range of new features, improvements, and fixes to make your experience with Snigdha OS even better. Below are the highlights:
|
||||
|
||||
#### 🌟 **New Features:**
|
||||
- **🛠️ Improved Penetration Testing Tools**: Added new and enhanced tools to the Blackbox framework, improving the overall security toolkit for penetration testers.
|
||||
- **💻 Snigdha OS Installer Update**: The installation process is now more intuitive with new prompts and error handling.
|
||||
- **🌐 Language Support Expansion**: Snigdha OS now supports multiple languages! In addition to English, Hindi and Bengali are now available for the user interface.
|
||||
|
||||
#### 🚀 **Performance Enhancements:**
|
||||
- **⚡ Faster Boot Time**: Optimized startup sequence, reducing boot time for both virtual and physical installations.
|
||||
- **🧹 Reduced Resource Usage**: Performance improvements for minimal installations, making Snigdha OS lighter and more efficient for low-resource systems.
|
||||
|
||||
#### 🐞 **Bug Fixes:**
|
||||
- **🌍 Fixed Network Connectivity Issues**: Resolved a rare bug where network interfaces would not be properly detected on certain hardware configurations.
|
||||
- **🎨 UI Improvements**: Fixed several UI glitches, including alignment issues in the installation wizard and system settings panel.
|
||||
- **💪 Stability Enhancements**: Addressed minor stability issues related to system updates and package management.
|
||||
|
||||
#### 🔒 **Security Updates:**
|
||||
- **🔧 Kernel Updates**: Updated the Zen Kernel to the latest stable version for better hardware compatibility and security patches.
|
||||
- **🛡️ Tool Security**: Various tools in the Blackbox framework have received security updates to address recent vulnerabilities.
|
||||
|
||||
#### 🚨 **Known Issues:**
|
||||
- ⚠️ Some third-party applications may not be fully compatible with the latest version of the Zen Kernel.
|
||||
- 🖥️ Minor display issues may still occur with specific hardware configurations in dark mode.
|
||||
|
||||
#### 🔄 **Upgrade Instructions:**
|
||||
To upgrade to Snigdha OS ARCTIC V, simply run the following command:
|
||||
|
||||
```bash
|
||||
sudo pacman -Syyu
|
||||
```
|
||||
|
||||
For a fresh installation, download the latest ISO from our [official website](https://snigdhaos.org/) and follow the installation guide.
|
||||
|
||||
|
||||
|
||||
Thank you for using Snigdha OS! 🎉 We appreciate your continued support and feedback. Stay tuned for more updates, and feel free to reach out to us on [Discord](https://discord.gg/snigdha-os) or [GitHub](https://github.com/Snigdha-OS) for any questions or suggestions. 🙌
|
@@ -0,0 +1,176 @@
|
||||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Customize Snigdha OS
|
||||
|
||||
### 🖌️ **Guide to Customizing Snigdha OS**
|
||||
|
||||
Snigdha OS, with its polished look and powerful tools, is highly customizable. Whether you want to tweak the desktop environment, improve system performance, or add your personal touch, this guide will walk you through the steps to make Snigdha OS your own.
|
||||
|
||||
|
||||
|
||||
### ⚙️ **Step 1: Select Your Desktop Environment (DE)**
|
||||
Snigdha OS comes with several desktop environments, such as KDE Plasma, GNOME, XFCE, i3, and more. Customization options depend on your DE.
|
||||
|
||||
- **KDE Plasma**: Highly customizable with themes, widgets, and layouts.
|
||||
- **GNOME**: Simplistic and clean with extensions.
|
||||
- **XFCE**: Lightweight and minimalistic with theming options.
|
||||
|
||||
#### To install additional DEs:
|
||||
```bash
|
||||
sudo pacman -S xfce4 gnome
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🎨 **Step 2: Change Themes**
|
||||
Snigdha OS includes **Snigdha OS Settings Manager** for managing themes, icons, and cursors.
|
||||
|
||||
#### Using Snigdha OS Settings Manager:
|
||||
1. Open **Snigdha OS Settings Manager** from the application menu.
|
||||
2. Navigate to the **Appearance** or **Desktop Theme** section.
|
||||
3. Select and apply a **theme**, **icon pack**, or **cursor**.
|
||||
|
||||
#### For KDE Plasma:
|
||||
1. Go to **System Settings → Appearance**.
|
||||
2. Customize:
|
||||
- **Global Theme**: Change the entire desktop look.
|
||||
- **Plasma Style**: Adjust panel and widget styles.
|
||||
- **Icons**: Pick a new icon set.
|
||||
- **Application Style**: Change the window and button styles.
|
||||
|
||||
#### Installing New Themes:
|
||||
1. Open **System Settings → Appearance → Get New Themes**.
|
||||
2. Browse and install themes, icons, or cursors.
|
||||
3. Apply them from the same menu.
|
||||
|
||||
|
||||
|
||||
### 📂 **Step 3: Customize Widgets and Panels**
|
||||
Widgets and panels enhance functionality and aesthetics.
|
||||
|
||||
#### For KDE Plasma:
|
||||
- Right-click on the desktop or panel and select **Add Widgets**.
|
||||
- Drag and drop widgets to the desired location.
|
||||
- Adjust panel size, position, and contents by right-clicking the panel and selecting **Edit Panel**.
|
||||
|
||||
|
||||
|
||||
### 🖼️ **Step 4: Change Wallpapers**
|
||||
Snigdha OS comes with stunning default wallpapers, but you can easily add your own.
|
||||
|
||||
#### Steps:
|
||||
1. Right-click on the desktop and select **Configure Desktop** (KDE) or **Change Background** (GNOME).
|
||||
2. Select a wallpaper from the list or **Add Image** to upload your own.
|
||||
|
||||
#### Online Wallpapers:
|
||||
Install dynamic wallpaper applications like **Komorebi** or use online wallpaper tools.
|
||||
|
||||
|
||||
|
||||
### 🖥️ **Step 5: Modify the GRUB Bootloader**
|
||||
Customize the GRUB bootloader for a personal touch.
|
||||
|
||||
#### Install a GRUB Theme:
|
||||
1. Install `grub-customizer`:
|
||||
```bash
|
||||
sudo pacman -S grub-customizer
|
||||
```
|
||||
2. Open GRUB Customizer and select a theme.
|
||||
3. Save and reboot to see the changes.
|
||||
|
||||
|
||||
|
||||
### 💡 **Step 6: Add Extensions and Plugins**
|
||||
Extensions add extra functionality to your desktop environment.
|
||||
|
||||
#### For GNOME:
|
||||
1. Install `gnome-shell-extensions`:
|
||||
```bash
|
||||
sudo pacman -S gnome-shell-extensions
|
||||
```
|
||||
2. Use the **GNOME Extensions** website ([extensions.gnome.org](https://extensions.gnome.org)) to enable and manage extensions.
|
||||
|
||||
#### For KDE:
|
||||
Use the **KDE Store** to download and manage plugins, scripts, and widgets.
|
||||
|
||||
|
||||
|
||||
### 🔧 **Step 7: Adjust Performance Settings**
|
||||
Snigdha OS includes tools for optimizing performance.
|
||||
|
||||
#### Using Snigdha OS Assistant:
|
||||
1. Open **Snigdha OS Assistant**.
|
||||
2. Enable performance tweaks like **ZRAM**, **CPU governor**, or **RAM optimization**.
|
||||
3. Use **System Cleaner** to remove unnecessary files.
|
||||
|
||||
#### Manage Startup Applications:
|
||||
Disable unnecessary startup applications to improve boot time:
|
||||
1. Open **Startup and Shutdown** in **System Settings**.
|
||||
2. Uncheck apps you don’t need at startup.
|
||||
|
||||
|
||||
|
||||
### 🔍 **Step 8: Install Useful Applications**
|
||||
Snigdha OS includes essential applications, but you can add more tools to suit your workflow.
|
||||
|
||||
#### Example Commands:
|
||||
- **Install a Web Browser**:
|
||||
```bash
|
||||
sudo pacman -S firefox
|
||||
```
|
||||
- **Install a Terminal Emulator**:
|
||||
```bash
|
||||
sudo pacman -S alacritty
|
||||
```
|
||||
- **Install AUR Packages** (e.g., Google Chrome):
|
||||
```bash
|
||||
yay -S google-chrome
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🖥️ **Step 9: Configure Keybindings**
|
||||
Set custom keyboard shortcuts for frequently used actions.
|
||||
|
||||
#### KDE Plasma:
|
||||
1. Open **System Settings → Shortcuts**.
|
||||
2. Customize global shortcuts for applications and system actions.
|
||||
|
||||
#### GNOME:
|
||||
1. Open **Settings → Keyboard → Custom Shortcuts**.
|
||||
2. Add and modify shortcuts for specific commands or actions.
|
||||
|
||||
|
||||
|
||||
### 🎵 **Step 10: Customize Sounds**
|
||||
You can change system sounds to add a unique auditory flair.
|
||||
|
||||
#### KDE Plasma:
|
||||
1. Open **System Settings → Audio → Event Sounds**.
|
||||
2. Choose and apply custom sound themes.
|
||||
|
||||
|
||||
|
||||
### 🛡️ **Step 11: Enable Gaming Tweaks**
|
||||
Snigdha OS has a **Gaming Edition** optimized for gaming, but you can also add tweaks manually.
|
||||
|
||||
#### Install Gaming Tools:
|
||||
1. Install **Lutris** for managing game libraries:
|
||||
```bash
|
||||
sudo pacman -S lutris
|
||||
```
|
||||
2. Install **Steam**:
|
||||
```bash
|
||||
sudo pacman -S steam
|
||||
```
|
||||
3. Enable **GameMode** for performance:
|
||||
```bash
|
||||
sudo pacman -S gamemode
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🚀 **Conclusion**
|
||||
Snigdha OS is one of the most customizable Linux distributions, offering endless possibilities to tailor your desktop. From themes to performance tweaks, you can make it your perfect operating system. Dive in, experiment, and enjoy your personalized Linux experience! 🎉
|
@@ -0,0 +1,110 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
# Install Packages
|
||||
|
||||
### 📦 **How to Install a Package on Snigdha OS**
|
||||
|
||||
Installing packages on Snigdha OS primarily involves using the **Pacman** package manager or an **AUR helper** for community-contributed software. Here's a step-by-step guide:
|
||||
|
||||
|
||||
|
||||
### 🛠️ **Step 1: Update Your System**
|
||||
Before installing a package, ensure your system is up-to-date to avoid dependency issues:
|
||||
```bash
|
||||
sudo pacman -Syu
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 📂 **Step 2: Search for a Package**
|
||||
To find the package you want to install, use the following command:
|
||||
```bash
|
||||
pacman -Ss package-name
|
||||
```
|
||||
|
||||
#### Example:
|
||||
Search for the Firefox browser:
|
||||
```bash
|
||||
pacman -Ss firefox
|
||||
```
|
||||
This command displays available packages with "firefox" in their name or description.
|
||||
|
||||
|
||||
|
||||
### ✅ **Step 3: Install the Package**
|
||||
Once you know the exact package name, install it using:
|
||||
```bash
|
||||
sudo pacman -S package-name
|
||||
```
|
||||
|
||||
#### Example:
|
||||
Install Firefox:
|
||||
```bash
|
||||
sudo pacman -S firefox
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 📦 **Step 4: Verify Installation**
|
||||
To check if a package is installed:
|
||||
```bash
|
||||
pacman -Q package-name
|
||||
```
|
||||
|
||||
#### Example:
|
||||
Verify Firefox installation:
|
||||
```bash
|
||||
pacman -Q firefox
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🔍 **Step 5: Explore Package Details**
|
||||
View information about an installed package:
|
||||
```bash
|
||||
pacman -Qi package-name
|
||||
```
|
||||
|
||||
#### Example:
|
||||
```bash
|
||||
pacman -Qi firefox
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🌐 **Installing AUR Packages**
|
||||
If the package you want is not in the official repositories but is available in the **Arch User Repository (AUR)**, use an AUR helper like `yay` or `paru`.
|
||||
|
||||
#### Install a Package from AUR
|
||||
```bash
|
||||
yay -S package-name
|
||||
```
|
||||
|
||||
#### Example:
|
||||
Install Google Chrome from AUR:
|
||||
```bash
|
||||
yay -S google-chrome
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🧹 **Clean Up After Installation**
|
||||
After installing a package, clean up unused dependencies (optional):
|
||||
```bash
|
||||
sudo pacman -Rns $(pacman -Qdtq)
|
||||
```
|
||||
|
||||
|
||||
:::tip
|
||||
:::
|
||||
1. **Enable Parallel Downloads**: To speed up installation, enable parallel downloads in `/etc/pacman.conf` by adding:
|
||||
```
|
||||
ParallelDownloads = 5
|
||||
```
|
||||
2. **Use Trusted Sources**: Only install AUR packages from trusted sources and review the `PKGBUILD` file before installation.
|
||||
|
||||
|
||||
|
||||
### 🎉 **Conclusion**
|
||||
Installing packages on Snigdha OS is straightforward with `pacman`. For additional software, AUR helpers like `yay` expand the possibilities. With these tools, you can access a vast array of software tailored to your needs! 🚀
|
@@ -0,0 +1,88 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
# Language
|
||||
|
||||
### 🌐 **Installing Language Packs and Google Fonts on Arch/Snigdha OS**
|
||||
|
||||
Here’s how you can install language packs for better localization support and Google Fonts for enhanced typography.
|
||||
|
||||
---
|
||||
|
||||
### 🌏 **Step 1: Install Language Packs**
|
||||
|
||||
#### **Step 1.1: Install System Language Pack**
|
||||
Language packs are provided by the desktop environment or specific applications. For example:
|
||||
|
||||
- **KDE Plasma**:
|
||||
```bash
|
||||
sudo pacman -S plasma-desktop kde-l10n
|
||||
```
|
||||
- **GNOME**:
|
||||
```bash
|
||||
sudo pacman -S gnome-shell gnome-getting-started-docs
|
||||
```
|
||||
|
||||
- **Snigdha OS Asian Fonts**:
|
||||
```bash
|
||||
sudo pacman -S snigdhaos-asian-fonts
|
||||
```
|
||||
|
||||
#### **Step 1.2: Enable Your Preferred Language**
|
||||
1. Open **System Settings** → **Regional Settings** or **Language**.
|
||||
2. Select and add your desired language.
|
||||
3. Apply the changes and reboot if necessary.
|
||||
|
||||
#### **Step 1.3: Install Additional Fonts for Localization**
|
||||
To display text correctly in specific languages (e.g., CJK, Arabic):
|
||||
```bash
|
||||
sudo pacman -S noto-fonts noto-fonts-cjk noto-fonts-emoji noto-fonts-extra
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### ✍️ **Step 2: Install Google Fonts**
|
||||
|
||||
Google Fonts can be installed to enhance the typography for web design, office applications, or general use.
|
||||
|
||||
#### **Option 1: Install via Pacman**
|
||||
Arch Linux provides a package for Google Fonts:
|
||||
```bash
|
||||
sudo pacman -S ttf-google-fonts
|
||||
```
|
||||
|
||||
#### **Option 2: Install via AUR**
|
||||
For the latest collection of Google Fonts, use an AUR helper like `yay`:
|
||||
```bash
|
||||
yay -S ttf-google-fonts-git
|
||||
```
|
||||
|
||||
#### **Option 3: Manual Installation**
|
||||
1. Download the fonts:
|
||||
- Visit the [Google Fonts](https://fonts.google.com/) website.
|
||||
- Select and download your desired font(s).
|
||||
|
||||
2. Extract and install:
|
||||
```bash
|
||||
mkdir -p ~/.local/share/fonts
|
||||
unzip /path/to/downloaded-fonts.zip -d ~/.local/share/fonts
|
||||
```
|
||||
|
||||
3. Refresh the font cache:
|
||||
```bash
|
||||
fc-cache -fv
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### 🧹 **Step 3: Verify Installation**
|
||||
- **Check Available Fonts**:
|
||||
```bash
|
||||
fc-list | grep "font-name"
|
||||
```
|
||||
- Test the fonts in applications like LibreOffice, GIMP, or your web browser.
|
||||
|
||||
---
|
||||
|
||||
### 🎉 **Conclusion**
|
||||
With language packs and Google Fonts installed, your system will be well-suited for multilingual usage and professional-grade typography. Enjoy customizing your experience! 🚀
|
@@ -0,0 +1,107 @@
|
||||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
# Update Snigdha OS
|
||||
|
||||
### 🔄 **How to Update Snigdha OS**
|
||||
|
||||
Snigdha OS, based on Arch Linux, uses a **rolling release model**, meaning you always have access to the latest updates. Keeping your system up-to-date ensures stability, security, and access to the latest features.
|
||||
|
||||
Follow these steps to safely and effectively update your Snigdha OS system:
|
||||
|
||||
|
||||
|
||||
### 🔧 **Step 1: Open the Terminal**
|
||||
|
||||
Press `Ctrl + Alt + T` to open the terminal or use the **Konsole** or any terminal emulator installed on your system.
|
||||
|
||||
|
||||
|
||||
### 🔄 **Step 2: Update the System**
|
||||
|
||||
Run the following commands to update your Snigdha OS system:
|
||||
|
||||
#### **Basic Update Command**
|
||||
Use **Pacman** (the default package manager) to synchronize and upgrade packages:
|
||||
```bash
|
||||
sudo pacman -Syu
|
||||
```
|
||||
|
||||
#### **Snigdha OS Assistant (Optional)**
|
||||
Snigdha OS provides a GUI tool called **Snigdha OS Assistant** for system management, including updates.
|
||||
- Open **Snigdha OS Assistant** from the application menu.
|
||||
- Click on **Update System** and follow the prompts.
|
||||
|
||||
#### **With AUR Packages (Using an AUR Helper)**
|
||||
If you use AUR packages, update them alongside system packages with a tool like `yay` or `paru`:
|
||||
```bash
|
||||
yay -Syu
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🛠️ **Step 3: Rebuild Outdated Configurations**
|
||||
|
||||
After major updates, especially those involving the kernel or critical system components, rebuild configurations to avoid issues. Snigdha OS makes this easy with:
|
||||
```bash
|
||||
sudo pacman -S linux-headers
|
||||
```
|
||||
|
||||
If you use the **ZRAM** feature or **custom kernels**, ensure they're updated and aligned with the current system kernel.
|
||||
|
||||
|
||||
|
||||
### 🧹 **Step 4: Clean Up Unused Packages**
|
||||
|
||||
Remove unused or orphaned packages to free up space:
|
||||
```bash
|
||||
sudo pacman -Rns $(pacman -Qdtq)
|
||||
```
|
||||
|
||||
Clear the package cache to save disk space (Snigdha OS already does this automatically with **paccache**):
|
||||
```bash
|
||||
sudo paccache -r
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🚀 **Step 5: Reboot Your System**
|
||||
|
||||
If a kernel or other core system components were updated, reboot your system to apply the changes:
|
||||
```bash
|
||||
reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🌟 **Tips for Safe Updates**
|
||||
|
||||
1. **Use Snigdha OS's Snapshot Feature**:
|
||||
- Snigdha OS uses **Btrfs** snapshots via **Timeshift**. If something goes wrong during an update, you can roll back to a previous working state.
|
||||
- Before updating, create a manual snapshot:
|
||||
```bash
|
||||
sudo timeshift --create
|
||||
```
|
||||
|
||||
2. **Check for Arch News**:
|
||||
Before major updates, check the **Arch Linux News** page for important announcements:
|
||||
- [Arch Linux News](https://archlinux.org/news/)
|
||||
|
||||
3. **Run Updates Regularly**:
|
||||
Snigdha OS is a rolling release, so it's important to update frequently to avoid large, time-consuming updates and potential conflicts.
|
||||
|
||||
|
||||
|
||||
### 💻 **Example Commands**
|
||||
|
||||
Here’s a single command for a complete update, including AUR packages and cleaning up:
|
||||
```bash
|
||||
sudo pacman -Syu && yay -Syu && sudo pacman -Rns $(pacman -Qdtq)
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🎉 **Conclusion**
|
||||
|
||||
Keeping Snigdha OS updated is straightforward and ensures you always have the latest features and security patches. With tools like **Snigdha OS Assistant**, **Pacman**, and **Timeshift**, managing updates is efficient and safe. 🚀
|
@@ -0,0 +1,168 @@
|
||||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
# Troubleshooting Display Issues
|
||||
|
||||
If you're facing display issues like screen resolution problems, black screens, or no display output on Snigdha OS, follow this guide to get everything back to normal. Let’s fix it step by step! 🔧
|
||||
|
||||
|
||||
|
||||
### 1. **Check Display Cable and Connection 🖥️🔌**
|
||||
|
||||
#### **Is Your Display Properly Connected?**
|
||||
- Make sure your monitor or laptop screen is properly connected to the system.
|
||||
- If using an external monitor, ensure that the display cable (HDMI, VGA, DisplayPort, etc.) is firmly connected.
|
||||
- If applicable, check if the monitor is set to the correct input (HDMI1, HDMI2, etc.).
|
||||
|
||||
|
||||
|
||||
### 2. **Check for External Display Detection 📺📱**
|
||||
|
||||
If you’re using multiple displays, your external monitor might not be recognized automatically.
|
||||
|
||||
- Open the terminal and run:
|
||||
```bash
|
||||
xrandr
|
||||
```
|
||||
This will list all connected displays. If your external monitor isn't showing, you might need to force detection.
|
||||
|
||||
- To detect the monitor manually:
|
||||
```bash
|
||||
xrandr --auto
|
||||
```
|
||||
|
||||
- If the external monitor is still not detected, try to restart your system or use a different cable.
|
||||
|
||||
|
||||
|
||||
### 3. **Set the Correct Display Resolution 🎨💻**
|
||||
|
||||
Sometimes, the wrong resolution can cause display issues. Use `xrandr` to set the correct resolution.
|
||||
|
||||
- List available display modes:
|
||||
```bash
|
||||
xrandr
|
||||
```
|
||||
|
||||
- To change the resolution:
|
||||
```bash
|
||||
xrandr --output <DISPLAY_NAME> --mode <RESOLUTION>
|
||||
```
|
||||
Example:
|
||||
```bash
|
||||
xrandr --output HDMI-1 --mode 1920x1080
|
||||
```
|
||||
|
||||
Replace `<DISPLAY_NAME>` and `<RESOLUTION>` with your actual display name and resolution.
|
||||
|
||||
|
||||
|
||||
### 4. **Check Graphics Driver 🔧🖥️**
|
||||
|
||||
#### **Is Your Graphics Driver Installed?**
|
||||
Make sure you have the correct drivers installed for your graphics card.
|
||||
|
||||
- For **Intel graphics**:
|
||||
```bash
|
||||
sudo pacman -S xf86-video-intel
|
||||
```
|
||||
|
||||
- For **NVIDIA graphics**:
|
||||
```bash
|
||||
sudo pacman -S nvidia nvidia-utils
|
||||
```
|
||||
|
||||
- For **AMD graphics**:
|
||||
```bash
|
||||
sudo pacman -S xf86-video-amdgpu
|
||||
```
|
||||
|
||||
After installing the necessary driver, restart your system:
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 5. **Reconfigure Xorg 🎨🛠️**
|
||||
|
||||
Sometimes, Xorg (the display server) configuration might cause issues.
|
||||
|
||||
- Reconfigure Xorg by regenerating the configuration file:
|
||||
```bash
|
||||
sudo Xorg -configure
|
||||
```
|
||||
|
||||
- Then restart the system:
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 6. **Check Logs for Errors 📝🔍**
|
||||
|
||||
Check the system logs to find any errors related to the display.
|
||||
|
||||
- View Xorg logs:
|
||||
```bash
|
||||
cat /var/log/Xorg.0.log
|
||||
```
|
||||
|
||||
Look for error messages related to your graphics driver or display hardware.
|
||||
|
||||
|
||||
|
||||
### 7. **Check Display Manager 🌐⚙️**
|
||||
|
||||
If you’re getting a black screen after logging in, it could be a problem with your display manager.
|
||||
|
||||
- If using **LightDM**, restart it:
|
||||
```bash
|
||||
sudo systemctl restart lightdm
|
||||
```
|
||||
|
||||
- If using **GDM** (GNOME Display Manager), restart it:
|
||||
```bash
|
||||
sudo systemctl restart gdm
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 8. **Update System 💻🔄**
|
||||
|
||||
Make sure your system is up to date, as outdated packages may cause display issues.
|
||||
|
||||
- Update your system:
|
||||
```bash
|
||||
sudo pacman -Syu
|
||||
```
|
||||
|
||||
This ensures all packages, including graphics drivers, are up to date.
|
||||
|
||||
|
||||
|
||||
### 9. **Try Using a Different Display Server (Wayland vs Xorg) 🌙⚙️**
|
||||
|
||||
If you are facing issues with **Xorg**, try using **Wayland** instead, which is another display server protocol.
|
||||
|
||||
- On GNOME, you can choose Wayland or Xorg from the login screen (click the gear icon after selecting your user).
|
||||
|
||||
|
||||
|
||||
### 10. **Reboot Your System 🔄💻**
|
||||
|
||||
Sometimes, a simple reboot can fix display issues:
|
||||
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Conclusion 🎉
|
||||
|
||||
Display issues on Snigdha OS can usually be fixed by ensuring proper cables, checking drivers, and configuring the display settings. If problems continue, check for hardware faults or consult the Snigdha OS or Arch community for further assistance.
|
||||
|
||||
Enjoy your display! 🖥️🎨
|
@@ -0,0 +1,189 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Troubleshooting NVIDIA Issues
|
||||
|
||||
If you're facing issues with NVIDIA graphics or the proprietary NVIDIA driver on Snigdha OS, follow these steps to properly install, configure, and troubleshoot your NVIDIA driver setup.
|
||||
|
||||
|
||||
|
||||
### 1. **Ensure Your System is Updated 🖥️🔄**
|
||||
|
||||
Before installing or troubleshooting drivers, make sure your system is fully updated to avoid compatibility issues.
|
||||
|
||||
- Update your system:
|
||||
```bash
|
||||
sudo pacman -Syu
|
||||
```
|
||||
|
||||
- Reboot your system after the update:
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 2. **Check for Existing NVIDIA Drivers 🕵️♂️**
|
||||
|
||||
First, verify if the NVIDIA driver is already installed or partially installed.
|
||||
|
||||
- Check for the installed NVIDIA package:
|
||||
```bash
|
||||
pacman -Qs nvidia
|
||||
```
|
||||
|
||||
- If you see packages like `nvidia`, `nvidia-utils`, or `nvidia-dkms`, it indicates the driver is installed.
|
||||
|
||||
|
||||
|
||||
### 3. **Install the Proprietary NVIDIA Driver 🖱️🖥️**
|
||||
|
||||
#### **Install NVIDIA Drivers on Snigdha OS**
|
||||
Snigdha OS, being based on Arch Linux, supports the **proprietary NVIDIA drivers** provided by **nvidia** package, which provides full support for gaming, rendering, and GPU acceleration.
|
||||
|
||||
1. **For NVIDIA 390xx Legacy Cards** (older models):
|
||||
```bash
|
||||
sudo pacman -S nvidia-390xx
|
||||
```
|
||||
|
||||
2. **For Latest NVIDIA Drivers (most common)**:
|
||||
```bash
|
||||
sudo pacman -S nvidia nvidia-utils
|
||||
```
|
||||
|
||||
3. **For the NVIDIA Optimus (Hybrid Graphics)**:
|
||||
If you have a laptop with both Intel and NVIDIA graphics (Optimus), you may want to install the `bumblebee` or `nvidia-prime` package:
|
||||
|
||||
- For **Bumblebee** (for better battery life and automatic switching):
|
||||
```bash
|
||||
sudo pacman -S bumblebee primus
|
||||
sudo systemctl enable bumblebeed
|
||||
sudo systemctl start bumblebeed
|
||||
```
|
||||
|
||||
- For **NVIDIA Prime** (useful for newer systems):
|
||||
```bash
|
||||
sudo pacman -S nvidia-prime
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 4. **Configure Xorg for NVIDIA 🖥️⚙️**
|
||||
|
||||
Snigdha OS should automatically configure Xorg to use the NVIDIA driver upon installation. If it doesn’t work, you can manually configure it by creating or modifying the Xorg configuration.
|
||||
|
||||
- Create the NVIDIA configuration file:
|
||||
```bash
|
||||
sudo nvidia-xconfig
|
||||
```
|
||||
|
||||
- Restart the Xorg server or reboot the system:
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 5. **Verify the Installation ✅**
|
||||
|
||||
After installing or reconfiguring the NVIDIA drivers, verify the installation using the following commands:
|
||||
|
||||
- Check if NVIDIA modules are loaded correctly:
|
||||
```bash
|
||||
lsmod | grep nvidia
|
||||
```
|
||||
|
||||
- Check the NVIDIA driver version:
|
||||
```bash
|
||||
nvidia-smi
|
||||
```
|
||||
|
||||
This will show you information about the installed NVIDIA driver, including the GPU model, driver version, and usage statistics.
|
||||
|
||||
|
||||
|
||||
### 6. **Troubleshooting Common Issues 🛠️**
|
||||
|
||||
#### **No Display / Blank Screen 💻❌**
|
||||
|
||||
1. Ensure that the driver is properly loaded by checking the Xorg log:
|
||||
```bash
|
||||
cat /var/log/Xorg.0.log | grep nvidia
|
||||
```
|
||||
|
||||
2. If you still have no display, try booting into **recovery mode** and reinstall the drivers.
|
||||
|
||||
#### **Optimizing Hybrid Graphics (Optimus) 🖥️🔋**
|
||||
|
||||
If you're using an Optimus laptop with both Intel and NVIDIA, ensure that you're using either **Bumblebee** or **nvidia-prime** to manage the GPU switching.
|
||||
|
||||
- Test if Bumblebee is working with the `optirun` command:
|
||||
```bash
|
||||
optirun glxgears
|
||||
```
|
||||
|
||||
- For **NVIDIA Prime**, you can switch between the Intel GPU and the NVIDIA GPU using:
|
||||
```bash
|
||||
sudo prime-select nvidia # To use the NVIDIA GPU
|
||||
sudo prime-select intel # To switch back to the Intel GPU
|
||||
```
|
||||
|
||||
#### **Black Screen After Boot 💻❌**
|
||||
|
||||
1. If the system boots into a black screen, try the following:
|
||||
- Boot into a terminal or recovery mode and check the **Xorg logs** for errors.
|
||||
- Check the logs at `/var/log/Xorg.0.log` or `dmesg` for NVIDIA driver-related errors.
|
||||
|
||||
2. If needed, you can remove the NVIDIA drivers:
|
||||
```bash
|
||||
sudo pacman -Rns nvidia nvidia-utils
|
||||
```
|
||||
|
||||
And then reinstall or switch to **nouveau** (open-source NVIDIA driver):
|
||||
```bash
|
||||
sudo pacman -S xf86-video-nouveau
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 7. **Reinstall or Update NVIDIA Drivers 🔄**
|
||||
|
||||
If you encounter persistent issues, try reinstalling the drivers:
|
||||
|
||||
- Uninstall the NVIDIA drivers:
|
||||
```bash
|
||||
sudo pacman -Rns nvidia nvidia-utils
|
||||
```
|
||||
|
||||
- Reinstall the drivers:
|
||||
```bash
|
||||
sudo pacman -S nvidia nvidia-utils
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 8. **Check for Kernel Compatibility 🐧🛠️**
|
||||
|
||||
The NVIDIA driver requires a compatible kernel. If you recently updated your kernel or switched to a custom one, you may need to install the correct kernel modules.
|
||||
|
||||
- For the **Zen Kernel** (often used in Snigdha OS):
|
||||
```bash
|
||||
sudo pacman -S linux-zen
|
||||
```
|
||||
|
||||
- For other kernel versions, such as **linux-lts** (Long Term Support):
|
||||
```bash
|
||||
sudo pacman -S linux-lts
|
||||
```
|
||||
|
||||
- After installing a new kernel, you will need to rebuild or reinstall the NVIDIA kernel module:
|
||||
```bash
|
||||
sudo pacman -S nvidia-dkms
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Conclusion 🚀
|
||||
|
||||
By following these steps, you should be able to install, configure, and troubleshoot NVIDIA drivers on Snigdha OS. If you continue to experience issues, checking the **NVIDIA** and **Arch Wiki** documentation, as well as visiting Snigdha OS community forums, might help. Happy computing! 😄🎮
|
@@ -0,0 +1,190 @@
|
||||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Troubleshooting Sound Issues
|
||||
|
||||
If you're having trouble with sound on Snigdha OS, follow these steps to diagnose and resolve the issue. Whether it's no sound, low volume, or distorted audio, let's get your audio working properly! 🔧🎶
|
||||
|
||||
|
||||
|
||||
### 1. **Check the Audio Output 🔌🔊**
|
||||
|
||||
#### **Ensure the Correct Output Device is Selected**
|
||||
Sometimes, the wrong audio output device might be selected, especially if you have multiple devices (like speakers, headphones, or HDMI output).
|
||||
|
||||
- Open **PulseAudio Volume Control**:
|
||||
```bash
|
||||
sudo pacman -S pavucontrol
|
||||
pavucontrol
|
||||
```
|
||||
|
||||
- Go to the **Playback** tab and check that the audio is routed to the correct device.
|
||||
- In the **Output Devices** tab, make sure the desired audio output (e.g., headphones, speakers) is selected and not muted.
|
||||
|
||||
|
||||
|
||||
### 2. **Check Volume Levels 🔊🎛️**
|
||||
|
||||
#### **Ensure Volume is Turned Up**
|
||||
- Make sure the system volume is not muted or set too low.
|
||||
- You can adjust the volume with the sound settings in your desktop environment or use the command line:
|
||||
|
||||
- To check the volume with **`amixer`**:
|
||||
```bash
|
||||
amixer sget Master
|
||||
```
|
||||
|
||||
- To increase the volume:
|
||||
```bash
|
||||
amixer sset Master 50%+
|
||||
```
|
||||
|
||||
- To unmute:
|
||||
```bash
|
||||
amixer sset Master unmute
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 3. **Check Audio Driver Installation 🔧🎶**
|
||||
|
||||
#### **Is the Audio Driver Installed?**
|
||||
Snigdha OS uses **ALSA** (Advanced Linux Sound Architecture) and **PulseAudio** to manage audio. Ensure that the correct drivers are installed for your sound card.
|
||||
|
||||
- For **Intel HD Audio**:
|
||||
```bash
|
||||
sudo pacman -S alsa-utils
|
||||
sudo pacman -S alsa-firmware
|
||||
```
|
||||
|
||||
- For **Realtek Audio** (often found on laptops):
|
||||
```bash
|
||||
sudo pacman -S alsa-utils
|
||||
```
|
||||
|
||||
- For **NVIDIA HDMI Audio**:
|
||||
```bash
|
||||
sudo pacman -S nvidia
|
||||
```
|
||||
|
||||
- After installing, restart your system:
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 4. **Restart PulseAudio 🔄🔊**
|
||||
|
||||
Sometimes, restarting **PulseAudio** can resolve sound issues.
|
||||
|
||||
- To restart PulseAudio, run:
|
||||
```bash
|
||||
pulseaudio -k
|
||||
pulseaudio --start
|
||||
```
|
||||
|
||||
- You can also restart the service with:
|
||||
```bash
|
||||
sudo systemctl --user restart pulseaudio
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 5. **Check ALSA Mixer Levels 🎚️**
|
||||
|
||||
#### **Adjust ALSA Mixer Settings**
|
||||
The ALSA mixer might have some channels muted or set to low levels, which can cause sound problems.
|
||||
|
||||
- Open the ALSA mixer:
|
||||
```bash
|
||||
alsamixer
|
||||
```
|
||||
|
||||
- Use the arrow keys to navigate and adjust volume levels.
|
||||
- Unmute any muted channels by pressing `M` (if they are muted).
|
||||
|
||||
|
||||
|
||||
### 6. **Test Audio with `aplay` 🎧**
|
||||
|
||||
You can test if the system is producing audio by using `aplay`, a command-line sound player.
|
||||
|
||||
- Test the sound card with a sample sound:
|
||||
```bash
|
||||
aplay /usr/share/sounds/alsa/Front_Center.wav
|
||||
```
|
||||
|
||||
- If you hear the sound, the audio system is working. If not, it might indicate a deeper issue with your audio configuration.
|
||||
|
||||
|
||||
|
||||
### 7. **Check for Audio Errors in Logs 📝🔍**
|
||||
|
||||
Check the system logs to see if there are any relevant error messages related to sound.
|
||||
|
||||
- View PulseAudio logs:
|
||||
```bash
|
||||
journalctl --user -u pulseaudio
|
||||
```
|
||||
|
||||
- View ALSA logs:
|
||||
```bash
|
||||
dmesg | grep -i audio
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 8. **Reconfigure Audio Settings 🔧🎶**
|
||||
|
||||
#### **Reconfigure ALSA and PulseAudio**
|
||||
Sometimes, resetting the audio configuration can resolve conflicts:
|
||||
|
||||
- Delete the PulseAudio configuration:
|
||||
```bash
|
||||
rm -r ~/.config/pulse/
|
||||
```
|
||||
|
||||
- Reset ALSA:
|
||||
```bash
|
||||
sudo alsactl restore
|
||||
```
|
||||
|
||||
- Restart your system:
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 9. **Update Your System 💻🔄**
|
||||
|
||||
Ensure your system is up-to-date, as updates can fix bugs related to sound.
|
||||
|
||||
- Update your system:
|
||||
```bash
|
||||
sudo pacman -Syu
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 10. **Try Different Audio Tools 🎶🔊**
|
||||
|
||||
If the problem persists, consider trying different audio tools like **PipeWire** or **Jack**.
|
||||
|
||||
- For **PipeWire** (a modern audio server):
|
||||
```bash
|
||||
sudo pacman -S pipewire
|
||||
```
|
||||
|
||||
- After installing, restart your system:
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Conclusion 🎉
|
||||
|
||||
Sound issues on Snigdha OS can be caused by many factors, such as incorrect drivers, muted settings, or configuration problems. Follow this guide step by step to resolve most common sound issues. If the problem persists, check the community forums or support channels for additional help. Enjoy your sound! 🔊🎶
|
@@ -0,0 +1,151 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Troubleshooting Wi-Fi Issues
|
||||
|
||||
If you're facing Wi-Fi connectivity issues on Snigdha OS, don’t worry! Follow this guide to resolve the problem. It covers common issues and solutions. Let's get your Wi-Fi back up and running! 😄
|
||||
|
||||
|
||||
|
||||
### 1. **Check Wi-Fi Adapter 🏠🔍**
|
||||
|
||||
#### **Is Your Wi-Fi Adapter Recognized?**
|
||||
First, check if Snigdha OS recognizes your Wi-Fi adapter.
|
||||
|
||||
- Open a terminal and run:
|
||||
```bash
|
||||
ip link
|
||||
```
|
||||
Look for your Wi-Fi interface (usually named `wlan0`, `wlp2s0`, or similar). If it’s not listed, your adapter might not be recognized or the driver may be missing.
|
||||
|
||||
#### **Install Drivers 🚗💨**
|
||||
If your Wi-Fi adapter is not detected, you may need to install additional drivers.
|
||||
|
||||
- Check for available Wi-Fi drivers:
|
||||
```bash
|
||||
sudo pacman -Ss wifi
|
||||
```
|
||||
Install the appropriate driver for your device:
|
||||
```bash
|
||||
sudo pacman -S <driver-name>
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 2. **Check Wi-Fi Network Status 📶🔌**
|
||||
|
||||
#### **Make Sure Your Network is Active**
|
||||
Ensure that the Wi-Fi network you're trying to connect to is functioning properly. Try connecting with another device to verify the network works.
|
||||
|
||||
#### **Restart Your Router 🔄**
|
||||
If there are issues, try restarting your router by turning it off and on again.
|
||||
|
||||
|
||||
|
||||
### 3. **NetworkManager Issues ⚙️**
|
||||
|
||||
Snigdha OS uses **NetworkManager** to manage network connections. If it’s causing issues, try restarting it.
|
||||
|
||||
- Restart NetworkManager:
|
||||
```bash
|
||||
sudo systemctl restart NetworkManager
|
||||
```
|
||||
|
||||
Check the status of NetworkManager:
|
||||
```bash
|
||||
sudo systemctl status NetworkManager
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 4. **Verify Wireless Interface is Up 📡🆙**
|
||||
|
||||
Sometimes, the wireless interface might be down. Bring it up with this command:
|
||||
|
||||
```bash
|
||||
sudo ip link set wlan0 up
|
||||
```
|
||||
Replace `wlan0` with your correct interface name if it’s different.
|
||||
|
||||
|
||||
|
||||
### 5. **Check Wi-Fi Configuration 🛠️**
|
||||
|
||||
#### **NetworkManager Configuration 🖧**
|
||||
- Open **NetworkManager** and ensure your Wi-Fi network is listed. If it’s not, scan for networks again:
|
||||
```bash
|
||||
nmcli dev wifi rescan
|
||||
```
|
||||
|
||||
To connect to a network:
|
||||
```bash
|
||||
nmcli dev wifi connect <SSID> password <password>
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 6. **Check for Conflicting Software ⚠️🛑**
|
||||
|
||||
Sometimes, software like `netctl` or `wpa_supplicant` can conflict with NetworkManager.
|
||||
|
||||
- Disable `netctl`:
|
||||
```bash
|
||||
sudo systemctl disable netctl
|
||||
sudo systemctl stop netctl
|
||||
```
|
||||
|
||||
- Disable `wpa_supplicant`:
|
||||
```bash
|
||||
sudo systemctl disable wpa_supplicant
|
||||
sudo systemctl stop wpa_supplicant
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 7. **Check for IP Address Issues 🌐🛠️**
|
||||
|
||||
If Wi-Fi is connected but you have no internet access, there may be an IP address issue.
|
||||
|
||||
- To release and renew your IP address:
|
||||
```bash
|
||||
sudo dhclient -r
|
||||
sudo dhclient
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 8. **Check Logs for Errors 📝🔍**
|
||||
|
||||
If the issue persists, checking the system logs might help.
|
||||
|
||||
- View `dmesg` logs related to Wi-Fi:
|
||||
```bash
|
||||
dmesg | grep wlan
|
||||
```
|
||||
|
||||
Look for error messages related to your Wi-Fi device, such as missing firmware or drivers.
|
||||
|
||||
|
||||
|
||||
### 9. **Test Using a Different Network 🌍📶**
|
||||
|
||||
If your Wi-Fi issue persists, try connecting to a different Wi-Fi network, like a mobile hotspot or another router, to see if the issue is with your device or the original network.
|
||||
|
||||
|
||||
|
||||
### 10. **Reboot Your System 🔄💻**
|
||||
|
||||
Sometimes, a simple reboot can fix the problem:
|
||||
|
||||
```bash
|
||||
sudo reboot
|
||||
```
|
||||
|
||||
|
||||
|
||||
### Conclusion 🎉
|
||||
|
||||
Wi-Fi issues on Snigdha OS can usually be resolved by checking the adapter, ensuring drivers are installed, and troubleshooting with NetworkManager. If problems continue, check your hardware or consult the Snigdha OS or Arch community.
|
||||
|
||||
Happy browsing! 🌐🚀
|
@@ -0,0 +1,122 @@
|
||||
---
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# Installing with AUR
|
||||
|
||||
|
||||
### 🌟 **Installing Packages with an AUR Helper on Snigdha OS**
|
||||
|
||||
Snigdha OS is known for its powerful **Arch User Repository (AUR)**, which provides access to user-contributed packages that are not included in the official repositories. To simplify the process of building and installing packages from the AUR, many users rely on **AUR helpers** like `yay`, `paru`, or `trizen`.
|
||||
|
||||
|
||||
|
||||
### 🔧 **Step 1: Install an AUR Helper**
|
||||
|
||||
#### **Popular AUR Helpers**
|
||||
|
||||
1. **Yay (Yet Another Yaourt)**
|
||||
Lightweight and popular among Arch users.
|
||||
- Install:
|
||||
```bash
|
||||
sudo pacman -S --needed git base-devel
|
||||
git clone https://aur.archlinux.org/yay.git
|
||||
cd yay
|
||||
makepkg -si
|
||||
```
|
||||
|
||||
2. **Paru**
|
||||
A modern AUR helper written in Rust, which offers fast operations and is actively maintained.
|
||||
- Install:
|
||||
```bash
|
||||
sudo pacman -S --needed git base-devel
|
||||
git clone https://aur.archlinux.org/paru.git
|
||||
cd paru
|
||||
makepkg -si
|
||||
```
|
||||
|
||||
3. **Trizen**
|
||||
Another reliable AUR helper that integrates with pacman and supports clean builds.
|
||||
- Install:
|
||||
```bash
|
||||
sudo pacman -S --needed git base-devel
|
||||
git clone https://aur.archlinux.org/trizen.git
|
||||
cd trizen
|
||||
makepkg -si
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🌟 **Step 2: Search and Install AUR Packages**
|
||||
|
||||
Once your AUR helper is installed, you can easily search for and install AUR packages.
|
||||
|
||||
#### **Basic Commands**
|
||||
| **Command** | **Description** |
|
||||
|----------------------------------|------------------------------------------|
|
||||
| `yay -S package-name` | Install a package from AUR. |
|
||||
| `paru -S package-name` | Install a package from AUR. |
|
||||
| `trizen -S package-name` | Install a package from AUR. |
|
||||
| `yay -Ss package-name` | Search for a package in AUR. |
|
||||
| `paru -Ss package-name` | Search for a package in AUR. |
|
||||
| `trizen -Ss package-name` | Search for a package in AUR. |
|
||||
| `yay -Syu` | Update all installed packages (including AUR). |
|
||||
| `paru -Syu` | Update all installed packages (including AUR). |
|
||||
| `trizen -Syu` | Update all installed packages (including AUR). |
|
||||
| `yay -R package-name` | Remove a package. |
|
||||
| `paru -R package-name` | Remove a package. |
|
||||
| `trizen -R package-name` | Remove a package. |
|
||||
|
||||
|
||||
|
||||
### 🌐 **Step 3: Example Installations**
|
||||
|
||||
1. **Install `visual-studio-code-bin` (AUR package)**:
|
||||
```bash
|
||||
yay -S visual-studio-code-bin
|
||||
```
|
||||
|
||||
2. **Search for a package (e.g., Brave Browser)**:
|
||||
```bash
|
||||
paru -Ss brave
|
||||
```
|
||||
|
||||
3. **Update All Packages**:
|
||||
```bash
|
||||
yay -Syu
|
||||
```
|
||||
|
||||
4. **Remove a Package (e.g., Discord)**:
|
||||
```bash
|
||||
paru -R discord
|
||||
```
|
||||
|
||||
|
||||
|
||||
### ⚠️ **Tips and Precautions**
|
||||
|
||||
1. **Enable Parallel Builds**: Speed up builds by editing `/etc/makepkg.conf` and setting:
|
||||
```bash
|
||||
MAKEFLAGS="-j$(nproc)"
|
||||
```
|
||||
This uses all available CPU cores for compiling.
|
||||
|
||||
2. **Check PKGBUILDs**: Always review the **PKGBUILD** file for security before installing a package:
|
||||
```bash
|
||||
yay -G package-name
|
||||
cd package-name
|
||||
cat PKGBUILD
|
||||
```
|
||||
|
||||
3. **Use Trusted Helpers**: Stick to widely-used and actively maintained AUR helpers to minimize risks.
|
||||
|
||||
4. **Update Regularly**: Keep your system updated, as outdated packages can lead to dependency issues:
|
||||
```bash
|
||||
yay -Syu
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### 🚀 **Conclusion**
|
||||
|
||||
Using an AUR helper like `yay`, `paru`, or `trizen` streamlines the process of installing and managing AUR packages, making Snigdha OS even more powerful and user-friendly. Happy exploring! 😄
|
@@ -0,0 +1,89 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
||||
# Chaotic AUR
|
||||
|
||||
### 🔧 **What is Chaotic-AUR?**
|
||||
Chaotic-AUR is an unofficial **AUR (Arch User Repository)** repository that provides pre-built packages for **Arch Linux**, **Snigdha OS**, and **Manjaro** users. It hosts packages that are not included in the official repositories or AUR, allowing for quicker and easier installation of a variety of applications. Chaotic-AUR makes it easier for users to access a wide range of packages without the need to manually compile them.
|
||||
|
||||
### 🌟 **Key Features**
|
||||
1. **Pre-built Packages**: Chaotic-AUR hosts pre-built packages, saving you time on compiling.
|
||||
2. **Extensive Package Selection**: It includes a vast range of packages from AUR, even those with complex build processes.
|
||||
3. **Up-to-date**: The repository is continuously updated, so packages stay current with the latest versions available in the AUR.
|
||||
4. **AUR-based**: It is based entirely on the AUR, so it contains packages contributed by the Arch community.
|
||||
5. **Available for Arch Linux, Snigdha OS, and Manjaro**: Chaotic-AUR is suitable for **Arch Linux**, **Snigdha OS**, and **Manjaro** users, making it a versatile option for multiple Linux distributions.
|
||||
|
||||
|
||||
|
||||
### 🌐 **Official Installation Documentation for Chaotic-AUR**
|
||||
|
||||
Follow the official steps below to install Chaotic-AUR on **Arch Linux**, **Snigdha OS**, or **Manjaro**:
|
||||
|
||||
#### **Step 1: Import the Chaotic-AUR Keyring**
|
||||
The first step is to import the GPG key used to sign packages from Chaotic-AUR. Run the following command:
|
||||
|
||||
```bash
|
||||
pacman-key --recv-key 3056513887B78AEB --keyserver keyserver.ubuntu.com
|
||||
pacman-key --lsign-key 3056513887B78AEB
|
||||
pacman -U 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-keyring.pkg.tar.zst'
|
||||
pacman -U 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-mirrorlist.pkg.tar.zst'
|
||||
```
|
||||
|
||||
#### **Step 2: Add the Chaotic-AUR Repository to Your Pacman Configuration**
|
||||
To enable Chaotic-AUR, you need to add the repository to the **pacman.conf** file.
|
||||
|
||||
1. Open **pacman.conf** using your favorite text editor (e.g., nano or vim):
|
||||
```bash
|
||||
sudo nano /etc/pacman.conf
|
||||
```
|
||||
|
||||
2. Add the following lines at the end of the file:
|
||||
```ini
|
||||
[chaotic-aur]
|
||||
Server = https://repo.archlinuxcn.org/$arch
|
||||
```
|
||||
|
||||
3. Save the file and close the editor.
|
||||
|
||||
#### **Step 3: Update Package Database**
|
||||
After adding the repository, update your package database to fetch the latest list of packages:
|
||||
```bash
|
||||
sudo pacman -Sy
|
||||
```
|
||||
|
||||
#### **Step 4: Install Packages from Chaotic-AUR**
|
||||
Now you can install packages from the Chaotic-AUR repository using **pacman**:
|
||||
```bash
|
||||
sudo pacman -S package-name
|
||||
```
|
||||
For example, to install **Google Chrome**:
|
||||
```bash
|
||||
sudo pacman -S google-chrome
|
||||
```
|
||||
|
||||
|
||||
|
||||
### 🌐 **Advantages of Using Chaotic-AUR**
|
||||
1. **Speed**: Pre-built binaries are much faster to install compared to building from source, especially for large or complex packages.
|
||||
2. **Convenience**: It saves users the trouble of having to manually manage dependencies or deal with build failures.
|
||||
3. **Large Package Selection**: Chaotic-AUR includes many packages that may not be available in the official Arch repositories.
|
||||
4. **No Build Failures**: As the packages are pre-compiled, you don’t need to worry about running into build issues.
|
||||
|
||||
|
||||
|
||||
### ⚠️ **Precautions**
|
||||
1. **Trust**: Since Chaotic-AUR is an unofficial repository, some users may have security concerns about trusting the source. Always review the packages you install and consider the risks.
|
||||
2. **Stability**: Although Chaotic-AUR is frequently updated, it's still unofficial, so there may be occasional issues with certain packages.
|
||||
3. **Package Availability**: While Chaotic-AUR offers many AUR packages, not every package may be available, and some packages might be outdated compared to those in the official AUR.
|
||||
|
||||
|
||||
|
||||
### 🛠️ **Chaotic-AUR vs AUR Helpers**
|
||||
- **AUR Helpers**: Tools like `yay`, `paru`, and `trizen` allow users to build and install AUR packages from source. This provides more control over the installation but can be slower and prone to build errors.
|
||||
- **Chaotic-AUR**: Provides pre-built binaries for faster installation but lacks the customization and flexibility of building from source. It's an excellent option for users looking for speed and ease of use.
|
||||
|
||||
|
||||
|
||||
### 🚀 **Conclusion**
|
||||
Chaotic-AUR is an excellent tool for **Arch Linux**, **Snigdha OS**, and **Manjaro** users who want the convenience of pre-built packages from the AUR without the hassle of compiling them. It provides faster installations and a vast selection of packages while being actively updated and maintained by the community. However, it's important to consider the potential security and stability trade-offs when using an unofficial repository.
|
@@ -0,0 +1,303 @@
|
||||
---
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
# Shortcut for Developers
|
||||
|
||||
### Git Commands & Aliases
|
||||
Here are your Git aliases with explanations and emojis for easy reference:
|
||||
|
||||
|
||||
- **`alias gs="git status"`** 📜:
|
||||
Show the current status of the Git repository (modified files, untracked files, etc.).
|
||||
|
||||
- **`alias ga="git add"`** ➕:
|
||||
Stage changes for commit (adds a file to the staging area).
|
||||
|
||||
- **`alias gaa="git add --all"`** 📥:
|
||||
Stage all modified, deleted, and untracked files for commit.
|
||||
|
||||
- **`alias gc="git commit"`** ✏️:
|
||||
Commit the staged changes to the repository.
|
||||
|
||||
- **`alias gca="git commit --amend"`** 🔄✏️:
|
||||
Amend the last commit (useful for correcting commit messages or adding more changes).
|
||||
|
||||
- **`alias gcm="git commit -m"`** 📝💬:
|
||||
Commit changes with a specific commit message.
|
||||
|
||||
- **`alias gco="git checkout"`** 🔀:
|
||||
Switch branches or restore working directory files.
|
||||
|
||||
- **`alias gbr="git branch"`** 🌿:
|
||||
List, create, or delete Git branches.
|
||||
|
||||
- **`alias gb="git branch"`** 🌱:
|
||||
List all branches in the repository.
|
||||
|
||||
- **`alias gl="git log"`** 📖:
|
||||
View the commit history with details like author and message.
|
||||
|
||||
- **`alias glg="git log --oneline --graph --all"`** 🗂️📊:
|
||||
View a visualized, condensed commit history (one-line format with a graph showing branching and merging).
|
||||
|
||||
- **`alias gst="git stash"`** 🗂️🔒:
|
||||
Temporarily save changes that are not ready for commit.
|
||||
|
||||
- **`alias gpo="git push origin"`** 🚀🌍:
|
||||
Push your local commits to the remote repository on the `origin` remote.
|
||||
|
||||
- **`alias gpl="git pull"`** 🔄🔃:
|
||||
Pull changes from the remote repository (fetch and merge).
|
||||
|
||||
- **`alias gup="git pull --rebase"`** 🔄📅:
|
||||
Pull changes from the remote repository but rebase your local commits on top of the remote branch.
|
||||
|
||||
- **`alias gd="git diff"`** 🔍📝:
|
||||
Show changes between commits, working directory, and staged changes.
|
||||
|
||||
- **`alias gds="git diff --staged"`** 📑:
|
||||
Show the differences between the staged changes and the last commit.
|
||||
|
||||
- **`alias gls="git ls-files"`** 🗃️:
|
||||
List all files currently tracked by Git in the repository.
|
||||
|
||||
- **`alias gcl="git clone"`** 🛠️:
|
||||
Clone a Git repository into a new directory.
|
||||
|
||||
- **`alias gtag="git tag"`** 🏷️:
|
||||
Create, list, or delete tags in the Git repository.
|
||||
|
||||
These Git aliases provide quick access to common Git operations, making version control more efficient and saving you time while working with Git repositories.
|
||||
|
||||
Here are the explanations for your aliases across various tools, with some added emojis to make them more visually engaging:
|
||||
|
||||
### npm Aliases
|
||||
- **`ni="npm install"`** 🛠️:
|
||||
Install dependencies for the project.
|
||||
|
||||
- **`nis="npm install --save"`** 💾:
|
||||
Install and save the package in the `dependencies` section of `package.json`.
|
||||
|
||||
- **`nisdev="npm install --save-dev"`** 🛠️🔧:
|
||||
Install and save the package as a development dependency.
|
||||
|
||||
- **`nup="npm update"`** 🔄:
|
||||
Update all installed npm packages to their latest versions.
|
||||
|
||||
- **`nstart="npm start"`** ▶️:
|
||||
Start the application (runs the start script).
|
||||
|
||||
- **`nrun="npm run"`** ▶️💻:
|
||||
Run any custom npm script defined in `package.json`.
|
||||
|
||||
- **`ntest="npm test"`** 🧪:
|
||||
Run tests defined in the `test` script.
|
||||
|
||||
- **`nls="npm ls"`** 📜:
|
||||
List all installed packages in the current project.
|
||||
|
||||
- **`nci="npm ci"`** ⚡:
|
||||
Perform a clean install (faster and more predictable than `npm install`).
|
||||
|
||||
- **`nfund="npm fund"`** 💰:
|
||||
Show the funding information for your project's dependencies.
|
||||
|
||||
- **`npublish="npm publish"`** 📦:
|
||||
Publish your package to the npm registry.
|
||||
|
||||
- **`nversion="npm version"`** 🔢:
|
||||
View and manage versioning for your project.
|
||||
|
||||
- **`nrm="npm run"`** 🔄:
|
||||
Run a specific npm script.
|
||||
|
||||
- **`nout="npm outdated"`** ⏳:
|
||||
Check for outdated packages in your project.
|
||||
|
||||
### pnpm Aliases
|
||||
- **`pni="pnpm install"`** 🛠️:
|
||||
Install dependencies using pnpm.
|
||||
|
||||
- **`pnis="pnpm install --save"`** 💾:
|
||||
Install and save the package in `dependencies`.
|
||||
|
||||
- **`pnisdev="pnpm install --save-dev"`** 🛠️🔧:
|
||||
Install and save the package as a development dependency.
|
||||
|
||||
- **`pnm="pnpm manager"`** ⚙️:
|
||||
Use pnpm as the package manager.
|
||||
|
||||
- **`pnup="pnpm update"`** 🔄:
|
||||
Update all installed pnpm packages.
|
||||
|
||||
- **`pnstart="pnpm start"`** ▶️:
|
||||
Start the application with pnpm.
|
||||
|
||||
- **`pnrun="pnpm run"`** ▶️💻:
|
||||
Run any script defined in `package.json` using pnpm.
|
||||
|
||||
- **`pntest="pnpm test"`** 🧪:
|
||||
Run tests defined in the `test` script using pnpm.
|
||||
|
||||
- **`pnls="pnpm list"`** 📜:
|
||||
List all installed pnpm packages.
|
||||
|
||||
- **`pnci="pnpm ci"`** ⚡:
|
||||
Perform a clean install with pnpm.
|
||||
|
||||
- **`pnpublish="pnpm publish"`** 📦:
|
||||
Publish a package to the pnpm registry.
|
||||
|
||||
- **`pnversion="pnpm version"`** 🔢:
|
||||
View and manage versioning for your pnpm project.
|
||||
|
||||
- **`pnout="pnpm outdated"`** ⏳:
|
||||
Check for outdated pnpm packages.
|
||||
|
||||
### Python Aliases
|
||||
- **`py="python"`** 🐍:
|
||||
Shortcut for the Python interpreter.
|
||||
|
||||
- **`py3="python3"`** 🐍3:
|
||||
Shortcut for Python 3 interpreter.
|
||||
|
||||
- **`pip="pip3"`** 📦:
|
||||
Use `pip3` to manage Python packages.
|
||||
|
||||
- **`pipup="pip install --upgrade"`** ⬆️📦:
|
||||
Upgrade pip packages.
|
||||
|
||||
- **`pyvenv="python3 -m venv"`** 🐍🧳:
|
||||
Create a Python virtual environment.
|
||||
|
||||
- **`pyactivate="source venv/bin/activate"`** 🔑:
|
||||
Activate a Python virtual environment.
|
||||
|
||||
- **`pydeactivate="deactivate"`** ❌:
|
||||
Deactivate the current Python virtual environment.
|
||||
|
||||
- **`pyrun="python"`** 🐍🏃♂️:
|
||||
Run a Python script.
|
||||
|
||||
- **`pycheck="python -m py_compile"`** 🔍📝:
|
||||
Check Python script syntax without running it.
|
||||
|
||||
- **`pytest="python -m pytest"`** 🧪:
|
||||
Run tests with pytest.
|
||||
|
||||
- **`pydoc="python -m pydoc"`** 📚:
|
||||
Launch Python documentation server.
|
||||
|
||||
- **`pylist="pip list"`** 📜:
|
||||
List installed Python packages.
|
||||
|
||||
- **`pyfreeze="pip freeze"`** ❄️:
|
||||
List installed packages in `requirements.txt` format.
|
||||
|
||||
- **`pyinstall="pip install"`** 📦:
|
||||
Install Python packages.
|
||||
|
||||
- **`pyuninstall="pip uninstall"`** ❌📦:
|
||||
Uninstall Python packages.
|
||||
|
||||
### C++ Aliases
|
||||
- **`cpp-compile="g++ -std=c++17 -Wall -Wextra -o output"`** ⚙️📦:
|
||||
Compile C++ code with standard C++17 features and output as `output`.
|
||||
|
||||
- **`cpp-run="g++ -std=c++17 -Wall -Wextra -o output && ./output"`** ▶️:
|
||||
Compile and run a C++ program.
|
||||
|
||||
- **`cpp-compile-opt="g++ -std=c++17 -O2 -Wall -Wextra -o output"`** ⚙️🔧:
|
||||
Compile C++ code with optimizations (`-O2`).
|
||||
|
||||
- **`cpp-clean="rm -f output"`** 🧹:
|
||||
Remove the compiled output file.
|
||||
|
||||
- **`cpp-build-all="g++ -std=c++17 -Wall -Wextra *.cpp -o output"`** 🔨:
|
||||
Compile all `.cpp` files in the directory.
|
||||
|
||||
- **`cpp-edit="nano"`** ✏️:
|
||||
Open the code in the `nano` text editor.
|
||||
|
||||
- **`cpp-exec="./output"`** ▶️💻:
|
||||
Execute the compiled output.
|
||||
|
||||
### C Aliases
|
||||
- **`c-compile="gcc -std=c11 -Wall -Wextra -o output"`** ⚙️📦:
|
||||
Compile C code with standard C11 features and output as `output`.
|
||||
|
||||
- **`c-run="gcc -std=c11 -Wall -Wextra -o output && ./output"`** ▶️:
|
||||
Compile and run a C program.
|
||||
|
||||
- **`c-compile-opt="gcc -std=c11 -O2 -Wall -Wextra -o output"`** ⚙️🔧:
|
||||
Compile C code with optimizations (`-O2`).
|
||||
|
||||
- **`c-clean="rm -f output"`** 🧹:
|
||||
Remove the compiled output file.
|
||||
|
||||
- **`c-build-all="gcc -std=c11 -Wall -Wextra *.c -o output"`** 🔨:
|
||||
Compile all `.c` files in the directory.
|
||||
|
||||
- **`c-edit="nano"`** ✏️:
|
||||
Open the code in the `nano` text editor.
|
||||
|
||||
- **`c-exec="./output"`** ▶️💻:
|
||||
Execute the compiled output.
|
||||
|
||||
### Rust Aliases
|
||||
- **`rustc="rustc"`** ⚙️:
|
||||
Compile Rust programs using the `rustc` compiler.
|
||||
|
||||
- **`rust-run="cargo run"`** ▶️📦:
|
||||
Run the current Rust project.
|
||||
|
||||
- **`rust-build="cargo build"`** 🏗️:
|
||||
Build the current Rust project.
|
||||
|
||||
- **`rust-build-rel="cargo build --release"`** 🏗️🚀:
|
||||
Build the project in release mode for optimizations.
|
||||
|
||||
- **`rust-test="cargo test"`** 🧪:
|
||||
Run tests for the current project.
|
||||
|
||||
- **`rust-clean="cargo clean"`** 🧹:
|
||||
Clean the build directory.
|
||||
|
||||
- **`rust-fmt="cargo fmt"`** 🔧📐:
|
||||
Format the Rust code.
|
||||
|
||||
- **`rust-clippy="cargo clippy"`** 🔍:
|
||||
Run Clippy to check the code for potential issues.
|
||||
|
||||
- **`rust-doc="cargo doc --open"`** 📚:
|
||||
Generate and open Rust documentation.
|
||||
|
||||
- **`rust-new="cargo new"`** 🛠️📦:
|
||||
Create a new Rust project.
|
||||
|
||||
- **`rust-init="cargo init"`** ⚙️:
|
||||
Initialize a new Rust project in an existing directory.
|
||||
|
||||
- **`rust-add="cargo add"`** ➕:
|
||||
Add a dependency to the Rust project.
|
||||
|
||||
- **`rust-upd="rustup update"`** 🔄:
|
||||
Update the Rust toolchain.
|
||||
|
||||
- **`rust-ver="rustc --version"`** 📅:
|
||||
Display the version of `rustc`.
|
||||
|
||||
- **`rust-watch="cargo watch -x run"`** 👀:
|
||||
Watch for changes in the Rust project and run automatically.
|
||||
|
||||
- **`rust-deps="cargo tree"`** 🗂️:
|
||||
Show the dependency tree of the Rust project.
|
||||
|
||||
- **`rust-check="cargo check"`** ✅:
|
||||
Check the code for errors without building it.
|
||||
|
||||
- **`rust-ls="ls -alh --color=auto"`** 📂:
|
||||
List the project directory contents with detailed info.
|
||||
|
||||
These aliases will help streamline your workflow in a variety of languages and package managers!
|
@@ -0,0 +1,135 @@
|
||||
---
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
# Introduction to Terminal
|
||||
|
||||
## Launch Terminal
|
||||
Here’s a list of common shortcuts to launch the terminal in various desktop environments and window managers on Snigdha OS, along with relevant emojis:
|
||||
|
||||
### 🌐 **Desktop Environments & Window Managers**
|
||||
|
||||
1. **KDE Plasma**
|
||||
- Shortcut: `Ctrl + Alt + T`
|
||||
|
||||
|
||||
2. **GNOME**
|
||||
- Shortcut: `Super (Windows key) + T`
|
||||
|
||||
|
||||
3. **XFCE**
|
||||
- Shortcut: `Ctrl + Alt + T`
|
||||
|
||||
|
||||
4. **LXQt**
|
||||
- Shortcut: `Ctrl + Alt + T`
|
||||
|
||||
|
||||
5. **Cinnamon**
|
||||
- Shortcut: `Ctrl + Alt + T`
|
||||
|
||||
|
||||
6. **MATE**
|
||||
- Shortcut: `Ctrl + Alt + T`
|
||||
|
||||
|
||||
7. **i3wm** (Tiling Window Manager)
|
||||
- Shortcut: `Mod + Enter` (where "Mod" is usually the `Super` key or `Alt`)
|
||||
|
||||
|
||||
8. **Sway** (Wayland-based i3-like WM)
|
||||
- Shortcut: `Mod + Enter`
|
||||
|
||||
|
||||
9. **Openbox**
|
||||
- Shortcut: `Super + Enter` (or configure manually)
|
||||
|
||||
|
||||
10. **AwesomeWM**
|
||||
- Shortcut: `Mod + Return`
|
||||
|
||||
|
||||
11. **Fluxbox**
|
||||
- Shortcut: `Super + Return`
|
||||
|
||||
|
||||
12. **Budgie**
|
||||
- Shortcut: `Super + T`
|
||||
|
||||
|
||||
13. **LXDE**
|
||||
- Shortcut: `Ctrl + Alt + T`
|
||||
|
||||
|
||||
14. **Herbstluftwm**
|
||||
- Shortcut: `Mod + Return`
|
||||
|
||||
## Shortcodes(Regular)
|
||||
|
||||
Here’s the explanation of your aliases with relevant emojis:
|
||||
|
||||
### System and Package Management
|
||||
|
||||
- **`alias ls='ls -l --color=auto'`** 🖥️🌈:
|
||||
List files in long format (`-l`) and colorize the output for better readability (`--color=auto`).
|
||||
|
||||
- **`alias grep='grep --color=auto'`** 🔍🌈:
|
||||
Highlight matching text in color when using `grep` for easier identification of search results.
|
||||
|
||||
- **`alias rs="sudo pacman -Rs"`** 🚫📦:
|
||||
Remove a package and its dependencies (`pacman -Rs`) with `sudo`.
|
||||
|
||||
- **`alias s="sudo pacman -S"`** 📦✨:
|
||||
Install a package with `pacman` using the shortcut `s`, which runs `sudo pacman -S`.
|
||||
|
||||
- **`alias sy="sudo pacman -Syy"`** 🔄📦:
|
||||
Force sync the package databases (`-Syy`) to fetch the latest information from mirrors.
|
||||
|
||||
- **`alias syyu="sudo pacman -Syyu"`** ⬆️📦💻:
|
||||
Perform a system update by forcing a database refresh (`-Syy`) and upgrading all packages (`-u`).
|
||||
|
||||
- **`alias lck="sudo rm /var/lib/pacman/db.lck"`** 🔒🗑️:
|
||||
Remove the lock file (`db.lck`) that may block `pacman` from functioning properly.
|
||||
|
||||
- **`alias vm="sudo systemctl enable --now vmtoolsd.service"`** 🖥️⚙️:
|
||||
Enable and start the VMware Tools service (`vmtoolsd.service`) in a virtual machine.
|
||||
|
||||
- **`alias rip="expac --timefmt='%Y-%m-%d %T' '%l\t%n %v' | sort | tail -200 | nl"`** 🕒📋:
|
||||
List the most recent 200 installed packages, sorted by date, with numbered entries.
|
||||
|
||||
- **`alias ys="yay -S"`** 🚀📦:
|
||||
Install packages from the AUR using `yay` with the `ys` shortcut.
|
||||
|
||||
- **`alias pas="paru -S"`** 🛠️📦:
|
||||
Install packages from the AUR using `paru` with the `pas` shortcut.
|
||||
|
||||
- **`alias wget="wget -c"`** 🌐⬇️:
|
||||
Resume interrupted downloads with the `-c` option for `wget`.
|
||||
|
||||
### Navigation
|
||||
|
||||
- **`alias ..="cd .."`** 🔼📁:
|
||||
Move up one directory level using the shortcut `..` instead of typing `cd ..`.
|
||||
|
||||
- **`alias home="cd ~"`** 🏠💻:
|
||||
Quickly go to your home directory with the `home` alias.
|
||||
|
||||
- **`alias docs="cd ~/Documents"`** 📂📝:
|
||||
Navigate to your `Documents` folder with the `docs` alias.
|
||||
|
||||
- **`alias dl="cd ~/Downloads"`** 📥🗂️:
|
||||
Go to the `Downloads` folder using the `dl` alias.
|
||||
|
||||
- **`alias music="cd ~/Music"`** 🎵🎶:
|
||||
Navigate to your `Music` folder with the `music` alias.
|
||||
|
||||
- **`alias pics="cd ~/Pictures"`** 🖼️📸:
|
||||
Quickly jump to the `Pictures` folder using the `pics` alias.
|
||||
|
||||
- **`alias vids="cd ~/Videos"`** 🎬📹:
|
||||
Go to the `Videos` folder with the `vids` alias.
|
||||
|
||||
- **`alias desk="cd ~/Desktop"`** 🖥️💻:
|
||||
Jump to the `Desktop` folder using the `desk` alias.
|
||||
|
||||
These aliases with emojis make it easy to remember their functions and provide a fun, visual way to enhance your terminal experience!
|
Reference in New Issue
Block a user