-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
โโโโโโโ โโโโโโโโ โโโโโโ โโโโโโโ โโโโโโโโโโ โโโ
โโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโโโโโโโโ โโโ
โโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโโโโโ โโโโโโโโ
โโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโโโโโ โโโโโโโโ
โโโ โโโโโโโโโโโ โโโ โโโโโโ โโโโโโโโโโโโโโ โโโ
โโโ โโโโโโโโโโโ โโโ โโโโโโ โโโ โโโโโโโโโโ โโโ
Frequently asked questions and comprehensive answers about RE-ARCH installation and usage.
A: RE-ARCH focuses on three key areas:
- Desktop-optimized features: Automatic snapshots, performance optimization, security hardening
- Multiple desktop environments: KDE, GNOME, XFCE, and Hyprland with proper configuration
- Two-phase architecture: Uses proven archinstall for packages, custom script for configuration
A: Total installation time is 25-35 minutes:
- Step 1 (archinstall): 22-32 minutes
- Step 2 (re-arch-lite.sh): 2-3 minutes
- First boot initialization: 2-3 minutes
A: No. RE-ARCH is designed for fresh installations and will erase the entire disk. Always back up important data before installation.
A: Advanced users only. The default configurations assume full disk usage. Dual-boot requires manual partition configuration and is not officially supported.
A: Download the config file and edit it:
curl -O https://re-arch.xyz/config-kde.json
# Open the file in a text editor and find the disk_config section
# Look for "device": "/dev/sda" and change it to your disk (e.g., "/dev/nvme0n1")
# The JSON structure is nested, so be careful with formatting
archinstall --config config-kde.json --creds-url https://re-arch.xyz/creds.jsonNote: The configuration file uses a complex JSON structure. Take care when editing to maintain proper JSON formatting.
A: For most users: KDE Plasma (recommended)
- New to Linux: KDE Plasma (familiar interface)
- Minimal resource usage: XFCE
- Modern design: GNOME
- Advanced/tiling: Hyprland
A: Not recommended. Each configuration is optimized for its specific DE. While switching is technically possible, we do not provide support for it and users would need to research the process themselves.
A: Security reasons. Web browsers should be installed via Flatpak for sandboxing and security. Install after first boot:
flatpak install flathub org.mozilla.firefoxA:
- KDE Plasma: SDDM
- GNOME: GDM
- XFCE: LightDM
- Hyprland: LightDM
The script automatically detects and enables the correct display manager.
A: Security philosophy. GUI applications should be installed via Flatpak for:
- Sandboxing and security
- Isolated dependencies
- Independent updates
- System stability
A: Use the appropriate package manager:
# GUI applications (recommended)
flatpak install flathub app-name
# System tools and CLI utilities
sudo pacman -S package-name
# AUR packages (after installing paru)
paru -S package-name
# Development tools
brew install package-nameA: No. Install manually if needed:
sudo pacman -S base-devel git
git clone https://aur.archlinux.org/paru.git
cd paru && makepkg -siA: Update each package manager separately:
# System packages
sudo pacman -Syu
# Flatpak applications
flatpak update
# AUR packages (if paru is installed)
paru -Syu
# Development tools
brew update && brew upgradeA:
-
Username:
user -
Password:
rearch
A: Automatic snapshots are created:
- Before package updates (via snap-pac)
- Periodically (via snapper timeline)
- Accessible through GRUB menu for recovery
A: Yes. Snapshots appear in the GRUB menu:
- Boot to GRUB menu
- Select "Arch Linux snapshots"
- Choose desired snapshot
- Boot from snapshot
A: After booting from a snapshot:
sudo snapper rollback
sudo grub-mkconfig -o /boot/grub/grub.cfgA: Check common issues:
- Verify internet connection:
ping google.com - Check disk space:
df -h - Verify disk device:
lsblk - Try alternative URLs (see Installation Guide)
A: Boot from Arch ISO and check:
- Mount your system:
mount /dev/sdXY /mnt - Check logs:
arch-chroot /mnt && journalctl -b -1 - Verify display manager:
systemctl status sddm gdm lightdm
A: Check PipeWire status:
systemctl --user status pipewire.service
systemctl --user restart pipewire.service
pactl list short sinksA: Check NetworkManager:
systemctl status NetworkManager
sudo systemctl enable --now NetworkManager
nmcli device wifi connect "NetworkName" password "password"A: Yes. RE-ARCH includes:
- linux-zen kernel (optimized for gaming)
- multilib repository (32-bit support)
- Performance optimizations (ananicy-cpp)
- Steam and Wine compatibility
A: Via Flatpak (recommended):
flatpak install flathub com.valvesoftware.SteamOr via pacman:
sudo pacman -S steamA: NVIDIA users need proprietary drivers:
sudo pacman -S nvidia nvidia-utils nvidia-settingsAMD users: Mesa drivers are included by default.
A: Yes. Security features include:
- Firewall enabled by default (firewalld)
- Flatpak sandboxing for GUI apps
- Regular security updates
- Minimal attack surface
A: Only if needed. SSH is not enabled by default. Enable if required:
sudo systemctl enable --now sshd
sudo firewall-cmd --permanent --add-service=ssh
sudo firewall-cmd --reloadA: Use firewall-cmd:
# Check status
sudo firewall-cmd --state
# Allow service
sudo firewall-cmd --permanent --add-service=service-name
sudo firewall-cmd --reload
# Allow port
sudo firewall-cmd --permanent --add-port=port/tcp
sudo firewall-cmd --reloadA: Standard PC hardware:
- x86_64 processors (Intel/AMD)
- UEFI or Legacy BIOS
- SATA or NVMe storage
- Standard graphics cards
- Common WiFi adapters
A: Yes. Recommended VM settings:
- 8GB RAM minimum
- 50GB disk space
- Enable hardware acceleration
- Ensure internet access
A: Not supported. RE-ARCH is designed for x86_64 architecture only.
A: Recommended schedule:
- Daily: Check for Flatpak updates
-
Weekly: Full system update (
sudo pacman -Syu) - Monthly: AUR package updates and cleanup
A: Unlikely. Snapshots provide automatic recovery:
- Snapshots created before updates
- Boot from snapshot if issues occur
- Automatic rollback available
A: Limited. The optimization script can be re-run:
curl -fsSL https://re-arch.xyz/re-arch-lite.sh | bashNote: This may overwrite customizations.
A: Yes, with caveats. Re-Arch simplifies installation but:
- You should understand basic Linux concepts
- Learn package management principles
- Understand the terminal basics
- Be comfortable with troubleshooting
A: Resources:
- Arch Wiki: https://wiki.archlinux.org/ (comprehensive)
- Forums: r/archlinux, Arch Linux forums
- Documentation: Package Management, Technical Details
A: Ways to help:
- Report issues: GitHub Issues
- Suggest improvements: GitHub Discussions
- Submit documentation: Wiki improvements
- Test configurations: VM testing
For more detailed information, see the Installation Guide, Troubleshooting, and other wiki pages.