On 3/17/11 11:18 PM, Mike Frysinger wrote:
also, this code is run at the pkg_* stage, so it's not the normal src host
feature detection. and we're talking about minor output behavior.
Is calling pax-mark in src_compile a misuse then? At least one ebuild I
maintain does that (and at least in
On Mon, Mar 21, 2011 at 8:26 AM, Paweł Hajdan, Jr. wrote:
On 3/17/11 11:18 PM, Mike Frysinger wrote:
also, this code is run at the pkg_* stage, so it's not the normal src host
feature detection. and we're talking about minor output behavior.
Is calling pax-mark in src_compile a misuse then?
On Thursday, March 17, 2011 19:40:31 Zac Medico wrote:
On 03/17/2011 03:18 PM, Mike Frysinger wrote:
On Thursday, March 17, 2011 17:59:44 Kevin F. Quinn wrote:
I'd suggest doing something like:
use hardened elog ...
There's an argument that it's better to make decisions according
On 03/17/2011 11:45 PM, Mike Frysinger wrote:
On Thursday, March 17, 2011 19:40:31 Zac Medico wrote:
On 03/17/2011 03:18 PM, Mike Frysinger wrote:
On Thursday, March 17, 2011 17:59:44 Kevin F. Quinn wrote:
I'd suggest doing something like:
use hardened elog ...
There's an argument that
On Thursday, March 17, 2011 17:59:44 Kevin F. Quinn wrote:
On Sun, 13 Mar 2011 17:38:29 -0400
Anthony G. Basile bluen...@gentoo.org wrote:
On 03/13/2011 04:19 PM, Mike Frysinger wrote:
On Saturday, March 12, 2011 07:36:35 Paweł Hajdan, Jr. wrote:
I wonder why pax-utils.eclass uses elog
On 03/17/2011 03:18 PM, Mike Frysinger wrote:
On Thursday, March 17, 2011 17:59:44 Kevin F. Quinn wrote:
I'd suggest doing something like:
use hardened elog ...
There's an argument that it's better to make decisions according to
make.conf settings rather than the host system configuration,
On Saturday, March 12, 2011 07:36:35 Paweł Hajdan, Jr. wrote:
I wonder why pax-utils.eclass uses elog instead of just einfo. An
example message looks like this:
* Fallback PaX marking -m
* out/Release/chrome
IMHO it's not very useful in the elog messages, but maybe there are
On 03/13/2011 04:19 PM, Mike Frysinger wrote:
On Saturday, March 12, 2011 07:36:35 Paweł Hajdan, Jr. wrote:
I wonder why pax-utils.eclass uses elog instead of just einfo. An
example message looks like this:
* Fallback PaX marking -m
* out/Release/chrome
IMHO it's not very useful in
On Sunday, March 13, 2011 17:38:29 Anthony G. Basile wrote:
On 03/13/2011 04:19 PM, Mike Frysinger wrote:
maybe have it `elog` only when [[ $(uname -r) == *-grsec* ]]
blueness@yellowness ~ $ uname -r
2.6.37-hardened-r5
so you need == *-hardened-*
you want to additionally match hardened,
On 03/13/2011 06:01 PM, Mike Frysinger wrote:
On Sunday, March 13, 2011 17:38:29 Anthony G. Basile wrote:
On 03/13/2011 04:19 PM, Mike Frysinger wrote:
maybe have it `elog` only when [[ $(uname -r) == *-grsec* ]]
blueness@yellowness ~ $ uname -r
2.6.37-hardened-r5
so you need ==
On Sunday, March 13, 2011 18:07:48 Anthony G. Basile wrote:
2) This works for me, but I'm not familiar with any gentoo kernels that
have -grsec in the uname. Am I missing something, or is this just in
case some of our users are deploying their own kernels?
not everyone uses sys-kernel/* ... i
I wonder why pax-utils.eclass uses elog instead of just einfo. An
example message looks like this:
* Fallback PaX marking -m
* out/Release/chrome
IMHO it's not very useful in the elog messages, but maybe there are
scenarios in which it is useful.
My idea is to just replace all elogs with
12 matches
Mail list logo
