[Ovirt-devel] [PATCH] Changed the source for UUID to be dmidecode for now.

[Perry N. Myers]

Perry N. Myers wrote:
> Daniel P. Berrange wrote:
>> On Wed, Jun 25, 2008 at 01:58:05PM -0400, Darryl L. Pierce wrote:
>>> -    ovirt-identify-node -s $SRV_HOST -p $SRV_PORT
>>> +    UUID=`/usr/sbin/dmidecode | grep -i uuid | awk '{ print $2; }'`
>>
>> Don't use dmidecode - this is x86 specific and won't work in ia64/ppc I
>> believe. Instead use HAL to get it
> 
> Just to clear up...  We do not have any plans at the current time to run 
> the managed node on IA64/PPC architectures.
> 
>> eg
>>
>>   $ lshal | grep system.hardware.uuid
>>   system.hardware.uuid = 'E9CD5280-4897-11CB-9596-A088B277D677'  (string)
>>
>> This has added benefit of not needing root privileges
> 
> We'll need hal for SAN support in libvirt anyhow, according to Dan B, so 
> go ahead and include hal in the managed node.  This will add about 14MB 
> of dependencies to the uncompressed node image.  We may need to start 
> more aggressively whitelisting out unneeded libraries and binaries.  For 
> example, hal brings in pm-utils which brings in radeontool.  I can't 
> imagine that we'd need radeon support in the managed node.  If anything 
> we'd be using vesa probably if we ran X for local console support.

Here's the list of dependent RPMs that hal is bringing in on the current 
managed node image:

    1:libsmbios
    2:smbios-utils
    3:vbetool
    4:usermode
    5:radeontool
    6:kbd
    7:hdparm
    8:libusb
    9:hal-libs
   10:dmidecode
   11:cryptsetup-luks
   12:acl
   13:ConsoleKit
   14:hwdata
   15:pciutils
   16:pm-utils
   17:hal
   18:hal-info

Perry