No, it is impossible to solve this on filesystem level. In theory, it would be possible to adopt some video codec for compression of such photo series, but it would be a lot of work to integrate it into immich.
No, it is impossible to solve this on filesystem level. In theory, it would be possible to adopt some video codec for compression of such photo series, but it would be a lot of work to integrate it into immich.
What error you get exactly?
It is easy to get hacked if you make stupid mistakes. Just don’t make them.
What kind of changes? Package installation, removal and configuration? Use apt-mark showmanual
to save list of manually installed packages, dpkg --get-selections | grep 'deinstall$'
to save list of removed packages, debconf --get-selections
to save debconf package settings, backup files that you edited in /etc
. This should be enough for restoration, wouldn’t take a long time for backup and avoid risk of filesystem inconsistency.
The standard answer: don’t backup the system, automate its deployment instead. Backup only data.
Package managers.
This script won’t work in any distro, you have to use a lot of distro specific commands in it. But if you write a script for a specific distro anyway, why not use a tool that distro provides? You’ll be sure that it does everything correct way and you even won’t need to run anything after installation completed. You can also save time and disk space by excluding packages you don’t need but that would be installed by default. You can also automate disk partitioning and customize other installer settings saving even more time.
Speaking about configuration management tools, they can look a bit overkill, but they have at least one advantage of shell script - idempotency. They won’t try to install already installed software, change configs that don’t need to be changed etc.
Kickstart and preseed do not require installing anything. These are features of distro installers. Such configuration management tools as ansible also do nat require installing agent on a target machine (only python is needed, but it is usually installed by default).
There are automation tools that are much better suited for that then pure shell. Kickstart for anaconda based installers, preseed for debian installer etc. Or configuration management tools.
deleted by creator
Do you have experience of restoring such a backup?
Right. You can’t get a correct image of rw mounted filesystem.
On my system that file is /etc/apt/apt.conf.d/20auto-upgrades
. You can read description of its parameters in comments in the /usr/lib/apt/apt.systemd.daily
script. It does not require unattended-upgrades
to work.
BTW I have unattended-upgrades
enabled for many years on all my systems, both desktops and servers, and it never caused any troubles when only stable repos are configured.
Why did you create it manually? You should just edit the existing file. And this can be done via sudo dpkg-reconfigure unattended-upgrades
IIRC.
There are also forkgram, nekogram x, whatevergram… I use negkogram x, in particular, and I don’t want to switch to another fork to get unified push but losing other features. I guess forkgram users also stick to its features. Etc.
Too many forks, each with its own enhancements… If the purpose of this one is just a single feature, why not contribute it to another popular fork?
BTW there is a “show available updates” setting that I have enabled. Unsure what exactly it does, probably it’s a solution.
Disable systemd-resolved.service? Uninstall systemd-resolved?