深海游弋的鱼 – 第 125 页

国内如何访问维基百科(Wikipedia)

目前，维基百科已经被墙了，但是上面毕竟有很多有用的东西。目前找到比较好用的办法，就是下载zim格式的维基百科的离线文件。

首先访问开源免费软件Kiwix所在的网页，地址为: http://wiki.kiwix.org/wiki/Main_Page/zh-cn 在这个网址中下载阅读软件，也可以在本站下载Kiwix-Windows, Kiwix-Mac

其次，下载维基百科对应语言的快照，zim格式的文件，目前中文语言文件的大小是10GB左右的样子。可以直接在 http://wiki.kiwix.org/wiki/Main_Page/zh-cn 这个网站中下载，也可以访问 https://dumps.wikimedia.org/ 在这网页中选择"Kiwix files"这部分的内容去下载。注意里面包含了几乎所有的语言，只需要选择对应的语言即可。

参考链接

解决Apache Archiva下载文件超时的问题

注意： Apache Archiva 2024-02 开始已经停止维护建议使用 JFrog Artifactory 替代。

最近使用自己搭建的Apache Archiva来代理Maven仓库，经常发生失败的情况，观察Archiva的日志(logs/archiva.log)，看到如下的内容：

2016-11-22 19:52:02,773 [ajp-bio-127.0.0.1-8009-exec-74] WARN  org.apache.archiva.proxy.DefaultRepositoryProxyConnectors [] - Transfer error from repository central for artifact org.mockito:mockito-core:2.2.22::jar , continuing to next repository. Error message: Download failure on resource [https://repo.maven.apache.org/maven2/org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar]:GET request of: org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar from central failed (cause: java.net.SocketTimeoutException: Read timed out)
2016-11-22 19:52:02,773 [ajp-bio-127.0.0.1-8009-exec-74] ERROR org.apache.archiva.webdav.ArchivaDavResourceFactory [] - Failures occurred downloading from some remote repositories:
        central: Download failure on resource [https://repo.maven.apache.org/maven2/org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar]:GET request of: org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar from central failed (cause: java.net.SocketTimeoutException: Read timed out)
org.apache.archiva.policies.ProxyDownloadException: Failures occurred downloading from some remote repositories:
        central: Download failure on resource [https://repo.maven.apache.org/maven2/org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar]:GET request of: org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar from central failed (cause: java.net.SocketTimeoutException: Read timed out)
        at org.apache.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:366) ~[archiva-proxy-2.2.1.jar:?]
        at org.apache.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:820) [archiva-webdav-2.2.1.jar:?]
        at org.apache.archiva.webdav.ArchivaDavResourceFactory.processRepository(ArchivaDavResourceFactory.java:629) [archiva-webdav-2.2.1.jar:?]
        at org.apache.archiva.webdav.ArchivaDavResourceFactory.createResource(ArchivaDavResourceFactory.java:325) [archiva-webdav-2.2.1.jar:?]
        at org.apache.archiva.webdav.RepositoryServlet.service(RepositoryServlet.java:126) [archiva-webdav-2.2.1.jar:?]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) [servlet-api-3.0.jar:?]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) [tomcat-catalina-7.0.52.jar:7.0.52]
        at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:193) [tomcat-coyote-7.0.52.jar:7.0.52]
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) [tomcat-coyote-7.0.52.jar:7.0.52]
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313) [tomcat-coyote-7.0.52.jar:7.0.52]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_111]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_111]
        at java.lang.Thread.run(Thread.java:745) [?:1.7.0_111]

2016-11-22 19:52:02,773 [ajp-bio-127.0.0.1-8009-exec-74] WARN org.apache.archiva.proxy.DefaultRepositoryProxyConnectors [] - Transfer error from repository central for artifact org.mockito:mockito-core:2.2.22::jar , continuing to next repository. Error message: Download failure on resource [https://repo.maven.apache.org/maven2/org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar]:GET request of: org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar from central failed (cause: java.net.SocketTimeoutException: Read timed out)

2016-11-22 19:52:02,773 [ajp-bio-127.0.0.1-8009-exec-74] ERROR org.apache.archiva.webdav.ArchivaDavResourceFactory [] - Failures occurred downloading from some remote repositories:

central: Download failure on resource [https://repo.maven.apache.org/maven2/org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar]:GET request of: org/mockito/mockito-core/2.2.22/mockito-core-2.2.22.jar from central failed (cause: java.net.SocketTimeoutException: Read timed out)

org.apache.archiva.policies.ProxyDownloadException: Failures occurred downloading from some remote repositories:

at org.apache.archiva.proxy.DefaultRepositoryProxyConnectors.fetchFromProxies(DefaultRepositoryProxyConnectors.java:366) ~[archiva-proxy-2.2.1.jar:?]

at org.apache.archiva.webdav.ArchivaDavResourceFactory.fetchContentFromProxies(ArchivaDavResourceFactory.java:820) [archiva-webdav-2.2.1.jar:?]

at org.apache.archiva.webdav.ArchivaDavResourceFactory.processRepository(ArchivaDavResourceFactory.java:629) [archiva-webdav-2.2.1.jar:?]

at org.apache.archiva.webdav.ArchivaDavResourceFactory.createResource(ArchivaDavResourceFactory.java:325) [archiva-webdav-2.2.1.jar:?]

at org.apache.archiva.webdav.RepositoryServlet.service(RepositoryServlet.java:126) [archiva-webdav-2.2.1.jar:?]

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) [servlet-api-3.0.jar:?]

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) [tomcat-catalina-7.0.52.jar:7.0.52]

at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:193) [tomcat-coyote-7.0.52.jar:7.0.52]

at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) [tomcat-coyote-7.0.52.jar:7.0.52]

at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313) [tomcat-coyote-7.0.52.jar:7.0.52]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_111]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_111]

at java.lang.Thread.run(Thread.java:745) [?:1.7.0_111]

明显是从https://repo.maven.apache.org/maven2这个地址下载数据的时候发生了异常。这个仓库的地址是Apache Archiva中的默认仓库地址。从目前的测试来看，这个地址在国内访问，经常出现问题。对于国内用户来说https://repo1.maven.org/maven2这个中央仓库的地址是相对来说更加稳定。因此只要在Remote Repositories中增加这个中央仓库地址即可。
如下图操作：

repositorylist

add_repository

