* Felix Fietkau [10.11.2013 08:00]:
> > hotplug-call: script: /etc/hotplug.d/iface/00-netstate READY: 1194
> > hotplug-call: script: /etc/hotplug.d/iface/15-teql START: 1194
> > hotplug-call: script: /etc/hotplug.d/iface/15-teql READY: 1194
> > hotplug-call: script: /etc/hotplug.d/iface/30-6relay
On Sat, Nov 9, 2013 at 6:31 AM, Florian Effenberger wrote:
> Hello,
>
> 2013/11/8 Weedy :
>
> > Just use trunk. I update my 4300 once a week to HEAD. I I've had zero
> > problems.
>
> what is your experience with configuration files? I haven't tested
> yet, but I am a bit afraid that my current co
On Sat, Nov 9, 2013 at 2:54 PM, David Lang wrote:
> That doesn't slow down bitrot of the patches, that just works for one
> person's systems, for not.
>
> Is there something wrong with this series that is preventing it from being
> merged upstream?
>
> do you need people to report that they need
On 2013-11-09 21:27, Bastian Bittorf wrote:
> i recognized that a "simple" 'ifup lan' can be
> very expensive for a router with low ressources,
> below a typcal call/execution trace:
>
> hotplug-call: $1 = 'iface' START: 1139
> hotplug-call: $1 = 'net' START: 1141
> hotplug-call: script: /etc/hotp
i recognized that a "simple" 'ifup lan' can be
very expensive for a router with low ressources,
below a typcal call/execution trace:
hotplug-call: $1 = 'iface' START: 1139
hotplug-call: $1 = 'net' START: 1141
hotplug-call: script: /etc/hotplug.d/iface/00-netstate START: 1139
hotplug-call: script:
That doesn't slow down bitrot of the patches, that just works for one person's
systems, for not.
Is there something wrong with this series that is preventing it from being
merged upstream?
do you need people to report that they need it to get it review priority?
do you need reports of it wor
Without netifd generates an error:
daemon.notice netifd: wan (1249): /bin/sh: /sbin/modprobe: not found
Signed-off-by: Cezary Jackiewicz
---
Index: package/network/services/ppp/patches/510-fix-modprobe.patch
===
--- package/network
* Florian Effenberger [09.11.2013 19:22]:
> > Is there an easy way to compile OpenWRT stable only with those
> > patchsets necessary to make it work with newer hardware revisions?
> > From what I recall, micro releases of OpenWRT stable often include
> > newer hardware revisions, without any other
* Ben West [09.11.2013 19:22]:
> anecdotal experience that some processes don't behave well when paged to
> swap. I'm running AR7240 devices with 32MB RAM (i.e. UBNT M gear) as mesh
> nodes, and I've found that services like olsrd, coovachilli, and
> wpa_supplicant seem to behave erratically if t
Hello,
2013/11/8 Weedy :
> Just use trunk. I update my 4300 once a week to HEAD. I I've had zero
> problems.
what is your experience with configuration files? I haven't tested
yet, but I am a bit afraid that my current configuration and
user-defined scripts might not work anymore, as trunk is us
10 matches
Mail list logo
