Question about the D-Bus uuid

[Soh Kam Yung]

I'm doing some work on an embedded linux-based system running d-bus.
Only apps running in the system can access d-bus (session and system
bus).

In such an environment, should the d-bus uuid be:

1) generated only once (during initial production) and stored permanently, or
2) re-generated on each cold-boot

Since the d-bus is not accessable to external applications, is it okay
to use only one uuid across all devices, if 1) is the correct answer?

Also, are there pointers (in the mailing list archive) that can help
me in understanding the use of the d-bus uuid?

Regards,
Kam-Yung
-- 
Soh Kam Yung
my Google Reader Shared links:
(http://www.google.com/reader/shared/16851815156817689753)
my Google Reader Shared SFAS links:
(http://www.google.com/reader/shared/user/16851815156817689753/label/sfas)