Committed in r27244 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r27238 - thank you!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3+feAACgkQdputYINPTPMZYwCfUhf3BQ5jE87LRV4AT0jza1rx
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
mangled by your mailer?
- -- 8 --
patching file net/wing/files/lib/network/wing.sh
Hunk #1 FAILED at 49.
Hunk #2 FAILED at 77.
Hunk #3 FAILED at 104.
3 out of 3 hunks FAILED -- saving rejects to file
net/wing/files/lib/network/wing.sh.rej
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r27239 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3+f4gACgkQdputYINPTPPT2wCfcSLEgF6423dfZ0tzv08jOfdh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Deleted in r27240 - thanks for the heads up.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3+gBoACgkQdputYINPTPOe0wCZASfMi+A/tdlkr+p8Y4OFemjT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I committed a simplified version in r27241 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
can you provide details?
I see no issues with tcpdump on recent backfire.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Hi.
- $(INSTALL_DIR) $(1)/etc
- $(INSTALL_DATA) ./files/rsyncd.conf $(1)/etc/
+ $(INSTALL_DIR) $(1)/etc/config
+ $(INSTALL_DATA) ./files/rsyncd.conf $(1)/etc/config/rsyncd
NACK on this. The /etc/config/ directory is reserved for UCI
configuration files, the rsyncd.conf is
The obvious next step is to find out where it crashes exactly -
set -x might help with that. I suppose its when it tries to call into
(former) system resources.
Maybe calling reboot at all is not such a great idea as it attempts to
run the (former) init scripts to stop them.
~ Jow
Just a thought. The directory reserved for uci should have been named
something like /etc/uci-config.
But it hasn't so any further discussion on this is futile.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Im pretty sure that sysupgrade has a flag to use that mode?
Yes, it has:
-c attempt to preserve all changed files in /etc/
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maybe it already helps to enable SysRq support in your builds.
Sysupgrade tries to trigger a system reset through it if its still alive
10 seconds after calling reboot.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment:
Hi,
without knowing the details here I would argue that a config domain
entry in /etc/config/dhcp may be better due to the following reasons:
- I believe users expect /etc/hosts to be unmanaged, means nothing
writes in there
- The domain entries in /etc/config/dhcp appear in the gui and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
just set start to 257 and it will lease addresses beginning with x.y.1.1 .
192.168.0.0/16 + 257 = 192.168.1.1
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did you flash a jffs2 image with a wrong blocksize maybe?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Committed in r26977 - thanks again.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26979 - thanks.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26980 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26981 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Shouldn't this be done for all targets?
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26982 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26983 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26984 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Am 24.05.11 11:03, schrieb Tim Fletcher:
Would it be worth adding /etc/crontabs to the standard list of stuff to
keep over upgrades?
Definitely, added in r26986.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Committed in r26988 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26993 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26994 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26995 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26998 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26929 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26930 r26931 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It obviously depends on how your module is packaged.
Do you patch it into the kernel tree? In this case the most fine grained
make target to use is make target/linux/{clean,compile} .
If you can you should consider packaging your source as an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A 'make path/to/package/compile' (i.e. 'make package/busybox/compile')
in the TOPDIR with an optional V=99 switch will do the trick.
Note that the patch/to/package bit is misleading.
Even if a package is in package/feeds/packages/foobar/ you can
Hi,
a less invasive method is setting
RSTRIP:=true
in your package Makefile.
(Not: true in this context means /bin/true)
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The problem is that if I just copy my own configuration file to
/etc/config/openvpn, it will be overwritten by the one from the
openvpn-package. So my config is lost.
Not if you put it in the files/ dir of the buildroot topdir as I wrote.
Its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The linked discussion refers to an entirely different matter.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It was a patch that added the file in the first place. src/posix.c is
not part of any official Lua distribution.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Hi.
Any mechanism that relies on any particular package installation order
during image creation is by definition broken.
Better use the files/ directory in your buildroot toplevel folder (you
have to create it first) and then put your stuff there, e.g.
files/etc/openvpn/cert.crt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Each device article is supposed to contain a flashing openwrt and
upgrading openwrt section which clearly outlines the image to use.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
profiles are nothing more than package preselections.
Anything that modifies the kernel / requires different compile options
or flags has to be a subtarget.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using
Hi,
patch applies this time but compilation fails horribly.
It looks like there is no shared library built anymore and it tries to
install binaries into /usr/lib/ during compilation.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Sorry it still does not apply:
patching file package/libpcap/patches/101-makefile_create_bindir.patch
patching file package/libpcap/patches/103-makefile_flex_workaround.patch
Hunk #1 FAILED at 3.
1 out of 1 hunk FAILED -- saving rejects to file
Hi,
why not just change ld-*.so to ld-*.so* ?
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Applied in r26782, thanks.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26783, thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26784 - thanks.
Would you be willing to maintain this package in the future?
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Patch didn't apply but I added the entry anyway in r26785 - thanks.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26787 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26788 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
This one was committed in r26694, thanks.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26789 - thanks!
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi,
committed in r26790 with two slight changes:
- Fixed the copyright string to display 2011
- Added PKG_FIXUP:=autoreconf to make sure the OpenWrt
libtool is used.
Would you be willing to maintain this package in the future?
~ Jow
___
This patch was committed in r26727.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r26792, thanks.
Would you be willing to maintain that package in the future?
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Are both really needed?
No, they should be harmonized. Maybe we should just make the ieee80211d
bool default on and drop the newly added parameter handling?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's my proposal:
Index: package/hostapd/files/hostapd.sh
===
- --- package/hostapd/files/hostapd.sh (revision 26771)
+++ package/hostapd/files/hostapd.sh(working copy)
@@ -136,9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thank you, committed in r26728.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2t338ACgkQdputYINPTPPcQACgjOc2ImL1JOHp1K988BIE471d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the patch is broken (long lines wrapped).
After fixing the line wraps it does not apply cleanly:
patching file package/libpcap/patches/201-space_optimization.patch
Hunk #1 succeeded at 1 with fuzz 2.
Hunk #2 succeeded at 23 with fuzz 1.
Hunk #3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
same issue here - long lines are wrapped.
Didn't test whether it applies otherwise.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I agree. But I thought that description supposed to be like on the tools
home page. I mean you should not learn how to use a tool from OpenWrt
description. Or am I wrong?
Nope not at all.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG
Hi,
please do not do dirty hacks like relying on an interface called wan
in your scripts. You should develop a hotplug handler which is invoked
for ifup events on any interface. As soon as one interface appears
which carries as 0/0 route, you have your wan.
See the 6in4 and 6to4 packages for
I'd suggest to use ip route list exact 0.0.0.0/0 to find the device
and then the find_config() shell function to map the device to an uci
interface name.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
I think the current situation of enforcing ETSI limits on US machines
flies in the face of WIRELESS FREEDOM.
In the interest of collaboration Atheros specifically wants OpenWrt to
not publish unregulated binaries. One prerequisite for publishing a
fully open driver was the ability to enforce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
patching file scripts/feeds
Hunk #1 FAILED at 106.
Hunk #2 FAILED at 283.
2 out of 2 hunks FAILED -- saving rejects to file scripts/feeds.rej
Can you rebase your patch?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
is this patch still applicable after
https://dev.openwrt.org/changeset/26426 ?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
can you resend the patches as one big one?
svn diff package/feeds/packages/iftop/{Makefile,patches} \
iftop-update.patch
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
- Removed the avm patch, as lots of things got included in the newer
version and the left-over parts seemed to break samba
The left over parts where stripping down of samba.
How big is the final 3.0.37 smbd without this AVM patch?
~ Jow
Hi.
Currently the ext-blockroot solution feels very racy, and the init
scripts sometimes end up in a fun state due to being started before
overlays are in place and not. ( what is it, S93 and forwards that are
safe to use? Not much )
You're doing something very wrong then as init is not even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the patches, I'll take a look at them shortly.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Hi,
interesting read, looks like they more or less mandate DHCPv6 (both
server and client). This slightly bothers me since the currently
available DHCPv6 server implementations are rather big and there are no
plans to support this protocol in dnsmasq.
The rest looks like it is doable, but not
Hi,
no I have no list yet but it boils down to the fact that the current
network and interface setup mechanisms are rather constrained, old and
inflexible.
Big problems are the lack of statefulness, the tendency for race
conditions, the inability to properly nest protocols and the limited
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the disabling is being done deliberately to give users a chance / force
them to clean up the overlay after a reflash.
Since uclibc has no stable abi, overlay may contain old binaries,
especially ones involved in system init, which could cause
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I'm building trunk with 2.6.38 enabled, but ocf is failing to build:
[...] Also, looking at the arrangement of the files... they aren't
done as standard patches, but just normal files copied into the
kernel source tree...
That's a little
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Comments inline.
--- utils/mc/Makefile (revision 26195)
+++ utils/mc/Makefile (working copy)
@@ -8,19 +8,19 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=mc
-PKG_VERSION:=4.6.2
+PKG_VERSION:=4.7.5.1
PKG_RELEASE:=1
How am I supposed to figure out the exact revision number corresponding to a
particular binary release (or release candidate)?
So far we mentioned it in every release note, posted to the devel list, the
users list, the forum and for finals in the Trac roadmap again.
- Jow
PGP.sig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01.03.2011 22:47, Daniel A. Nagy wrote:
Hello,
I am wondering how to make sure that a re-compilation of a released (tagged)
OpenWrt distribution from svn would result in compiling the same packages that
come from feeds, as feeds.conf.default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
│ Depends on: LINUX_2_6
There is no LINUX_2_6 symbol anymore.
Change your DEPENDS to @!LINUX_2_4 - this will work on both backfire and
trunk.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with
If you didn't want to list every arm processor there, neither do it here.
Maybe this?
ifneq ($(filter -march=armv%,$(TARGET_OPTIMIZATION)),)
ARCH_SUFFIX:=_$(patsubst -march=arm%,%,$(filter
-march=armv%,$(TARGET_OPTIMIZATION)))
endif
~ Jow
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I will add a substitution to replace + with , to maintain
compatibility with BusyBox httpd.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
see https://dev.openwrt.org/ticket/8418#comment:1 .
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Thats an upstream dnsmasq decision and not within the scope of this patch:
-6 --dhcp-script=path
Whenever a new DHCP lease is created, or an old one destroyed, the
executable specified by this option is run. [...]
~ Jow
___
openwrt-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
What's the clean way of:
1) adding custom configuration (running custom scripts) on first boot.
/etc/uci-defaults/foo.sh, a script which can contain arbritary commands,
its deleted by the system after it was invoked once.
2) adding custom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
1) do these scripts require the same /etc/rc.common format as the files
in /etc/init.d folder or are they just straight shell scripts?
Plain shell scripts, no dependencies.
2) when are they called exactly? before or after the init.d scripts,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
/usr/lib/lua/luci/model/cbi/admin_network/wifi.lua:219: bad argument
#1 to 'ipairs' (table expected, got nil)
Will investigate it.
PS: Is this the right forum for Luci error reports? The Luci's Trac is
closed for reporting tickets, but open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In Luci 0.10 this has regressed to just a plain input field.
Try pressing enter.
Remember, I am am using a custom header based on 0.9 version of header.htm.
And yes, there is a cbi.js, whci needs to be loaded in the htm header.
I added that to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
there is no such html in the official themes, is this with a custom
header.htm? If yes, would you mind to show it to me? It looks like its
missing a pcdata() call somewhere.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Try replacing
%=nnode.title%
with
%=pcdata(nnode.title)%
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well its not new but more commonly used.
The pcdata() function sanitizes UTF-8 and escapes XML special chars so
it basically guarantees that text filtered through it cannot break the
document. I'll add it to the docs later.
~ Jow
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Do you use custom templates or something?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk03R4QACgkQdputYINPTPMPEwCfTsm3kx57nomLiG138tHXfiJP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, make sure that your own header.htm contains this:
script type=text/javascript src=%=resource%/xhr.js/script
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is a short migration guideline here:
http://luci.subsignal.org/trac/wiki/Documentation/LuCI-0.10
I'll add the JS stuff shortly.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Which chrome build/release exactly? Can you rule out any caching issues?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, its an oversight. I'll fix it today.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk01bRcACgkQdputYINPTPPsNgCbBXUQoO8XsSlQwfEm0aOHC2jh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I just tried it in the SDK and mini is still default if present.
Are you sure you didn't just clear the cache in /tmp ?
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fixed.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk01/U4ACgkQdputYINPTPPJFgCfTXh6L7ddZ/WQcyxV21lMJ0U+
93sAoKKxz9XTxwklfD1BJZCZflo8F8a2
=hdpM
-END
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
This is expected. The uhttpd server is single threaded and will only
process one connection at a time, waits until the operation is finished,
and then switch to the next. By querying the server from within a
running cgi script you basically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At least use lowercase vars in your refactured code. All those all-caps
names make it look like SQL...
The all-caps names should be reserved for global vars (resembling
constants) and stuff passed in from the environment.
~ Jow
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r24959 - thanks!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0rLsoACgkQdputYINPTPMEIwCfZWB08Z5OFr2D7UcbiRnUpq/e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
r...@openwrt: _http redirect 302 http://1.1.1.1
HTTP/1.1 302 Temporary Redirect
This is only valid for nph scripts. The CGI spec defines the following
header for overriding the HTTP status:
Status: code message\r\n
So your script has to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You could change the CGI prefix back to /cgi-bin and add this instead:
list interpreter 'cgi-bin-splash=/bin/ash'
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
901 - 1000 of 1241 matches
Mail list logo
