How to add kernel boot command line args?

2017-02-10 Thread Forest
Hi, folks. How do I add arguments to the kernel boot command line for Debian Jessie on a Marvell Kirkwood device? I want to use AppArmor on a QNAP NAS, and the wiki says I need to enable the appropriate LSM with kernel args apparmor=1 security=apparmor, but I don't know how to configure this on

Re: How to add kernel boot command line args?

2017-02-10 Thread David Lechner
On 02/10/2017 12:06 PM, Forest wrote: Hi, folks. How do I add arguments to the kernel boot command line for Debian Jessie on a Marvell Kirkwood device? I want to use AppArmor on a QNAP NAS, and the wiki says I need to enable the appropriate LSM with kernel args apparmor=1 security=apparmor,

Re: How to add kernel boot command line args?

2017-02-10 Thread Martin Michlmayr
* David Lechner [2017-02-10 14:22]: > I don't know about that specific board, but in general, you can edit > /etc/default/flash-kernel and add the command line parameters there, > then run flash-kernel and reboot. That won't work with the QNAP devices which don't use the

Re: How to add kernel boot command line args?

2017-02-10 Thread Martin Michlmayr
* Forest [2017-02-10 10:06]: > How do I add arguments to the kernel boot command line for Debian > Jessie on a Marvell Kirkwood device? > > I want to use AppArmor on a QNAP NAS, and the wiki says I need to > enable the appropriate LSM with kernel args apparmor=1 >

Re: How to add kernel boot command line args?

2017-02-10 Thread Eric Cooper
On Fri, Feb 10, 2017 at 02:06:20PM -0800, Martin Michlmayr wrote: > * David Lechner [2017-02-10 14:22]: > > I don't know about that specific board, but in general, you can edit > > /etc/default/flash-kernel and add the command line parameters there, > > then run flash-kernel

Re: How to add kernel boot command line args?

2017-02-10 Thread Forest
On Fri, 10 Feb 2017 14:06:20 -0800, Martin Michlmayr wrote: >> I don't know about that specific board, but in general, you can edit >> /etc/default/flash-kernel and add the command line parameters there, >> then run flash-kernel and reboot. > >That won't work with the QNAP devices which don't use

Re: How to add kernel boot command line args?

2017-02-10 Thread Forest
On Fri, 10 Feb 2017 14:15:28 -0800, Martin Michlmayr wrote: >> Aside from the problem of how to set kernel parameters on QNAP >> devices, the SECURITY_APPARMOR kernel option is not enabled on armel >> kernels due to size restrictions on some machines. > >I should have made it clearer that "some

Re: htop wierdness

2017-02-10 Thread Gene Heskett
On Friday 10 February 2017 10:32:59 Milan P. Stanic wrote: > On Fri, 2017-02-10 at 09:03, Gene Heskett wrote: > > I just noticed an oddity about htop, running uptodate jessie on an > > r-pi-3b. > > > > If sudo to run it, or if run from root shell, the top panels > > contents are duplicated, both

Re: htop wierdness

2017-02-10 Thread Milan P. Stanic
On Fri, 2017-02-10 at 09:03, Gene Heskett wrote: > I just noticed an oddity about htop, running uptodate jessie on an > r-pi-3b. > > If sudo to run it, or if run from root shell, the top panels contents are > duplicated, both sides of it. No such oddity if running as user 1000. > > I have not

htop wierdness

2017-02-10 Thread Gene Heskett
Greetings arm people; I just noticed an oddity about htop, running uptodate jessie on an r-pi-3b. If sudo to run it, or if run from root shell, the top panels contents are duplicated, both sides of it. No such oddity if running as user 1000. I have not noted such a "bug" on the x86 boxes