Casey DeLorme
b1077bb660
add additional items to todo list
|
5 anni fa | |
|---|---|---|
| install | 5 anni fa | |
| setup | 5 anni fa | |
| .gitignore | 5 anni fa | |
| Vagrantfile | 5 anni fa | |
| arch.sh | 5 anni fa | |
| packer.json | 5 anni fa | |
| readme.md | 5 anni fa | |
| todo.md | 5 anni fa |
readme.md
arch-desktop
This repository contains automation that matches debian-stretch-desktop, but has been retooled for arch systems.
As a rolling release, there will be no need to create new repositories, I will simply update this one as needed.
There are two driving factors for me using arch:
- I want it on my laptop and arch has way better modern driver support as it is a rolling release.
- We have just entered the post-freeze on debian buster which is always a painful wait.
During the creation of this project I have been surprised at how stable arch is and while I will still use debian for servers I may consider moving to arch for my desktop and development machine.
usage
If you want to test my build locally, you can do so with virtualbox, packer, and vagrant by running these commands with them installed.
packer build packer.json
vagrant up
The first will build an entire image, which takes roughly 5GB of disk space, and the second will launch an instance from that image that is accessible with the username and password of vagrant.
You can also run these commands from the installation terminal:
pacman -S git
git clone https://git.caseydelorme.com/cdelorme/arch-desktop.git
cd arch-desktop
./setup/install.sh
notes
I ran into quite a few interesting caveats during the creation of this project, and wanted to comment on them.
The pinned comments on the AUR are offensive to beginners and do not answer any questions, RTFM does not explain how to actually fix GPG signature errors. The wiki is useful, but it is hard to pin down what you are looking for. So good job being useless by threatening a ban hammer on comments with questions related to the lack of clear instructions on packages.
The makepkg restriction that prevents execution as root is dumb as hell. I get the security constraints, but the instructions to run as nobody are hella flawed; test suites basically can't run as nobody due to directory permissions (so many with loads of undocumented ENV variables), and creating a faux user from a script just to install some relatively common and popular packages seems like a ridiculous work-around. So great job making automation harder and solving nothing.
Finally, while I am not a fan of how systemd forced proliferation into all linux distributions, nor do I care for binary logs (that seems like a major step backwards), I am incredibly thankful for how simple bootctl made EFI bootloader setup, and also user-space unit files. I only wish there was a more clear way to deal with setting up user-space files from scripts during arch installation.