Casey DeLorme
d2d1a2232e
add shift+insert override as future task
|
2 anni fa | |
|---|---|---|
| install | 2 anni fa | |
| notes | 2 anni fa | |
| setup | 2 anni fa | |
| .gitignore | 2 anni fa | |
| Vagrantfile | 5 anni fa | |
| arch.sh | 2 anni fa | |
| packer.json | 2 anni fa | |
| readme.md | 3 anni fa | |
| todo.md | 2 anni fa |
readme.md
arch-desktop
This repository contains automation to establish a highly functional and lightweight desktop environment.
It was originally written to parity debian-stretch-desktop.
As there are no "releases" to match, this repository will instead be updated over time as is needed.
why
I have been a debian proponent for years, and will continue to be for servers.
However, the 6 months prior to a new debian release are horrible for desktop users.
Additionally, if attempting to upgrade hardware the lack of up to date drivers due to locked kernel are a serious pain.
Finally, having now used Arch as my main system for nearly 6 months I am shocked at how stable it is.
usage
If you want to test my build locally, you can do so by installing virtualbox, packer, and vagrant.
Simply run these commands; the first will build the base image and the second will launch a VM using that base image:
packer build packer.json
vagrant up
This may require a combined total of 5GB of disk space for the installation image and outputs, and uses the user name and password of vagrant.
If you are actually doing an installation, you can run these commands from the arch installation terminal:
pacman -S git
git clone https://git.caseydelorme.com/cdelorme/arch-desktop.git
cd arch-desktop
./setup/install.sh
This may ask for input, and will reboot when finished.
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. However, this also means traditional DOS/BIOS boot loaders such as grub are not supported by these scripts. I only wish there was a more clear way to deal with setting up user-space files from scripts during arch installation.