I tried to run unattended-upgrades with “–dry-run” and “-d” but that didn’t help much. So, the issue here is that Wheezy is out. Wheezy being out, it will look for packages for Wheezy, instead of Squeeze. So this section:

I tried to copy all files from a VM running on VMWare Workstation 10 for Linux, to a Windows machine with the same software installed. When trying to power on the machine, I got an error that said “Failed to Lock the File” and something about not finding the vmdk file or one of the snapshots. I tried re-copying those files about 3 times with no success. After a short google search, you’ll have to remove the folders that have .lck at the end. After removing those, I powered on the machine, and up and running it is.

So, I edited crontab because I wanted to reschedule cron.daily to a convenient time. After restarting cron, I noticed there’s an error in logs. Not a worry, the service was running fine, but I didn’t want to see that error. Problem is that is world-wide writable:

ls -la crontab
-rw-rw-rw- 1 root root 724 Sep 17 09:20 crontab

Don’t know how this changed, but it’s now 666, Devil’s number. So after:

chmod 644 /etc/crontab

..everything is back to normal again.

Still trying to figure out why logrotate doesn’t rotate some logs while running from cron.daily, but works just fine while running from command-line.