-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I need a copy of /dev/mtdblock5 and /dev/mtdblock6.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9CiTcACgkQdputYINPTPNeaQCfaGnYJiAvRQyxheSgaSJTRmg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If the AHB bus is used then there is no PCI information, the IDs must
then be extracted from the appropriate offset in the eeprom or
boardconfig mtd partition.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thanks for providing the dump, it should get properly recognized now
after https://dev.openwrt.org/changeset/30663 .
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The Pico2 and Pico2HP however are not recognised.
> There is also a regression in so much as the Nanostation2 is no longer
> recognised as such (see below).
Fixed in r30678.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r30684
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9E+UsACgkQdputYINPTPPJ5ACeIdE8/pKGxM+0D2WXGqc4SWwb
9DcAn1Je3r1OafvBFVxcEA3Th5tRJYQ1
=VB6u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r30683
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9E+T0ACgkQdputYINPTPNWdACfTa/fYqynh7ouofI+3Om/DlO6
/FcAnRSZGSBSPmNj5OKBJIzKo2Ealza1
=bGQM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Embarrassing... but hey, it compiles - so ship it ! ;)
Fixed in r30685.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9E+y8ACgkQdputYINPTPM93wCeJL8p1jvWZM
Applied in r30707 - thank you!
~ 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.
I think it should be handled in mtd, rewriting the complete image only
because a single block had a transient erase problem is a bit excessive imo.
It also means that sysupgrade would loop forever in case of a really
fatal issue, like when the im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> maybe we should limit the loop to X times?
That would still mean needlessly rewriting good blocks X times.
Your loop approaches the problem several layers too high.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> so "just" the error-handling within the
> sysupgrade-script. fire telnet + landev?
Yes, that'd be a good solution - plus maybe netmsg to send the usual UDP
broadcast stating that something is broken.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4
Hey,
> 11ng/11na is confusing for me, there is no something
> like 11ng/11na outside OpenWrt world (or I'm not aware of :)), there is
> 11n on 5 ghz band and 11n on 2.4 ghz band so in my opinion band
> selection is reasonable and means much more for end user.
Imo this notation is inconsistent wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Honestly I don't care how it is done so far, I think it should be done
> as best as possible and this is my concern.
We do care how its done so far - and mapping 11ng / 11na seems way
simpler to me than introducing an explicit band selection.
It al
Applied in r30833 - 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
This random related message is perfectly normal.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9ZGLgACgkQdputYINPTPN9fgCgoBK7OFEJLwBfxpMpxxKXG8Fz
a
Hi,
new languages must be enabled by an administrator in the wiki.
I added japanese now, it should get offered as choice in the sidebar as
soon as you login.
HTH,
Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I now looked over the patch and have a couple of comments.
First of all, I added GPT support to the trunk kernel config a few days
ago, so it should be always there by now.
I don't like conditional compilation of kernel features triggered by a
us
> * I could not find a working copy of pangocairo. Check config.log for
> hints on why
As usual, dig through config.log
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
You need
include $(INCLUDE_DIR)/nls.mk
in your OpenWrt makefile. That will add the needed iconv search paths to
TARGET_CFLAGS.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Yes, you need to patch out intltool related stuff.
Usually its enough to remove the "po" from SUBDIRS in the Makefile.am
and then declaring "PKG_FIXUP:=autoreconf" in the OpenWrt Makefile.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
"-R" is a linker option but unknown to gcc. Either (if you can) change
"-R/usr/lib" to "-Wl,-rpath=/usr/lib" or make sure that LD points to the
cross ld and not the cross gcc.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
While the existing perl code isn't the best either, yours is extremely
inefficient, you should rework it using native functions.
> + system("find $cache -follow -name $filename 2>/dev/null 1>>
> temp.dls");
perldoc -f open
> + my $lines = `cat temp.dls | wc -l`;
perldoc -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, you can optimize out the temporary dl file.
> diff -Naur a/scripts/download.pl b/scripts/download.pl
> --- a/scripts/download.pl 2012-04-04 13:19:27.0 +0530
> +++ b/scripts/download.pl 2012-04-04 13:20:34.0 +0530
> @@ -9,6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Philipp,
in principle I aggree but I've seen Perl distributions without
Digest::MD5 available by default, so shelling out to call "md5sum"
sounds ok to me.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It got line wrapped.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9+DYgACgkQdputYINPTPPmbgCePy75NtkXFACVcCe01xA4Go7G
9uAAn0DGSguFrkM+5U01dbltb4Yg9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this one is fine...
Now we still have to wait fore gabor to review it :)
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9+Fn4ACgkQdputYINPTPPd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> 1. Following "deny by default" principle, change the default section
> policy to DROP. The firewall package already add rules to allow all
> lo traffic, there should be no impact to user.
NACK. If at all it should be reject, not drop - to at le
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://wiki.openwrt.org/doc/howto/generic.failsafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+Cy+EACgkQdputYINPTPMQkwCfXuYbhT1uSzxZ8rKTdip2NoG/
IZ0An1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thank your for your contribution.
There are a few issues, comments inline.
On 10.04.2012 21:56, Jiri Slachta wrote:
> Signed-off-by: Jiri Slachta
> Index: feeds/packages/net/kamailio3/files/kamailio.init
> ===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r31270, thanks.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+HbmsACgkQdputYINPTPMR2ACgkx7DPQ1Fl2z7NjyOCyc3Vm6G
j+kAoIR17bALDooABY793sg
mosquitto.init
>
> diff --git a/net/mosquitto/Makefile b/net/mosquitto/Makefile
> index 4ed8bc4..551f286 100644
> --- a/net/mosquitto/Makefile
> +++ b/net/mosquitto/Makefile
> @@ -1,5 +1,5 @@
> #
> -# Copyright (C) 2011 OpenWrt.org
> +# Copyright (C) 2011,2012 OpenWrt.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Compiling anything is for developers. Whatever helps is a Good Thing;
> nobody expects the holy grail.
Adding a version symbol the way it was proposed in the patch does not
help, it increases our maintenance burden and implies that changing the
kern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
That sounds fine with me. The various guis will redirect "/" anyway.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+MW8YACgkQdputYINPTPMXhQCcD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thanks - applied in r31374.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+Rg7oACgkQdputYINPTPOVWgCfSWxkBOqoh5vpYm/b9NSe4PZe
6ccAn2KAQFZDb0A1s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No objections from anyone so added in r31375, thanks Michael.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+Rg+cACgkQdputYINPTPMcgQCffcxVwRhVrmZwD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
thanks for the udated patch, applied in r31376.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+RhD4ACgkQdputYINPTPMOXQCfdyDkFr0wTafoQ1J3DIp364
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I committed a modified version of this patch in r31377 - thanks!
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+RhaMACgkQdputYINPTPOb8gCgokn+W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
comments inline.
> Index: utils/nut/patches/001-fix-missing-libmath-flags.patch
> ===
>
>
- --- utils/nut/patches/001-fix-missing-libmath-flags.patch(revision 0)
> +++ utils/nu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, its a known issue.
See https://dev.openwrt.org/ticket/11341 and
http://freetz.org/browser/trunk/make/libs/uclibcxx/patches/050-gcc47x-proper-two-phase-lookup.uclibcxx.patch
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
I applied your patch series in r31569 - r31571, thank your for your
contribution.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+i6ZsACg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> So, finally please understand also, that there is a 99,48%-world
> besides v6 which has to work as it is.
Finally, please understand that your IPv6 discussion in this thread is
pointless, off topic and and unproductive. It draws attention away from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
after reading the patche multiple times I still don't get the purpose.
Shouldn't $link already contain the last value when leaving the inner
while() loop? Why do you need yet another variable which is just a copy
of the existing one?
~ Jow
-B
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> It looks like chgset 13936 broke the x86 target:
Are you using the latest trunk after a make distclean?
The multi-libc support introduced an openwrt vendor tag which changes that
directory from
i386-pc to i386-openwrt. Please try again with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Fixed with https://dev.openwrt.org/changeset/13963 - sorry for the long delay.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJaSxVdputYINPTPMRAr0RAJ9xq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
A typical write with mtd spans across multiple partitions (linux, rootfs, maybe
rootfs_data). I don't think this is possible by catting stuff into
/dev/mtdblockN unless
you start to cut the image in pieces with dd and friends, but at this point
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian J. Murrell wrote:
| On Wed, 2009-01-21 at 08:51 +0100, Markus Wigge wrote:
|> Hello,
|
| Hi,
|
|> Have you ever tried "sysupgrade"?
|
| No.
|
|> A nice little tool to save your
|> config,
|
| And how does it know where all of the various config i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Right. But that's a list that will continually need updating as new
> packages are brought in. As I said in a previous message, having
> package maintainers identify config files within their packaging is
> still error-prone but probably less so th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| Is it, or will it some day get Luci driven to operate as seamlessly as
| native firmware upgrades?
LuCI's firmware upgrade pages already use sysupgrade (or better it's shell
libraries)
internally.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Thanks for reporting, I closed it.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkl5vFIACgkQdputYINPTPNNqACfdGTbIoCLY2JLsP26sv+CyIN6
ZngAoJvZaCJE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed with r14427 - thank you.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJjPZcdputYINPTPMRAr76AJ9wJnwADiGekaesALqy1zULz+IrGQCeJvKO
zk77aHvKiZccTEQzE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey.
I think a length-based detection is more intuitive as the users don't have to
memorize
another option to control the actual interpretation of the key.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> Posibly it must be a way to make it work in openwrt, because it is
> working well in debian, please see this link:
> http://wpkg.org/Running_Debian_on_ASUS_WL-500W
Nope. They're using OpenWrt to boot into Debian, OpenWrt's kernel uses b43 - ot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Thanks. I committed it in r14742 and made some additional changes.
I splitted the whole package into transmission-daemon, transmission-cli
and transmission-web.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Use "PKG_BUILD_DEPENDS". It works similiar to DEPENDS but is for compile time.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknB92MACgkQdputYINPT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> You can just let users migrate the content, Just setup guidelines and
> templates first.
Hmm, no - imho the migration needs some developer oversight to ensure
the correctness of the information in the articles, w.g. whether certain
configs are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks, applied in r15258.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrQy0ACgkQdputYINPTPPDBACdGfJOlebWVFMyjf8ITmye3Q02
kAoAnjVmkcqnw284mW0DOXDPu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks. It's applied in r15259 now.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrRCcACgkQdputYINPTPPwEQCdHFyoEx44V+GWE0Zqnq+18PKi
6PcAnRZ76aisuvJW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Applied in r15261 - thanks!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrRm8ACgkQdputYINPTPMdsgCfXRtQXKr9bxVYLrQ/dTajkLea
ahYAnjBvwZZ3gzdXsbQjgaj4QGygyjP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
r15262.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrSFUACgkQdputYINPTPPAmgCfc9wog0VRYVEWm1lFNjnZf6Pg
ar0An2IoWGKbTvZKjzZf4qVC4+rui0x8
=MRgH
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
r15263.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrSQYACgkQdputYINPTPOExwCglPpAx1wcDsLv192sCD6yvslK
zikAn06+a4REq+aVzr3U6Ko5Ur6Uxbti
=kjvt
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
r15264.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrSXoACgkQdputYINPTPMXuACffvZouVMdY95RP/gauDZNwIOj
s2UAnA/VPLUEFuJdBjEz+KA1eb/I7eSG
=1N+O
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
r15265.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrSfMACgkQdputYINPTPNVAQCaArzO2aoeZvOAL9sviqT858cy
tlUAn0Mdsiyc8dlP5hLmLiMQuaWrwIWJ
=I9Mb
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed with some minor indentination cleanups in r15266.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrTEEACgkQdputYINPTPP7YACcD8p8HtLmuSuQ0NJ02PLAL3CL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
15267.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrTboACgkQdputYINPTPNvTQCfWGyYyCylvYvD0DiUHre1Om7b
bmEAn1Rq/8UPsJXuBxHb9AvOktGwyCvf
=tedV
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
r15268.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrThEACgkQdputYINPTPOfkwCfal81dUfA732PWtLKbo7lTtrq
Z6AAoJhlRvhNgkXqcNdsF3pi7duRC7mR
=BrOQ
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
r15269.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrTz4ACgkQdputYINPTPMiWgCfYEzXf2qL/XIk5EzpHyPgIGg6
w3sAnA97ZY/1T/4rSufUl4qTn77/D1qz
=wLSx
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
r15270.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrT58ACgkQdputYINPTPNdmACcCkFRGOgQEwyYbzCwcCobnrS1
3egAn01uXwsfBf/4KXjg4fwgPIalORYg
=40Bu
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I looked at it and made some little changes.
It's committed in r15271 now.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknrUfcACgkQdputYINPTPPUl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andrea.
I committed your patch in r15289.
Not sure what you mean with enable by default; OpenWrt will usually
build every package as part of a release so that it's installable with
opkg later. Once the snapshot builds are reactivated, your module
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> I have contributed to the wiki, and I expect that the history of pages
> will disappear.
Nope, I was able to restore the full edit history of each page.
Only missing info is the username which I have substituted with the ip
address.
We'll run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Rod.
The udhcpc script is currently rewritten, we'll include this change.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkn2MQUACgkQdputYINPTPM0OQC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hmm, on vanilla OpenWrt the /etc/hosts is stored on flash, that would
mean a write on each dhcp renew. Wouldn't it be better to write the
hostname to an extra file somewhere in /tmp and pass that to dnsmasq
with addnhosts ?
~ JoW
-BEGIN PGP SIGNAT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> I'm not 100% sure that the tools accessing /etc/hosts were doing so
> through DNS. Do any uclibc functions access /etc/hosts directly?
Hmm ... I'm no expert with this but shouldn't /etc/nsswitch.conf take
care of the order of used resolvers? C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Fix committed in r15535.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkn62wAACgkQdputYINPTPP/YQCgjOB+PklbzrTNbr6YEGJIqX1R
9DQAnjPxjkCisoBX/7LAFw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15669.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC388ACgkQdputYINPTPPjYACfUvE6WqTxsApAJczNbG7yyrcB
/OYAoKeWF0KEGsSC4Nn3B0cGRIKMWr7Y
=0s7p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15671.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC4IIACgkQdputYINPTPP8LwCeN0BkQ6e8ub/tkNEGG74BoJBY
SRsAnRIByx2nY2m1+GlXPhdgRyZtFWYc
=KrWN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15672.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC4b0ACgkQdputYINPTPMQ4gCfXD4sT2GV1pTfI0sPFbcDUEz4
mDAAn1cwdLvbNpVCawlxoVfxzOQ0sgB8
=SDtr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15673.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC4yEACgkQdputYINPTPPlaACdGkype9mZVlIFNSc+mQUx7MOO
XngAnRDZzlnjAzXDR0V4wUquQ8fOCh5N
=4PYq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15674.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC454ACgkQdputYINPTPNY9gCeIdWtJ/JI5lLV0570wODDFxhi
TDkAnRNl5kICc5lPm4Xe2KgQOFOW4T1Q
=vReV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15675.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC5GEACgkQdputYINPTPPnswCffQHgnWirBiB1U2x+9/n8SZ9l
BPkAnRFvadZxJuA4DywJhMI/Slrqs8Vq
=mlmx
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15676.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC5NsACgkQdputYINPTPPMDgCgn/WCGz2UDAU6MjwgXjIdoGjg
LOoAnjXt834BvNJF2wzl2hGOYt/NNcsI
=PM2S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15677.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC5QsACgkQdputYINPTPNn5wCglviYbEkXIqnl8puaSGh0nO5Y
0DMAn2AHJaRkvqfkipQWeSxggqWTX3CD
=PnjW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15678, together with B.A.T.M.A.N. route support.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC5YsACgkQdputYINPTPN72QCfffKQnS8llhJ1AE0ZHRY9m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15679.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC5ewACgkQdputYINPTPMA8ACdHNTRw9ZieLpvlQynPnbppkkM
jWEAnjo8YewqBHjP1fErZQit6HkIs13P
=Ep/d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15680.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC5mcACgkQdputYINPTPNpoQCffH9MFXRy9P6tx5FDycolqa0f
UFwAnjSq5bPkTsqd/bQSFuKJ9AemNFhm
=oC1V
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15681.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC5rIACgkQdputYINPTPOoRQCgm7LiPtmaIgDQ7NEJ7hf1Lzph
LQAAoJagbLSsVCEYRfBn03fOXoqNW4Ep
=XLH+
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15682.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC5xwACgkQdputYINPTPPfCQCfRGa+oPvlVLx+c7OBAS/odUqt
C8EAn1C8OwtIKSNWmacfwyguI+Ii7RCr
=qDpH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15683.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC538ACgkQdputYINPTPNVLQCfW9FaSBElLMJtM8ZXT0r5Ssh6
ZOkAoJfYQGv+O0IhYs1T8vWhv9HkYzOJ
=IXjc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15678.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC56YACgkQdputYINPTPOwDQCfWZEuxWjWW9c7NR/KPhmPlMYO
zUwAnRkagwlBnSr+lzEur3fbTFzGiscE
=I/3P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15684 (and adepted for .29 and .30)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC6tMACgkQdputYINPTPMsaQCeKiRKZa3K6kwmIHjA33+/s7hW
FekAnimTW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15685.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC6xYACgkQdputYINPTPOImwCfXcbZ3nzEAMtQYvdwRHVlLEcY
CvUAn0W07DuEioBNs09Lq/kJ4+L5O7RT
=FTVt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15686.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC7O4ACgkQdputYINPTPNk+gCdF7Quw5RG0lPpxp81f+ljM+PP
W7kAnRtpS9ViUse/dPn+s/IY3/KiDNlx
=SvDQ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Unfortunately your patch does not apply here:
patching file libs/libinklevel/patches/003-fix_usb_device_location.patch
patching file libs/libinklevel/patches/001-makefile.patch
Reversed (or previously applied) patch detected! Assume -R? [n] ^C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed in r15687 but might not work until libinklevel is bumped (see
other mail).
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC8HkACgkQdputYINP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allright, must have overlooked your second mail.
It's applied in r15692 now.
~ JoW
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkoC+fIACgkQdputYINPTPNYyACf
Hi.
> I wonder if there is somewhere the config used to build the 8.09 release.
> My goal is to modify/add my kernel driver (or other packages) but without
> having
> to reflash the kernel or changing official packages.
Afaik the 8.09 release was built with the default config suggested by
menuco
Committed in r15940.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r15943.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r15945.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Committed in r15947.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
901 - 1000 of 1348 matches
Mail list logo
