| 1 |
On пн, 2004-08-02 at 00:49, pageexec@××××××××.hu wrote: |
| 2 |
> > Yes did chpax -mrp.. on /usr/bin/python, then run ... - killed. |
| 3 |
> |
| 4 |
> why chpax and not paxctl? |
| 5 |
> |
| 6 |
> |
| 7 |
> -- |
| 8 |
> gentoo-hardened@g.o mailing list |
| 9 |
> |
| 10 |
hi, |
| 11 |
paxctl doesn't work for me (must be my fault). Using -v <file> gives me |
| 12 |
empty line (must assume all flags are OFF), while chpax lists the flags, |
| 13 |
even disabled. Then using: paxctl -M.. <path_to_java> and paxctl -v |
| 14 |
<path_to_java> doesn't show any change (empty line-paxctl-0.2). |
| 15 |
Same thing works with chpax. |
| 16 |
Know that chpax is obsolete, but it works for me, so instead of trying |
| 17 |
to get paxctl to work i use chpax, a little bit lazy. |
| 18 |
Suggestions. TIA. |
| 19 |
Rumen |
Archives