如何检查使用yum历史记录更新了哪些软件包?


0

好,让我们做一个小实验:在全新安装的CentOS上,当我输入时yum history list,输出为:

[user@machine ~]# yum history list
Loaded plugins: security
ID | Login user               | Date and time    | Action(s)      |  Altered
 -------------------------------------------------------------------------------
 8 | root <root>              | 2017-03-02 09:42 | I, U           |   28   
 7 | root <root>              | 2017-03-02 09:41 | I, U           |    8   
 6 | root <root>              | 2016-01-30 10:48 | Update         |   10   
 5 | root <root>              | 2015-09-26 16:35 | Update         |    1  <
 4 | System <unset>           | 2015-07-14 21:28 | I, U           |   91 > 
 3 | System <unset>           | 2015-07-14 21:27 | Install        |    1   
 2 | System <unset>           | 2015-07-14 21:27 | Install        |    1   
 1 | System <unset>           | 2015-07-14 21:16 | Install        |  474   
 history list

现在让我们使用来更新vim yum update vim -y,然后yum history list生成以下代码:

 [user@machine ~]# yum history list
 Loaded plugins: security
 ID     | Login user               | Date and time    | Action(s)      | Altered
 ------------------------------------------------------------------------------- 
 9 | root <root>              | 2017-07-28 18:08 | I, U           |    3   
 8 | root <root>              | 2017-03-02 09:42 | I, U           |   28   
 7 | root <root>              | 2017-03-02 09:41 | I, U           |    8   
 6 | root <root>              | 2016-01-30 10:48 | Update         |   10   
 5 | root <root>              | 2015-09-26 16:35 | Update         |    1  <
 4 | System <unset>           | 2015-07-14 21:28 | I, U           |   91 > 
 3 | System <unset>           | 2015-07-14 21:27 | Install        |    1   
 2 | System <unset>           | 2015-07-14 21:27 | Install        |    1   
 1 | System <unset>           | 2015-07-14 21:16 | Install        |  474 

问题是,如果我有兴趣查看更新了哪个软件包,我如何理解此输出?

Answers:


0

仅凭该输出,您就无法真正理解它。但是,如果您查看文档,您会发现它yum history info可以为您提供更多实际发生的信息。它接受ID作为参数。

By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.