Todd Zullinger wrote:
david walcroft wrote:
Pardon my ignorance but what are my options.
rpm {-V|--verify} [select-options] [verify-options]
A little further down in the rpm manpage, the select-options and
verify-options are given:
select-options
[PACKAGE_NAME] [-a,--all] [-f,--file FILE]
[-g,--group GROUP] {-p,--package PACKAGE_FILE]
[--fileid MD5] [--hdrid SHA1] [--pkgid MD5] [--tid TID]
[--querybynumber HDRNUM] [--triggeredby PACKAGE_NAME]
[--whatprovides CAPABILITY] [--whatrequires CAPABILITY]
...
verify-options
[--nodeps] [--nofiles] [--noscripts]
[--nodigest] [--nosignature]
[--nolinkto] [--nomd5] [--nosize] [--nouser]
[--nogroup] [--nomtime] [--nomode] [--nordev]
Further down that that, the PACKAGE SELECTION OPTIONS and VERIFY
OPTIONS sections got into more detail about each of these options.
For the purposes of finding out whether something was wrong with your
hal or hal-libs packages, you don't need any particular options except
for the command I suggested (rpm -V hal hal-libs). That command will
verify that the packages hal and hal-lib are installed and that the
contents of those packages matches what was installed by rpm
originally.
OK I found some more reading and found "rpm -vv"
There was nothing about 'hal'
rpm -vv will just show the help if run by itself. Were you adding
some other options in addition to -vv?
As I see it, to determine what you're having a problem starting and
stopping the hal daemon, you want to first verify that the hal
packages are installed and that they match what was installed by rpm
(using the rpm -V command above). If that command produces no output,
then all should be well with your install. The next step would be to
see if there is any information in the system logs about the failures.
Step 3: ?? Step 4: Profit! :)
Rpm -V hal shows nothing
[david@reddwarf ~]$ sudo rpm -V hal hal-libs
[david@reddwarf ~]$
david
