Devices with less memory are still common so why limit ZRAM usage just to swap
when it could be very useful as for /tmp storage.
This patch changes 3 things:
- sets default number of ZRAM devices to 2 (1st for /tmp, 2nd for swap)
- adds ZRAM (default) support to procd's init (TMPFS is used when
Package util-linux-dmesg is broken (at least) in Barrier Breaker git repo
as you can select it within menuconfig, it will compile (as a part of
util-linux) but it will not install as install section is missing from
package Makefile.
Signed-off-by: Tomasz Wasiak tjwas...@gmail.com
---
Makefile |
OpenWRT patch 255-lib80211_kconfig_hacks gives user possiblity to select
LIB80211 dependant settings (LIB80211_CRYPT_*) without having LIB80211
selected which is wrong.
My patch changes OpenWRT patch so LIB80211 is vissible and all
LIB80211_CRYPT_* options selects LIB80211 automatically.
Hi,
please send patches directly against the procd git tree.
John
On 22/10/2014 09:20, Tomasz Wasiak wrote:
Devices with less memory are still common so why limit ZRAM usage
just to swap when it could be very useful as for /tmp storage.
This patch changes 3 things: - sets default
Thanks!
I guess I'm used to doing it the old way and usually documentation is
quite lagging and I usually update old info on the wiki all the
time... Thanks once more!
On Sat, Oct 18, 2014 at 10:30 PM, Matthias Strubel
matthias.stru...@aod-rpg.de wrote:
On 10/18/2014 08:45 PM,
Hello,
Here you are (of course it is just 1/3 of the original patch).
---
diff --git a/initd/early.c b/initd/early.c
index a9f6afb..b4a375f 100644
--- a/initd/early.c
+++ b/initd/early.c
@@ -12,34 +12,130 @@
* GNU General Public License for more details.
*/
-#include sys/mount.h
-#include
Hi,
I am about to buy a TP-Link WDR4900 because of its powerful NAT
throughput (https://forum.openwrt.org/viewtopic.php?pid=244167#p244167)
Some say that this router with his rather uncommon platform mpcC85xx
has been abandoned. I'm not sure about this.
Could you clarify the state of the
* Klaus Maus klaus.ma...@aol.com [22.10.2014 10:57]:
Could you clarify the state of the future support this router or SoC
i have some (~50) and the german Telekom uses the platform in the
trains, so i bet somebody will take core of it 8-) and it's FOSS
and ath9k based, so you will not totally
kernel: update 3.10.49 to 3.10.58 (released 2014-oct-15)
All platforms which are using 3.10.x at the moment are upgraded.
Changelogs:
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.50
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.51
Hi,
a few comments inline. i am not sure if we want this inside procd
directly. maybe we should put this into fstools and then call that code
from early init. i need to think about that before i can make a decision.
John
On 22/10/2014 10:30, Tomasz Wasiak wrote:
Hello,
Here you
Signed-off-by: Hans Dedecker dedec...@gmail.com
---
interface-ip.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/interface-ip.c b/interface-ip.c
index 62d15fd..1459e9c 100644
--- a/interface-ip.c
+++ b/interface-ip.c
@@ -1154,9 +1154,11 @@ void
Reinserts the config IP parameters as the config_ip
parameter of the new interface is set to false in
interface_alloc and thus not loading the config ip
options of the old interface
Signed-off-by: Hans Dedecker dedec...@gmail.com
---
interface.c | 7 +--
1 file changed, 5 insertions(+), 2
Netifd commit b2dcb02570939d98b92c7c55db1c328693a5d52a introduces
a race condition resulting into infinite toggling interfaces
(eg static interfaces with linksensing enabled, vlan interfaces
with proto none (#18106)) when linksensing is enabled resulting into
a crash.
As netlink event messages
Hello,
In my opinion early init is too late as we need /tmp sooner - for example to be
able
to mount overlayfs (even init procd needs writeable /tmp!). Maybe we can
temporaily
mount something (RAMFS/TMPFS depending on kernel configuration) on /tmp and
then
remount ZRAM but I do not think it
On 2014-10-22 14:14, Hans Dedecker wrote:
Netifd commit b2dcb02570939d98b92c7c55db1c328693a5d52a introduces
a race condition resulting into infinite toggling interfaces
(eg static interfaces with linksensing enabled, vlan interfaces
with proto none (#18106)) when linksensing is enabled
By the way. Has anyone compiled and used BB 14.07 for devices with 16MB
of RAM that went unsupported with AA release because of lack of ZRAM ?
Fernando
On 22/10/2014 08:20, Tomasz Wasiak wrote:
Devices with less memory are still common so why limit ZRAM usage just to swap
when it could be
From: Thomas Langer thomas.lan...@lantiq.com
Many packages define already metadata about their license (PKG_LICENSE),
but this is only included in the ipk files.
This change allows to create the information also on the build-host,
to get an overview on the used licenses.
In the full list, also
On 22/10/14 11:33, Klaus Maus wrote:
Hi,
I am about to buy a TP-Link WDR4900 because of its powerful NAT
throughput (https://forum.openwrt.org/viewtopic.php?pid=244167#p244167)
Some say that this router with his rather uncommon platform mpcC85xx has
been abandoned. I'm not sure about this.
Seems this target does not get as much attention as for example ar71xx.
Until now there is this nasty mac address bug that every wdr4900 has the
same mac address [1] (if you don't manually set it in /etc/config/network).
Regards
Nico
[1] https://dev.openwrt.org/ticket/14714
Am 22.10.2014 um
Hi Felix,
Thx for the feedback. Regarding the remaining race condition I assume you
refer
to the vlan device link status which can be set as enabled due to reading
directly
the carrier state in cb_rtnl_event while the parent interface is still link
status disabled?
I will rework my patch based
this saves 10kb on libssl and 5kb on openssl-util
Signed-off-by: Etienne CHAMPETIER champetier.etie...@gmail.com
---
package/libs/openssl/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile
index
disabling sslv2 save 10kb, disabling sslv3 save 1kb more
for now leave sslv3 enable by default
Signed-off-by: Etienne CHAMPETIER champetier.etie...@gmail.com
---
package/libs/openssl/Config.in | 5 +
package/libs/openssl/Makefile | 14 +++---
2 files changed, 16 insertions(+), 3
no-smime option doesn't seems to exists
this saves 20+5 kb
Signed-off-by: Etienne CHAMPETIER champetier.etie...@gmail.com
---
package/libs/openssl/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile
index
Signed-off-by: Etienne CHAMPETIER champetier.etie...@gmail.com
---
package/libs/openssl/Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile
index 9c4855f..31cd32d 100644
--- a/package/libs/openssl/Makefile
2014-10-22 21:28 GMT+02:00 Etienne CHAMPETIER champetier.etie...@gmail.com
:
disabling sslv2 save 10kb, disabling sslv3 save 1kb more
for now leave sslv3 enable by default
Signed-off-by: Etienne CHAMPETIER champetier.etie...@gmail.com
---
package/libs/openssl/Config.in | 5 +
I am going to test a totally not supported device with only 16MB of RAM if time
permits. Unfortunately now I am having some strange issues with my development
device - tmp on ZRAM works without any issues but I have to switch off swap on
ZRAM as it was getting some random oops'es which might be
Please no on this one? SRP is great, and it's never going to be used if it
keeps getting turned off. If you're going to use openssl, you're already
choosing the big package, can we keep it at least mostly featureful?
I've been using TLS-PSK, but I'd rather use SRP. (No, I'm not using it
Here's an nvram dump for a WRT600N v1.1 running DD-WRT.
Passwords and certs have been removed.
altdns1=
altdns2=
altdns3=
apd_enable=0
apwatchdog_enable=0
apwatchdog_interval=15
auth_dnsmasq=1
autofw_port0=
block_activex=0
block_cookie=0
block_ident=0
block_java=0
block_loopback=0
On 2014-08-15 09:42, Rafał Miłecki wrote:
On 14 August 2014 07:48, Rafał Miłecki zaj...@gmail.com wrote:
On 14 August 2014 05:46, quickbooks office quickbooks.off...@gmail.com wrote:
Is it possible to install Open WRT on Netgear WNR1000 v3 N150 without
opening the box up?
(...)
OpenWrt
29 matches
Mail list logo
