Barry K. Nathan

This is absolutely not the purpose of zap-snapshots.sh. To avoid confusion, I think I'll rename zap-snapshots.sh to delete-old-snapshots.sh. Then I can integrate this as delete-all-snapshots.sh. I'll deal with this later...

On second thought, what I might do instead is leave zap-snapshots.sh with its current name and current default behavior, but add a --all/-a command line option to make it do...

Unfortunately, since my last comment some stuff in my life has started going crazy, so I'll have to release v0.5.0 without this and merge this into v0.5.1 when things settle...

I'm trying to get v0.5.1 out before Big Sur itself, or at least not too long afterward, so I've run out of time to merge this for v0.5.1. I'll merge...

After seeing the latest changes, I'm a bit confused about what this code is trying to do (or, to be more clear, what advantages it has over my existing code)....

I probably won't add the warning in v0.5.2, but I think I'll add it in v0.5.3.

I just got my first Apple Silicon Mac (M1 Mac Mini, for what it's worth) and ran into this problem, as well as a different "solution"/workaround. Basic steps to reproduce:...

This reminds me that I need to update that part of the readme. I'll update it before the next patcher release. These are [Apple's official instructions for downloading previous macOS...

Also, here's the download link for the [Big Sur 11.7.1 InstallAssistant.pkg](https://swcdn.apple.com/content/downloads/62/53/012-90253-A_05NBWHTA4J/wk1on4mznvduz1jbd0javp5p1zid5z5uvn/InstallAssistant.pkg), which is the current release as of this writing. Edited to add: This link downloads from Apple's servers.

Link to [Big Sur 11.7.2 InstallAssistant.pkg](https://swcdn.apple.com/content/downloads/36/35/032-12833-A_767J3FVTQ1/27g8em98uo6ghra4newzc7lkhd4ek0u0xm/InstallAssistant.pkg) on Apple's servers