To give a background, Icebreaker is a Facebook Application. IceBreaker is the cute way to spread love and friendship by motivating communication between your friends!!
You ca use the *IceBreaker App* to request your Friend 1 and Friend2 to 'Break the Ice' and Talk with each other. Both of your friends will be informed about your kind gesture on their Facebook Wall. Literally, the phrase 'Break the Ice' means to break down social or emotional stiffness and start talking.
You can visit Icebreaker App on Facebook.Icebreaker App on Facebook. This link may require you to be logged into your Facebbok account. This Application is envisioned, designed, and authored by Mohd Anwar Jamal Faiz. No need to mention, its Me. Cheers ;)
Icebreaker Application is hosted on meonshow servers, as this is a product from the owners of Meonshow. To visit directly the Icebreaker page on Meonshow servers Click hereThis will ask to login through your facebook credentials, if you are not logged in yet.
Now coming back to the question Do we actually need an Icebreaker Tool... I guess this is as trivial question as to ask do we really need to be good. Or keeping it simple, do we really need to advise our friends to talk. I guess, it is an absolute yes. We need to tell our friends that they have not been talking to each other for long. The causes may vary from job, work pressures, family issues, or it can even be as small as forgetting. Whatever be the cause, your request of talking among themselves will be a boost, a reminder to them. This will mature your relations with your friends and also they would start sharing thoughts with each other. Afterall, this is what is life. And this is what Facebook stands for.
You can view this discussion at the official Icebreaker Application discussions page too. Click Here for Icebreaker facebook Discussions Page
Thursday, July 7, 2011
Wednesday, July 6, 2011
Terminal (Shell) on Mac OSX or Unix continues to show a folder even if it is deleted or renamed
I have logged this defect with Apple. But since then I have only been told it is legacy Unix behavior. And Unix is supposed to behave that way. In any case, I find it valuable to share this now.
-------------------------------------------------------------
This is already present on Apple Website since 19th March 2010 and has one response in addition to the emails. Read Further Apple Mac OSX Bug By Anwar Faiz.
-------------------------------------------------------------
Make a folder, let us say "xyz" on desktop and cd to this location on a terminal using 'cd' command.
Now rename that folder to "abc".
Now type 'ls' command on Terminal to see the content of folder "xyz", it still shows.
In addition if you use 'pwd' command, it still shows that you are in directory "xyz"
Worse is that even if you delete the folder "xyz" and empty trash. Even then using 'pwd' command would show your present working directory as "xyz" folder.
--------------------------------------------------------------
I got a detailed response for this. The same can be read over at same Apple Official website also. I am thankful to Mr. Bob Harris from New England, USA, who took time to explain.:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
All expected behavior.
The 'cd' command makes a chdir() system service call, which opens the target directory and stores the open file descriptor in the process.
When you rename the folder, that just changes the directory entry in its parent folder, it does not change the file system inode for the directory nor does it affect already open file descriptors to the directory.
So when you do an 'ls' with no path, the 'ls' command will ask the file system for the '.' (current directory), which the file systems knows to use the current working directory it already has saved in the process.
This is how Unix has worked forever.
'cd' and 'pwd' are bash built-in commands, so bash has cached the last 'cd' path, and when you issue 'pwd', bash just echos the cached path information. It does not verify anything before displaying the path.
If you want to see the real current path, then try using
/bin/pwd
this will do the more complex reverse path reconstruction, which can have some unexpected responses, because of symbolic and hard links that may have been used to navigate down to the current directory location.
Worse is that even if you delete the folder "xyz" and empty trash. Even then using 'pwd' command would show your present working directory as "xyz" folder.
Again, bash is just echoing the cached path that bash last knew about.
Also since the process still has an open file descriptor to the directory open in the process as the current working directory, the file system will defer the actual directory delete until after that file descriptor is closed.
The fact that a file or directory will not be truely deleted if it is still open, allows an application to continue to use a file if it has it open, even when some other process deletes the file. This can be good for the application, but if that was a huge file and you were trying to free up space, you would not see the space returned until after the process that has the file open, closes the file.
You can use the 'lsof' command to find what processes have what files/directories open.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In addition, it was advised that, if I have additional Unix or Terminal related questions it would be best to post them in the Mac OS X Technologies > Unix Forum. So, one place where you can also redirect yourself for taking other unix Vodka Shots is Apple Unix Discussions
-------------------------------------------------------------
This is already present on Apple Website since 19th March 2010 and has one response in addition to the emails. Read Further Apple Mac OSX Bug By Anwar Faiz.
-------------------------------------------------------------
Make a folder, let us say "xyz" on desktop and cd to this location on a terminal using 'cd' command.
Now rename that folder to "abc".
Now type 'ls' command on Terminal to see the content of folder "xyz", it still shows.
In addition if you use 'pwd' command, it still shows that you are in directory "xyz"
Worse is that even if you delete the folder "xyz" and empty trash. Even then using 'pwd' command would show your present working directory as "xyz" folder.
--------------------------------------------------------------
I got a detailed response for this. The same can be read over at same Apple Official website also. I am thankful to Mr. Bob Harris from New England, USA, who took time to explain.:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
All expected behavior.
The 'cd' command makes a chdir() system service call, which opens the target directory and stores the open file descriptor in the process.
When you rename the folder, that just changes the directory entry in its parent folder, it does not change the file system inode for the directory nor does it affect already open file descriptors to the directory.
So when you do an 'ls' with no path, the 'ls' command will ask the file system for the '.' (current directory), which the file systems knows to use the current working directory it already has saved in the process.
This is how Unix has worked forever.
'cd' and 'pwd' are bash built-in commands, so bash has cached the last 'cd' path, and when you issue 'pwd', bash just echos the cached path information. It does not verify anything before displaying the path.
If you want to see the real current path, then try using
/bin/pwd
this will do the more complex reverse path reconstruction, which can have some unexpected responses, because of symbolic and hard links that may have been used to navigate down to the current directory location.
Worse is that even if you delete the folder "xyz" and empty trash. Even then using 'pwd' command would show your present working directory as "xyz" folder.
Again, bash is just echoing the cached path that bash last knew about.
Also since the process still has an open file descriptor to the directory open in the process as the current working directory, the file system will defer the actual directory delete until after that file descriptor is closed.
The fact that a file or directory will not be truely deleted if it is still open, allows an application to continue to use a file if it has it open, even when some other process deletes the file. This can be good for the application, but if that was a huge file and you were trying to free up space, you would not see the space returned until after the process that has the file open, closes the file.
You can use the 'lsof' command to find what processes have what files/directories open.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In addition, it was advised that, if I have additional Unix or Terminal related questions it would be best to post them in the Mac OS X Technologies > Unix Forum. So, one place where you can also redirect yourself for taking other unix Vodka Shots is Apple Unix Discussions
Monday, July 4, 2011
Mohd Anwar Jamal Faiz listed in Adobe X Credits - adobexcredits -on official Adobe.com website in Licencing and installer technologies
Hi,
This title seems to be pretty straightforward in explaining what i want to convey.
again is self explanatory:
"Mohd Anwar Jamal Faiz listed in Adobe X Credits on official Adobe.com website in Licencing and installer technologies"
Obviously, Mohd Anwar Jamal Faiz is me ;)
You can see the AdobeXCredits Page here. View AdobeXcredits Page
You may also refer for information on Acrobat X Team Overview
My work in Adobe was truely a great learning experience with best minds of the industry. I could in short summarize my stay in Adobe as follows:
I worked in Adobe Systems from April 2009 - Jan 2011.
You can see the Credits in Adobe Acrobat v 10.1.2 from Help menu. The same is visible in Free downloadable Acrobat X Reader also. I am pasting snapsjot from version 10.1.2
I was Working in Creative Suite Team and helping development and API testing of CS Installer. The development was in Visual Studio 8.0, VC++, and XCode on Mac OSX. The Whitebox Unit test framework was an in-house one:Potluck. I was responsible for developing testcases, writing Unit test cases in VC++, adding to the framework and executing them. The test cases were maintained on TestStudio and for bug/defect tracking we used Watson. I worked in development and enhancement of a White Box Testing Framework and automation of entire process.
The biggest achievement was Develop a System to fully automate the CodeCoverage estimation using BullsEye. I developed the system and in its final forms, it was able to get triggered automatically, all code synched, build, instrumented binaries collected, functional testing done, results analyzed, reports prepared, and finally send via email and on a centralized host server where the reports can be viewed in Flash Swf animation.
I a sort of lead the Whitebox and Security Testing team of 2 people. Apart from using Excel Macros, VBA, various databases, XML, and dozens of utilities, my work primarily circumscribed Whitebox, security, performance, memory leaks testing. Some handy tools were Veracode, AppVerifier, Fortify, DevPartner, WinDbg, IBM Rational Purify, and Glowcode.
Definitely Perforce, MSOutlook, Office, McAfee AV, Google, Yahoomail, and Facebook were in routine ;)
This title seems to be pretty straightforward in explaining what i want to convey.
again is self explanatory:
"Mohd Anwar Jamal Faiz listed in Adobe X Credits on official Adobe.com website in Licencing and installer technologies"
Obviously, Mohd Anwar Jamal Faiz is me ;)
You can see the AdobeXCredits Page here. View AdobeXcredits Page
You may also refer for information on Acrobat X Team Overview
My work in Adobe was truely a great learning experience with best minds of the industry. I could in short summarize my stay in Adobe as follows:
I worked in Adobe Systems from April 2009 - Jan 2011.
You can see the Credits in Adobe Acrobat v 10.1.2 from Help menu. The same is visible in Free downloadable Acrobat X Reader also. I am pasting snapsjot from version 10.1.2
I was Working in Creative Suite Team and helping development and API testing of CS Installer. The development was in Visual Studio 8.0, VC++, and XCode on Mac OSX. The Whitebox Unit test framework was an in-house one:Potluck. I was responsible for developing testcases, writing Unit test cases in VC++, adding to the framework and executing them. The test cases were maintained on TestStudio and for bug/defect tracking we used Watson. I worked in development and enhancement of a White Box Testing Framework and automation of entire process.
The biggest achievement was Develop a System to fully automate the CodeCoverage estimation using BullsEye. I developed the system and in its final forms, it was able to get triggered automatically, all code synched, build, instrumented binaries collected, functional testing done, results analyzed, reports prepared, and finally send via email and on a centralized host server where the reports can be viewed in Flash Swf animation.
I a sort of lead the Whitebox and Security Testing team of 2 people. Apart from using Excel Macros, VBA, various databases, XML, and dozens of utilities, my work primarily circumscribed Whitebox, security, performance, memory leaks testing. Some handy tools were Veracode, AppVerifier, Fortify, DevPartner, WinDbg, IBM Rational Purify, and Glowcode.
Definitely Perforce, MSOutlook, Office, McAfee AV, Google, Yahoomail, and Facebook were in routine ;)
Mohd Anwar Jamal Faiz wins in Symantec Cutting Edge Capture the Flag Hacking Vulnerability contest 2011
Hi
I am glad to post this news to my readers. The tilte is self explanatory:
"Mohd Anwar Jamal Faiz wins in Symantec Cutting Edge Capture the Flag Hacking Vulnerability contest 2011"
Obviously, Mohd Anwar jamal Faiz is me ;)
Symantec Cutting Edge Winners
You can click on the above link to find all Cutting Edge 2011 winners and also look at my photo.
I am glad to post this news to my readers. The tilte is self explanatory:
"Mohd Anwar Jamal Faiz wins in Symantec Cutting Edge Capture the Flag Hacking Vulnerability contest 2011"
Obviously, Mohd Anwar jamal Faiz is me ;)
Symantec Cutting Edge Winners
You can click on the above link to find all Cutting Edge 2011 winners and also look at my photo.
Friday, July 1, 2011
Javascript to open new popup window center on screen
I have met this requirement several times and have written this many times from scratch.
I seem to forget the syntax and refer on the internet again and again. this time I formaly wanted to give it a place on my blog itself.
So here comes a simple java script function that opens a new pop-up window and puts it on middle of screen :-
For example you may try out the following link...
Click Here to open POPUP WINDOW
Clicking on the above link will open a new window. Voila!! U achieved a popup window. True, it was as easy as this. But the syntax to open a new window should be kept in mind.
You can return to this blog, whenever you feel like. There are a lots more advices, secret tricks, tips in programming. I do this for joy and passion. But no wrong if I request you to click on few of the Advertisement links. It would help me getting my bread and butter.
And for you all, I promise that the next article will be a very buttery. Yum! Yum!
I seem to forget the syntax and refer on the internet again and again. this time I formaly wanted to give it a place on my blog itself.
So here comes a simple java script function that opens a new pop-up window and puts it on middle of screen :-
For example you may try out the following link...
Click Here to open POPUP WINDOW
Clicking on the above link will open a new window. Voila!! U achieved a popup window. True, it was as easy as this. But the syntax to open a new window should be kept in mind.
You can return to this blog, whenever you feel like. There are a lots more advices, secret tricks, tips in programming. I do this for joy and passion. But no wrong if I request you to click on few of the Advertisement links. It would help me getting my bread and butter.
And for you all, I promise that the next article will be a very buttery. Yum! Yum!
Subscribe to:
Posts (Atom)