Of course, the software has to be well written and maintained and so forth. And in the long term there are no guarantees about that, unless the software is extremely important, and there is a lot of money riding on it.
But the lead developer of Borg is a pretty good guy. Of course, there is no guarantee he will be around forever. And he's already put a ton of time into it.
Frankly I don't understand the motivation of free software developers. The real kind, not those who work for corporations (not that there is anything wrong with that).
They must have plenty of spare time, and a very stable job and home life.
Or they really really like free software development.
@FaheemMitha I wish I had that much time, I don't understand either. also I'm a terrible coder except in Java which doesn't belong to the futur of code. And I rather drink my own pee than learn javascript and those new fancy dev langage (though javascript in itself isn't new)
I think it partly comes down to having something interesting to work on and tinker with. If other people benefits from it, that's even more of a motivation to continue with it. i
@PrabhjotSingh The only thing you should have been aware of is that that command modifies files in various system locations. If you previously had installed pip using a package manager, that package may now be broken, along with dependent packages...
@PrabhjotSingh Note that I said "may". I don't know whether you previously had pip installed as a package. I also don't know if pip3 --upgrade pip overwrites the package files on Fedora (it would do on my OpenBSD system), and I don't know how dependent any dependent packages may be.
@PrabhjotSingh If anything (Python-related) starts behaving strangely, then you at least know what the possible cause may be.
The few times I've used pip, I've used it with the --user flag to only install under my home directory (in ~/.local). I tend to use sudoextremely seldom.
(actually never, but that's only because OpenBSD does not have sudo, it has doas instead).
@Kiwy I second @Kusalananda's comment. Luck is an extremely bad backup system.
Even a crappy backup system is better than no backup system at all. For years, I just use to rsync some stuff to another computer. Only recently did I start using Borg.
Well, not that recently, perhaps. Speaking of which, the changes to my backup scripts I made last night aren't working properly. Time to investigate.
Hmm, when I run it from the command line, it works.
@FaheemMitha It will print backup when you run in on the command line. And it should print the same when running from cron (I can't see a reason why it shouldn't, but just to be sure).
Huh, Matthias Klose is uploading Mercurial? Strange.
/usr/local/bin/backup_local_hourly_remote: line 14: syntax error near unexpected token `"$1"'
/usr/local/bin/backup_local_hourly_remote: line 14: `echo "$1"'
I came across a very strange thing today. When I tried to hibernate machine went to shutdown. But clicking on pause icon hibernates system.
@Kusalananda knows everything.
Even if answer doesn't help, then read carefully this gives you some direction.
When you were discussing about freelance coders, I was thinking look who is praising. You deserve praise for guiding us and sometimes we find hard to mention this in words.
@FaheemMitha Now I remember one of the reasons I switched to restic from borgbackup. It was because with restic, you don't need to have the backup program installed on the backup host.