As part of completing the Device Service, we need to servicify //device/udev_linux. The path to doing this servicification is not immediately straightforward: The library has consumers ranging from extensions to //components to //media to //ui, and it looks like the primary interfaces that it exposes are all synchronous. (The library also has consumers in //device; these I'm not as concerned with as they should sooner or later also end up in the Device Service).
The first step here needs to be understanding the relationship between //device/udev_linux and its consumers in order to shape what the path for servicification should look like.
Comment 1 by blundell@chromium.org
, Nov 7 2017