深海游弋的鱼 – 第 51 页 – 智障儿童欢乐多

AX88179 USB网卡无法在macOS Big Sur(11.0.1)系统上正常使用

Background
Last year, we wrote that older macOS drivers, known as System Extensions (KEXTs), would begin to be deprecated as of the macOS 10.15 Catalina release. This week, as macOS 11 Big Sur is released, KEXTs have officially been deprecated and are no longer functional.

Instead, Apple is now enforcing the requirement for devices that require third-party drivers to operate as DriverKit Extensions (DEXTs). This change affects many products across the consumer electronics industry, including Docking Stations, USB peripherals, Security/Anti-Virus software, and Networking adapters.

Luckily, most platform vendors and integrated circuit (IC) manufacturers have been prepared for this change and began working on their DEXT implementation after Apple released pertinent documentation at their WWDC (World Wide Developer Conference) in June 2019.

Unfortunately, some vendors could not begin their full transition from KEXT to DEXT until this year. Not all pertinent DriverKit documentation was released at the 2019 event as expected, but, instead, was released at WWDC 2020 in June. Specifically, for Plugable and many other brands, this applies to ASIX-based USB Ethernet Adapters like our USB3-E1000, USBC-E1000, USB2-E1000, and USB2-E100, which we wrote about here for the release of macOS 10.15 Catalina:
https://plugable.com/2019/10/04/usb-ethernet-adapter-not-working-after-macos-catalina-10-15-update-we-can-help/

Current Status for ASIX-based Ethernet Adapters [Novemeber 13, 2020]
We began removing macOS support from our most popular wired network adapters (USB3-E1000 and USBC-E1000) in October 2019. We saw the continued potential for a poor or broken user experience with ASIX-based adapters on macOS and could not in good conscience market the adapters as fully compatible in the long-term as long as ASIX was unwilling to commit to continued development and support of their ICs on macOS.

We have continued to push ASIX for a DEXT beta driver to validate and test internally in the past year. Unfortunately, ASIX has been unable to deliver this solution as requested in anticipation of this significant macOS milestone. We expect a Beta driver from ASIX by the end of November for AX88179 products like the USB3-E1000 and USBC-E1000. Once the driver is validated, we will update this blog post and product driver pages with links to download the driver.

If a wired Ethernet connection is critical to your workflow, Plugable recommends not updating to macOS 11 Big Sur from macOS 10.15 Catalina.

At this time, Plugable is unable to provide a DEXT driver for the following products:
USB3-E1000 IC: AX88179
USBC-E1000 IC: AX88179
USB2-E1000 IC: AX88178 (ASIX has discontinued the IC in this product, and they have not committed to a compatible driver for macOS 11 Big Sur)
The USB2-E100 IC: AX88772 ASIX-based product continues to function, utilizing the in-box drivers in macOS.

We understand this news can be frustrating for our customers and is a situation we have been working to avoid for over one year. We will update this blog post as new information is available to us.

While we cannot promise a functional DEXT driver at any point in the future, if you would like to be notified of that news should it occur, please sign-up on the form below, and we will email everyone as soon as it is available.

继续阅读AX88179 USB网卡无法在macOS Big Sur(11.0.1)系统上正常使用

ubuntu 20.04编译Android 11源代码&模拟器

Android 11 系统映像可直接将 ARM 指令转换成 x86 指令，因此以前很多需要真机测试的情况，现在只需要模拟器就可以进行操作了。

不过，根据官方博客 Run ARM apps on the Android Emulator 尾部的一段注意事项：

这段事项说明，自己编译的镜像是没办法用上这个功能的，必须是Google编译好的镜像。

由于众所周知的原因，我们是没办法正常下载Android的源代码的，因此只能使用国内的镜像来操作了。

1.安装repo工具以及依赖

$ sudo apt-get install gcc make perl

$ sudo apt-get install ccache

$ sudo apt-get install curl

$ sudo apt-get install python

# 安装repo的时候需要指定 --devmode ，否则同步的时候，会报告如下错误信息：
#repo sync -j4 --fail-fast
#/snap/git-repo/18/usr/bin/python: can't open file '~/aosp/.repo/repo/main.py': [Errno 13] Permission denied
# 不要使用 snap 安装的repo, 目前存在很多异常问题， 
# ubuntu 20.04缺少repo 原因是 repo 废弃 python2 的进度慢了一些，
# 导致没办法集成到这个版本的系统里面
# sudo snap install git-repo --devmode

# 手工下载 repo 
$ mkdir -p ~/.bin

$ PATH="${HOME}/.bin:${PATH}"

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo

$ chmod a+rx ~/.bin/repo

$ echo "PATH=${HOME}/.bin:${PATH}" >> ~/.bashrc

$ sudo apt-get install aria2

$ sudo apt-get install git

$ sudo apt install -y libssl-dev

# 解决 
# prebuilts/clang/host/linux-x86/clang-3289846/bin/clang.real: error while loadin
g shared libraries: libncurses.so.5: cannot open shared object file: No such fi
le or directory

$ sudo apt install libncurses5


# 安装VSCode，方便后续查看代码
$ sudo snap install code --classic

$ git config --global user.email "user@email.com"

$ git config --global user.name "user"

$ sudo apt-get install gcc make perl

$ sudo apt-get install ccache

$ sudo apt-get install curl

$ sudo apt-get install python

# 安装repo的时候需要指定 --devmode ，否则同步的时候，会报告如下错误信息：

#repo sync -j4 --fail-fast

