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 discussion
I wanted to see if I can get more details about the buildbot setup.
I understand[1] how the defconfig is generated. How is feeds.conf
configured? Is luci part of the build? Is there automated testing that
follows the build? Perhaps posting master.cfg would be helpful.
Thanks,
Ryan
1. https:/
package-version-override calls autoreconf which breaks on any package
that doesn't use autoconf. This patch removes that assumption.
---
include/package-version-override.mk |1 -
1 file changed, 1 deletion(-)
diff --git a/include/package-version-override.mk
b/include/package-version-overri
This adds an ESSENTIAL_PROCESSES shell variable to /etc/init.d/sshd.
The corresponding openwrt patch has the details.
Signed-off-by: Ryan Nowakowski
---
net/openssh/files/sshd.init |1 +
1 file changed, 1 insertion(+)
diff --git a/net/openssh/files/sshd.init b/net/openssh/files/sshd.init
ntial processes. There's a corresponding patch for the
packages repo.
* add /etc/rc.common listessential action
* modify /lib/upgrade/common.sh to query essential processes
* add ESSENTIAL_PROCESSES to appropriate init scripts
Signed-off-by: Ryan Nowakowski
---
package/base-f
On Thu, Aug 02, 2012 at 05:32:51PM +0700, Nguyễn Hồng Quân wrote:
> To make a software use UCI for configuration instead of its own
> config, what do we have to do? Do we change in that software source
> code or UCI source code?
>
> For example, I want to make UCI setting for WifiDog.
Many package
Doing a make distclean fixed the issue. It must have been a artifact
from switching branches.
On Tue, Apr 12, 2011 at 10:57:38AM -0500, Ryan Nowakowski wrote:
> I'm getting "invalid block reference" errors when booting the VDI image.
> Also, / is mounted read-only where
I have a userspace package that depends on having NF_CONNTRACK_EVENTS
enabled in the kernel. However, currently that option is not selected
by any OpenWRT package. So, I've added it to ipt-nathelper-extra:
--- a/package/kernel/modules/netfilter.mk
+++ b/package/kernel/modules/netfilter.mk
@@ -20
I'd like to do a whole root pivot and then an overlay on top of that.
Do the current preinit hooks support that?
- Ryan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I noticed that the svn trunk gets tagged for releases. For example,
the backfire release[1]. Do you guys tag the packages[2][3] for a
particular release too? Is there a backfire version of the packages?
Thanks,
Ryan
1. svn://svn.openwrt.org/openwrt/tags/backfire_10.03/
2. http://downloads.ope
On Wed, Dec 08, 2010 at 02:57:41PM -0600, Ryan Nowakowski wrote:
> I noticed that the svn trunk gets tagged for releases. For example,
> the backfire release[1]. Do you guys tag the packages[2][3] for a
> particular release too? Is there a backfire version of the packages?
&g
Is the buildbot config checked in anywhere?
- Ryan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I'm getting "invalid block reference" errors when booting the VDI image.
Also, / is mounted read-only whereas in backfire it was mounted
read-write. I think the 2 might be related. Any ideas?
- Ryan
___
openwrt-devel mailing list
openwrt-devel@lists.op
13 matches
Mail list logo
