Ignore:
Timestamp:
2019-08-06T18:18:37Z (5 years ago)
Author:
Matthieu Riolo <matthieu.riolo@…>
Children:
e55741e
Parents:
dd5c623
git-author:
Michal Koutný <xm.koutny+hos@…> (2015-05-11 16:50:40)
git-committer:
Matthieu Riolo <matthieu.riolo@…> (2019-08-06 18:18:37)
Message:

sysman: Add VFS FS server autostart

  • VFS autostart instrumentation removes explicit dependency on FS servers.
  • Compositor service properly named, it's now resolved as implicit dependency.

Conflicts:

boot/Makefile.common
uspace/lib/gui/window.c
uspace/srv/locsrv/locsrv.c
uspace/srv/vfs/vfs.c
uspace/srv/vfs/vfs_ops.c

File:
1 edited

Legend:

Unmodified
Added
Removed
  • uspace/srv/sysman/connection_broker.c

    rdd5c623 r4224ef7  
    3737        sysman_log(LVL_DEBUG2, "%s", __func__);
    3838        async_answer_0(iid, EOK);
    39         // TODO implement
     39        /* TODO implement
     40         *  What exactly? Similar behavior that has locsrv with servers,
     41         *  so that subsequent calls can be assigned to broker. Still that
     42         *  makes sense only when brokers will somehow scope unit/exposee
     43         *  names. Why I wanted this registration?
     44         */
    4045}
    4146
Note: See TracChangeset for help on using the changeset viewer.