base on The InitWare Suite of Middleware allows you to manage services and system resources as logical entities called units. Its main component is a service management ("init") system.  **Please note that InitWare is still alpha software**. But all disclosed security concerns have now been addressed. Running InitWare as an auxiliary service manager under NetBSD can now, then, be regarded as safe; but beware relying on this in production until a first stable release is made. The InitWare Suite of Middleware allows you to manage services and system resources as logical entities called units. It runs on NetBSD, GNU/Linux, and all the other modern BSD systems. Units are automatically scheduled by a job scheduler according to their dependency specifications. A user session manager facilitates tracking of users' login sessions, with each user provided their own dedicated service manager. Finally the InitWare System Log provides a system-wide event log aggregating diverse log sources. The Suite may run either as an init system or as an auxiliary service management system under another init system. InitWare originates as a fork of systemd and retains compatibility with many systemd interfaces, even on non-Linux platforms. | Platform | Build Status | |----------|--------------| |GNU/Linux (Alpine) |[](https://builds.sr.ht/~netbsduser/initware/commits/alpine.yaml?)| |FreeBSD |[](https://builds.sr.ht/~netbsduser/initware/commits/freebsd.yaml?)| |NetBSD |[](https://builds.sr.ht/~netbsduser/initware/commits/netbsd.yaml?)| |OpenBSD |[](https://builds.sr.ht/~netbsduser/initware/commits/openbsd.yaml?)| ## Frequently Asked Questions #### How does InitWare differ from systemd? In three ways: InitWare is highly portable, it is more modular, and it is of a much more clearly-defined scope. See [The InitWare philosophy]. Some components of systemd failing to provide compelling benefits are dropped; see [Dropped components]. [The InitWare philosophy]: https://github.com/InitWare/InitWare/wiki/The-InitWare-philosophy [Dropped components]: https://github.com/InitWare/InitWare/wiki/Dropped-components #### How compatible is InitWare with systemd? Unit-files, the `systemctl`, `loginctl`, and `journalctl` commands (provided as `svcctl`, `sessionctl`, and `syslogctl` respectively), the systemd1 and Login1 D-Bus APIs, the sd_notify API, the journald stream and datagram socket protocols, and several other interfaces are largely supported on all ports. Some details differ by port. See [Systemd compatibility]. [Systemd compatibility]: https://github.com/InitWare/InitWare/wiki/Systemd-compatibility #### On what platforms does InitWare run? InitWare is native to NetBSD. It runs on NetBSD, FreeBSD, and GNU/Linux - its first-class targets - as an init system; on macOS, DragonFly BSD and OpenBSD, it runs as an auxiliary service manager. See [Support matrix]. [Support Matrix]: https://github.com/InitWare/InitWare/wiki/Support-Matrix #### Under what licence is InitWare released? Most code is under the GNU Library GPL v2.1, some of it is under liberal licences. #### How does one build InitWare? Install the dependencies first: these are a C toolchain, cmake, gperf, m4, awk, pkg-config or pkgconf, and on BSD platforms, libinotify. Then run: ```git submodule update --init --recursive && cmake && make && make install``` See [Building] for further details. [Building]: https://github.com/InitWare/InitWare/wiki/Building #### Where will InitWare go from here? Check the Issues and Projects tabs, or the [Roadmap](https://github.com/InitWare/InitWare/wiki/Roadmap). #### How can I contribute? See [Contributing](https://github.com/InitWare/InitWare/wiki/Contributing). #### Where can I find out more? Check [the Wiki]. The [Myths and Truths] page is a good place to start. [The Wiki]: https://github.com/InitWare/InitWare/wiki [Myths and Truths]: https://github.com/InitWare/InitWare/wiki/Myths-and-Truths ", Assign "at most 3 tags" to the expected json: {"id":"13357","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"