# vim /etc/zypp/zypp.conf
将部分内容修改如下:
......
multiversion = provides:multiversion(kernel)
......
multiversion.kernels = latest,latest-1,running
......
(补充:这里以保留正在运行的内核版本、最新的内核版本和倒数新的内核版本为例)
# vim /etc/zypp/zypp.conf
将部分内容修改如下:
......
multiversion = provides:multiversion(kernel)
......
multiversion.kernels = latest,latest-1,running
......
(补充:这里以保留正在运行的内核版本、最新的内核版本和倒数新的内核版本为例)
# vim /etc/zypp/zypp.conf
添加以下内容:
......
gpgcheck=0
openSUSE & SLES 的 PAM 文件默认是一些软链接,指向另一个文件:
/etc/pam.d/common-account --> /etc/pam.d/common-account-pc
/etc/pam.d/common-auth --> /etc/pam.d/common-auth-pc
/etc/pam.d/common-password --> /etc/pam.d/common-password-pc
/etc/pam.d/common-session --> /etc/pam.d/common-session-pc
而当 openSUSE & SLES 升级 pam-config 软件包时可能会自动刷新以下文件:
/etc/pam.d/common-account-pc
/etc/pam.d/common-auth-pc
/etc/pam.d/common-password-pc
/etc/pam.d/common-session-pc
所以,如果 openSUSE & SLES 的 PAM 文件是一些单独的文件,不指向后缀以 -pc 结尾的文件的软链接,那么里面的内容就不会被自动刷新
# ll /etc/pam.d/common-account
# ll /etc/pam.d/common-auth
# ll /etc/pam.d/common-password
# ll /etc/pam.d/common-session
# rm /etc/pam.d/common-{account,auth,password,session}
# cp /etc/pam.d/common-account-pc /etc/pam.d/common-account
# cp /etc/pam.d/common-auth-pc /etc/pam.d/common-auth
# cp /etc/pam.d/common-password-pc /etc/pam.d/common-password
# cp /etc/pam.d/common-session-pc /etc/pam.d/common-session
# ll /etc/pam.d/common-account
# ll /etc/pam.d/common-auth
# ll /etc/pam.d/common-password
# ll /etc/pam.d/common-session
(步骤略)
https://www.suse.com/support/kb/doc/?id=000018934
# cat /etc/crypto-policies/back-ends/krb5.config
aes128-cts-hmac-sha256-128 aes256-cts-hmac-sha384-192
(补充:从这里的输出结果可以看出,目前使用的后台加密方式有 aes128-cts-hmac-sha256-128 aes256-cts-hmac-sha384-192)
# vi /etc/crypto-policies/back-ends/krb5.config
error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Resource temporarily unavailable)
# rm -rf /var/lib/rpm/_db*
# rpm --rebuilddb
# zypper refresh