Re: [LEDE-DEV] Running init in a chroot LEDE Image

2017-08-08 Thread Nicolas Pace
Thanks for replying! On Wed, 2017-08-09 at 10:09 +0800, Yousong Zhou wrote: > On 9 August 2017 at 08:01, Mirko Parthey > wrote: > > On Tue, Aug 08, 2017 at 11:32:23PM +0300, Nicolas Pace wrote: > > > I'm trying to run a rootfs chroot on my desktop computer to easen > > >

Re: [LEDE-DEV] Running init in a chroot LEDE Image

2017-08-08 Thread Yousong Zhou
On 9 August 2017 at 08:01, Mirko Parthey wrote: > On Tue, Aug 08, 2017 at 11:32:23PM +0300, Nicolas Pace wrote: >> I'm trying to run a rootfs chroot on my desktop computer to easen the >> development of userspace applications, but as I'm using ubus I need a >> complete LEDE

Re: [LEDE-DEV] Running init in a chroot LEDE Image

2017-08-08 Thread Mirko Parthey
On Tue, Aug 08, 2017 at 11:32:23PM +0300, Nicolas Pace wrote: > I'm trying to run a rootfs chroot on my desktop computer to easen the > development of userspace applications, but as I'm using ubus I need a > complete LEDE environment. > Using chroot also reduces the turnaround time for code/test

[LEDE-DEV] Running init in a chroot LEDE Image

2017-08-08 Thread Nicolas Pace
Hello everyone, Thanks a lot for an amazing project! I'm trying to run a rootfs chroot on my desktop computer to easen the development of userspace applications, but as I'm using ubus I need a complete LEDE environment. Using chroot also reduces the turnaround time for code/test cause I can just

Re: [LEDE-DEV] wifi and wan ipv6 connectivity

2017-08-08 Thread e9hack
Hi, for testing I add a hotplug script. Bellow I did copy my test sequence and the output. There are a few seconds between the commands. If 'wifi ...' is called, the 2003: address of my wan interface is gone. The other addresses are still assigned. If 'ubus ...' is called, the wan interface

Re: [LEDE-DEV] [PATCH] kernel: try to remove TCP_RENO from the kernel.

2017-08-08 Thread Baptiste Jonglez
Hi, On Sat, Aug 05, 2017 at 06:15:46PM -0700, Rosen Penev wrote: > LEDE currently uses CUBIC and not RENO by default. In theory, this > change should remove RENO from the kernel, but it doesn't. Might > as well keep it like this in case something changes. As far as I can tell, Reno is hard-wired