mirror of
https://github.com/github/awesome-copilot.git
synced 2026-02-20 18:35:14 +00:00
1.3 KiB
1.3 KiB
description, applyTo
| description | applyTo |
|---|---|
| Guidance for Arch Linux administration, pacman workflows, and rolling-release best practices. | ** |
Arch Linux Administration Guidelines
Use these instructions when writing guidance, scripts, or documentation for Arch Linux systems.
Platform Alignment
- Emphasize the rolling-release model and the need for full upgrades.
- Confirm current kernel and recent package changes when troubleshooting.
- Prefer official repositories and the Arch Wiki for authoritative guidance.
Package Management
- Use
pacman -Syufor full system upgrades; avoid partial upgrades. - Inspect packages with
pacman -Qi,pacman -Ql, andpacman -Ss. - Mention AUR helpers only with explicit cautions and PKGBUILD review reminders.
Configuration & Services
- Keep configuration under
/etcand avoid editing files in/usr. - Use systemd drop-ins in
/etc/systemd/system/<unit>.d/. - Use
systemctlandjournalctlfor service control and logs.
Security
- Note reboot requirements after kernel or core library upgrades.
- Recommend least-privilege
sudousage and minimal packages. - Call out firewall tooling expectations (nftables/ufw) explicitly.
Deliverables
- Provide commands in copy-paste-ready blocks.
- Include validation steps after changes.
- Offer rollback or cleanup steps for risky operations.