One inventory targets a local machine (`inv-local.yaml`, chosen by default) while the other targets a chrooted installation accessible from another system, usually in the `/mnt/void` directory (`inv-chroot.yaml`, has to be called like `ansible-playbook -i inv-chroot.yaml`).
1.7 KiB
Install void linux from arch linux
Uses btrfs subvolumes, chroot and the void linux root tarball for a full installation. Can be used for a local system to keep it up-to-date and enable a whole bunch of services for a full wayland workstation experience. This is primarily made for my setup to quickly get void linux up and running for playing around with stuff.
Usage
Currently the playbook defaults to keeping a 'local' system configured. That means, you are running ansible on a void installation and it will operate on the local system itself.
To run like that just invoke (sudo) ansible-playbook play.yaml
or (sudo) ansible-playbook play.yaml --tags=backup
to run a specific tag.
To run a full installation from an arch host system to a btrfs subvolume (through a void tarball)
run (sudo) ansible-playbook -i inv-chroot.yaml play.yaml
, or a tagged version.
Roadmap
-
printing
-
audio
-
arduino/iot
-
vpn
-
statusbar integration
-
custom repository
-
automatic kernel rebuild
- should try to update kernel first (if desired_state == latest)
- if changed should hook into booster kernel rebuild
- then delete last kernel?
-
automatic kernel boot selection
- refind should either manually be pointed to correct kernel(s)
- or kernel/initramfs/config should be renamed to simple items
- could maybe symlink to
booster-void.img
andinitramfs-void.img
? - and then do a search and add subitems for each 6.12.xyz kernel found?
- could maybe symlink to
Package wishlist
packages to build xbps-src style: - [x] filtile (src) - [x] dotter (src) - [x] git-bug (src) - [ ] bemoji! - [~] git-delta - [ ] bugwarrior - [ ] viddy - [ ] netbird
- wifi setup
- impala (iwd TUI)