aboutsummaryrefslogtreecommitdiffstats
path: root/arch-system
Commit message (Collapse)AuthorAgeFilesLines
* arch-system: remove yubikey udev rulesTharre2024-03-033-19/+2
| | | | | | | This seems to now be done by gpg since version 2.2.6[0], so remove this hack. [0] https://dev.gnupg.org/T3825
* arch-system: fix broken checksumsTharre2023-07-012-3/+3
|
* arch-system: include custom repo in pacman.confTharre2023-04-251-0/+4
|
* arch-system: inline short config filesTharre2023-04-254-15/+11
|
* arch-system: add pci_pm.rulesTharre2023-04-253-3/+24
|
* arch-system: backup system updatesTharre2023-04-255-33/+30
|
* Add .SRCINFO to all packages that don't have itTharre2021-12-181-0/+70
|
* arch-system: update pacman.conf for 6.0Tharre2021-12-182-5/+5
|
* arch-system: add intel-undervoltTharre2021-12-182-2/+56
|
* arch-system: fix a couple small thingsTharre2021-12-183-7/+7
|
* arch-system: borgbackup: ignore archive already exists errorTharre2019-06-302-2/+2
|
* arch-system: place mirrorupgrade hook in /usrTharre2019-06-301-1/+1
| | | | .. same directory as the other hook.
* arch-system: enable btrfs-scrub@-.timerTharre2019-06-301-0/+2
| | | | .. but only on systems that have a btrfs filesystem mounted on `/`.
* arch-system: fix .install and run itTharre2019-06-302-9/+12
| | | | | | | | | Before, base-system.install wasn't actually run, since it wasn't specified in `install=` in the PKGBUILD anywhere. Also run it both in the post-upgrade and post-install steps. `--global` was removed since it caused errors, it's unclear what exactly it does in the first place, but other official PKGBUILDs did it this way..
* arch-system: borgbackup: use proper ssh timeoutTharre2019-04-212-2/+2
| | | | | | ConnectTimeout merely specifies the TCP timeout, what we really want is ServerAliceInterval, which makes the client send a null packet every X seconds.
* arch-system: $pkgver: avoid dependency on `date`Tharre2019-02-091-1/+1
| | | | | | | | This avoids errors when date is unavailable, like the one below: Error: error: invalid package file Error: PKGBUILD: line 5: date: command not found Error: /startdir/PKGBUILD is not a valid PKGBUILD
* arch-system: borgbackup: use snapshot timestampsTharre2019-02-093-2/+4
| | | | | | | | | Previously, a archive would get the timestamp of the time it was uploaded, instead of the time when the snapshot was created. This is problematic, since archives are pruned by this timestamp, meaning if multiple archives are uploaded together most of them would be pruned immediately after.
* arch-system: use `date` as pkgverTharre2018-09-291-1/+1
| | | | | | | Since arch-system has no upstream versions, and I'm too lazy to change pkgver manually, just expand the current date. This is slightly odd, maybe even a bad idea, but worth a try.
* arch-system: add udev rule for scdaemon lockupTharre2018-09-292-1/+16
|
* arch-system: /etc/sysctl.d -> /usr/lib/sysctl.dTharre2018-09-291-1/+1
| | | | | This makes systemd-sysctl.hook detect the change and apply the sysctl settings accordingly.
* arch-system: borgbackup: change repo to rsync.netTharre2018-08-072-3/+3
|
* arch-system: borgbackup: better connectivity checkTharre2018-08-072-6/+7
| | | | | | | | | | Instead of trying to execute borg, which would give us a false positive if borg itself isn't working on the remote, just connect to the server without executing a command. We check for 255 because `man 1 ssh` states the following: ssh exits with the exit status of the remote command or with 255 if an error occured.
* arch-system: fix i915 module paramsTharre2018-07-312-2/+2
| | | | | | Linux 4.16 reworked the guc/huc parameters for i915 in [0]. [0] https://github.com/torvalds/linux/commit/121981fafe699d9f398a3c717912ef4eae6719b1
* arch-system: borgbackup: treat rc 1 as a warningTharre2018-07-312-7/+15
|
* arch-system: borgbackup: --keep-hourly 24 -> 72Tharre2018-07-162-2/+2
| | | | | | | | Since borg-prune only keeps the last snapshot of each day with --keep-daily, it's possible that a file that was accidentally deleted is only kept for 24h (if the machine is running) before it's purged from backups. Increase to 72h to give the user a better chance of noticing this in time.
* arch-system: borgbackup: notify about upload skipTharre2018-07-162-1/+4
|
* arch-system: borgbackup: use correct key with sshTharre2018-06-152-3/+4
|
* arch-system: borgbackup: check connection with sshTharre2018-06-142-13/+9
| | | | | | Networkmanager isn't really all that reliable, and we actually don't want to depend on it anyway. So trying to connect via ssh is the better thing to do.
* arch-system: borgbackup: only notify when scriptedTharre2018-05-302-2/+5
|
* arch-system: borgbackup: add -p when interactiveTharre2018-05-292-2/+6
|
* arch-system: run borgbackup with lower CPU/IO prioTharre2018-05-062-1/+4
|
* arch-system: borgbackup: break locks before backupTharre2018-05-052-2/+4
|
* arch-system: borgbackup: check network statusTharre2018-05-052-5/+16
|
* arch-system: add hook for modprobe.d rebuildingTharre2018-05-052-0/+14
|
* arch-system: update i915 module optionsTharre2018-05-052-2/+2
| | | | | | enable_fbc=1: already enabled by default enable_rc6: already enabled by default modeset: keep it at -1, kernel will enable it by default
* arch-system: add backup-system packageTharre2018-03-276-1/+144
| | | | | | | | | This implements fully automated, hourly backups of my /home via borgbackup, btrfs and systemd timers. Note that `setup_borgbackup`, a related function that is part of my dotfiles, is needed to setup backups for the first time, as well as a call to `borg init` with the proper environment variables.
* arch-system: fix sudoers.d ordering of wheelTharre2018-02-261-1/+1
|
* arch-system: add sysctl.conf (REISUB)Tharre2018-02-062-1/+4
|
* arch-system: initial commitTharre2018-01-2210-0/+222