On 02/05/2015 00:54, Michael Roth wrote: >> > >> > What about unparenting children devices in the device's unrealize >> > callback? It sucks that you have to do it manually, but using stale >> > canonical paths isn't the nicest thing either. > That does seems to do the trick. It felt wrong when I first looked at > it because in some cases the children attach themselves to the parent > without making making the parent aware,
Can you point to an example? The parent "owns" its property namespace, so it would be wrong for a child to attach itself unbeknownst to the parent. There are a couple cases where an object adds a property to another object, e.g. the rtc-time property of /machine, but in that case the property is a well-known name whose setting is "outsourced" by /machine to the device. Paolo
