咨询Raspberry Pi无线AP配置自动化及回退的内置可行方案

Great question! Let’s break this down clearly since you’re looking to automate a Raspberry Pi wireless AP setup with reliable rollback support, and wondering if Debian’s package tools can handle it—spoiler: they absolutely can, plus there are other built-in options to consider.

Debian’s dpkg/apt ecosystem is designed to handle exactly this kind of custom configuration and state management. You’ll just need to build a custom .deb package that uses maintainer scripts to wrap your setup and rollback logic.

a. Handling Package Removals & Config Changes #

When building your package, you’ll use four key scripts in the DEBIAN/ directory of your package structure:

• postinst (runs after installation):
  • Remove unwanted packages with commands like apt-get remove --purge -y package1 package2
  • Deploy your custom daemon configs (e.g., hostapd.conf, dnsmasq.conf) by including them in the package’s /etc/ directory—dpkg automatically backs up original files with a .dpkg-old suffix, which is handy for rollback.
• postrm (runs after package removal):
  • Reinstall the packages you removed (save a list of them during installation, e.g., in /var/lib/my-ap-setup/removed-packages.txt so you know exactly what to bring back)
  • Restore original configs: either use the .dpkg-old backups, or explicitly save copies of original files in preinst (run before installation) to a safe location like /var/backups/my-ap-config/

b. Making Rollback Bulletproof #

To avoid headaches during rollback:

• Use dpkg-divert for critical system files: This tool renames the original file so dpkg doesn’t overwrite it, making restoration as simple as renaming it back in your postrm script.
• Track package states: Use apt-mark in your scripts to note whether removed packages were installed manually or automatically, so you can reset that state during rollback.
• Keep your scripts idempotent: Make sure running the setup/rollback scripts multiple times doesn’t break things—for example, check if a package is already removed before trying to purge it.

If building a custom Debian package feels overkill, there are simpler built-in tools to automate setup and rollback:

• etckeeper: This tool tracks changes to /etc/ using Git. Take a snapshot of your system’s original state before running your setup script, then revert to that snapshot with git reset if you need to rollback. Pair it with a bash script that handles package installs/removes, and you’ve got a solid lightweight solution.
• apt-mark + bash scripts: Write a setup script that uses apt-mark showauto to save the original auto/manual state of packages, then removes unwanted ones and installs AP dependencies. Your rollback script can use that saved state to reinstall removed packages and reset their auto/manual status, plus restore config backups you saved upfront.

• Test rigorously: Always test both setup and rollback on a fresh Raspberry Pi image—older OS versions might have slightly different config paths or package dependencies.
• Declare dependencies: If you go the custom deb route, list all required AP packages (like hostapd, dnsmasq) in the package’s control file so apt installs them automatically during setup.
• Document everything: Keep notes on exactly which configs you modify and packages you remove—this will make troubleshooting rollback issues way easier.

As a quick example workflow for a custom deb:

1. Create a package folder structure with DEBIAN/control, DEBIAN/postinst, DEBIAN/postrm, and your custom config files in /etc/
2. Build the package with dpkg-deb --build my-ap-setup/
3. Install with apt install ./my-ap-setup.deb
4. Rollback with apt remove my-ap-setup—the postrm script will handle restoring your system to its original state.

内容的提问来源于stack exchange，提问作者glades