| 1 |
I make kernel with CONFIG_KALLSYMS (and some settings will enabled by |
| 2 |
defaults), and run him, but I have another problem |
| 3 |
when I strating emerge (--sync or -pv or -f or simple emerge packet) I got |
| 4 |
|
| 5 |
sem_post: Invalid argument |
| 6 |
sem_post: Invalid argument |
| 7 |
...^C |
| 8 |
Traceback (most recent call last): |
| 9 |
File "/usr/bin/emerge", line 6, in ? |
| 10 |
import sys |
| 11 |
KeyboardInterrupt |
| 12 |
|
| 13 |
Other commands, ls, mount, mv, cp, cd, nano, for example work correctly |
| 14 |
and apache did work slowly (pages in browser loads with some delays) |
| 15 |
|
| 16 |
pageexec@××××××××.hu пишет: |
| 17 |
> On 7 Feb 2008 at 9:25, wrote: |
| 18 |
> |
| 19 |
> |
| 20 |
>> now system works with non-PaX kernel, I can't restart system often, and |
| 21 |
>> can't attach screenshot of error-message, or make it on next weekend (9-10Feb) |
| 22 |
>> |
| 23 |
> |
| 24 |
> it's fine, whenever you have time. make sure you enable CONFIG_KALLSYMS |
| 25 |
> (iirc, you have to disable HIDESYM in grsec for that). |
| 26 |
> |
| 27 |
> |
| 28 |
>>> PS: if you enable HIGHMEM64G/PAGEEXEC then PaX will make use of |
| 29 |
>>> the NX bit. |
| 30 |
>>> |
| 31 |
>> 1. PaX or incorect settings in "Processor type and features" of kernel |
| 32 |
>> config is my problem |
| 33 |
>> |
| 34 |
> |
| 35 |
> what makes you think it's a processor type setting problem? i'd rather |
| 36 |
> guess it's some PaX bug/feature at this point in time ;-). |
| 37 |
> |
| 38 |
> |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-hardened@l.g.o mailing list |
Archives