|
Hi All, Just an advisory, which may or may not affect you. Since inception, /etc/linuxcnc has contained a hard coded UUID under the 'MKUUID=' field This despite the text above it stating that all machines should have a unique MKUUID to enable the zeroconf browsing for particular instances to work. This has now actually caused problems, with some users exploring the networked communications aspect of machinekit, as perhaps it was originally envisaged. So, from today for RIP builds and as of machinekit package serial 'machinekit_0.1.1547649222.gitc44e93e-1' onwards, there are a couple of wrinkles to be aware of, if you actually intend using the MKUUID for anything. RIP builds A fresh clone will generate a new UUID when built. If you want to use a particular UUID, keep it in a separate system file called /etc/linuxcnc/mkuuid [1] and manually edit RIP/etc/linuxcnc/machinekit.ini to use it. When you rebuild the machinekit.ini UUID will be preserved, however be aware doing a complete ' git clean -xdf && ./autogen.sh && ./configure' will wipe it. ([1] For RIPs, this file is just a suggested failsafe storage option for now, it will actually be used by package installs) Package installs A package install onto a blank system will generate a new UUID. If you are updating and do not purge your configs:
For the vast majority of users, this change will have no impact, their configs just use whatever UUID is in machinekit.ini, if at all, without consequence. regards -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout. |
- [Machinekit] machinekit.ini and MKUUID [email protected]
