As you know, the FCC is enforcing rules around securing regulatory and DFS
behavior and that is affecting how manufacturers respond to end-user
re-flashing. We're aware of some suggestions that have been proposed[1], but
some of those inherently would block re-flashing. We'd like to open
On 09/18/2016 04:18 PM, Hauke Mehrtens wrote:
> Hi,
>
> I updated the ar7 target to kernel 4.4 in this branch:
> https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/kernel-4.4
>
> If you have any device supported by this target please test it and
> report back if the
Hi all,
I can get you started with LEDE infrastructure and get Martin and Jan-Tarek
appropriate access to a Digital Ocean droplet for setup. Please contact me
directly if you want to go ahead with a LEDE droplet for the Wiki and we can go
from there. I will at least need your SSH RSA public keys
Hi Rafał,
Thank you for the detailed comment!
Update status:
prefixed with ">" --done
Copyright --done
make target/linux/refresh V=s --done
Patches prefix with 1xxx,2xxx...refer target/linux/generic/PATCHES
ok, lets do that then. i'll have a look at your patch from last week
during the day
John
On 20/09/2016 09:49, Lebleu Pierre wrote:
> Hi John,
>
> Indeed, I already tried that solution with the default shadow :
> --- a/package/base-files/files/etc/shadow
Hi John,
Indeed, I already tried that solution with the default shadow :
--- a/package/base-files/files/etc/shadow
+++
Hi John,
Thank you for your answer.
I tried your solution but it seems not to work or it does not do what I want.
Indeed, the password is one thing but there is also the fact that the system is
not ready (the scripts are still running).
As we can see, the hostname is not even set. I would like
