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