|
|
Log in / Subscribe / Register

Another daemon for managing control groups

Another daemon for managing control groups

Posted Dec 5, 2013 12:28 UTC (Thu) by NAR (subscriber, #1313)
In reply to: Another daemon for managing control groups by ovitters
Parent article: Another daemon for managing control groups

Try being specific: why *must* *everything* be reimplemented multiple times?

Exactly: why is an operating system (Linux) implemented when there were (and are) multiple other operating systems?

More seriously: one answer is that specifications can be "verified" by implementing them multiple times by different people and see if the result interoperates. Of course, my gut feeling is that the systemd and cgroup developers are not interested in interoperability or portability or even stable APIs because they hinder progress. Whether one agrees with this position or not, that's an other question.


to post comments

Another daemon for managing control groups

Posted Dec 5, 2013 12:41 UTC (Thu) by ovitters (guest, #27950) [Link]

You're not being specific, you're just answering one question. Where is the specification for every software available on Debian? Where are the multiple implementations for every software?

I was asking why *everything must* be implemented multiple times.

Also your answer implies that systemd has a specification which it is being written against. I'm not aware of such specification. Systemd did create various specifications.

Suggest thinking about my question a little bit more.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds