On 04/08/2013 10:57 PM, Aaron Lewis wrote:
> Hi,
>
> I'm running Arch with 3.8.6. kernel, and I got it patched with 2.8.1 releases.
>
> But aa-status got errors,
>
> apparmor module is loaded.
> apparmor filesystem is not mounted.
>
> Any ideas?
>
> P.S securityfs is mounted, mount shows:
>
>
Hi John!
On 01:38 Tue 09 Apr , John Johansen wrote:
> On 04/08/2013 10:57 PM, Aaron Lewis wrote:
> > Hi,
> >
> > I'm running Arch with 3.8.6. kernel, and I got it patched with 2.8.1
> > releases.
> >
> > But aa-status got errors,
> >
> > apparmor module is loaded.
> > apparmor filesystem i
On 04/09/2013 01:58 AM, Aaron Lewis wrote:
> Hi John!
>
> On 01:38 Tue 09 Apr , John Johansen wrote:
>> On 04/08/2013 10:57 PM, Aaron Lewis wrote:
>>> Hi,
>>>
>>> I'm running Arch with 3.8.6. kernel, and I got it patched with 2.8.1
>>> releases.
>>>
>>> But aa-status got errors,
>>>
>>> appar
Hello,
Am Montag, 8. April 2013 schrieb Jamie Strandboge:
> Recent kernels/glibc also now trigger reads for
> /proc/sys/vm/overcommit_memory. This is explained in both malloc(3)
> and proc(5). Basically, there are different memory allocation
> strategies and /proc/sys/vm/overcommit_memory contains
On 04/09/2013 06:36 AM, Christian Boltz wrote:
> Hello,
>
> Am Montag, 8. April 2013 schrieb Jamie Strandboge:
>> Recent kernels/glibc also now trigger reads for
>> /proc/sys/vm/overcommit_memory. This is explained in both malloc(3)
>> and proc(5). Basically, there are different memory allocation