From mboxrd@z Thu Jan 1 00:00:00 1970 From: efault@gmx.de (Mike Galbraith) Date: Sun, 01 Oct 2017 19:03:03 +0200 Subject: How to verify linux-next In-Reply-To: <649f4bab-608d-9422-f2c3-401038c036c3@infradead.org> References: <159555.1506688878@turing-police.cc.vt.edu> <1506690885.1771.6.camel@icloud.com> <20170929215007.kpea2kan6hg7jzcw@thunk.org> <20170930052530.rf7bcwe3o327sobe@thunk.org> <1506876289.2536.2.camel@icloud.com> <649f4bab-608d-9422-f2c3-401038c036c3@infradead.org> Message-ID: <1506877383.5529.1.camel@gmx.de> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote: > On 10/01/17 09:44, Damian Tometzki wrote: > > > i resolved the issue with: > > sudo /etc/init.d/apparmor stop > > or boot with: apparmor=0 or systemctl mask apparmor