另外，在添加完成后，顺便在属性中修改一下Download Timeout，从默认的60秒修改到600秒，减少超时的发生即可。

如上操作只能部分解决问题，在现实过程中，依旧会发生失败，失败主要集中在下载https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz这个索引文件的时候，这个索引文件有300-400MB的样子，一次完整的下载基本上是都会失败，要命的是Apache Archiva在处理这个文件的时候，基本上没有进行任何容错处理。这个时候我们要么修改源代码来修正，要么需要辅助Apache Archiva完成这个文件的下载。

下面，我们实验通过Linux定时任务，nginx，aria2来实现对Apache Archiva下载的辅助处理。

1.首先安装必须的软件

$ sudo apt-get install nginx

$ sudo apt-get install aria2

$ sudo apt-get install nginx

$ sudo apt-get install aria2

2.接下来，配置nginx

$ sudo vim /etc/nginx/sites-enabled/default

1	$ sudo vim /etc/nginx/sites-enabled/default

整个配置文件的原文如下：

##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
	listen 80 default_server;
	listen [::]:80 default_server;

	# SSL configuration
	#
	# listen 443 ssl default_server;
	# listen [::]:443 ssl default_server;
	#
	# Note: You should disable gzip for SSL traffic.
	# See: https://bugs.debian.org/773332
	#
	# Read up on ssl_ciphers to ensure a secure configuration.
	# See: https://bugs.debian.org/765782
	#
	# Self signed certs generated by the ssl-cert package
	# Don't use them in a production server!
	#
	# include snippets/snakeoil.conf;

	root /var/www/html;

	# Add index.php to the list if you are using PHP
	index index.html index.htm index.nginx-debian.html;

	server_name _;

	location / {
		# First attempt to serve request as file, then
		# as directory, then fall back to displaying a 404.
		try_files $uri $uri/ =404;
	}

	# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
	#
	#location ~ \.php$ {
	#	include snippets/fastcgi-php.conf;
	#
	#	# With php7.0-cgi alone:
	#	fastcgi_pass 127.0.0.1:9000;
	#	# With php7.0-fpm:
	#	fastcgi_pass unix:/run/php/php7.0-fpm.sock;
	#}

	# deny access to .htaccess files, if Apache's document root
	# concurs with nginx's one
	#
	#location ~ /\.ht {
	#	deny all;
	#}
}


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
#	listen 80;
#	listen [::]:80;
#
#	server_name example.com;
#
#	root /var/www/example.com;
#	index index.html;
#
#	location / {
#		try_files $uri $uri/ =404;
#	}
#}

# You should look at the following URL's in order to grasp a solid understanding

# of Nginx configuration files in order to fully unleash the power of Nginx.

# http://wiki.nginx.org/Pitfalls

# http://wiki.nginx.org/QuickStart

# http://wiki.nginx.org/Configuration

# Generally, you will want to move this file somewhere, and start with a clean

# file but keep this around for reference. Or just disable in sites-enabled.

# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.

# Default server configuration

server {

listen 80 default_server;

listen [::]:80 default_server;

# SSL configuration

# listen 443 ssl default_server;

# listen [::]:443 ssl default_server;

# Note: You should disable gzip for SSL traffic.

# See: https://bugs.debian.org/773332

# Read up on ssl_ciphers to ensure a secure configuration.

# See: https://bugs.debian.org/765782

# Self signed certs generated by the ssl-cert package

# Don't use them in a production server!

# include snippets/snakeoil.conf;

root /var/www/html;

# Add index.php to the list if you are using PHP

index index.html index.htm index.nginx-debian.html;

server_name _;

location / {

# First attempt to serve request as file, then

# as directory, then fall back to displaying a 404.

try_files $uri $uri/ =404;

}

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000

#location ~ \.php$ {

# include snippets/fastcgi-php.conf;

# # With php7.0-cgi alone:

# fastcgi_pass 127.0.0.1:9000;

# # With php7.0-fpm:

# fastcgi_pass unix:/run/php/php7.0-fpm.sock;

# deny access to .htaccess files, if Apache's document root

# concurs with nginx's one

#location ~ /\.ht {

# deny all;

}

# Virtual Host configuration for example.com

# You can move that to a different file under sites-available/ and symlink that

# to sites-enabled/ to enable it.

#server {

# listen 80;

# listen [::]:80;

# server_name example.com;

# root /var/www/example.com;

# index index.html;

# location / {

# try_files $uri $uri/ =404;

# }

修改后的结果如下：

##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
	#listen 80 default_server;
	#listen [::]:80 default_server;
	listen 127.0.0.1:8090 default_server;
	# SSL configuration
	#
	# listen 443 ssl default_server;
	# listen [::]:443 ssl default_server;
	#
	# Note: You should disable gzip for SSL traffic.
	# See: https://bugs.debian.org/773332
	#
	# Read up on ssl_ciphers to ensure a secure configuration.
	# See: https://bugs.debian.org/765782
	#
	# Self signed certs generated by the ssl-cert package
	# Don't use them in a production server!
	#
	# include snippets/snakeoil.conf;

	root /data/nginx/maven_index;

	# Add index.php to the list if you are using PHP
	index index.html index.htm index.nginx-debian.html;

	server_name _;

	location / {
		# First attempt to serve request as file, then
		# as directory, then fall back to displaying a 404.
		try_files $uri $uri/ =404;
		resolver 114.114.114.114 218.85.152.99;
		resolver_timeout 30s;
		
		#nginx 不支持if嵌套也不支持多条件判断，因此只能用下面的方式来模拟
		#留意判断语句与括号之间的空格，缺失空格会导致语法错误		
		#if ( ( $host ~* "repo1\.maven\.org" ) && ( $request_uri ~* "maven2/\.index" ) ) {
		set $flag 0;
		if ( $host ~* "repo1\.maven\.org" ) {
			set $flag "${flag}1";
		}
		if ( $request_uri ~* "maven2/\.index" ) {
			set $flag "${flag}2";
		}
		if ($flag = "012") {
			proxy_pass http://127.0.0.1:8090$request_uri;
		}
		#避免循环重定向问题
 		if ( $host != "127.0.0.1" ) {
			proxy_pass http://$host$request_uri;
		}		
	}

	# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
	#
	#location ~ \.php$ {
	#	include snippets/fastcgi-php.conf;
	#
	#	# With php7.0-cgi alone:
	#	fastcgi_pass 127.0.0.1:9000;
	#	# With php7.0-fpm:
	#	fastcgi_pass unix:/run/php/php7.0-fpm.sock;
	#}

	# deny access to .htaccess files, if Apache's document root
	# concurs with nginx's one
	#
	#location ~ /\.ht {
	#	deny all;
	#}
}


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
#	listen 80;
#	listen [::]:80;
#
#	server_name example.com;
#
#	root /var/www/example.com;
#	index index.html;
#
#	location / {
#		try_files $uri $uri/ =404;
#	}
#}

