Nothing specific...
I just thought i should put down two things that i might possibly forget...
The first thing is about being notified when a certain process running in the console window gets completed...like say we are compiling some big program like openoffice which takes hell lot of time. and we would obviously not like to keep looking at the terminal window once every few seconds/minutes to see if its over. Its easy to set it up so that a sound is played once the thing is done..By adding a && player-name filename.wav...for example, to install some software in one go when you are sure that everything will go according to plan (meaning all dependencies have been satisfied), we can use this command after cd-ing to the program directory..
(I use aplay as i have alsa player installed on my system and it can play independently of the main music player like xmms/amarok.) Guess that was easy..It took me sometime to realise that i could use the chaining together of commands in such a way. hope it helps someone :)
Now, onto the second thing i wanted to mention...The methodology of working of gtalk..Its a pretty interesting piece of software when you think about it. When most other voice chat applications dont work well even on fast connections, google talk has been able to get landline level voice clarity between the two parties..Its pretty clear that the technology, rather methodology, used by google talk is very different from other talk clients like skype or yahoo messenger. One is led to guess that it sets up a direct connection between the 2 clients instead of routing the data through the server..and my hunch is that this is indeed what happens though I havent read any article that states this as such. My belief is strengthened by what happened the other day..This guy had called me up and we were in the middle of a voice conversation. and as usual, mr.your-freedom had to disconnect (for those not in the know, we are behind a restrictive proxy server and so, the need to use a tunneling client like your-freedom to be able to connect to the yahoo and google servers) as it does once in 2 hours as mine is a free account. But though it reconnects almost instantaneously, psi does disconnect and completely reconnects only after 30 seconds or so..but in the meanwhile, we kept talking. I noticed that psi had disconnected and was tring to reconnect only a little after it had actually gotten disconnected. but surprisingly, nothing happened to our voice chat..that i feel is proof enough of the fact that data never goes through the google server..something for us to cheer about..google cant tape our conversations even if it wanted to. As they already know lots about you and me from our usage of their services like search, gmail and (yup)blogger and loads of other things like orkut... if this isnt the case and data is indeed routed through the server, it would be interesting to see how the thing works...maybe thats why google is refusing the part with the source code.
in fact, i have never tried talking with anyone who is physically distant from me..only within the college lan have i (and most of us) used it..would be interesting to see how the voice clarity is when i talk to someone from another country..
The first thing is about being notified when a certain process running in the console window gets completed...like say we are compiling some big program like openoffice which takes hell lot of time. and we would obviously not like to keep looking at the terminal window once every few seconds/minutes to see if its over. Its easy to set it up so that a sound is played once the thing is done..By adding a && player-name filename.wav...for example, to install some software in one go when you are sure that everything will go according to plan (meaning all dependencies have been satisfied), we can use this command after cd-ing to the program directory..
./configure && make && make install && aplay /usr/share/sounds/alsa/Noise.wav
(I use aplay as i have alsa player installed on my system and it can play independently of the main music player like xmms/amarok.) Guess that was easy..It took me sometime to realise that i could use the chaining together of commands in such a way. hope it helps someone :)
Now, onto the second thing i wanted to mention...The methodology of working of gtalk..Its a pretty interesting piece of software when you think about it. When most other voice chat applications dont work well even on fast connections, google talk has been able to get landline level voice clarity between the two parties..Its pretty clear that the technology, rather methodology, used by google talk is very different from other talk clients like skype or yahoo messenger. One is led to guess that it sets up a direct connection between the 2 clients instead of routing the data through the server..and my hunch is that this is indeed what happens though I havent read any article that states this as such. My belief is strengthened by what happened the other day..This guy had called me up and we were in the middle of a voice conversation. and as usual, mr.your-freedom had to disconnect (for those not in the know, we are behind a restrictive proxy server and so, the need to use a tunneling client like your-freedom to be able to connect to the yahoo and google servers) as it does once in 2 hours as mine is a free account. But though it reconnects almost instantaneously, psi does disconnect and completely reconnects only after 30 seconds or so..but in the meanwhile, we kept talking. I noticed that psi had disconnected and was tring to reconnect only a little after it had actually gotten disconnected. but surprisingly, nothing happened to our voice chat..that i feel is proof enough of the fact that data never goes through the google server..something for us to cheer about..google cant tape our conversations even if it wanted to. As they already know lots about you and me from our usage of their services like search, gmail and (yup)blogger and loads of other things like orkut... if this isnt the case and data is indeed routed through the server, it would be interesting to see how the thing works...maybe thats why google is refusing the part with the source code.
in fact, i have never tried talking with anyone who is physically distant from me..only within the college lan have i (and most of us) used it..would be interesting to see how the voice clarity is when i talk to someone from another country..