12-5: Listing Installed RPM Packages in .NET

Integrate code128b in .NET 12-5: Listing Installed RPM Packages
Listing 12-5: Listing Installed RPM Packages
Code 128C barcode library with .net
use visual studio .net code 128 barcode development toinsert barcode standards 128 for .net
bible:/media/dvd/suse/i586 # rpm -qa aaa_skel-2003.9.18-93 XFree86-fonts-scalable- providers-2004.4.2-4 EastWest-0.1-30 suse-release-9.1-0 dos2unix-3.1-279 netcat-1.10-864 mktemp-1.5-729 gle-3.0.6-642 gpart-0.1h-475 eject-2.0.13-185 usbutils-0.11-211 popt-1.7-176 ziptool-1.4.0-105
Barcode Standards 128 barcode library on .net
Using Barcode reader for .net framework Control to read, scan read, scan image in .net framework applications.
Again, we have cut the list down as we have a lot of packages installed, but you get the point.
Bar Code encoding in .net
using barcode drawer for visual .net control to generate, create bar code image in visual .net applications.
Tip The program sort is useful in this situation to sort the output of the rpm -qa command into an alphanumeric list. Using the pipe (|) command, you can redirect the output of the rpm -qa command through the sort command (rpm -qa | sort).
Add barcode for .net
use vs .net crystal bar code generation topaint barcode in .net
Once listed, you can go through the RPM list and remove any packages not needed.
Control code 128 code set c data in c#
uss code 128 data for visual c#
Removing installed packages
Control code 128 data with .net
barcode 128 data with .net
Once an RPM has been installed, you may need to remove it from the system for one reason or another. As it does when installing packages, RPM will check the dependencies of the package you wish to remove. This check of dependencies is as important as checking package dependency during installation because you could end up deleting files that another RPM package depends on. To remove packages, you need to erase (-e) the package from the system. As with installation of packages, RPM checks to see if any other RPM packages on the system depend on the package you wish to remove. If a package does depend on it, the removal will fail. See Listing 12-6 for an example.
Paint code-128 with visual basic
using barcode implement for visual .net control to generate, create barcode code 128 image in visual .net applications.
Part III Using the Command Line in SUSE Linux
Linear 1d Barcode integration with .net
using visual studio .net tomake 1d barcode for asp.net web,windows application
Listing 12-6: Removing a Dependent Package
Bar Code integrating in .net
using vs .net torender bar code with asp.net web,windows application
bible:/media/dvd/suse/i586 # rpm -e blackbox error: Failed dependencies: blackbox is needed by (installed) bbtools-2003.10.16-97
VS .NET Crystal bar code maker for .net
use visual .net crystal bar code integration touse bar code in .net
In this example, you have been told that the package bb-tools depends on the Blackbox package we are trying to remove. To resolve this, you have two options, one good and one bad: The bad option, which can prove marginally useful during both installation and removal of packages, is to tell RPM to ignore package dependencies. This should never really be used when removing a package, because as in the case of bbtools, other packages will stop working. However, during package installation, you may know for certain that a dependency that RPM is aware of is in fact resolved by a source-compiled library you have installed, or are testing. To tell RPM to not check for dependencies, use the -nodeps parameter as well as the usual rpm -Uvh. The good option (you do want to be a good administrator, don t you ) is to remove the dependent package as well as the package you originally wanted to remove, as shown in the following:
Receive bar code on .net
using .net framework crystal toreceive bar code for asp.net web,windows application
bible:/media/dvd/suse/i586 # rpm -e blackbox bbtools Caution You may have noticed a very important characteristic of package removal, one common with most things in Unix that is, when you are root, you are not warned that you are removing files. This holds true when removing packages. You were not asked to confirm the removal of bbtools and blackbox; rpm assumed you knew what we were doing.
Build 2 of 5 barcode on .net
using .net framework toaccess ansi/aim itf 25 for asp.net web,windows application
Verifying an RPM
Insert 2d barcode on .net
using barcode implement for aspx.net control to generate, create 2d barcode image in aspx.net applications.
If you want to verify whether an RPM is correctly installed, you can use the rpm -V command. Using the verify command will check the files, their permissions, and also if the package s dependencies are installed so that it can function correctly.
Control upc - 13 size with excel spreadsheets
to make ean / ucc - 13 and ean13 data, size, image with microsoft excel barcode sdk
bible:~ # rpm V logcheck bible:~ #
Control data matrix data with office excel
2d data matrix barcode data for office excel
If rpm -V returns nothing, then the RPM itself has been successfully verified and all is well. On the other hand, if something is wrong with the package, you are told what file in the package is different from the original installed file from the RPM.
Visual .net ean / ucc - 13 maker with visual basic.net
using barcode generation for .net framework control to generate, create image in .net framework applications.
bible:~ # rpm V i4l-isdnlog S.5....T c /etc/isdn/isdn.conf bible:~ #
Barcode barcode library on .net
use aspx bar code integrating toinclude barcode in .net
For each file in an RPM that differs from the norm, you receive a letter that dictates what the difference was and why. Table 12-1 details what the differences can be and their respective status letters (or number).
Java barcode generating with java
use java barcode integrated toaccess barcode with java
12 Working with Packages
Visual .net pdf-417 2d barcode recognizer on .net
Using Barcode reader for Visual Studio .NET Control to read, scan read, scan image in Visual Studio .NET applications.
Table 12-1: RPM Verification Output
Control gtin - 13 data in office word
ean-13 supplement 5 data for word documents
Status S M 5 D L U G T Description Different file size. The file mode is different. The MD5 sum differs. If this is a device file, the major or minor number is different. If this is a file link, then its status is different from what is expected. The owner of the file differs. The group owner differs. The modification time differs (the file contents have changed since being installed)
So in the case of the /etc/isdn/isdn.conf example given previously, the current file differs in size (S), its MD5 sum is different (5), and the modification time is different (T). This might lead you to assume that the configuration file has changed since installation.
Note As with the RPM list command (rpm -qa), you can verify all the packages installed on the system with rpm -Va.
Using RPM is not as difficult as most new users think. As we hope you can see, RPM provides a very useful tool for your arsenal, and any competent administrator or user should know how to use it. For more information, see the rpm man page, which lists the full range of what RPM can do.