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 743A01381F3 for ; Sat, 22 Jun 2013 10:07:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6D18BE0B00; Sat, 22 Jun 2013 10:07:31 +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 7BEA8E0A8F for ; Sat, 22 Jun 2013 10:07:30 +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 9D1BB33E5EB; Sat, 22 Jun 2013 10:07:28 +0000 (UTC) Message-ID: <1371895644.30388.7.camel@localhost> Subject: Re: [gentoo-dev] Re: eselect init From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Cc: lxnay@gentoo.org, williamh Date: Sat, 22 Jun 2013 12:07:24 +0200 In-Reply-To: References: <51A08A68.3020900@gentoo.org> <20130620205609.GB23719@linux1> <20130621043959.7eae0921@gentoo.org> <51C42B33.9090709@gentoo.org> <1371814006.2486.10.camel@localhost> <51C43DEA.6000006@gentoo.org> <20130621143657.GA26044@linux1> <1371829739.2486.20.camel@localhost> 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: 7bit X-Archives-Salt: fb9f4997-c550-4ec7-b133-d0fe60356cca X-Archives-Hash: 285af4c2941c5a4329b8b099d4159584 After talking with WilliamH yesterday, I have this opinion: - Playing with /sbin/init (instead of /sbin/einit) has two interesting advantages: 1. For example, I now have init=/sbin/e4rat-preload in my grub.conf, if I do a typo, it would fallback to /sbin/init. If /sbin/init is provided by sysvinit, people running other init providers could have problems. This wouldn't occur if /sbin/init has been changed to use desired init system. 2. Tools like e4rat or bootchart launch /sbin/init, if I switch to systemd, I would need to edit separate configuration files for each tool to point to new init. This wouldn't occur if we "play" with /sbin/init => we would only change init in one place - I have two doubts: 1. Why do we need a wrapper instead of changing symlinks? 2. Why Fabio chose to move sysvinit to subdirectories... wouldn't be much simpler to simply rename /sbin/init to /sbin/sysvinit?