- the mysql directory now includes a pure mysql 5.1.37 source
- 2 patches for mysql and file .host.tgz added to patches/mysql
- script mycheck moved also from mysql directory to patches dir
- updated appropriate Mafefile's
----------------------------------------------------------------------------------------
Updated info about MySQL 5.1 compilation on Tomato routers by shibby and Hyzoom (BWQ518)
----------------------------------------------------------------------------------------
Info for devs: if you have a problem with compilation then you have to prepare own .host.tgz archive under mysql dorectory.
1) copy mysql directory to other location.
2) run ./configure
3) cp mysql/include/config.h mysql/include/my_config.h
4) compile parts of mysql on the host with the host gcc (non-cross-compile):
make -C mysql/vio
make -C mysql/mysys
make -C mysql/strings
make -C mysql/dbug
make -C mysql/regex
make -C mysql/sql gen_lex_hash
make -C mysql/scripts comp_sql
make -C mysql/extra comp_err
5) copy files:
mysql/sql/gen_lex_hash
mysql/scripts/comp_sql
mysql/extra/comp_err
to mysql/host directory
6) compress host directory as .host.tgz and copy it under tomato router/mysql/ (overwrite existing file)
7) now you should be able to compile mysql
Try other servers if first returns REFUSED when --strict-order active.
Remove ping-check of configured DHCP address.
Fix CVE-2017-13704, which resulted in a crash on a large DNS query.
Don't return arcount=1 if EDNS0 RR won't fit in the packet.
On two different SDK7 routers (R8000 & AC3200) belonging to two different people, USB drives were recognized but any filesystem on them were unable to be mounted after reboot.
So better left disabled this value as exfat is rarely used, even though SDK6 doesn't present this issue.
With commit 1374c3861abdc66f3a1410e26cc85f86760b51dd Neil added a
-test-client- export to test the exportability of filesystems when exportfs
is run. When using the old cache controls (i.e. /proc/fs/nfsd is not
mounted) exportfs will read /proc/fs/nfs/exports to process existing
exports and find these test client entries. The dash at the beginning of
-test-client- will be cause getexportent to look for default options in the
rest of the string, which test-client- will not match:
exportfs: /proc/fs/nfs/exports:1: unknown keyword "test-client-(rw"
This patch resolves that problem (as Steve suggested) by not processing any
default options if we are reading the list of existing exports from the
kernel. Default options are converted to individual exports by exportfs so
the kernel won't have any regardless.
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=56f537535190d034039570bafd9a0de71b79b8f1
pedro
AndreDVJ
kille72