| 1 |
On 03/13/2011 04:19 PM, Mike Frysinger wrote: |
| 2 |
> On Saturday, March 12, 2011 07:36:35 Paweł Hajdan, Jr. wrote: |
| 3 |
>> I wonder why pax-utils.eclass uses elog instead of just einfo. An |
| 4 |
>> example message looks like this: |
| 5 |
>> |
| 6 |
>> * Fallback PaX marking -m |
| 7 |
>> * out/Release/chrome |
| 8 |
>> |
| 9 |
>> IMHO it's not very useful in the elog messages, but maybe there are |
| 10 |
>> scenarios in which it is useful. |
| 11 |
>> |
| 12 |
>> My idea is to just replace all elogs with einfos in pax-utils.eclass. |
| 13 |
>> What do you think? |
| 14 |
> i think it depends on the person. for people who dont use grsec/PaX, they |
| 15 |
> probably could care less and never see this output. for people who do, they |
| 16 |
> probably do want to see this. |
| 17 |
> |
| 18 |
> maybe have it `elog` only when [[ $(uname -r) == *-grsec* ]] |
| 19 |
> -mike |
| 20 |
|
| 21 |
blueness@yellowness ~ $ uname -r |
| 22 |
2.6.37-hardened-r5 |
| 23 |
|
| 24 |
so you need == *-hardened-* |
| 25 |
|
| 26 |
-- |
| 27 |
Anthony G. Basile, Ph.D. |
| 28 |
Gentoo Developer |
Archives