arch

LINUX下YUM源配置 1.确保RHEL5中已经安装了yum [root@lvs-master ~]# rpm -qa |grep yum yum-metadata-parser-1.1.2-3.el5 yum-updatesd-0.9-2.el5 yum-3.2.22-26.el5 yum-security-1.1.16-13.el5 yum-rhn-plugin-0.5.4-15.el5 2.修改源配置文件 ＃vim /etc/yum.repos.d/CentOS-Base.repo [base] name=CentOS-5-Base #mirrorlist=http://mirrorlist.centos.org/?release=$releasever5&arch=$basearch&repo=os #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/ baseurl=http://ftp.sjtu.edu.cn/centos/5/os/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-centos5 #released updates [update] name=CentOS-5-Updates

第一步：先安装好nvidia驱动 第二步：打开终端，输入命令：nvcc --version，查看是否安装了cuda 运行命令：nvidia-smi 可以看到CUDA Version：10.2 第三步：入官网下载cuda10.2版本，按下面选好后，会给出安装命令 wget http://developer.download.nvidia.com/compute/cuda/10.2/Prod/local_installers/cuda-repo-rhel8-10-2-local-10.2.89-440.33.01-1.0-1.x86_64.rpm sudo rpm -i cuda-repo-rhel8-10-2-local-10.2.89-440.33.01-1.0-1.x86_64.rpm sudo dnf clean all sudo dnf -y module install nvidia-driver:latest-dkms sudo dnf -y install cuda 第四步：打开~/.bashrc，加入配置信息 [root@localhost ~]# vi ~/.bashrc export PATH=/usr/local/cuda/bin:$PATH export LD_LIBRARY_PATH=/usr/local/cuda/lib64:$LD_LIBRARY

Deployment: kind: Deployment apiVersion: extensions/v1beta1 metadata: name: skx spec: replicas: 3 template: metadata: labels: app: skx_server spec: containers: name: httpd-test image: 192.168.1.10:5000/httpd:v1 ports: containerPort: 80 PS：注意，在Deployment资源对象中，可以添加Port字段，但此字段仅供用户查看，并不实际生效。 如下： ports: containerPort: 80 SERVICE kind: Service apiVersion: v1 metadata: name: skx-svc spec: selector: app: skx_server ports: protocol: TCP port: 80 targetPort: 80 关联主机： kind: Service apiVersion: v1 metadata: name: skx-svc spec: type: NodePort selector: app: skx_server ports: protocol: TCP port: 80

[lwk@archlinux ~]$ vim .bashrc # # ~/.bashrc # alias ls='ls --color=auto' alias ll='ls -la --color=auto' # If not running interactively, don't do anything [[ $- != *i* ]] && return #PS1='[\u@\h \W]\$ ' PS1='\[\033[1;32m\]\u@\h \w $\[\033[0m\] ' [lwk@archlinux ~]$ [lwk@archlinux ~]$source .bashrc lwk@archlinux ~ $ 显示效果如下 lwk@archlinux ~ $ vim terminal_color.sh #!/bin/bash # # This file echoes a bunch of color codes to the # terminal to demonstrate what's available. Each # line is the color code of one forground color, # out of 17 (default + 16 escapes), followed by a # test use of that color on

第一部分 日常维护 一 正确打开主库和备库 1 主库: SQL> STARTUP MOUNT; SQL> ALTER DATABASE ARCHIVELOG; SQL> ALTER DATABASE OPEN; 2 备库: SQL> STARTUP MOUNT; SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; 二 正确关闭顺序 1 备库: SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; SQL>SHUTDOWN IMMEDIATE; 2 主库 SQL>SHUTDOWN IMMEDIATE; ---先于standby执行 三 备库 Read-Only模式打开 当前主库正常 OPEN状态 备库处于日志传送状态 . 1 在备库停止日志传送 SQL> alter database recover managed standby database cancel; 2 备库Read-only模式打开 SQL> alter database open read only; 3 备库回到日志传送模式 SQL>alter database recover managed standby database

sudo gem install jekyll 安装报错 Building native extensions. This could take a while .. . ERROR: Error installing jekyll: ERROR: Failed to build gem native extension. current directory: /Library/Ruby/Gems/2.3.0/gems/ffi-1.11.3/ext/ffi_c /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby -r ./siteconf20200103-63706-1n7uc12.rb extconf.rb checking for ffi.h .. . no checking for ffi.h in /usr/local/include,/usr/include/ffi .. . yes checking for ffi_call ( ) in -lffi .. . yes checking for ffi_closure_alloc ( ) .. . no checking for shlwapi.h .. . no checking for rb_thread_call_without

1.子目录的Makefile 已知有文件:a.c b.c 要在Makefile中设置成编译进内核，可用：obj-y +=a.o b.o 实现 如果用a.c b.c 组合成一个模块ab.o呢？ 可用: obj -m +=ab.o ab-objs :=a.o b.o 这个在Documentation\kbuild\makefiles.txt有详细说明 2.架构相关的Makefile 根据命令 make uimage 分析 搜索uimage发现Uimage并不在顶层Makefile，而在arch/arm/makefile中，这说明arch/arm/下的Makefile肯定被包含在顶层Makefile中，在代码中搜索发现的确如此，如下： include $(srctree) /arch/$(ARCH)/Makefile 3.顶层Makefile 执行make Uimage 分析他的执行过程，依赖那些文件可以从Makefile入手 搜索可以知道uimage依赖与vmlinux，一步步追踪如下 zImage Image xipImage bootpImage uImage: vmlinux vmlinux: $(vmlinux-lds) $(vmlinux-init) $(vmlinux-main) $(kallsyms.o) FORCE vmlinux-init := $(head-y) $

------------------方法1在主库上使用备份的进行恢复丢失的归档日志------------------------- 1.发现主库备份后删除了归档,但是这些归档从库还没应用,也没有传到从库 从库应用的最新的归档日志为592 SQL> connect / as sysdba Connected. SQL> Select Max(t.SEQUENCE#) From V$archived_Log t; MAX(T.SEQUENCE#) ---------------- 592 主库的归档日志 SQL> connect / as sysdba Connected. SQL> Column Name format a100; SQL> Column THREAD# format 99; SQL> Column SEQUENCE# format 999999; SQL> Column STANDBY_DEST format a10; SQL> Column ARCHIVED format a10; SQL> Column APPLIED format a10; SQL> Column STATUS format a10; SQL> Column fal format a10; SQL> Column COMPLETION_TIME format a20; SQL> Select

点击打开链接 1、get_abs_build_var() 和 get_build_var()的实现都在build/envsetup.sh中。 2、在buld目录下grep这两个函数可知：这两个函数只在build/envsetup.sh脚本中使用。 言归正传，贴代码 [plain] view plain copy # Get the value of a build variable as an absolute path. function get_abs_build_var() { T=$(gettop) if [ ! "$T" ]; then echo "Couldn't locate the top of the tree. Try setting TOP." >&2 return fi (\cd $T; CALLED_FROM_SETUP=true BUILD_SYSTEM=build/core \ command make --no-print-directory -f build/core/config.mk dumpvar-abs-$1) } # Get the exact value of a build variable. function get_build_var() { T=$(gettop) if [ ! "$T" ]; then echo "Couldn