1-7-i386-l4w6Z_/fcitx-4.2.4.1 /src/lib/fcitx/addon.c:100-加载附加组件配置文件: fcitx-table.conf [INFO] /build/buildd-fcitx_4.2.4.1-7-i386-l4w6Z_/fcitx-4.2.4.1/src/lib/fcitx /addon.c:100-加载附加组件配置文件: fcitx-xim.conf [INFO] 1-7-i386-l4w6Z_/fcitx-4.2.4.1/src/lib/fcitx /addon.c:100-加载附加组件配置文件: fcitx-lua.conf [INFO] /build/buildd-fcitx_4.2.4.1-7-i386-l4w6Z_/fcitx-4.2.4.1/src/lib/fcitx /addon.c:100-加载附加组件配置文件: fcitx-pinyin.conf [INFO] 1-7-i386-l4w6Z_/fcitx-4.2.4.1/src/lib/fcitx /addon.c:100-加载附加组件配置文件: fcitx-autoeng.conf [INFO] /build/buildd-fcitx_4.2.4.1-7-i386-l4w6Z_/fcitx-4.2.4.1/src/lib/fcitx /addon.c:100-加载附加组件配置文件: fcitx-xkb.conf [INFO]

foo@example.org] [-f ” 名称姓氏”] [-i ” 构建工具” | -j] [-l license_file] [-m] [-o file] [-q] [-s] [-v] [-w ”addon, …”] [-x [01234]] [-y] [-L] [-P] [-T] A.3 描述 debmake 协助从上游源代码构建一个 Debian 软件包，通常做法如下： • 下载上游源码压缩包（tarball）并命名为 显示版本信息。 -w ”addon,…”, --with ”addon,…” 在 debian/rules 文件中向 dh(1) 命令的参数中添加额外的 dh(1) 参数以 指定所使用的附加组件（addon）。 这里 addon 的值中各项使用“,”进行分隔，例如“-w ”python3,autoreconf””。 对于基于 Autotools 的软件包，autoreconf 作为 addon 运行“autoreconf 次构建软件包的默认行为。 对基于 Autotools 的软件包，如果它们要安装 Python(版本 3) 程序，您需要指定 python3 作为 addon 到 debmake 命令参数，因为这不是显而易见的。但对基于 setup.py 的软件包来说，并不需要指定 python3 作为 addon 到 debmake 命令参数，因为这是显而易见的，debmake 会自动为 dh(1) 命令设 置这样的参数。 -x n

--pod-network-cidr=10.217.0.0/16 --skip-phases=addon/kube- proxy In K8s 1.15 and older it is not yet possible to disable kube-proxy via --skip- phases=addon/kube-proxy in kubeadm, therefore the below workaround STATUS RESTARTS AGE cilium-5074s 1/1 Running 0 58m kube-addon-manager-minikube 1/1 Running 0 59m kube-dns-268032401-j0vml 3/3 not managed by Cilium: $ ./contrib/k8s/k8s-unmanaged.sh kube-system/cilium-hqpk7 kube-system/kube-addon-manager-minikube kube-system/kube-dns-54cccfbdf8-zmv2c kube-system/kubernetes-dashboard-77d8b98585-g52k5

kube-proxy deployment phase, so it has to be executed with the --skip- phases=addon/kube-proxy option: kubeadm init --skip-phases=addon/kube-proxy For more information please refer to the Kubernetes without K8s 1.15 and older kubeadm init --skip-phases=addon/kube-proxy In K8s 1.15 and older it is not yet possible to disable kube-proxy via --skip- phases=addon/kube-proxy in kubeadm, therefore the below workaround STATUS RESTARTS AGE cilium-5074s 1/1 Running 0 58m kube-addon-manager-minikube 1/1 Running 0 59m kube-dns-268032401-j0vml 3/3