100

101

102

103

104

105

106

# You should look at the following URL's in order to grasp a solid understanding

# of Nginx configuration files in order to fully unleash the power of Nginx.

# http://wiki.nginx.org/Pitfalls

# http://wiki.nginx.org/QuickStart

# http://wiki.nginx.org/Configuration

# Generally, you will want to move this file somewhere, and start with a clean

# file but keep this around for reference. Or just disable in sites-enabled.

# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.

# Default server configuration

server {

#listen 80 default_server;

#listen [::]:80 default_server;

listen 127.0.0.1:8090 default_server;

# SSL configuration

# listen 443 ssl default_server;

# listen [::]:443 ssl default_server;

# Note: You should disable gzip for SSL traffic.

# See: https://bugs.debian.org/773332

# Read up on ssl_ciphers to ensure a secure configuration.

# See: https://bugs.debian.org/765782

# Self signed certs generated by the ssl-cert package

# Don't use them in a production server!

# include snippets/snakeoil.conf;

root /data/nginx/maven_index;

# Add index.php to the list if you are using PHP

index index.html index.htm index.nginx-debian.html;

server_name _;

location / {

# First attempt to serve request as file, then

# as directory, then fall back to displaying a 404.

try_files $uri $uri/ =404;

resolver 114.114.114.114 218.85.152.99;

resolver_timeout 30s;

#nginx 不支持if嵌套也不支持多条件判断，因此只能用下面的方式来模拟

#留意判断语句与括号之间的空格，缺失空格会导致语法错误

#if ( ( $host ~* "repo1\.maven\.org" ) && ( $request_uri ~* "maven2/\.index" ) ) {

set $flag 0;

if ( $host ~* "repo1\.maven\.org" ) {

set $flag "${flag}1";

}

if ( $request_uri ~* "maven2/\.index" ) {

set $flag "${flag}2";

}

if ($flag = "012") {

proxy_pass http://127.0.0.1:8090$request_uri;

}

#避免循环重定向问题

if ( $host != "127.0.0.1" ) {

proxy_pass http://$host$request_uri;

}

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000

#location ~ \.php$ {

# include snippets/fastcgi-php.conf;

# # With php7.0-cgi alone:

# fastcgi_pass 127.0.0.1:9000;

# # With php7.0-fpm:

# fastcgi_pass unix:/run/php/php7.0-fpm.sock;

# deny access to .htaccess files, if Apache's document root

# concurs with nginx's one

#location ~ /\.ht {

# deny all;

}

# Virtual Host configuration for example.com

# You can move that to a different file under sites-available/ and symlink that

# to sites-enabled/ to enable it.

#server {

# listen 80;

# listen [::]:80;

# server_name example.com;

# root /var/www/example.com;

# index index.html;

# location / {

# try_files $uri $uri/ =404;

# }

接下来，重启nginx服务。

3.设置定时任务，定时检查远端服务器上的数据是否有更新

任务脚本内容如下：

nginx_dir="/data/nginx"
mvn_idx_dir="$nginx_dir/maven2/.index"
mvn_idx_dl_dir="$nginx_dir/maven2/.CacheIndex"
mvn_idx_name="nexus-maven-repository-index"
mvn_idx_path_name="$mvn_idx_dir/$mvn_idx_name"
mvn_idx_gz_name="$mvn_idx_dir/$mvn_idx_name.gz"
mvn_idx_prop_name="$mvn_idx_dir/$mvn_idx_name.properties"
mvn_idx_dl_gz_name="$mvn_idx_dl_dir/$mvn_idx_name.gz"
mvn_idx_dl_prop_name="$mvn_idx_dl_dir/$mvn_idx_name.properties"
log_file="/data/nginx/maven_index_log.txt"
dt_fmt="`date "+%Y-%m-%d %H:%M:%S"`"



if [ ! -d $mvn_idx_dl_dir ]; then
	mkdir -p $mvn_idx_dl_dir
fi

if [ ! -d $mvn_idx_dir ]; then
	mkdir -p $mvn_idx_dir
fi

if [ ! -d $mvn_idx_dl_dir ]; then
	echo "$dt_fmt	mkdir $mvn_idx_dl_dir failed !" >> $log_file
	exit -1 
fi

if [ ! -d $mvn_idx_dir ]; then
	echo "$dt_fmt	mkdir $mvn_idx_dir failed !" >> $log_file
	exit -1 
fi

cd $mvn_idx_dl_dir

dl_idx="true"
dl_prop="true"

#echo mvn_idx_gz_name="$mvn_idx_gz_name"
#先检查是不是需要下载文件，然后再下载文件，减少不必要的网络请求数据
if [ -f "$mvn_idx_gz_name" ]; then
	remote_idx_md5=$(curl -s https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz.md5)
	 
	if [ "${#remote_idx_md5}" != "32" ] ; then
		echo "$dt_fmt	download $mvn_idx_gz_name.md5 failed !" >> $log_file
		exit -1
	fi
	local_idx_md5=$(md5sum $mvn_idx_gz_name | cut -b 1-32)
	
	#echo remote_idx_md5="$remote_idx_md5" local_idx_md5="$local_idx_md5"
	if [ "$remote_idx_md5" = "$local_idx_md5" ] ; then
		dl_idx="false"
		if [ -f "$mvn_idx_prop_name" ]; then
			remote_prop_md5=$(curl -s https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.properties.md5)
			if [ "${#remote_prop_md5}" != "32" ] ; then
				echo "$dt_fmt	download $mvn_idx_prop_name failed !" >> $log_file
				exit -1
			fi
			local_prop_md5=$(md5sum $mvn_idx_prop_name | cut -b 1-32)
			if [ "$remote_prop_md5" = "$local_prop_md5" ] ; then
				dl_prop="false"
				echo "$dt_fmt	check file success ,no need to update !" >> $log_file
				exit 0
			fi
		fi
	fi
fi

if [ "$dl_idx" = "true" ] ; then
	aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz
	aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz.md5
	aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz.sha1
fi

if [ "$dl_prop" = "true" ] ; then
	aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.properties
	aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.properties.md5
	aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.properties.sha1
fi

#校验下载到的文件
if [ "$dl_idx" = "true" ] ; then
	dl_idx_md5=$(md5sum $mvn_idx_dl_gz_name | cut -b 1-32)
	dl_idx_f_md5=$(cat $mvn_idx_dl_gz_name.md5)
	if [ "$dl_idx_md5" = "$dl_idx_f_md5" ] ; then
		rm -rf $mvn_idx_gz_name
		mv $mvn_idx_dl_gz_name $mvn_idx_gz_name
		rm -rf $mvn_idx_gz_name.md5 
		mv $mvn_idx_dl_gz_name.md5 $mvn_idx_gz_name.md5
		rm -rf $mvn_idx_gz_name.sha1
		mv $mvn_idx_dl_gz_name.sha1 $mvn_idx_gz_name.sha1
	else
		echo "$dt_fmt	check downloaded index file failed !" >> $log_file
		cd  $nginx_dir
		rm -rf $mvn_idx_dl_dir
	fi
fi

if [ "$dl_prop" = "true" ] ; then
	dl_prop_md5=$(md5sum $mvn_idx_dl_prop_name | cut -b 1-32)
	dl_prop_f_md5=$(cat $mvn_idx_dl_prop_name.md5)
	if [ "$dl_prop_md5" = "$dl_prop_f_md5" ] ; then
		rm -rf $mvn_idx_prop_name
		mv $mvn_idx_dl_prop_name $mvn_idx_prop_name
		rm -rf $mvn_idx_prop_name.md5 
		mv $mvn_idx_dl_prop_name.md5 $mvn_idx_prop_name.md5
		rm -rf $mvn_idx_prop_name.sha1
		mv $mvn_idx_dl_prop_name.sha1 $mvn_idx_prop_name.sha1
	else
		echo "$dt_fmt	check downloaded properties file failed !" >> $log_file
		cd  $nginx_dir
		rm -rf $mvn_idx_dl_dir
	fi
fi

100

101

102

103

104

105

106

107

108

109

110

111

112

113

nginx_dir="/data/nginx"

mvn_idx_dir="$nginx_dir/maven2/.index"

mvn_idx_dl_dir="$nginx_dir/maven2/.CacheIndex"

mvn_idx_name="nexus-maven-repository-index"

mvn_idx_path_name="$mvn_idx_dir/$mvn_idx_name"

mvn_idx_gz_name="$mvn_idx_dir/$mvn_idx_name.gz"

mvn_idx_prop_name="$mvn_idx_dir/$mvn_idx_name.properties"

mvn_idx_dl_gz_name="$mvn_idx_dl_dir/$mvn_idx_name.gz"

mvn_idx_dl_prop_name="$mvn_idx_dl_dir/$mvn_idx_name.properties"

log_file="/data/nginx/maven_index_log.txt"

dt_fmt="`date "+%Y-%m-%d %H:%M:%S"`"

if [ ! -d $mvn_idx_dl_dir ]; then

mkdir -p $mvn_idx_dl_dir

if [ ! -d $mvn_idx_dir ]; then

mkdir -p $mvn_idx_dir

if [ ! -d $mvn_idx_dl_dir ]; then

echo "$dt_fmt mkdir $mvn_idx_dl_dir failed !" >> $log_file

exit -1

if [ ! -d $mvn_idx_dir ]; then

echo "$dt_fmt mkdir $mvn_idx_dir failed !" >> $log_file

exit -1

cd $mvn_idx_dl_dir

dl_idx="true"

dl_prop="true"

#echo mvn_idx_gz_name="$mvn_idx_gz_name"

#先检查是不是需要下载文件，然后再下载文件，减少不必要的网络请求数据

if [ -f "$mvn_idx_gz_name" ]; then

remote_idx_md5=$(curl -s https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz.md5)

if [ "${#remote_idx_md5}" != "32" ] ; then

echo "$dt_fmt download $mvn_idx_gz_name.md5 failed !" >> $log_file

exit -1

local_idx_md5=$(md5sum $mvn_idx_gz_name | cut -b 1-32)

#echo remote_idx_md5="$remote_idx_md5" local_idx_md5="$local_idx_md5"

if [ "$remote_idx_md5" = "$local_idx_md5" ] ; then

dl_idx="false"

if [ -f "$mvn_idx_prop_name" ]; then

remote_prop_md5=$(curl -s https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.properties.md5)

if [ "${#remote_prop_md5}" != "32" ] ; then

echo "$dt_fmt download $mvn_idx_prop_name failed !" >> $log_file

exit -1

local_prop_md5=$(md5sum $mvn_idx_prop_name | cut -b 1-32)

if [ "$remote_prop_md5" = "$local_prop_md5" ] ; then

dl_prop="false"

echo "$dt_fmt check file success ,no need to update !" >> $log_file

exit 0

if [ "$dl_idx" = "true" ] ; then

aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz

aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz.md5

aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz.sha1

if [ "$dl_prop" = "true" ] ; then

aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.properties

aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.properties.md5

aria2c -c https://repo1.maven.org/maven2/.index/nexus-maven-repository-index.properties.sha1

#校验下载到的文件

if [ "$dl_idx" = "true" ] ; then

dl_idx_md5=$(md5sum $mvn_idx_dl_gz_name | cut -b 1-32)

dl_idx_f_md5=$(cat $mvn_idx_dl_gz_name.md5)

if [ "$dl_idx_md5" = "$dl_idx_f_md5" ] ; then

rm -rf $mvn_idx_gz_name

mv $mvn_idx_dl_gz_name $mvn_idx_gz_name

rm -rf $mvn_idx_gz_name.md5

mv $mvn_idx_dl_gz_name.md5 $mvn_idx_gz_name.md5

rm -rf $mvn_idx_gz_name.sha1

mv $mvn_idx_dl_gz_name.sha1 $mvn_idx_gz_name.sha1

else

echo "$dt_fmt check downloaded index file failed !" >> $log_file

cd $nginx_dir

rm -rf $mvn_idx_dl_dir

if [ "$dl_prop" = "true" ] ; then

dl_prop_md5=$(md5sum $mvn_idx_dl_prop_name | cut -b 1-32)

dl_prop_f_md5=$(cat $mvn_idx_dl_prop_name.md5)

if [ "$dl_prop_md5" = "$dl_prop_f_md5" ] ; then

rm -rf $mvn_idx_prop_name

mv $mvn_idx_dl_prop_name $mvn_idx_prop_name

rm -rf $mvn_idx_prop_name.md5

mv $mvn_idx_dl_prop_name.md5 $mvn_idx_prop_name.md5

rm -rf $mvn_idx_prop_name.sha1

mv $mvn_idx_dl_prop_name.sha1 $mvn_idx_prop_name.sha1

else

echo "$dt_fmt check downloaded properties file failed !" >> $log_file

cd $nginx_dir

rm -rf $mvn_idx_dl_dir

默认我们把脚本执行路径为/data/nginx/mvn_index_corn.sh。

设置定时任务的脚本如下：

chmod +x /data/nginx/mvn_index_corn.sh
#write out current crontab
crontab -l > addcron
#echo new cron into cron file ,每隔30分钟我们调度一次任务,前面是文件锁，防止并发冲突
echo "30 * * * * flock -x -w 10 /dev/shm/mvn_index_corn.lock -c \"sh /data/nginx/mvn_index_corn.sh\"" >> addcron
#install new cron file
crontab addcron
rm addcron

chmod +x /data/nginx/mvn_index_corn.sh

#write out current crontab

crontab -l > addcron

#echo new cron into cron file ,每隔30分钟我们调度一次任务,前面是文件锁，防止并发冲突

echo "30 * * * * flock -x -w 10 /dev/shm/mvn_index_corn.lock -c \"sh /data/nginx/mvn_index_corn.sh\"" >> addcron

#install new cron file

crontab addcron

rm addcron

执行上面的脚本。

4.设置Apache Archiva的代理服务器配置

Linux下查看指定目录的大小

此处以名为"Archiva"的目录为例：

$ du -h --max-depth=0 Archiva

1	$ du -h --max-depth=0 Archiva

或者(优先推荐此命令，速度快）

$ du -sh Archiva

1	$ du -sh Archiva

参考链接

Linux中查看各文件夹大小命令du -h --max-depth=1

Spring Junit 读取WEB-INF下的配置文件

假设spring配置文件为applicationContext.xml

一.Spring配置文件在类路径下面

在Spring的Java应用程序中，一般我们的Spring的配置文件都是放在放在类路径下面(也即编译后会进入到classes目录下)。

以下是我的项目，因为是用maven管理的，所以配置文件都放在"src/main/resources"目录下,这时候，在代码中可以通过

ApplicationContext applicationContext = new ClassPathXmlApplicationContext("applicationContext.xml");

1	ApplicationContext applicationContext = new ClassPathXmlApplicationContext("applicationContext.xml");

然后获取相应的bean。

如果代码想用Junit测试框架来测试，则Spring提供了对Junit支持，还可以使用注解的方式：

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations={"classpath:applicationContext.xml"})

1 2	@RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations={"classpath:applicationContext.xml"})

