I forgot my Yahoo!-ID for my flickR account. I know it’s nothing to be proud of…
But what really annoys me is what Yahoo calls their customer support. I sent in their contact form with a description of my problem which I though to be easy to solve. One day later (!) they replied by a standard email describing how to get your lost password (!) and what mistakes one can make when typing one’s ID.
That was on Wednesday. Since then I got the same email four times signed by four different employees. Each time I replied with a description of my problem and ~24 hours later the same dumb email reached me.
In the meantime I already found out my ID using the english help pages (the german copy doesn’t seem to be complete), but I think I will continue playing mail ping pong with Yahoo for some time.
Month: December 2008
Yahoo! or better Oh-no!
shared git repo + ssh = umask problems
When you want to share a little git repository on your own server the first thing that comes to your mind is SSH. It’s installed virtually everywhere, secure and easy to configure.
In the beginning there are no problems, because everyone can clone your repo and if they don’t change files concurrently even pushing works. About one day latter you get umask problems and start to search the web for solutions. To make it short, here it is:
git repo-config core.sharedRepository true
This option makes git care about the permission stuff.
I wasted about 10 hours of my lifetime for this one and found an odd thing about ~/.ssh/rc:
umask 002
date > ~/sshrc-executed
I added the second line, because I wasn’t sure if it was executed. It was (look at the file permissions):
... -rw-rw-r-- 1 moser git 29 Dec 19 18:41 sshrc-executed
But my umask didn’t last:
moser@HellAgent:~$ ssh xxx.net -n 'umask' Password: 0022
Don’t know why, if anyone knows tell me please.



