| 1 |
On Saturday, March 12, 2011 07:36:35 Paweł Hajdan, Jr. wrote: |
| 2 |
> I wonder why pax-utils.eclass uses elog instead of just einfo. An |
| 3 |
> example message looks like this: |
| 4 |
> |
| 5 |
> * Fallback PaX marking -m |
| 6 |
> * out/Release/chrome |
| 7 |
> |
| 8 |
> IMHO it's not very useful in the elog messages, but maybe there are |
| 9 |
> scenarios in which it is useful. |
| 10 |
> |
| 11 |
> My idea is to just replace all elogs with einfos in pax-utils.eclass. |
| 12 |
> What do you think? |
| 13 |
|
| 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 |
Archives