minor bug in libsmbios-0.13.2 rpm

[Linda W.]

I ran into a small snag in the rpm.

At some point there is an attempt to call "scripts/<xxx>.py" a python 
script.

It "might" be safer if it was called with "python 
scripts/<scripname>.py", as
when the rpm was unpacked into the packages/build dir, they didn't have the
execute bit set.

At first I wasn't sure if the pathname in the script's first line
was where my path was, but that wasn't the problem -- just a matter of
chmod+x'ing *.py in the script dir.

While that fixed my problem, I don't know if the path in the scripts
is dynamically found with config.  Assuming the first line in the scripts
with the python pathname is static, calling the scripts with "python scrip"
syntax will solve both problems (scripts not being executable and if a user
has python in some location other than /usr/bin).

BTW, for what its worth, I tried "lm_sensors" and it doesn't seem to be
able to find any temp probes for my dell systems. 

I ran dumpCmos to see if tokens 0xF001 or 0xF00n (or 0xF00[*])
were present.  They were not.

I don't think everything is in place for my local libsmbios gen.
When I use the one installed in the system, I see entries that make
varying amounts of sense, but the one I generated in the supported-bins
dir doesn't seem to have any interpretations of the data.

May not be important -- I probably don't have things setup in some write
order/position somewhere. :-)

linda w