Search Criteria
Package Details: pacman-boot-backup-hook 1.7-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/pacman-boot-backup-hook.git (read-only, click to copy) |
---|---|
Package Base: | pacman-boot-backup-hook |
Description: | Pacman hook that creates a copy of the /boot directory prior and post to upgrades of the systemd package or when mkinitcpio is triggered. |
Upstream URL: | None |
Keywords: | backup boot-partition snapper |
Licenses: | MIT |
Submitter: | superhansel |
Maintainer: | superhansel |
Last Packager: | superhansel |
Votes: | 7 |
Popularity: | 0.066249 |
First Submitted: | 2017-12-31 00:33 (UTC) |
Last Updated: | 2023-10-21 21:00 (UTC) |
Latest Comments
« First ‹ Previous 1 2
superhansel commented on 2018-01-05 21:58 (UTC)
Implemented your feedback :)
Muflone commented on 2017-12-31 15:23 (UTC) (edited on 2017-12-31 15:23 (UTC) by Muflone)
@superhansel Hi, there are not any best-practies that I could recommend you. I think the best solution would be to place a .conf file in /etc and let the hook use that path.
superhansel commented on 2017-12-31 13:16 (UTC)
Hey Muflone, thanks for your feedback. I actually used the hook proposed in the wiki[1] as a blueprint. However, I think that it is somewhat opiniated to prefer a non-hidden backup directory over a hidden one or vice-versa. Is there any guideline or best-practice that supports your suggestion?
I believe this package is mostly interesting for people that use snapper to create (bootable) snapshots of their system. I believe storing the backup in a hidden directory is following the snapper philosophy more because snapper itself stores its snapshots in a hidden directoy (
.snapshots
).[1] https://wiki.archlinux.org/index.php/Snapper#Backup_non-btrfs_boot_partition_on_pacman_transactions
Muflone commented on 2017-12-31 11:57 (UTC)
Good idea, I like it but please don't use a hidden directory for backup. /boot-backup would be a better place where to place the backup
« First ‹ Previous 1 2