Just been through the azure python code - my intiial impressin was wrong, its not the chnage to the periphlist output which is the issue. Instead its the fact that a simple 'devlist' now puts the pass devices first in the list, and the azure waagent uses the first listed device when it initially looks for the device. A simple fix for this is to reject what that call returns and then to drop back to using periphlist, nd this is what I have done, but it would be nice to fix it properly.
What was the reason behind the chnage of ordering anyway ? Any script which naiively parses the output of camcontrol devlist will hit a similar issue potentially ? It's not exactly a bug, but... -pete. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
