Red Hat Enterprise rhel5.0 software package management

After RHEL (Red Hat Enterprise Linux) is upgraded to 5.0, yum (yellow dog update manager) is used to manage software packages, including software package updates and patch delivery. This is not a small change! So far:
1. If you have not purchased a RedHat subscription, you will not be able to get the Installation Number (note that it is not the serial number at the time of installation). Therefore, you will not be able to register the system, and you will not be able to get Red Hat software updates and patch services;
2. In "Add/delete software" (Package Manager, command name is pirut), the software "list" can only see installed software packages; on the "Browse" tab, no manageable Software Package categories will be visible (Some people think this is a bug, which is actually a "bug" intentionally created by RedHat "). Open the "Application/system tools/software package update tools" menu, you are required to enter the subscription or register and purchase the subscription.

In this way, you cannot get Red Hat updates in time (not paid, you can still understand it), and you cannot use the package management tool on the GUI to add/delete RPM software packages in the system. Although you can manually run the command rpm to install and uninstall the package (such as rpm-uvh packge. rpm and rpm-e package), and as long as the manual installation is correct, there will be no problems in use, but there is no convenience of the graphic interface.

In fact, all RPM packages are stored in the server directory of the RHEL installation CD (rhel_5.1 i386 DVD). During manual installation, the installation source is obtained from here. Rhel5.0 actually points the installation source to an HTTP service URL from here, and we can guess that it should be authenticated to directly connect to this URL. But we can imagine that it is also possible to direct the installation source to a local file system? In fact, it does.

Practice:

1. Load the DVD installation disk:
CD/Media
Mkdir ISO
Mount/dev/HDC ISO
In rhel5.3 installed with vmware6.0, run the DF command to see that my optical drive device is/dev/HDC. I have installed it in/Media/ISO.
Note that the system is automatically loaded to/Media/rhel_5.1 i386 DVD/, but there are spaces in the middle of the DVD's volume mark, which may cause problems when used. So we need to load it again and change the path.

2. Create the text file rhel5media. Repo in the/etc/yum. Repos. d/path and enter the following text content:
[Base]
Name = base RPM repository for rhel5
Baseurl = file: // media/ISO/Server/
Enabled = 1
Gpgcheck = 0

3. Modify the yumrepo. py file in the/usr/lib/python2.4/Site-packages/Yum/path (you can see that the system code of rhel5.0 is developed in Python !), Modify Row 3 from remote = URL + '/' + relative to remote = "file: /// MNT/ISO/Server/"+ '/' + relative.

Click "application/system tool/software package update tool" (the command name is pup). The "Software Package Update" window is displayed, prompting that no updates are available: "There are no software packages available for your system." The syntax is impeccable, but I feel like it's just a foul sentence. Is it a fake foreign devil translation?

Click "application/add or delete software" (the software package update tool cannot run together with the above tool, and an error will be prompted) to open the "Software Package Manager ", on the left side of "browsing" is "desktop environment", "application", "development", "server", "Basic System", and "language support, all software packages, including the packages already installed and not installed, are listed on the right.

Note that the mount command is used to temporarily load the optical drive device to/Media/ISO/. To manage the software package in the future, you must first perform this step. If you want to "automate", add this command to the Automatic Running file at startup. Add the following content to the end of the RC. Local file in/etc:
Mount/dev/HDC/Media/ISO

By the way, if you manually download the update package after RedHat and add it to the server directory of the disc (the disk cannot be written, change the path ), can I upgrade the system as usual? Theoretically, this is acceptable, but I don't know if I can solve the RPM package dependency problem? I don't know.

(This article is written in the gedit editor in rhel5.03 .)

2009-4-26
 

With the image version address: http://blog.why100000.com /? P = 481