Tuesday 13 January 2015

Re: upstart-local-bridge plan to support systemd

Hey Dimitri,

Dimitri John Ledkov [2015-01-12 19:39 +0000]:
> local-bridge will generate template target, which other units can
> BindsTo & WantedBy:
> e.g.
> persist.sys.usb.config=mtp on the local bridge will
> - stop all android-container@persis.sys.usb.config=*.target
> - start android-container@persist.sys.usb.config=mtp.target [*]

That's the mtp-server package's job, right?

> A job that should only be executed when such a property has value mtp
> will declare:
> [Unit]
> BindsTo=android-container@persist.sys.usb.config=mtp.target

I haven't checked yet, but systemd represents all udev devices with a
"systemd" udev tag as a device unit (see man systemd.device and
systemctl). services can then BindsTo= this (like
systemd-rfkill@.service).

If we actually see USB devices in the Ubuntu part, and not just in the
android container, this might even cut out the middle man and get us
one step closer to not depending on Android? I haven't checked yet
whether we see the device there, though.

Aside from that, I'm sure we'll need the android properties bridge for
other cases still, so many thanks for working on this!

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel