title, what title?

Soykırım, Tehcir, Büyük Felaket, Katliam... Adı ne olursa olsun, modernitenin kan fışkıran ilk volkanının yerlerinden ,yurtlarından ettiği, eziyet edip öldürdüğü/ölüme terk ettiği tüm halklarının anısına; aynı yüz yılda patlayan ikinci nefret volkanının yeryüzünden sildiği Ukrayna Yahudi'lerinin anısına yazılan Babi Yar senfonisini ithaf etmek isterim: Yaşanan acıları ve utançları "Soykırım, Tehcir, Büyük Felaket, Katliam... ... Bunlardan hangisi?" sorusuna kurban etmekten hiç memnun değilim. Sorunun cevabı belli: bu acılara maruz kalanlar ne diyorsa cevap O'dur...

Crashplan saved my life on so many occasions, that I had to work a bit to find and fix a relatively hard to spot error in my setup. It was brought to my attention by the very useful backup mails that my Crashplan hadn't done its job for 3 days. This made me shiver with fear of losing a lot of data - i am a bit paranoid when it comes to data. So I treaded the standard way, close the app, close the computer, restart again etc. When all of this did not work I tried re-installing the software, which did not fix the issue. After searching through the product knowledge base I learned that there are two components of Crashplan: one UI that you and I interract, and one Windows service that does all the background work. UI will give you an error in the line of "Unable to connect to the backup service." Which means the background service is dead. If one types services.msc in the commend prompt (which you can access by writing cmn on the start menu), the service manager of Windo