只需要在相应的Test类前面加上此两个注解（第二个注解用来指明Spring的配置文件位置），就可以在Junit Test类使用中Spring提供的依赖注入功能。

二.Spring配置文件在WEB-INF下面

当然在做J2EE开发时，有些人习惯把Spring文件放在WEB-INF目录（虽然更多人习惯放在类路径下面）下面,或者有些Spring配置文件是放在类路径下面，而有些又放在WEB-INF目录下面，如下图:

1336538723_9420

这时候，在代码中就不可以使用ClassPathXmlApplicationContext来加载配置文件了，而应使用FileSystemXmlApplicationContext。

ApplicationContext applicationContext = new FileSystemXmlApplicationContext("src/main/webapp/WEB-INF/applicationContext.xml");

1	ApplicationContext applicationContext = new FileSystemXmlApplicationContext("src/main/webapp/WEB-INF/applicationContext.xml");

然后获取相应的bean。

如果代码想用Junit测试框架来测试，则Spring提供了对Junit支持，还可以使用注解的方式：

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations={"file:src/main/webapp/WEB-INF/applicationContext.xml"})

1 2	@RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations={"file:src/main/webapp/WEB-INF/applicationContext.xml"})

只需要在相应的Test类前面加上此两个注解（第二个注解用来指明Spring的配置文件位置），就可以在Junit Test类使用中Spring提供的依赖注入功能。

