🐧 Moving from Debian to Void Linux — Notes & Tips

1. Runit and services

• Void Linux uses runit instead of systemd.
• Installing a package that provides a service adds its runit service directory to /etc/sv/servicename/.
• Services aren’t enabled automatically. To enable at boot:

ln -s /etc/sv/servicename /var/service/

Start it immediately:

sv up servicename

To see what's available:

ls /etc/sv/

Useful docs: Void Wiki - Services

2. Installing apps not in the repos

• Void can't use .deb files directly.
• Options:
• Find Flatpak / AppImage / Snap version.
• Build from source.
• Write an xbps-src template (Void's packaging system).
• Manual hack: extract contents:

ar x package.deb
tar -xf data.tar.xz

Then manually copy, but this is fragile.

3. Hardening the system

No official Void hardening manual, but you can adapt: Arch Wiki - Security

• Enable firewall (iptables-nft or ufw).
• Disable SSH password login.
• Keep system updated:

xbps-install -Su

Void Wiki: Security

4. Restricting app permissions

• Continue using Flatpak + Flatseal (supported on Void).
• For non-Flatpak apps:
• Use Firejail:

firejail --net=none myapp

AppArmor / SELinux possible but require extra setup on Void.

5. Encrypting /home

Void installer doesn’t have a GUI option.

• Options:
• Full disk encryption with LUKS (recommended).
• Encrypt only /home:
  • ecryptfs (older).
  • fscrypt (newer, for ext4/f2fs).

Manual setup:

• Partition disk.
• Create LUKS container.
• Mount and install Void onto it.

Guide: Void Linux Full Disk Encryption

6. xbps vs apt quick reference

Extras & recommendations

• Read the Void Handbook
• Check void-packages if you want to package your own software.
• Consider writing a migration checklist:
  • List of services you use.
  • Installed packages.
  • Dotfiles and configs.
• Use flatpak and firejail together for best app sandboxing coverage.

🐧 Enjoy Void Linux — it’s lightweight, rolling, and fun to tinker with!

Et voilà