[EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Wed, 27 Sep 2006 05:46:29 -0500:
> Alright. Another reason would be to use PaX for security. I’ve used > PaX and what I did for that, to get PIC code, was to use the > ‘hardened’ 3.x compiler. The ‘hardened no SSP’ setting would be the > one for prelink, I think. Right on the security thing in general, tho I'm not sure of the specific specs files specifics. (Wow, that sounds weird! <g>) > When I really want a program to start quickly, though, I use the > sticky bit, so the program stays in memory. I think this is the > default for GNU Emacs. Eh? That's a rather dated use of that bit, AFAIK. See the wikipedia (stub entry) here: http://en.wikipedia.org/wiki/Sticky_bit While keeping a program in memory was the original use of that bit, it hasn't been used for that for a long time, as modern swapping and caching methods tend to be decently efficient at that on their own. In modern system use, the sticky bit has significance only for directories, where it affects deletion/rename permissions in multiple user access situations, such as the /tmp dir, which is commonly world writable but set sticky so only a file's owner or root can delete files. Of course, you can use the sticky bit on non-dirs for other things if you wish, but there's no system significance on executables as there once was. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- gentoo-amd64@gentoo.org mailing list
