On Tue, Jun 18, 2013 at 07:08:35PM +0400, Dmitry Shachnev wrote: > Thomas said that “In the final setup, Mir will come up early on in the > boot process and act as system-level compositor” — I thought that > would be managed by Upstart. But if that is wrong, things are even > better :)
Starting early just means an upstart job / just another daemon. If Upstart manages the start/stop/restart of a daemon it doesn't require patching. For Mir I assume system-level compositor means that there will be 2 parts: 1. System-level compositor 2. Session "compositor" One who handles the keyboard events and so on. Then another which handles a session (login). This would allow a secure access key (something like CTRL-ALT-DEL in Windows, cannot be caught by another process). I don't know much about Mir though so I am just guessing and assume someone will correct me pretty quickly :P -- Regards, Olav -- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