--pod-network-cidr=10.217.0.0/16 --skip-phases=addon/kube- proxy In K8s 1.15 and older it is not yet possible to disable kube-proxy via --skip- phases=addon/kube-proxy in kubeadm, therefore the below workaround STATUS RESTARTS AGE cilium-5074s 1/1 Running 0 58m kube-addon-manager-minikube 1/1 Running 0 59m kube-dns-268032401-j0vml 3/3 not managed by Cilium: $ ./contrib/k8s/k8s-unmanaged.sh kube-system/cilium-hqpk7 kube-system/kube-addon-manager-minikube kube-system/kube-dns-54cccfbdf8-zmv2c kube-system/kubernetes-dashboard-77d8b98585-g52k5

kube-proxy deployment phase, so it has to be executed with the --skip- phases=addon/kube-proxy option: kubeadm init --skip-phases=addon/kube-proxy For more information please refer to the Kubernetes Without and newer kubeadm init --skip-phases=addon/kube-proxy K8s 1.15 and older In K8s 1.15 and older it is not yet possible to disable kube-proxy via --skip- phases=addon/kube-proxy in kubeadm, therefore the STATUS RESTARTS AGE cilium-5074s 1/1 Running 0 58m kube-addon-manager-minikube 1/1 Running 0 59m kube-dns-268032401-j0vml 3/3

kube-proxy deployment phase, so it has to be executed with the --skip- phases=addon/kube-proxy option: kubeadm init --skip-phases=addon/kube-proxy For more information please refer to the Kubernetes Without via kubeadm init and skip the installation of the kube-proxy add-on: $ kubeadm init --skip-phases=addon/kube-proxy Afterwards, join worker nodes by specifying the control-plane node IP address and the STATUS RESTARTS AGE cilium-5074s 1/1 Running 0 58m kube-addon-manager-minikube 1/1 Running 0 59m kube-dns-268032401-j0vml 3/3

RESTARTS AGE cilium-5074s 1/1 Running 0 58m kube-addon-manager-minikube 1/1 Running 0 59m kube-dns-268032401-j0vml 3/3 not managed by Cilium: $ ./contrib/k8s/k8s-unmanaged.sh kube-system/cilium-hqpk7 kube-system/kube-addon-manager-minikube kube-system/kube-dns-54cccfbdf8-zmv2c kube-system/kubernetes-dashboard-77d8b98585-g52k5 io/v1.1.0/tools/k8s-unmanaged.sh $ ./k8s-unmanaged.sh kube-system/cilium-hqpk7 kube-system/kube-addon-manager-minikube kube-system/kube-dns-54cccfbdf8-zmv2c kube-system/kubernetes-dashboard-77d8b98585-g52k5

kube-proxy deployment phase, so it has to be executed with the --skip- phases=addon/kube-proxy option: kubeadm init --skip-phases=addon/kube-proxy For more information please refer to the Kubernetes Without via kubeadm init and skip the installation of the kube-proxy add-on: $ kubeadm init --skip-phases=addon/kube-proxy Afterwards, join worker nodes by specifying the control-plane node IP address and the STATUS RESTARTS AGE cilium-5074s 1/1 Running 0 58m kube-addon-manager-minikube 1/1 Running 0 59m kube-dns-268032401-j0vml 3/3

令就可以达到这样的效果： [root@linuxprobe~]# tail -n 10 initial-setup-ks.cfg %addon com_redhat_subscription_manager %end %addon ADDON_placeholder --disable --reserve-mb=auto %end %anaconda pwpolicy root Server With GUI 选项。 31 %packages 32 @^graphical-server-environment 33 34 %end 35 36 %addon com_redhat_kdump --disable --reserve-mb='auto' 37 38 %end 39 40 %anaconda 41 pwpolicy root m./. --iscrypted -- gecos="linuxprobe" %packages @^graphical-server-environment %end %addon com_redhat_kdump --disable --reserve-mb='auto' %end %anaconda pwpolicy root --minlen=6 --minquality=1