summaryrefslogtreecommitdiff
path: root/etc
AgeCommit message (Collapse)Author
2024-11-02pacdiffXiao Pan
2024-09-14forget to change opt-level to 3Xiao Pan
2024-09-14pacdiffXiao Pan
2024-09-14merge pacdiffXiao Pan
2024-09-14migrate rustflags to /etc/makepkg.conf.d/rust.conf, merge zstd pacdiffXiao Pan
https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/f02d4d01cc9bcaf566e72dbb769250f8c2752e9e https://gitlab.archlinux.org/pacman/pacman/-/commit/71764b6d4cdee1f74cfc603050ced59009950169 https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/319671cc720a31cfaa81e25354d58699a1bedf6c
2024-09-14migrate configs from /etc/makepkg.confXiao Pan
Commit https://gitlab.archlinux.org/pacman/pacman/-/commit/71764b6d4cdee1f74cfc603050ced59009950169 and https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/099295fdcb33c875d0659510dc8e82969463a7c4 migrate rustflags to /etc/makepkg.conf.d/rust.conf. Note I also change opt-level to 3 because https://doc.rust-lang.org/cargo/reference/profiles.html shows opt-level 3 is all optimization which I want.
2024-09-14metaXiao Pan
2024-09-14default rust.confXiao Pan
2024-09-02pacdiffXiao Pan
2024-08-02locale.gen pacnewXiao Pan
2024-07-22/etc/sudoers pacnewXiao Pan
2024-07-06ia new ipv6 systemd networkd configXiao Pan
2024-04-22metaXiao Pan
2024-04-22Revert "according to manpage localtime.5: if no /etc/localtime, default UTC; ↵Xiao Pan
thus no need" This reverts commit 9afc357eb6480d57b71762567690ebe46d01a3ec. Because crunchbits Arch Linux cloud init auto install deafult symlink to Europe/London timezone which is different from UTC. I want UTC. So I choose to always symlink timezome to prevent similar things happen again.
2024-04-20pacdiffXiao Pan
2024-04-18sshd accept COLORTERM env to fix ls no colorXiao Pan
If client use alacritty, after ssh into this remote server, ls doesn't show color. Can be workarounded by server sshd accept COLORTERM and client sshd send env. More see my comments in alacritty.toml config.
2024-04-18ia ip changeXiao Pan
2024-04-18ia data loss incident, new vps2arch install from debianXiao Pan
2024-03-16pacdiffXiao Pan
2024-03-11makepkg no build debug packagesXiao Pan
Reasons: 1. I don't want to build debug packages 2. It breaks my mpra scirpt Upstream code change: - https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a - https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/merge_requests/1
2024-03-11Rename to wg0 so no need change names for new computer config.Xiao Pan
2024-03-06metaXiao Pan
2024-03-06ia add fstabXiao Pan
2024-03-05fix: name ia not kaXiao Pan
2024-03-05metaXiao Pan
2024-03-05fix: name ia not kaXiao Pan
2024-03-05init ia use ka configXiao Pan
/etc/.cfgl/config chagne to ia branch /etc/hostname change to xyzia hostname /etc/myconf/cfgl_meta change changed file meta /etc/systemd/network/default.network use ia network config instead /etc/systemd/system/paccache.service.d/10-remove-all.conf use pp config to save space on SSD root partition /home/xyz/.bashrc use another color for bash PS1 /home/xyz/.config/myconf/pacman_Qqne less package to install, to save space
2024-02-25updateXiao Pan
2024-02-10pacnewXiao Pan
2024-02-10pacnewXiao Pan
2024-02-05pacdiffXiao Pan
2024-01-22fix: htop new version seems break old way of make htoprc unwritable to keep ↵Xiao Pan
config unchanged In the past, `chmod a-w ~/.config/htop/htoprc` is sufficient to let htop not able to write to htoprc. So configs keeps the same if I press anything in htop. But it seems htop new version 3.3.0 makes it not working. I'm not sure why. I suspect "Write configuration to temporary file first" in changelog is the reason <https://github.com/htop-dev/htop/blob/main/ChangeLog#L19>. Luckily, `chmod a-w ~/.config/htop` still works by making htop config dir not writable.
2024-01-20updateXiao Pan
2024-01-13updateXiao Pan
2024-01-09updateXiao Pan
2023-12-28metaXiao Pan
2023-12-19updateXiao Pan
2023-12-03newer kernel no need for `chain prerouting { type nat hook prerouting ↵Xiao Pan
priority -100; policy accept; }`, more see https://www.procustodibus.com/blog/2021/11/wireguard-nftables/
2023-12-03maybe prevent ipv6 leakXiao Pan
2023-12-03updateXiao Pan
2023-12-03updateXiao Pan
2023-12-02updateXiao Pan
2023-12-01sysctl need net.ipv4.ip_forward=1 for wireguard masquerade? to workXiao Pan
2023-11-30updateXiao Pan
2023-11-27updateXiao Pan
2023-11-27updateXiao Pan
2023-11-25move to gitlabXiao Pan
2023-11-21updateXiao Pan
2023-11-17updateXiao Pan
2023-11-17updateXiao Pan