From owner-freebsd-hackers@freebsd.org Fri Mar 2 15:43:38 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE01FF2E02B for ; Fri, 2 Mar 2018 15:43:38 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 643F7874F0; Fri, 2 Mar 2018 15:43:38 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from [134.153.27.124] (unknown [127.0.1.132]) by freefall.freebsd.org (Postfix) with ESMTP id 24ACCFFED; Fri, 2 Mar 2018 15:43:38 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) From: "Jonathan Anderson" To: "Lars Engels" Cc: "Joe Maloney" , freebsd-hackers@freebsd.org Subject: Re: OpenRC 0.35 for FreeBSD Date: Fri, 02 Mar 2018 12:13:37 -0330 X-Mailer: MailMate (1.10r5443) Message-ID: In-Reply-To: <20180302083756.GH34685@e.0x20.net> References: <20180302083756.GH34685@e.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2018 15:43:38 -0000 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