* Christoph Pleger [2016-01-06 20:01]:
> But if I change bootcmd, how long will that be valid? The only way to
> connect to uboot is while booting, because I could not get the tools from
> package u-boot-tools to work. So, if I change bootcmd at boot time, will
Hello,
> It depends on how you've configured u-boot. Connect to u-boot and run:
>
> printenv bootcmd
>
> If it looks like this:
>
> bootcmd=setenv bootargs ${bootargs_console}; run bootcmd_usb; bootm
> 0x0080 0x0110
>
> (bootcmd_usb might be bootcmd_mmc or bootcmd_sata)
It is
Hello,
I already posted my question on debian-us...@lists.debian.org, but
probably here is a better place:
I want to enable apparmor on my SheevaPlug device. This requires the
kernel command line parameters "apparmor=1 security=apparmor" to be set.
But I do not know how to set kern
ello,
>
> I already posted my question on debian-us...@lists.debian.org, but
> probably here is a better place:
>
> I want to enable apparmor on my SheevaPlug device. This requires the
> kernel command line parameters "apparmor=1 security=apparmor" to be set.
> But I do
* Christoph Pleger <christoph.ple...@cs.tu-dortmund.de> [2016-01-04 10:59]:
> I already posted my question on debian-us...@lists.debian.org, but
> probably here is a better place:
>
> I want to enable apparmor on my SheevaPlug device. This requires the
> kernel command line p
5 matches
Mail list logo