http://activitystrea.ms/schema/1.0/commenthttps://bsd.network/users/lattera/statuses/100169508319783771New comment by lattera@bsd.network<p><a href="https://bsd.network/tags/bsdcan" class="mention hashtag" rel="tag">#<span>BSDCan</span></a> (Tragedy of <a href="https://bsd.network/tags/systemd" class="mention hashtag" rel="tag">#<span>SystemD</span></a>): What can we get from SystemD?</p><p>We shouldn't adopt it, but what ideas could we borrow?</p><p>First-class message transport would be cool. By placing the message transport in the kernel, the kernel could enforce identity management in messages.</p><p>An RPC framework.</p><p>A service lifecycle.</p><p>All of these things [and more that I couldn't type fast enough] would give us automation via API.</p>1180224http://activitystrea.ms/schema/1.0/post2018-06-08T13:43:18+00:002018-06-08T13:43:18+00:00http://activitystrea.ms/schema/1.0/personhttps://bsd.network/users/latteralattera@bsd.network<p>HardenedBSD cofounder, Emerald Onion Advisory Board member, OPNsense Core Team member, SoldierX High Council, all around infosec wonk.</p>lattera@bsd.networkShawn Webb<p>HardenedBSD cofounder, Emerald Onion Advisory Board member, OPNsense Core Team member, SoldierX High Council, all around infosec wonk.</p>tag:nu.federati.net,2018-06-08:objectType=thread:nonce=1fbb2f3f497bfcee