Welcome to the Linux Foundation Forum!

Question regarding Lab 10.2 (best way to revert back to rpm_BACKUP)

Posts: 19
edited December 2022 in LFS207 Class Forum

Hello Instructors/Mentors,

(I am running openSUSE Tumbleweed on a VM)

As a note I would like to mention that 'rpm' on openSUSE system is located on (symbolic linked) '/usr/lib/sysimage/'

The questions I have is:

  • What is the best way to revert back to 'rpm_BACKUP' in case (new) rpm doesn't function properly after '--rebuilddb'? I have tried 'sudo cp' and 'sudo mv' command to replace new 'rpm' with 'rpm_BACKUP' however when I lookup the number of files (using 'ls -l rpm rpm_BACKUP') afterwards they still differ as if replacing (using cp and mv) command didn't work.
  • (Not sure if it's the right question to ask however here it goes) Is 'rpm --rebuilddb' performs comparable action as 'apt update && apt upgrade' performs in ubuntu even though one is low-level and the other is high-level utility respectively?

(Screenshot attached for reference)

Please provide clarification.

Thank you,
Amar

Answers

  • Posts: 916

    I don't have access to a Tumbleweed, but on OpenSUSE Leap 15.4, please note that

    1. student@localhost:/var/lib/rpm> ls -li /var/lib/rpm /usr/lib/sysimage/rpm
    2. 131077 lrwxrwxrwx 1 root root 26 Nov 3 04:50 /var/lib/rpm -> ../../usr/lib/sysimage/rpm

    so it is /var/lb/rpm. The link is irrelevant. The layout of these files is quite different between redhat-based systems
    and SUSE, but the functionality of rpm --rebuilddb should not be different. I'm not sure what problem you are pointing to. Did you do a diff sinstead of a ls -l? Meta data can change without any meaning to it

    Note that so few students use SuSe-based platforms that it has been a while since we have checked this lab on openSuse but it worked as of last attempt.

  • Posts: 916

    and on opensuse this directory looks nothing like Tumbleweed so I cannot help you :smile:

    1. student@localhost:/> ls -l /usr/lib/sysimage/rpm
    2. total 347684
    3. -rw-r--r-- 1 root root 14778368 Dec 14 08:49 Basenames
    4. -rw-r--r-- 1 root root 20480 Dec 14 08:48 Conflictname
    5. -rw-r--r-- 1 root root 5304320 Dec 14 08:49 Dirnames
    6. -rw-r--r-- 1 root root 8192 Nov 23 11:47 Enhancename
    7. -rw-r--r-- 1 root root 8192 Oct 4 15:11 Filetriggername
    8. -rw-r--r-- 1 root root 61440 Dec 14 08:49 Group
    9. -rw-r--r-- 1 root root 106496 Dec 14 08:49 Installtid
    10. -rw-r--r-- 1 root root 151552 Dec 14 08:49 Name
    11. -rw-r--r-- 1 root root 73728 Dec 14 08:49 Obsoletename
    12. -rw-r--r-- 1 root root 326926336 Dec 14 08:49 Packages
    13. -rw-r--r-- 1 root root 6557696 Dec 14 08:49 Providename
    14. -rw-r--r-- 1 root root 49152 Dec 14 08:49 Recommendname
    15. -rw-r--r-- 1 root root 811008 Dec 14 08:49 Requirename
    16. -rw-r--r-- 1 root root 270336 Dec 14 08:49 Sha1header
    17. -rw-r--r-- 1 root root 151552 Dec 14 08:49 Sigmd5
    18. -rw-r--r-- 1 root root 16384 Dec 14 08:48 Suggestname
    19. -rw-r--r-- 1 root root 675840 Dec 14 08:48 Supplementname
    20. -rw-r--r-- 1 root root 8192 Jun 8 2022 Transfiletriggername
    21. -rw-r--r-- 1 root root 8192 Jun 8 2022 Triggername

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training