Date: Fri, 02 Mar 2018 12:13:37 -0330 From: "Jonathan Anderson" <jonathan@FreeBSD.org> To: "Lars Engels" <lme@FreeBSD.org> Cc: "Joe Maloney" <jmaloney@ixsystems.com>, freebsd-hackers@freebsd.org Subject: Re: OpenRC 0.35 for FreeBSD Message-ID: <BE852FF1-A856-4913-93CA-3F7F67DEB855@FreeBSD.org> In-Reply-To: <20180302083756.GH34685@e.0x20.net> References: <CAFvkmYNBtH-MizOLVnSR0c5VuYRpYEDpyWig2x%2By7PM6rQkL=A@mail.gmail.com> <20180302083756.GH34685@e.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 Mar 2018, at 5:07, Lars Engels wrote: > On Thu, Mar 01, 2018 at 08:02:23PM -0500, Joe Maloney wrote: >> [...] >> Why OpenRC? The licensing is right, and it's a way of adding modern >> features to service management without reinventing the wheel. That's >> my sales pitch. > > Hm, that does not convince me. FreeBSD's rc is also BSD licensed and > did > not reinvent any wheel. > Could you maybe give some comparison between OpenRC and our rc? What > does OpenRC better? In addition to asking that question (which is a good one), I think that we need to understand the differences among the various permissively-licensed init/inetd replacements. Personally I think that the time to replace rc is drawing near, but there are a number of options that I've heard of vying for consideration: - finit - jobd (is this still a thing?) - nosh - OpenRC - runit ... not to mention more out-there ideas like launchd. These decisions are never purely technical (as it's a matter of "technically sound" + "someone is willing to do the work"), but I for one wouldn't want to switch something as fundamental as the rc system without having a broad conversation about the merits of the various options and coming to some kind of rough consensus. Also, of course, I have an interest in choosing an init system that can play nicely with sandboxing services, but that's just one consideration among many. Jon -- Jonathan Anderson jonathan@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BE852FF1-A856-4913-93CA-3F7F67DEB855>