dbus/doc dbus-specification.xml,1.44,1.45

[Havoc Pennington]

Update of /cvs/dbus/dbus/doc
In directory kemper:/tmp/cvs-serv28036/doc

Modified Files:
	dbus-specification.xml 
Log Message:
2006-10-26  Havoc Pennington  <hp at redhat.com>

	* doc/dbus-specification.xml: clarify the UUID text slightly

	* dbus/dbus-sysdeps-pthread.c: check for and mostly abort on
	pthread errors. Add DBusMutexPThread and DBusCondVarPThread 
	in preparation for being able to extend them for e.g. recursive
	mutexes.



Index: dbus-specification.xml
===================================================================
RCS file: /cvs/dbus/dbus/doc/dbus-specification.xml,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -d -r1.44 -r1.45
--- dbus-specification.xml	21 Oct 2006 17:08:08 -0000	1.44
+++ dbus-specification.xml	27 Oct 2006 02:17:42 -0000	1.45
@@ -2311,11 +2311,24 @@
         UUID representing the identity of the machine the process is running on.
         This UUID must be the same for all processes on a single system at least
         until that system next reboots. It should be the same across reboots 
-        if possible, but may change due to reconfiguration or hardware changes.
+        if possible, but this is not always possible to implement and is not 
+        guaranteed.
         It does not matter which object path a GetMachineId is sent to.  The
         reference implementation handles this method automatically.
       </para>
       <para>
+        The UUID is intended to be per-instance-of-the-operating-system, so may represent
+        a virtual machine running on a hypervisor, rather than a physical machine.
+        Basically if two processes see the same UUID, they should also see the same
+        shared memory, UNIX domain sockets, process IDs, and other features that require 
+        a running OS kernel in common between the processes.
+      </para>
+      <para>
+        The UUID is often used where other programs might use a hostname. Hostnames 
+        can change without rebooting, however, or just be "localhost" - so the UUID
+        is more robust.
+      </para>
+      <para>
         The UUID must contain 128 bits of data and be hex-encoded (meaning, the hex 
         string contains 32 ASCII characters). The hex-encoded string may not contain 
         hyphens or other non-hex-digit characters, and it must be exactly 32 characters long.
@@ -2323,13 +2336,6 @@
         since the UNIX epoch in the last 32 bits of the UUID, and to put randomly-generated bits
         in the first 96 bits of the UUID.
       </para>
-      <para>
-        The UUID is intended to be per-instance-of-the-operating-system, so may represent
-        a virtual machine running on a hypervisor, rather than a physical machine.
-        Basically if two processes see the same UUID, they should also see the same
-        shared memory, UNIX domain sockets, process IDs, and other features that require 
-        a running OS kernel in common between the processes.
-      </para>
     </sect2>
 
     <sect2 id="standard-interfaces-introspectable">