#/snap/git-repo/18/usr/bin/python: can't open file '~/aosp/.repo/repo/main.py': [Errno 13] Permission denied

# 不要使用 snap 安装的repo, 目前存在很多异常问题，

# ubuntu 20.04缺少repo 原因是 repo 废弃 python2 的进度慢了一些，

# 导致没办法集成到这个版本的系统里面

# sudo snap install git-repo --devmode

# 手工下载 repo

$ mkdir -p ~/.bin

$ PATH="${HOME}/.bin:${PATH}"

$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo

$ chmod a+rx ~/.bin/repo

$ echo "PATH=${HOME}/.bin:${PATH}" >> ~/.bashrc

$ sudo apt-get install aria2

$ sudo apt-get install git

$ sudo apt install -y libssl-dev

# 解决

# prebuilts/clang/host/linux-x86/clang-3289846/bin/clang.real: error while loadin

g shared libraries: libncurses.so.5: cannot open shared object file: No such fi

le or directory

$ sudo apt install libncurses5

# 安装VSCode，方便后续查看代码

$ sudo snap install code --classic

$ git config --global user.email "user@email.com"

$ git config --global user.name "user"

2.在需要存储代码的地方创建文件夹

$ mkdir ~/AndSrc

$ cd ~/AndSrc

$ mkdir ~/AndSrc

$ cd ~/AndSrc

3.使用镜像下载Android源代码

清华大学的镜像

# 建议直接下载压缩包，使用repo更新基本上都会失败，即使用国内镜像也是一样（目前大约96GB）

$ aria2 -c https://mirrors.ustc.edu.cn/aosp-monthly/aosp-latest.tar

$ tar xvf aosp-latest.tar

$ cd aosp

# 解决 fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle

$ git clone https://gerrit-googlesource.lug.ustc.edu.cn/git-repo

# 建议直接下载压缩包，使用repo更新基本上都会失败，即使用国内镜像也是一样（目前大约96GB）

$ aria2 -c https://mirrors.ustc.edu.cn/aosp-monthly/aosp-latest.tar

$ tar xvf aosp-latest.tar

$ cd aosp

# 解决 fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle

$ git clone https://gerrit-googlesource.lug.ustc.edu.cn/git-repo

