@ongte: Thanks for giving a succinct and excellent reply to the sticky bit question. I found a helpful article by Wayne Pollock
that went into more details if anyone wish to read further.
I have a question about the Sticky bit 't' bit applied to executable. For example, in this Tips for Linux
... Setting the sticky bit tells Unix that once the concerned application is executed, it should remain in memory. Remember that Unix is a multi-user OS and was mainly designed so that multiple users can work simultaneously. Thus the logic used is that a program that exists in memory requires lesser time to start when a new user requests for the same program. Thus when one user has just used a program and then a new user wants to use the same program, the second user doesn't have to face a time delay for the program to initialize itself. It would be readily available to him. The concept of the sticky bit was a very useful one, long back when fast disk access and other memory access technologies weren't around. But in today's age the concept of sticky bit is obsolete, since modern day technology is advanced enough to reduce the time delay while loading applications into the memory. Thus currently the sticky bit is of very little significance. Sticky bit is only associated with executables.
Notice where I underlined. We defintely see sticky bits used in non-executables now (as the /tmp example mentioned above). There is no date on this article. Is that quote inaccurate or just out date?
Also, can someone shed some light on the current status of the above quoted "sticky bit for executables"? Is it still implemented in modern kernel/systems? If so, which system?
I understand that it is not necessarily a good idea to use such "sticky executable feature" to mess with the kernel's ability to manage memory in a modern kernel. The question is just if the "feature" still there?
Thanks in advanced for any help.