下面是我的一个Spring管理下的Junit测试类：

import java.util.List;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration({"file:src/main/webapp/WEB-INF/applicationContext.xml"})
public class SuFriendServiceImplOverRMITest {

	@Autowired
	private SuFriendService suFriendService;

	@Test
	public void getUserFollowerListTest(){
		List list = suFriendService.getUserFollowerList("liug_talk@163.com");
		System.out.println("------"+list);
	}
}

import java.util.List;

import org.junit.Test;

import org.junit.runner.RunWith;

import org.springframework.beans.factory.annotation.Autowired;

import org.springframework.test.context.ContextConfiguration;

import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;

@RunWith(SpringJUnit4ClassRunner.class)

@ContextConfiguration({"file:src/main/webapp/WEB-INF/applicationContext.xml"})

public class SuFriendServiceImplOverRMITest {

@Autowired

private SuFriendService suFriendService;

@Test

public void getUserFollowerListTest(){

List list = suFriendService.getUserFollowerList("liug_talk@163.com");

System.out.println("------"+list);

}

参考链接

Spring Junit 读取WEB-INF下的配置文件

HTML5文件实现拖拽上传

通过HTML的文件API ，Firefox、Chrome等浏览器已经支持从操作系统直接拖拽文件，并上传到服务器。

相对于使用了十多年的HTML表单，这是一个革命性的进步。虽然IE的落后让很多开发者还在观望中，但是Gmail邮箱的附件拖拽功能已经给部分用户带来了极大的方便，而需要大量上传文件的CMS（内容管理系统）也将会从中受益。

让我们看一下Firefox 是如何使用拖拽上传功能的：

首先提供一个区域来放置文件

Html代码

<div name="image" id="dropbox" style="min-width:300px;min-height:100px;border:3px dashed silver;"></div>

1	<div name="image" id="dropbox" style="min-width:300px;min-height:100px;border:3px dashed silver;"></div>

然后监听拖拽过程中的dragenter,dragleave,drop等事件

Js代码

document.addEventListener("dragenter", function(e){  
    dropbox.style.borderColor = 'gray';  
}, false);  
document.addEventListener("dragleave", function(e){  
    dropbox.style.borderColor = 'silver';  
}, false);  
dropbox.addEventListener("dragenter", function(e){  
    dropbox.style.borderColor = 'gray';  
    dropbox.style.backgroundColor = 'white';  
}, false);  
dropbox.addEventListener("dragleave", function(e){  
    dropbox.style.backgroundColor = 'transparent';  
}, false);  
dropbox.addEventListener("dragenter", function(e){  
    e.stopPropagation();  
    e.preventDefault();  
}, false);  
dropbox.addEventListener("dragover", function(e){  
    e.stopPropagation();  
    e.preventDefault();  
}, false);  
dropbox.addEventListener("drop", function(e){  
    e.stopPropagation();  
    e.preventDefault();  
       
    handleFiles(e.dataTransfer.files);  
       
    submit.disabled = false;  
}, false);

document.addEventListener("dragenter", function(e){

dropbox.style.borderColor = 'gray';

}, false);

document.addEventListener("dragleave", function(e){

dropbox.style.borderColor = 'silver';

}, false);

dropbox.addEventListener("dragenter", function(e){

dropbox.style.borderColor = 'gray';

dropbox.style.backgroundColor = 'white';

}, false);

dropbox.addEventListener("dragleave", function(e){

dropbox.style.backgroundColor = 'transparent';

}, false);

dropbox.addEventListener("dragenter", function(e){

e.stopPropagation();

e.preventDefault();

}, false);

dropbox.addEventListener("dragover", function(e){

e.stopPropagation();

e.preventDefault();

}, false);

dropbox.addEventListener("drop", function(e){

e.stopPropagation();

e.preventDefault();

handleFiles(e.dataTransfer.files);

submit.disabled = false;

}, false);

其中最主要的是drop事件中用handleFiles()依次处理所有文件

handleFiles = function(files) {  
    for (var i = 0; i < files.length; i++) {  
        var file = files[i];  
   
    }  
}

handleFiles = function(files) {

for (var i = 0; i < files.length; i++) {

var file = files[i];

}

对于图片类型的文件可以直接读取内容，显示预览图

if (!file.type.match(/image*/)) {  
    continue;  
}  
   
var img = document.createElement("img");  
img.classList.add("obj");  
img.file = file;  
preview.appendChild(img);  
   
var reader = new FileReader();  
reader.onload = (function(aImg) { return function(e) { aImg.src = e.target.result; }; })(img);  
reader.readAsDataURL(file);

if (!file.type.match(/image*/)) {

continue;

}

var img = document.createElement("img");

img.classList.add("obj");

img.file = file;

preview.appendChild(img);

var reader = new FileReader();

reader.onload = (function(aImg) { return function(e) { aImg.src = e.target.result; }; })(img);

reader.readAsDataURL(file);

接下来就是核心功能：ajax上传。首先新建一个XHR请求

var xhr = new XMLHttpRequest();  
xhr.open('post', '/file/upload', true);

1 2	var xhr = new XMLHttpRequest(); xhr.open('post', '/file/upload', true);

监听上传进度和完成事件

xhr.upload.addEventListener("progress", function(e) {  
    if (e.lengthComputable) {  
        var percentage = Math.round((e.loaded * 100) / e.total);  
        img.style.opacity = 1-percentage/100.0;  
    }  
}, false);  
   
xhr.upload.addEventListener("load", function(e){  
       
}, false);

xhr.upload.addEventListener("progress", function(e) {

if (e.lengthComputable) {

var percentage = Math.round((e.loaded * 100) / e.total);

img.style.opacity = 1-percentage/100.0;

}

}, false);

xhr.upload.addEventListener("load", function(e){

}, false);

最后把数据模拟成multipart/form-data的格式上传

xhr.setRequestHeader("Content-Type", "multipart/form-data, boundary="+boundary); // simulate a file MIME POST request.  
xhr.setRequestHeader("Content-Length", fileSize);  
   
var body = '';  
body += "--" + boundary + "\r\n";  
body += "Content-Disposition: form-data; name=\""+dropbox.getAttribute('name')+"\"; filename=\"" + fileName + "\"\r\n";  
body += "Content-Type: "+fileType+"\r\n\r\n";  
body += fileData + "\r\n";  
body += "--" + boundary + "--\r\n";  
   
xhr.sendAsBinary(body);

xhr.setRequestHeader("Content-Type", "multipart/form-data, boundary="+boundary); // simulate a file MIME POST request.

xhr.setRequestHeader("Content-Length", fileSize);

var body = '';

body += "--" + boundary + "\r\n";

body += "Content-Disposition: form-data; name=\""+dropbox.getAttribute('name')+"\"; filename=\"" + fileName + "\"\r\n";

body += "Content-Type: "+fileType+"\r\n\r\n";

body += fileData + "\r\n";

body += "--" + boundary + "--\r\n";

xhr.sendAsBinary(body);

参考链接

HTML5文件实现拖拽上传

Linux ls列出目录下所有文件数量

1.查看统计当前目录下文件的个数

$ ls -l | grep "^-" | wc -l

1	$ ls -l \| grep "^-" \| wc -l

2.查看统计当前目录下文件的个数，包括子目录里的。

$ ls -lR| grep "^-" | wc -l

1	$ ls -lR\| grep "^-" \| wc -l

3.查看某目录下文件夹(目录)的个数，包括子目录里的。

$ ls -lR| grep "^d" | wc -l

1	$ ls -lR\| grep "^d" \| wc -l

参考链接

linux ls列出目录下所有文件数量

WDMyCloud编译USB网卡MT7601U驱动（小米,小度，360WiFi)

前言

有人留言希望尝试在WDMyCloud上尝试使用USB无线网卡，目标芯片是MT7601U。

经过几天的研究，找到了相关的编译方式。

链接地址 https://github.com/porjo/mt7601u，提示在Linux-4.2以后的版本中已经集成MT7601U芯片的驱动了(drivers/net/wireless/mediatek目录下)，但是可惜的是WDMyCloud上的Linux内核版本号是3.2.26，曾经尝试升级到4.2版本之后的Linux内核，可惜尝试之后，发现无法成功编译Mindspeed C2000芯片(WDMyCloud使用的IC芯片,包含CPU,网卡等)驱动，因此只能退而求其次，使用MTK官方提供的驱动程序在3.2.26版本的Linux内核上进行编译。

另外注意，在WDMyCloud提供的默认系统镜像上，没有提供802.11相关的驱动，导致如果使用无线网卡，必须重新编译内核。

具体操作

1.下载MT7601U芯片驱动

驱动程序的下载地址为：http://www.mediatek.com/products/broadbandWifi/mt7601u#product-downloads

也可本站下载

2.下载最新的WDMyCloud的系统源代码

目前最新的下载地址为：http://downloads.wdc.com/gpl/gpl-source-wd_my_cloud-04.04.03-113.zip

3.参照 How to successfully build packages for WD My Cloud from source构建编译环境

4.解压缩下载到的代码中的"packages/kernel_3.2"到"64k-wheezy/build/root"目录下面。

5.执行如下命令,重新编译内核，为驱动的编译准备必备的文件

$ cd ~

$ cd 64k-wheezy

$ sudo chroot build

$ cd root

$ cd kernel_3.2

$ apt-get install uboot-mkimage

$ cd ~

$ cd 64k-wheezy

$ sudo chroot build

$ cd root

$ cd kernel_3.2

$ apt-get install uboot-mkimage

修改内核编译文件"/kernel_3.2/linux/arch/arm/configs/sequoia64k-wifi_defconfig",在文件的顶部增加"CONFIG_WEXT_PRIV=y",定义这个宏的目的，是为了编译MT7601U芯片驱动的时候使用的，缺少这个宏会导致芯片驱动编译的时候缺少变量。

6.编译内核

$ make sequoia64k-wifi

1	$ make sequoia64k-wifi

编译成功后，在"kernel_3.2/_bld"目录下生成编译文件，在"kernel_3.2/_bin"目录下生成最终的内核镜像和驱动程序。

7.解压缩MT7601U芯片驱动代码到"64k-wheezy/build/root"目录下面，并命名为"MT7601U"。

修改芯片驱动编译文件"Makefile"，找到

ifeq ($(PLATFORM),IXP)
LINUX_SRC = /project/stable/Gmtek/snapgear-uclibc/linux-2.6.x
CROSS_COMPILE = arm-linux-
endif

ifeq ($(PLATFORM),IXP)

LINUX_SRC = /project/stable/Gmtek/snapgear-uclibc/linux-2.6.x

CROSS_COMPILE = arm-linux-

endif

在这行下面增加

ifeq ($(PLATFORM),WDMyCloud)
# Linux 2.6
LINUX_SRC = /root/kernel_3.2/_bld
# Linux 2.4 Change to your local setting
#LINUX_SRC = /usr/src/linux-2.4
LINUX_SRC_MODULE = /root/kernel_3.2/kernel/linux/drivers/net/wireless/
CROSS_COMPILE = arm-linux-gnueabihf-
#export ARCH=arm 
endif

ifeq ($(PLATFORM),WDMyCloud)

# Linux 2.6

LINUX_SRC = /root/kernel_3.2/_bld

# Linux 2.4 Change to your local setting

#LINUX_SRC = /usr/src/linux-2.4

LINUX_SRC_MODULE = /root/kernel_3.2/kernel/linux/drivers/net/wireless/

CROSS_COMPILE = arm-linux-gnueabihf-

#export ARCH=arm

endif

修改"Makefile"中，编译目标系统从PLATFORM = PC为PLATFORM = WDMyCloud.

接下来修改"os/linux/config.mk",在文件尾部增加

ifeq ($(PLATFORM),WDMyCloud)
EXTRA_CFLAGS := -D__KERNEL__ -I$(LINUX_SRC)/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -Uarm -fno-common -pipe -march=armv6 -msoft-float -Uarm -DMODULE -DMODVERSIONS -include $(LINUX_SRC)/include/linux/version.h $(WFLAGS)

export EXTRA_CFLAGS
endif

ifeq ($(PLATFORM),WDMyCloud)

EXTRA_CFLAGS := -D__KERNEL__ -I$(LINUX_SRC)/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -Uarm -fno-common -pipe -march=armv6 -msoft-float -Uarm -DMODULE -DMODVERSIONS -include $(LINUX_SRC)/include/linux/version.h $(WFLAGS)

export EXTRA_CFLAGS

endif

最后，切换到驱动程序所在的"MT7601U"目录，执行编译。

$ make

$ make

编译完成后，在"MT7601U/os/linux/"目录下生成名为"mt7601Usta.ko"的驱动程序文件。

剩下的，参考"MT7601U"目录下的"README_STA_usb"中的说明进行操作即可。

注意，如果要成功使用无线网卡驱动，那么需要用刚刚编译好的Linux内核，替换掉原来的内核，并且把"kernel_3.2/_bin"目录下的驱动也拷贝到系统根目录下面相同的位置即可，这个操作是高风险操作，极可能这么操作之后，系统无法正常运行，因此要提前备份文件，并且做好拆硬盘，挂载到其他机器上撤销刚刚的修改的准备。

参考链接

mt7601驱动使用（三）

IPFire内核升级(Core Update)

IPFire内核有新版本的时候，会在页面的首页底部提示，如下图：

点击链接后，跳转到升级页面，点击升级按钮即可，如下图：

但是有时候会出现问题，点击升级是无效的，如下图：

这个时候需要通过远程控制台进行操作了,执行如下命令：

$ pakfire update --force

$ pakfire upgrade

# pakfire 访问的服务器地址为 pakfire.ipfire.org 最近这个地址的访问不是非常稳定
# 如果发生失败，观察日志 cat /var/log/messages

$ pakfire update --force

$ pakfire upgrade

# pakfire 访问的服务器地址为 pakfire.ipfire.org 最近这个地址的访问不是非常稳定

# 如果发生失败，观察日志 cat /var/log/messages

如果发生错误的时候 http://pakfire.ipfire.org/2.21-x86_64/lists/server-list.db 这个地址没办法访问，那么试试 https://pakfire.ipfire.org/2.21-x86_64/lists/server-list.db 看看是不是能正常访问。

如果 HTTPS 可以正常访问，那么需要手工修改一下系统的代码，如下：

$ sudo vim /opt/pakfire/lib/functions.pl

1	$ sudo vim /opt/pakfire/lib/functions.pl

搜索找到如下内容：

$proto = "HTTP" unless $proto;

1	$proto = "HTTP" unless $proto;

替换为:

$proto = "HTTPS" unless $proto;

1	$proto = "HTTPS" unless $proto;

这个属于客户端代码没有正确适配，同时服务器上的修改没有进行兼容导致的。

参考链接

How to upgrade to Core Update 62?

如何安装树莓派摄像头模块

树莓派摄像头模块(Pi Cam)发售于2013年5月。其第一个发布版本配备了500万像素的传感器，通过排线链接树莓派上的CSI接口。而Pi Cam的第二个发布版本——也被叫做Pi NoIR中，配备了相同的传感器，但没有红外线过滤装置。因此第二版的摄像头模块就像安全监控摄像机一样，可以观测到近红外线的波长(700 - 1000 nm)，不过当然同时也就牺牲了一定的显色性。

本文将会展示如何在树莓派上安装摄像头模块。我们将使用第一版摄像头模块来演示。在安装完摄像头模块之后，你将会使用三个应用程序来访问这个模块：raspistill, raspiyuv 和raspivid。其中前两个应用用来捕捉图像，第三个应用来捕捉视频。raspistill 工具生成标准的图片文件，例如 .jpg 图像，而 raspiyuv 可以通过摄像头生成未处理的 raw 图像文件。

安装树莓派摄像头模块

按照以下步骤来将树莓派摄像头模块连接搭配树莓派：

找到 CSI 接口(CSI接口在以太网接口旁边)，掀起深色胶带。
拉起 CSI 接口挡板。
拿起你的摄像头模块，将贴在镜头上的塑料保护膜撕掉。确保黄色部分的PCB(有字的一面)是安装完美的（可以轻轻按一下黄色的部分来保证安装完美）。
将排线插入CSI接口。记住，有蓝色胶带的一面应该面向以太网接口方向。同样，这时也确认一下排线安装好了之后，将挡板拉下。

130426pxvuxrqtnpppxx17

好了，现在你的 Pi Cam 已经准备就绪，可以拍摄照片或视频了。

在树莓派上启用摄像头模块

在安装完摄像头模块之后，首先要确认你已经升级了树莓派系统并应用了最新的固件。可以输入以下命令来操作：

$ sudo apt-get update
$ sudo apt-get upgrade

1 2	$ sudo apt-get update $ sudo apt-get upgrade

运行树莓派配置工具来激活摄像头模块：

$ sudo raspi-config

1	$ sudo raspi-config

移动光标至菜单中的 "Enable Camera（启用摄像头）"，将其设为Enable（启用状态）。完成之后重启树莓派。

130440dguwh6gwk1vk9jgv

130442rn19igalrfo1rmg5

130443uq0hldn4sfvc0nhs

安装完摄像头模块后的完成照：

130454br44z4dnp2c3zcyr

通过摄像头模块拍照

在重启完树莓派后，我们就可以使用Pi Cam了。要用它来拍摄照片的话，可以从命令行运行raspistill：

$ raspistill -o keychain.jpg -t 2000

1	$ raspistill -o keychain.jpg -t 2000

这句命令将在 2000ms 后拍摄一张照片，然后保存为 keychain.jpg。下面就是一张由 Pi Cam 拍摄的我的小熊公仔钥匙链。

130456h516ypyamyo5mst6

raspiyuv 工具用法差不多，只不过拍摄得到的是一张未处理过的raw图像。

通过摄像头模块拍视频

想要用摄像头模块拍一段视频的话，可以从命令行运行 raspivid 工具。下面这句命令会按照默认配置(长度5秒，分辨率1920x1080，比特率 17Mbps)拍摄一段视频。

$ raspivid -o mykeychain.h264

1	$ raspivid -o mykeychain.h264

如果你想改变拍摄时长，只要通过 "-t" 选项来设置你想要的长度就行了（单位是毫秒）。

$ raspivid -o mykeychain.h264 -t 10000

1	$ raspivid -o mykeychain.h264 -t 10000

使用 "-w" 和 "-h" 选项将分辨率降为 1280x720...

$ raspivid -o mykeychain.h264 -t 10000 -w 1280 -h 720

1	$ raspivid -o mykeychain.h264 -t 10000 -w 1280 -h 720

raspivid 的输出是一段未压缩的 H.264 视频流，而且这段视频不含声音。为了能被通常的视频播放器所播放，这个 raw 的 H.264 视频还需要转换。可以使用 gpac 包中所带有的 MP4Box 应用。

在 Raspbian 上安装 gpac，输入命令：

$ sudo apt-get install -y gpac

1	$ sudo apt-get install -y gpac

然后将这段 raw 的 H.264 格式的视频流转换为每秒30帧的 .mp4 格式视频：

$ MP4Box -fps 30 -add keychain.h264 keychain.mp4

1	$ MP4Box -fps 30 -add keychain.h264 keychain.mp4

视频长度为10秒，使用默认分辨率以及比特率。

如果想要获取 raspistill, raspiyuv 和 raspivid 的完整命令行选项，不加任何选项直接运行以上命令即可。

参考链接

如何安装树莓派摄像头模块

Android Studio 2.2 启用代码混淆

在新版本的Android Studio中开启混淆的方法如下：

buildTypes {
        release {
            minifyEnabled true //是否混淆
            shrinkResources true //是否去除无效的资源文件
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }

buildTypes {

release {

minifyEnabled true //是否混淆

shrinkResources true //是否去除无效的资源文件

proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'

}

具体解释一下minifyEnabled用来影响是不是开启混淆，shrinkResources只有在minifyEnabled为true的情况下，才能有效，用来去除无效的资源文件。proguard-android-optimize.txt是Android SDK->tools\proguard目录下，Google已经写好默认的混淆模板文件，其中的proguard-android.txt默认没有配置代码优化，而proguard-android-optimize.txt默认配置了代码优化，至于我们自己工程下面的proguard-rules.pro文件，只要配置我们自定义的额外配置即可，其他的用默认配置即可。

顺便讲一下代码混淆的好处：

1.代码安全，不易理解，增加破解难度。

2.减小APK的体积，减少内存开销。

3.缩减类名，方法名的长度，减少CPU开销。

2025 年 10 月
一	二	三	四	五	六	日
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31