4.Android 模拟器编译(可选）

# 配置默认的 python为python3,否则会在运行时报错  SyntaxError: invalid syntax to repo init in the AOSP code

$ sudo mv /usr/bin/python /usr/bin/python.bak

$ sudo ln -s /usr/bin/python3 /usr/bin/python

# Android 11模拟器对应分支 emu-30-release 

$ repo init -b emu-30-release 

# 可能会失败多次，不断尝试，直到完全成功
$ repo sync -j4 --fail-fast

$ cd external/qemu/android/

$ ./rebuild.sh --no-tests

# 配置默认的 python为python3,否则会在运行时报错 SyntaxError: invalid syntax to repo init in the AOSP code

$ sudo mv /usr/bin/python /usr/bin/python.bak

$ sudo ln -s /usr/bin/python3 /usr/bin/python

# Android 11模拟器对应分支 emu-30-release

$ repo init -b emu-30-release

# 可能会失败多次，不断尝试，直到完全成功

$ repo sync -j4 --fail-fast

$ cd external/qemu/android/

$ ./rebuild.sh --no-tests

编译完成之后，产生的模拟器可执行文件及库文件都位于external/qemu/objs/android目录下：

~/AndSrc/aosp/external/qemu/android/objs$ ls
android_emu64_unittests           emulator64-mips
android_emu_metrics64_unittests   emulator64_simg2img
bin64                             emulator64_test_crasher
build                             emulator64-x86
emugl64_common_host_unittests     emulator-check
emulator                          lib
emulator64-arm                    lib64
emulator64_crashreport_unittests  lib64GLcommon_unittests
emulator64-crash-service          lib64OpenglRender_unittests
emulator64_img2simg               qemu
emulator64_libui_unittests        resources
emulator64_make_ext4fs

~/AndSrc/aosp/external/qemu/android/objs$ ls

android_emu64_unittests emulator64-mips

android_emu_metrics64_unittests emulator64_simg2img

bin64 emulator64_test_crasher

build emulator64-x86

emugl64_common_host_unittests emulator-check

emulator lib

emulator64-arm lib64

emulator64_crashreport_unittests lib64GLcommon_unittests

emulator64-crash-service lib64OpenglRender_unittests

emulator64_img2simg qemu

emulator64_libui_unittests resources

emulator64_make_ext4fs

后面就可以像执行 SDK 中的模拟器那样，执行我们编译的模拟器了：

# 下面是个例子，只有设备上已经通过Android SDK 创建过 Nexus_5_API_30_x86，才可以成功执行

~/AndSrc/aosp/external/qemu/android/objs$ ./emulator -avd Nexus_5_API_30_x86

# 下面是个例子，只有设备上已经通过Android SDK 创建过 Nexus_5_API_30_x86，才可以成功执行

~/AndSrc/aosp/external/qemu/android/objs$ ./emulator -avd Nexus_5_API_30_x86

5.列出android-11全部分支

$ cd .repo/manifests && git branch -a | cut -d / -f 3 | grep android-11

1	$ cd .repo/manifests && git branch -a \| cut -d / -f 3 \| grep android-11

6.编译Android 11系统镜像

$ cd ~/AndSrc/aosp

# 前面的编译可能会产生部分垃圾文件，需要清理一下,清理之前，编译好的文件提前备份一下

$ rm -rf *

# 解决 fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle

$ git clone https://gerrit-googlesource.lug.ustc.edu.cn/git-repo

# 配置默认的 python为python3,否则会在运行时报错  SyntaxError: invalid syntax to repo init in the AOSP code

$ sudo mv /usr/bin/python /usr/bin/python.bak
 
$ sudo ln -s /usr/bin/python3 /usr/bin/python

$ repo init -b android-11.0.0_r48

# 可能会失败多次，不断尝试，直到完全成功
$ repo sync -j4 --fail-fast

# 如果上面的命令失败，可以尝试调整为单线程,目前测试发现单线程虽然慢点，但是基本不会失败，多线程经常失败 
# repo sync -j1 --fail-fast

$ cd ~/AndSrc/aosp

# 前面的编译可能会产生部分垃圾文件，需要清理一下,清理之前，编译好的文件提前备份一下

$ rm -rf *

# 解决 fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle

$ git clone https://gerrit-googlesource.lug.ustc.edu.cn/git-repo

# 配置默认的 python为python3,否则会在运行时报错 SyntaxError: invalid syntax to repo init in the AOSP code

$ sudo mv /usr/bin/python /usr/bin/python.bak

$ sudo ln -s /usr/bin/python3 /usr/bin/python

$ repo init -b android-11.0.0_r48

# 可能会失败多次，不断尝试，直到完全成功

$ repo sync -j4 --fail-fast

# 如果上面的命令失败，可以尝试调整为单线程,目前测试发现单线程虽然慢点，但是基本不会失败，多线程经常失败

# repo sync -j1 --fail-fast

7.引入编译环境变量

$ source build/envsetup.sh

1	$ source build/envsetup.sh

8.设置编译目标,此处我们指定编译x86_64下的完整调试版本

# eng：代表 engineer，开发工程师的版本，拥有最大的权限(root等)，具有额外调试工具的开发配置。
# 执行 lunch 命令可以输出全部的编译目标列表
# 更多的编译选项可以从 build/make/target/product/ 下看到
# lunch aosp_x86_arm-eng 编译后的镜像可以安装 arm 应用, 不过在不进行任何代码调整的情况下，应用启动会崩溃

# 不能安装 arm 应用
$ lunch aosp_x86_64-eng

# eng：代表 engineer，开发工程师的版本，拥有最大的权限(root等)，具有额外调试工具的开发配置。

# 执行 lunch 命令可以输出全部的编译目标列表

# 更多的编译选项可以从 build/make/target/product/ 下看到

# lunch aosp_x86_arm-eng 编译后的镜像可以安装 arm 应用, 不过在不进行任何代码调整的情况下，应用启动会崩溃

# 不能安装 arm 应用

$ lunch aosp_x86_64-eng

9.如果需要跟踪调试代码，建议编译为调试类型

$ export TARGET_BUILD_TYPE=debug

1	$ export TARGET_BUILD_TYPE=debug

10.编译

$ export USE_CCACHE=1  

# 清理代码，为编译准备干净的环境

$ make clobber

$ make -j8

$ export USE_CCACHE=1

# 清理代码，为编译准备干净的环境

$ make clobber

$ make -j8

注意此处如果发生编译失败，原因基本上是编译顺序导致的引用出错，也就是某些模块还没有编译完成，其他模块已经开始尝试链接，导致依赖错误，此时只要把多线程并发编译修改成单线程编译即可，即直接执行

$ make

$ make

如果由于内存不足导致的编译失败，可以增加物理内存。但是如果内存无法增加的话，那么适当增加交换分区/交换文件的大小（建议配置16GB以上的交换分区）可以解决此问题，只是编译速度会下降。

运行镜像

选择system-qemu.img和vendor-qemu.img，这两个镜像是专门为qemu运行制作的，如果选择system.img 和vendor.img，则avd运行失败。

$ cd ~/AndSrc/aosp

$ export ANDROID_BUILD_TOP=~/AndSrc/aosp

$ export PATH=$PATH:$ANDROID_BUILD_TOP/out/host/linux-x86/bin

$ export ANDROID_SWT=$ANDROID_BUILD_TOP/out/host/linux-x86/framework

$ export ANDROID_PRODUCT_OUT=$ANDROID_BUILD_TOP/out/target/product/generic_x86_64

$ ./prebuilts/android-emulator/linux-x86_64/emulator -system ./out/target/product/generic_x86_64/system-qemu.img -data ./out/target/product/generic_x86_64/data.img -ramdisk ./out/target/product/generic_x86_64/ramdisk-qemu.img -vendor ./out/target/product/generic_x86_64/vendor-qemu.img -verbose -show-kernel

$ cd ~/AndSrc/aosp

$ export ANDROID_BUILD_TOP=~/AndSrc/aosp

$ export PATH=$PATH:$ANDROID_BUILD_TOP/out/host/linux-x86/bin

$ export ANDROID_SWT=$ANDROID_BUILD_TOP/out/host/linux-x86/framework

$ export ANDROID_PRODUCT_OUT=$ANDROID_BUILD_TOP/out/target/product/generic_x86_64

$ ./prebuilts/android-emulator/linux-x86_64/emulator -system ./out/target/product/generic_x86_64/system-qemu.img -data ./out/target/product/generic_x86_64/data.img -ramdisk ./out/target/product/generic_x86_64/ramdisk-qemu.img -vendor ./out/target/product/generic_x86_64/vendor-qemu.img -verbose -show-kernel

上面运行起来的镜像是从~/AndSrc/aosp/out/debug/target/product/generic/hardware-qemu.ini即可读取配置信息的，但是这个文件直接修改无效，我们如果需要修改参数，只能从启动参数中设置。
比如我们如果需要增大内存，开启GPU的支持，则执行如下命令：

$ ./prebuilts/android-emulator/linux-x86_64/emulator -system ./out/target/product/generic_x86_64/system-qemu.img -data ./out/target/product/generic_x86_64/data.img -ramdisk ./out/target/product/generic_x86_64/ramdisk-qemu.img -vendor ./out/target/product/generic_x86_64/vendor-qemu.img -gpu on -memory 4096 -verbose -show-kernel

编译支持ARM应用的镜像

尽管根据

我们自己编译的镜像是没办法直接从源代码编译支持安装运行 ARM 应用的。

但是有两个变通方案:

从Google官方的 Android 11 镜像中提取需要的文件塞到我们自己编译的镜像里，参考方案： Adding ARM native bridge to the AOSP11 x86 emulator、android_vendor_google_emu-x86
使用 Intel Houdini 实现支持，参考方案：Include Intel Houdini in Android-x86

首先，我们尝试从Google官方的 Android 11 镜像中提取需要的文件，执行如下脚本：

# 安装镜像文件提取依赖库
$ sudo apt install curl rsync zip unzip binwalk

# git clone https://gitlab.com/android-generic/android_vendor_google_emu-x86 vendor/google/emu-x86

$ git clone https://gitlab.com/LongSky/android_vendor_google_emu-x86.git vendor/google/emu-x86

$ . vendor/google/emu-x86/update.sh x86_64

$ sed -i '$a\\n-include vendor/google/emu-x86/board/native_bridge_arm_on_x86.mk' build/make/target/board/generic_x86_64/BoardConfig.mk

$ sed -i '$a\\n$(call inherit-product-if-exists, vendor/google/emu-x86/target/native_bridge_arm_on_x86.mk)' build/make/target/board/generic_x86_64/device.mk

$ sed -i '$a\\n$(call inherit-product-if-exists, vendor/google/emu-x86/target/libndk_translation.mk)' build/make/target/board/generic_x86_64/device.mk

# 安装镜像文件提取依赖库

$ sudo apt install curl rsync zip unzip binwalk

# git clone https://gitlab.com/android-generic/android_vendor_google_emu-x86 vendor/google/emu-x86

$ git clone https://gitlab.com/LongSky/android_vendor_google_emu-x86.git vendor/google/emu-x86

$ . vendor/google/emu-x86/update.sh x86_64

$ sed -i '$a\\n-include vendor/google/emu-x86/board/native_bridge_arm_on_x86.mk' build/make/target/board/generic_x86_64/BoardConfig.mk

$ sed -i '$a\\n$(call inherit-product-if-exists, vendor/google/emu-x86/target/native_bridge_arm_on_x86.mk)' build/make/target/board/generic_x86_64/device.mk

$ sed -i '$a\\n$(call inherit-product-if-exists, vendor/google/emu-x86/target/libndk_translation.mk)' build/make/target/board/generic_x86_64/device.mk

执行编译：

# 禁用系统文件目录文件拷贝检查
$ export DISABLE_ARTIFACT_PATH_REQUIREMENTS="true"

$ lunch aosp_x86_64-eng

$ make

# 禁用系统文件目录文件拷贝检查

$ export DISABLE_ARTIFACT_PATH_REQUIREMENTS="true"

$ lunch aosp_x86_64-eng

$ make

参考链接

Python+Appium实现自动化测试(macOS 10.15.7)

一、环境准备

1.脚本语言：Python3.x IDE：安装Visual Studio Code

2.安装Java JDK 、Android SDK

3.adb环境，path添加%Android_SDK%\platform-tools

4.安装Appium for mac，官网地址 http://appium.io/

继续阅读Python+Appium实现自动化测试(macOS 10.15.7)

Android模拟器支持运行ARM应用，Android 11系统映像可直接将ARM指令转换成x86指令

随着 Android 11 开发者预览版的发布，我们同时也推出了 Android 11 系统映像。新的系统映像在执行 ARM 二进制文件方面取得了显著的性能提升。此前，依赖 ARM 库且无法构建 x86 版本应用的开发者只能使用完整的 ARM 模拟系统映像 (其速度远低于在 x86 设备上运行 x86 系统映像) 或者实体机。Android 11 系统映像能够在不影响整个系统的前提下，直接将 ARM 指令转换成 x86 指令。开发者无需搭建高负载的 ARM 环境即可执行 ARM 二进制文件并进行测试。

继续阅读Android模拟器支持运行ARM应用，Android 11系统映像可直接将ARM指令转换成x86指令

ThinkPad-T440安装Windows 7(USB 3.0)

ThinkPad-T440安装Windows 7的时候，使用USB外置光驱安装系统，由于系统光盘没有集成USB 3.0的驱动，导致在安装过程中，出现错误，错误信息如下图所示：

继续阅读ThinkPad-T440安装Windows 7(USB 3.0)

如何激活机器自带正版Windows10或Office/查询Windows内置序列号

不时看到新机友因为各种原因，无法正确激活机器自带的正版Windows10或Office，解决方法如下：
1、全新机器，第一次启动，连接上网。通常自动激活Windows10，Win10激活后，马上运行Office，据说因服务器原因很多机油无法立即激活，过一小会（几分钟）后就可以了。

2、通用手工激活方法，正确输入正版软件的系列号。该系列号位于机器Bios内，且不会因官方Bios升级取消。

不会查Bios的童鞋，请下载Produkey（绿色软件）自行查询（目前测试ThinkPad T440是可以的）

继续阅读如何激活机器自带正版Windows10或Office/查询Windows内置序列号

Spring Boot+MyBatis+SQLite配置

Spring Boot+MyBatis+SQLite配置例子参考下面

继续阅读Spring Boot+MyBatis+SQLite配置

ubuntu 18.04完整安装配置WordPress 5.5.3并调优

$ sudo apt-get install apache2

$ sudo apt-get install mysql-server

$ sudo apt-get install mysql-client

$ sudo apt-get install php7.2

$ sudo apt-get install php-gd

$ sudo apt install php-mbstring

$ sudo apt install php-dom

# 如果使用了WP-Statistics统计插件，需要安装依赖
$ sudo apt-get install php7.2-curl

$ sudo apt-get install php7.2-bcmath

# PHP Zip支持，提高网络以及内存压缩工具，提升性能
$ sudo apt-get install php-zip

# PHP图像处理支持，imagick替代默认的GD图像处理，提升图像处理性能
$ sudo apt install php-imagick

# 默认imagick是不启用的，需要手工开启
$ sudo phpenmod imagick

$ sudo a2dismod mpm_prefork

$ sudo a2enmod mpm_event

$ sudo apt-get install libapache2-mod-fastcgi php7.2-fpm

$ sudo service php7.2-fpm restart

$ sudo a2enmod actions fastcgi alias proxy_fcgi

$ sudo apt-get install php-mysql

# 启用 Rewrite 模块，我们后续的WP Super Cache需要这个模块的支持
$ sudo a2enmod rewrite

$ sudo service apache2 restart

# 我们以root连接数据库，我们需要手工创建数据库，否则会出现如下错误：
# “我们能够连接到数据库服务器(这意味着您的用户名和密码正确),但未能选择wordpress数据库。”
$ mysql -u root -p -e "create database wordpress;" 

$ cd /var/www

$ sudo chown -R www-data:www-data wordpress

$ sudo apt-get install apache2

$ sudo apt-get install mysql-server

$ sudo apt-get install mysql-client

$ sudo apt-get install php7.2

$ sudo apt-get install php-gd

$ sudo apt install php-mbstring

$ sudo apt install php-dom

# 如果使用了WP-Statistics统计插件，需要安装依赖

$ sudo apt-get install php7.2-curl

$ sudo apt-get install php7.2-bcmath

# PHP Zip支持，提高网络以及内存压缩工具，提升性能

$ sudo apt-get install php-zip

# PHP图像处理支持，imagick替代默认的GD图像处理，提升图像处理性能

$ sudo apt install php-imagick

# 默认imagick是不启用的，需要手工开启

$ sudo phpenmod imagick

$ sudo a2dismod mpm_prefork

$ sudo a2enmod mpm_event

$ sudo apt-get install libapache2-mod-fastcgi php7.2-fpm

$ sudo service php7.2-fpm restart

$ sudo a2enmod actions fastcgi alias proxy_fcgi

$ sudo apt-get install php-mysql

# 启用 Rewrite 模块，我们后续的WP Super Cache需要这个模块的支持

$ sudo a2enmod rewrite

$ sudo service apache2 restart

# 我们以root连接数据库，我们需要手工创建数据库，否则会出现如下错误：

# “我们能够连接到数据库服务器(这意味着您的用户名和密码正确),但未能选择wordpress数据库。”

$ mysql -u root -p -e "create database wordpress;"

$ cd /var/www

$ sudo chown -R www-data:www-data wordpress

WordPress配置文件

<VirtualHost *:80>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	#ServerName www.example.com

	ServerAdmin webmaster@localhost
	#DocumentRoot /var/www/html
	DocumentRoot /var/www/wordpress
	<Directory /var/www/wordpress>
		#Options Indexes FollowSymLinks MultiViews
		Options FollowSymLinks MultiViews
		AllowOverride All
#		Apache 2.2 
#		FCGIWrapper /usr/bin/php5-cgi .php
#		AddHandler fcgid-script .php
#               Options ExecCGI SymLinksIfOwnerMatch
#		Apache 2.4.10
		<FilesMatch \.php$>	
			SetHandler "proxy:unix:/run/php/php7.2-fpm.sock|fcgi://localhost"
		</FilesMatch>
		Order allow,deny
		allow from all
	</Directory>

	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
	# error, crit, alert, emerg.
	# It is also possible to configure the loglevel for particular
	# modules, e.g.
	#LogLevel info ssl:warn

	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

	# For most configuration files from conf-available/, which are
	# enabled or disabled at a global level, it is possible to
	# include a line for only one particular virtual host. For example the
	# following line enables the CGI configuration for this host only
	# after it has been globally disabled with "a2disconf".
	#Include conf-available/serve-cgi-bin.conf
</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

# The ServerName directive sets the request scheme, hostname and port that

# the server uses to identify itself. This is used when creating

# redirection URLs. In the context of virtual hosts, the ServerName

# specifies what hostname must appear in the request's Host: header to

# match this virtual host. For the default virtual host (this file) this

# value is not decisive as it is used as a last resort host regardless.

# However, you must set it for any further virtual host explicitly.

#ServerName www.example.com

ServerAdmin webmaster@localhost

#DocumentRoot /var/www/html

DocumentRoot /var/www/wordpress

#Options Indexes FollowSymLinks MultiViews

Options FollowSymLinks MultiViews

AllowOverride All

# Apache 2.2

# FCGIWrapper /usr/bin/php5-cgi .php

# AddHandler fcgid-script .php

# Options ExecCGI SymLinksIfOwnerMatch

# Apache 2.4.10

SetHandler "proxy:unix:/run/php/php7.2-fpm.sock|fcgi://localhost"

</FilesMatch>

Order allow,deny

allow from all

</Directory>

# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,

# error, crit, alert, emerg.

# It is also possible to configure the loglevel for particular

# modules, e.g.

#LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log

CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are

# enabled or disabled at a global level, it is possible to

# include a line for only one particular virtual host. For example the

# following line enables the CGI configuration for this host only

# after it has been globally disabled with "a2disconf".

#Include conf-available/serve-cgi-bin.conf

</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

启用Apache2的cache,expire,gzip模块，加强服务器性能

$ sudo a2enmod cache

$ sudo a2enmod expires

$ sudo a2enmod deflate

$ sudo service apache2 restart

$ sudo a2enmod cache

$ sudo a2enmod expires

$ sudo a2enmod deflate

$ sudo service apache2 restart

PHP-FPM进程数的设定，提高响应速度，解决页面加载时候缓慢的问题（如果感觉打开页面缓慢，建议调整下面的配置，这种情况尤其在访问量不大的时候会出现短暂的耗时增大，原因就是php进程被临时创建导致延迟增大）

# 增大最大并发进程数量，默认为5 根据需要增大
$ sudo sed -i "s/^pm.max_children = 5/pm.max_children = 20/g" /etc/php/7.2/fpm/pool.d/www.conf

# 增大系统启动初始化的进程数量，默认为 1 根据需要增大
$ sudo sed -i "s/^pm.start_servers = 1/pm.start_servers = 10/g" /etc/php/7.2/fpm/pool.d/www.conf

# 增大保留的最低空闲进程数量，默认为 2 根据需要增大
$ sudo sed -i "s/^pm.min_spare_servers = 2/pm.min_spare_servers = 10/g" /etc/php/7.2/fpm/pool.d/www.conf

# 增大保留的最高空闲进程数量，默认为 3 根据需要增大
$ sudo sed -i "s/^pm.max_spare_servers = 3/pm.max_spare_servers = 20/g" /etc/php/7.2/fpm/pool.d/www.conf

# 配置进程在处理多少个请求之后就退出，避免某些操作导致内存泄漏，及时进行资源回收操作
$ sudo sed -i "s/^#pm.max_requests = 500/pm.max_requests = 5000/g" /etc/php/7.2/fpm/pool.d/www.conf

# 增大最大并发进程数量，默认为5 根据需要增大

$ sudo sed -i "s/^pm.max_children = 5/pm.max_children = 20/g" /etc/php/7.2/fpm/pool.d/www.conf

# 增大系统启动初始化的进程数量，默认为 1 根据需要增大

$ sudo sed -i "s/^pm.start_servers = 1/pm.start_servers = 10/g" /etc/php/7.2/fpm/pool.d/www.conf

# 增大保留的最低空闲进程数量，默认为 2 根据需要增大

$ sudo sed -i "s/^pm.min_spare_servers = 2/pm.min_spare_servers = 10/g" /etc/php/7.2/fpm/pool.d/www.conf

# 增大保留的最高空闲进程数量，默认为 3 根据需要增大

$ sudo sed -i "s/^pm.max_spare_servers = 3/pm.max_spare_servers = 20/g" /etc/php/7.2/fpm/pool.d/www.conf

# 配置进程在处理多少个请求之后就退出，避免某些操作导致内存泄漏，及时进行资源回收操作

$ sudo sed -i "s/^#pm.max_requests = 500/pm.max_requests = 5000/g" /etc/php/7.2/fpm/pool.d/www.conf

启用PHP7的opcache配置

######避免PHP信息暴露在http头中
expose_php = Off

######在关闭display_errors后开启PHP错误日志（路径在php-fpm.conf中配置）
log_errors = On

######开启opcache
[opcache]
; Determines if Zend OPCache is enabled
;opcache.enable=0
opcache.enable=1

; The OPcache shared memory storage size.
;opcache.memory_consumption=128
opcache.memory_consumption=256

; The maximum number of keys (scripts) in the OPcache hash table.
; Only numbers between 200 and 1000000 are allowed.
;opcache.max_accelerated_files=10000
opcache.max_accelerated_files=1000000

; When disabled, you must reset the OPcache manually or restart the
; webserver for changes to the filesystem to take effect.
;opcache.validate_timestamps=1
opcache.validate_timestamps=3000

######避免PHP信息暴露在http头中

expose_php = Off

######在关闭display_errors后开启PHP错误日志（路径在php-fpm.conf中配置）

log_errors = On

######开启opcache

[opcache]

; Determines if Zend OPCache is enabled

;opcache.enable=0

opcache.enable=1

; The OPcache shared memory storage size.

;opcache.memory_consumption=128

opcache.memory_consumption=256

; The maximum number of keys (scripts) in the OPcache hash table.

; Only numbers between 200 and 1000000 are allowed.

;opcache.max_accelerated_files=10000

opcache.max_accelerated_files=1000000

; When disabled, you must reset the OPcache manually or restart the

; webserver for changes to the filesystem to take effect.

;opcache.validate_timestamps=1

opcache.validate_timestamps=3000

重启服务

$ sudo service php7.2-fpm restart

1	$ sudo service php7.2-fpm restart

参考链接

HttpClient利用MultipartEntityBuilder取代MultipartEntity上传图片文件到服务器

注意：在HttpClient4.3之后，原来的上传文件方法MultipartEntity已经不建议使用，现替换成新的httpmime下面的MultipartEntityBuilder。

需要添加httpclient-4.5.jar、httpmime-4.5.jar两个包

maven添加：

        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>httpmime</artifactId>
            <version>4.5</version>
        </dependency>
        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>httpclient</artifactId>
            <version>4.5</version>
        </dependency>

<groupId>org.apache.httpcomponents</groupId>

<artifactId>httpmime</artifactId>

</dependency>

<groupId>org.apache.httpcomponents</groupId>

<artifactId>httpclient</artifactId>

</dependency>

下面我们对比一下MultipartEntity和MultipartEntityBuilder的使用区别：

MultipartEntityBuilder：

             //传入参数可以为file或者filePath，在此处做转换
            File file = new File(filePath);
            CloseableHttpClient httpClient = HttpClients.createDefault();
            CloseableHttpResponse httpResponse = null;
            HttpPost httppost = new HttpPost(url);
            MultipartEntityBuilder builder = MultipartEntityBuilder.create();
            //设置浏览器兼容模式
            builder.setMode(HttpMultipartMode.BROWSER_COMPATIBLE);
            //设置请求的编码格式
            builder.setCharset(Consts.UTF_8);
            builder.setContentType(ContentType.MULTIPART_FORM_DATA);
            //添加文件
            builder.addBinaryBody("file", file);
            HttpEntity reqEntity = builder.build();
            httppost.setEntity(reqEntity);

            httpResponse = httpClient.execute(httppost);

//传入参数可以为file或者filePath，在此处做转换

File file = new File(filePath);

CloseableHttpClient httpClient = HttpClients.createDefault();

CloseableHttpResponse httpResponse = null;

HttpPost httppost = new HttpPost(url);

MultipartEntityBuilder builder = MultipartEntityBuilder.create();

//设置浏览器兼容模式

builder.setMode(HttpMultipartMode.BROWSER_COMPATIBLE);

//设置请求的编码格式

builder.setCharset(Consts.UTF_8);

builder.setContentType(ContentType.MULTIPART_FORM_DATA);

//添加文件

builder.addBinaryBody("file", file);

HttpEntity reqEntity = builder.build();

httppost.setEntity(reqEntity);

httpResponse = httpClient.execute(httppost);

MultipartEntity：

            //传入参数可以为file或者filePath，在此处做转换
            File file = new File(filePath);
            CloseableHttpClient httpClient = HttpClients.createDefault();
            CloseableHttpResponse httpResponse = null;
            HttpPost httppost = new HttpPost(url);
            FileBody filebody = new FileBody(file);
            MultipartEntity entity = new MultipartEntity(HttpMultipartMode.BROWSER_COMPATIBLE, null,
                    Charset.forName("UTF-8"));
            entity.addPart("file", filebody);
            httppost.setEntity(entity);

//传入参数可以为file或者filePath，在此处做转换

File file = new File(filePath);

CloseableHttpClient httpClient = HttpClients.createDefault();

CloseableHttpResponse httpResponse = null;

HttpPost httppost = new HttpPost(url);

FileBody filebody = new FileBody(file);

MultipartEntity entity = new MultipartEntity(HttpMultipartMode.BROWSER_COMPATIBLE, null,

Charset.forName("UTF-8"));

entity.addPart("file", filebody);

httppost.setEntity(entity);

直接上替换后的测试代码：

package com.test.util;
import net.sf.json.JSONObject;
import org.apache.commons.lang.StringUtils;
import org.apache.http.Consts;
import org.apache.http.HttpEntity;
import org.apache.http.HttpStatus;
import org.apache.http.client.ClientProtocolException;
import org.apache.http.client.methods.CloseableHttpResponse;
import org.apache.http.client.methods.HttpPost;
import org.apache.http.entity.ContentType;
import org.apache.http.entity.mime.HttpMultipartMode;
import org.apache.http.entity.mime.MultipartEntityBuilder;
import org.apache.http.impl.client.CloseableHttpClient;
import org.apache.http.impl.client.HttpClients;
import org.apache.http.util.EntityUtils;
import java.io.*;
import java.net.HttpURLConnection;
import java.net.URL;
import java.util.Iterator;
import java.util.Map;

public class HttpPostUploadUtil {

    /**
     * @param args
     */
    public static void main(String[] args) {
        String filePath = "D:\\Test\\0.jpg";
        String url = "http://127.0.0.1:8080/FastFds";
        //调用上传方法
        String backInfo = uploadPost(url, filePath);
        if(StringUtils.isNotBlank(backInfo)){
            //转json数据
            JSONObject json = JSONObject.fromObject(backInfo);
            if(!json.isEmpty()){
                //数据处理
                String value = json.getString("test");
                System.out.println(value);
            }
        }
    }

    /**
     * 上传图片/文件
     * @param url
     * @param filePath
     * @return String 用于转json或者其他信息
     */
    public static String uploadPost(String url, String filePath)  {
        String requestJson = "";
        //传入参数可以为file或者filePath，在此处做转换
        File file = new File(filePath);

        CloseableHttpClient httpClient = HttpClients.createDefault();
        CloseableHttpResponse httpResponse = null;
        try {
            HttpPost httppost = new HttpPost(url);
            MultipartEntityBuilder builder = MultipartEntityBuilder.create();
            //设置浏览器兼容模式
            builder.setMode(HttpMultipartMode.BROWSER_COMPATIBLE);
            //设置请求的编码格式
            builder.setCharset(Consts.UTF_8);
            builder.setContentType(ContentType.MULTIPART_FORM_DATA);
            //添加文件
            builder.addBinaryBody("file", file);
            HttpEntity reqEntity = builder.build();
            httppost.setEntity(reqEntity);

            httpResponse = httpClient.execute(httppost);
            int backCode = httpResponse.getStatusLine().getStatusCode();
            if(backCode == HttpStatus.SC_OK){
                HttpEntity httpEntity = httpResponse.getEntity();
                byte[] json= EntityUtils.toByteArray(httpEntity);
                requestJson = new String(json, "UTF-8");
                //关闭流
                EntityUtils.consume(httpEntity);
                return requestJson;
            }
        } catch (ClientProtocolException e) {
            e.printStackTrace();
        } catch (IOException e) {
            e.printStackTrace();
        } finally {
            //释放资源
            try {
                httpClient.close();
                httpResponse.close();
            } catch (IOException e) {
                e.printStackTrace();
            }

        }
        return null;
    }
}

package com.test.util;

import net.sf.json.JSONObject;

import org.apache.commons.lang.StringUtils;

import org.apache.http.Consts;

import org.apache.http.HttpEntity;

import org.apache.http.HttpStatus;

import org.apache.http.client.ClientProtocolException;

import org.apache.http.client.methods.CloseableHttpResponse;

import org.apache.http.client.methods.HttpPost;

import org.apache.http.entity.ContentType;

import org.apache.http.entity.mime.HttpMultipartMode;

import org.apache.http.entity.mime.MultipartEntityBuilder;

import org.apache.http.impl.client.CloseableHttpClient;

import org.apache.http.impl.client.HttpClients;

import org.apache.http.util.EntityUtils;

import java.io.*;

import java.net.HttpURLConnection;

import java.net.URL;

import java.util.Iterator;

import java.util.Map;

public class HttpPostUploadUtil {

/**

* @param args

public static void main(String[] args) {

String filePath = "D:\\Test\\0.jpg";

String url = "http://127.0.0.1:8080/FastFds";

//调用上传方法

String backInfo = uploadPost(url, filePath);

if(StringUtils.isNotBlank(backInfo)){

//转json数据

JSONObject json = JSONObject.fromObject(backInfo);

if(!json.isEmpty()){

//数据处理

String value = json.getString("test");

System.out.println(value);

}

/**

* 上传图片/文件

* @param url

* @param filePath

* @return String 用于转json或者其他信息

public static String uploadPost(String url, String filePath) {

String requestJson = "";

//传入参数可以为file或者filePath，在此处做转换

File file = new File(filePath);

CloseableHttpClient httpClient = HttpClients.createDefault();

CloseableHttpResponse httpResponse = null;

try {

HttpPost httppost = new HttpPost(url);

MultipartEntityBuilder builder = MultipartEntityBuilder.create();

//设置浏览器兼容模式

builder.setMode(HttpMultipartMode.BROWSER_COMPATIBLE);

//设置请求的编码格式

builder.setCharset(Consts.UTF_8);

builder.setContentType(ContentType.MULTIPART_FORM_DATA);

//添加文件

builder.addBinaryBody("file", file);

HttpEntity reqEntity = builder.build();

httppost.setEntity(reqEntity);

httpResponse = httpClient.execute(httppost);

int backCode = httpResponse.getStatusLine().getStatusCode();

if(backCode == HttpStatus.SC_OK){

HttpEntity httpEntity = httpResponse.getEntity();

byte[] json= EntityUtils.toByteArray(httpEntity);

requestJson = new String(json, "UTF-8");

//关闭流

EntityUtils.consume(httpEntity);

return requestJson;

}

} catch (ClientProtocolException e) {

e.printStackTrace();

} catch (IOException e) {

e.printStackTrace();

} finally {

//释放资源

try {

httpClient.close();

httpResponse.close();

} catch (IOException e) {

e.printStackTrace();

}

return null;

}

继续阅读HttpClient利用MultipartEntityBuilder取代MultipartEntity上传图片文件到服务器

正则表达式 - 字符匹配不以某字段开头或者结尾

最近有一个需求，要求是判断某个字符串不以什么开头。然后就开始探索这个不以什么开头和不易什么结尾的正则怎么写，why?

不以某字符串开头

这里需要提一个概念叫 否定式前项匹配 这个东东。

向前匹配

根据匹配的字符序列后面存在一个特定的字符序列或者不存在一个特定的序列来决定是否匹配。对于向前匹配，出现在指定项后面的字符序列不会被正则表达式返回。

这里说后面存在一个特定字符序列, 也称之为肯定式向前查找
不存在一个特定的序列，也称之为否定式向前查找
这两个概念后续再深入

开始解决这个问题不以某字符串开头:

^(?!str)

^(?!str)

这里使用了下面几个元符号:

^ 判断是否是开头
?! 这里是否定向前查询

示例:

不以test 开头字符串

/^(?!test).*/

1	/^(?!test).*/

继续阅读正则表达式 - 字符匹配不以某字段开头或者结尾

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