FAQ - buggerman/re-arch GitHub Wiki

██████╗ ███████╗      █████╗ ██████╗  ██████╗██╗  ██╗
██╔══██╗██╔════╝     ██╔══██╗██╔══██╗██╔════╝██║  ██║
██████╔╝█████╗  ████╗███████║██████╔╝██║     ███████║
██╔══██╗██╔══╝  ╚═══╝██╔══██║██╔══██╗██║     ██╔══██║
██║  ██║███████╗     ██║  ██║██║  ██║╚██████╗██║  ██║
╚═╝  ╚═╝╚══════╝     ╚═╝  ╚═╝╚═╝  ╚═╝ ╚═════╝╚═╝  ╚═╝

RE-ARCH FAQ

Frequently asked questions and comprehensive answers about RE-ARCH installation and usage.

🚀 Installation Questions

Q: What makes RE-ARCH different from other Arch installers?

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

Q: How long does installation take?

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

Q: Can I install RE-ARCH on a system with existing data?

A: No. RE-ARCH is designed for fresh installations and will erase the entire disk. Always back up important data before installation.

Q: Does RE-ARCH support dual-boot with Windows?

A: Advanced users only. The default configurations assume full disk usage. Dual-boot requires manual partition configuration and is not officially supported.

Q: My disk isn't /dev/sda. What should I do?

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.json

Note: The configuration file uses a complex JSON structure. Take care when editing to maintain proper JSON formatting.

🖥️ Desktop Environment Questions

Q: Which desktop environment should I choose?

A: For most users: KDE Plasma (recommended)

  • New to Linux: KDE Plasma (familiar interface)
  • Minimal resource usage: XFCE
  • Modern design: GNOME
  • Advanced/tiling: Hyprland

Q: Can I switch desktop environments after installation?

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.

Q: Why is there no web browser installed?

A: Security reasons. Web browsers should be installed via Flatpak for sandboxing and security. Install after first boot:

flatpak install flathub org.mozilla.firefox

Q: Which display manager does each DE use?

A:

  • KDE Plasma: SDDM
  • GNOME: GDM
  • XFCE: LightDM
  • Hyprland: LightDM

The script automatically detects and enables the correct display manager.

📦 Package Management Questions

Q: Why can't I install GUI applications with pacman?

A: Security philosophy. GUI applications should be installed via Flatpak for:

  • Sandboxing and security
  • Isolated dependencies
  • Independent updates
  • System stability

Q: How do I install applications after installation?

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-name

Q: Is the AUR helper (paru) installed by default?

A: No. Install manually if needed:

sudo pacman -S base-devel git
git clone https://aur.archlinux.org/paru.git
cd paru && makepkg -si

Q: How do I update the system?

A: 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 upgrade

🔧 System Configuration Questions

Q: What are the default login credentials?

A:

  • Username: user
  • Password: rearch

⚠️ Change these immediately after first login for security!

Q: How do snapshots work?

A: Automatic snapshots are created:

  • Before package updates (via snap-pac)
  • Periodically (via snapper timeline)
  • Accessible through GRUB menu for recovery

Q: Can I boot from a snapshot?

A: Yes. Snapshots appear in the GRUB menu:

  1. Boot to GRUB menu
  2. Select "Arch Linux snapshots"
  3. Choose desired snapshot
  4. Boot from snapshot

Q: How do I make a snapshot the default?

A: After booting from a snapshot:

sudo snapper rollback
sudo grub-mkconfig -o /boot/grub/grub.cfg

🚨 Troubleshooting Questions

Q: The installation failed. What should I do?

A: Check common issues:

  1. Verify internet connection: ping google.com
  2. Check disk space: df -h
  3. Verify disk device: lsblk
  4. Try alternative URLs (see Installation Guide)

Q: The system won't boot after installation.

A: Boot from Arch ISO and check:

  1. Mount your system: mount /dev/sdXY /mnt
  2. Check logs: arch-chroot /mnt && journalctl -b -1
  3. Verify display manager: systemctl status sddm gdm lightdm

Q: Audio isn't working.

A: Check PipeWire status:

systemctl --user status pipewire.service
systemctl --user restart pipewire.service
pactl list short sinks

Q: Network isn't working after installation.

A: Check NetworkManager:

systemctl status NetworkManager
sudo systemctl enable --now NetworkManager
nmcli device wifi connect "NetworkName" password "password"

🎮 Gaming Questions

Q: Is RE-ARCH good for gaming?

A: Yes. RE-ARCH includes:

  • linux-zen kernel (optimized for gaming)
  • multilib repository (32-bit support)
  • Performance optimizations (ananicy-cpp)
  • Steam and Wine compatibility

Q: How do I install Steam?

A: Via Flatpak (recommended):

flatpak install flathub com.valvesoftware.Steam

Or via pacman:

sudo pacman -S steam

Q: Do I need special drivers for gaming?

A: NVIDIA users need proprietary drivers:

sudo pacman -S nvidia nvidia-utils nvidia-settings

AMD users: Mesa drivers are included by default.

🔒 Security Questions

Q: Is RE-ARCH secure?

A: Yes. Security features include:

  • Firewall enabled by default (firewalld)
  • Flatpak sandboxing for GUI apps
  • Regular security updates
  • Minimal attack surface

Q: Should I enable SSH?

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 --reload

Q: How do I change the firewall settings?

A: 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 --reload

💻 Hardware Questions

Q: What hardware is supported?

A: Standard PC hardware:

  • x86_64 processors (Intel/AMD)
  • UEFI or Legacy BIOS
  • SATA or NVMe storage
  • Standard graphics cards
  • Common WiFi adapters

Q: Does RE-ARCH work on virtual machines?

A: Yes. Recommended VM settings:

  • 8GB RAM minimum
  • 50GB disk space
  • Enable hardware acceleration
  • Ensure internet access

Q: What about ARM processors (Apple Silicon, Raspberry Pi)?

A: Not supported. RE-ARCH is designed for x86_64 architecture only.

🔄 Update Questions

Q: How often should I update?

A: Recommended schedule:

  • Daily: Check for Flatpak updates
  • Weekly: Full system update (sudo pacman -Syu)
  • Monthly: AUR package updates and cleanup

Q: Will updates break my system?

A: Unlikely. Snapshots provide automatic recovery:

  • Snapshots created before updates
  • Boot from snapshot if issues occur
  • Automatic rollback available

Q: Can I update RE-ARCH configurations?

A: Limited. The optimization script can be re-run:

curl -fsSL https://re-arch.xyz/re-arch-lite.sh | bash

Note: This may overwrite customizations.

📚 Learning Questions

Q: I'm new to Arch Linux. Is Re-Arch suitable for beginners?

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

Q: Where can I learn more about Arch Linux?

A: Resources:

Q: How do I contribute to Re-Arch?

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.