- Joined
- May 20, 2013
- Messages
- 16
- Mac
- Classic Mac
- Mobile Phone
It seems that UUID handling has gone through a lot of changes in Chameleon over the past few years and I'm having a hard time figuring out what is the current best approach to ensure a unique and un-changing hardware UUID for my system so that when I reg software that uses UUID, the license will stick, and also for TimeMachine and anything else that uses this identifier.
There is a lot of confusing information on the net about it.
What is the proper way with Chimera 2.0.1 for configuring UUID at the lowest level possible so that TimeMachine, other licenses, etc..anything that is trying to use the hardware UUID, will work consistently?
I only know of two ways to view some UUID stuff. For one thing I see a UUID in system profiler, which it calls "Hardware UUID". But I do not know if that is a hard coded non-unique default from chameleon or where it comes from. Let's call that one XYZ for simplicity. Its not in any plist that I can find.
The other UUID I see is during boot up, I can check the bdmesg log and find several things:
- bootloader says it is reading nvram.00000000-0000-0000-<mymacaddress>.plist
I do not know how that file was created or why its being read, but that that kinda looks like a somewhat unique UUID insomuch that is has my mac address on the end.
- near the end of chameleon boot loading, just before starting Darwin, it says:
"Customizing SystemID with :00000000-0000-0000-0000-<mymacaddress>"
Same as the one above. However, after coming into OSX, system profiler shows a much more normal looking UUID and my mac address is not in it.
so... what is going on there....how can I be sure my UUID is both unique and unchanging and do I need to add anything to any plist somewhere to make sure?
while we're on this topic can someone tell me what that nvram plist file is?
From what I understand, its possible that chameleon may try to use some default value if it can't determine a unique value other ways, and that would not work for me as I would end up with a non-unique UUID. On the other hand I have read about people that have their UUID constantly changing on them every time they boot, which would also be a problem.
There is a lot of confusing information on the net about it.
What is the proper way with Chimera 2.0.1 for configuring UUID at the lowest level possible so that TimeMachine, other licenses, etc..anything that is trying to use the hardware UUID, will work consistently?
I only know of two ways to view some UUID stuff. For one thing I see a UUID in system profiler, which it calls "Hardware UUID". But I do not know if that is a hard coded non-unique default from chameleon or where it comes from. Let's call that one XYZ for simplicity. Its not in any plist that I can find.
The other UUID I see is during boot up, I can check the bdmesg log and find several things:
- bootloader says it is reading nvram.00000000-0000-0000-<mymacaddress>.plist
I do not know how that file was created or why its being read, but that that kinda looks like a somewhat unique UUID insomuch that is has my mac address on the end.
- near the end of chameleon boot loading, just before starting Darwin, it says:
"Customizing SystemID with :00000000-0000-0000-0000-<mymacaddress>"
Same as the one above. However, after coming into OSX, system profiler shows a much more normal looking UUID and my mac address is not in it.
so... what is going on there....how can I be sure my UUID is both unique and unchanging and do I need to add anything to any plist somewhere to make sure?
while we're on this topic can someone tell me what that nvram plist file is?
From what I understand, its possible that chameleon may try to use some default value if it can't determine a unique value other ways, and that would not work for me as I would end up with a non-unique UUID. On the other hand I have read about people that have their UUID constantly changing on them every time they boot, which would also be a problem.
