From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ccr.org (static-96-255-157-131.washdc.fios.verizon.net [96.255.157.131]) by huchra.bufferbloat.net (Postfix) with ESMTP id 632E0201B02 for ; Thu, 23 Jan 2014 09:58:18 -0800 (PST) Received: by ccr.org (Postfix, from userid 1001) id 1A127119C52; Thu, 23 Jan 2014 13:07:44 -0500 (EST) Received: from ccr.org (localhost [127.0.0.1]) by ccr.org (Postfix) with ESMTP id 192BA119C19 for ; Thu, 23 Jan 2014 13:07:44 -0500 (EST) To: cerowrt-devel@lists.bufferbloat.net In-reply-to: References: Comments: In-reply-to cerowrt-devel-request@lists.bufferbloat.net message dated "Wed, 22 Jan 2014 12:00:01 -0800." X-Mailer: MH-E 8.4; nmh 1.2; GNU Emacs 24.2.1 Date: Thu, 23 Jan 2014 13:07:44 -0500 Message-ID: <88756.1390500464@ccr.org> From: Mike O'Dell Subject: Re: [Cerowrt-devel] Cerowrt-devel Digest, Vol 26, Issue 49 X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 17:58:18 -0000 re: systemd vs procd vs etcd... If other distros have largely converged to systemd, is it worthwhile for CeroWrt to do something different? This assumes that the daemons in question have already or are in process of becoming systemd-compatible. If that is indeed the case, is it really worthwhile to spend time supporting something different? not trying to re-open old wounds, just wondering how many different approaches are actually "better" in some material way and how many are just "different". I've watched Apple go through the pains of moving all the lifetime control of services to launchd. It took a long time to justify it being different, but now that it's done, the fact there is only ONE place to look is really a feature. One thing, for instance, is that the Xserver and its helpers all start automagically when an X11 binary is run. Likewise, making a daemon periodic instead of continuous is changed in just one place - not moved from one to another. My point is that making is truly better, as opposed to "just different, yet again" requires doing the whole job, not just a different subset of it. So if there is a base of systemd-capable versions of the daemons in question, just use those to avoid the work. or do the whole job an import launchd. (which i'm *not* lobbying for!) -mo