What do you mean use git; commit and push?elatllat wrote:use dd to make another backup.img of your SD
and next time use git; commit and push often.
Yes I know about backups in more then one way. I've been burned many times by crashes but never expected it to happen because of a simple update. My dl380s are backed up every other day and it's not just an incremental backup either. Guess I'll just start mapping a drive through sshfs and keeping the files locally on my laptop.sdjf wrote:When I was doing a lot of heavy stuff on my PDA, I was doing tar backups twice a day as I never knew when the system would crash.
Are you programming stuff all over the place, so an ls -t wouldn't give you a list of files to tar up more like at least once or twice a week?
My plan is to put anything that is not easy to replace on external media, once my Pi arrives. I just do not trust Arch or the Pi that much, from all I have read. You obviously know a whole lot more than I do, but I have learned the backup lesson pretty intensely messing around with my Embedded system.
Speaking of which - I need to make some backups as well.
I'm guessing he means to backup only your programming using git (or any other version control system), as this saves you from having to backup all 32GB -- and has other advantages as well!What do you mean use git; commit and push?
How's that going to keep the firmware update from crashing the system?
Code: Select all
pacman -Sy linux-raspberrypi-next linux-headers-raspberrypi-next raspberrypi-firmware-next
Code: Select all
pacman -Sy linux-raspberrypi linux-headers-raspberrypi raspberrypi-firmware