From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 9EE681381F3 for ; Fri, 21 Jun 2013 11:26:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 69D69E09EF; Fri, 21 Jun 2013 11:26:51 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 81699E0957 for ; Fri, 21 Jun 2013 11:26:50 +0000 (UTC) Received: from [192.168.1.204] (39.164.16.95.dynamic.jazztel.es [95.16.164.39]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 1C7A933E469 for ; Fri, 21 Jun 2013 11:26:48 +0000 (UTC) Message-ID: <1371814006.2486.10.camel@localhost> Subject: Re: [gentoo-dev] eselect init From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Date: Fri, 21 Jun 2013 13:26:46 +0200 In-Reply-To: References: <51A08A68.3020900@gentoo.org> <20130620205609.GB23719@linux1> <20130621043959.7eae0921@gentoo.org> <51C42B33.9090709@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: f0a30b8d-6a05-468c-bb2f-ae5685958d27 X-Archives-Hash: 6d85250309d78981a28a4e5d59d104e9 El vie, 21-06-2013 a las 13:19 +0200, Fabio Erculiani escribió: > For me, the big selling points of eselect-init are: > > 1. as release engineer, i can prepare images that use either systemd > or openrc (at present time these are the two supported options) and do > it reliably, programmatically. > 2. as distro maintainer, i can roll out a migration path from openrc > to systemd (or vice versa). The properties of this migration path I am > looking for are reliability and "atomicity". Basically, once you move > logind/consolekit detection to runtime (and believe it or not, many > upstream just get it wrong), and have feature parity in the systemd > units available (wrt openrc initscripts), switching over is a matter > of 2 (soon 1) commands. > > Both of them are quite important, because there are scenarios in where > systemd fits better than openrc, and scenarios in where openrc is a > better fit (older kernels, production system with custom init scripts > that are not worth the porting, etc). > Making the switch between openrc and systemd easy is a big win (for > both developers, distro maintainers, users) and makes Gentoo more > attractive, but this is another topic... > Thanks for the explanation. But I think that, currently, the only remaining "objection" is whether play with /sbin/init (that needs sysvinit to be changed if I don't misremember) or with /sbin/einit. Looks like mgorny has shown some problems on relying on "einit" instead of plain "init" regarding to fallback :/