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 E72BA13838B for ; Mon, 22 Sep 2014 19:54:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 03853E0B08; Mon, 22 Sep 2014 19:54:36 +0000 (UTC) Received: from resqmta-po-05v.sys.comcast.net (resqmta-po-05v.sys.comcast.net [96.114.154.164]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 589DAE0AD6 for ; Mon, 22 Sep 2014 19:54:35 +0000 (UTC) Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230]) by resqmta-po-05v.sys.comcast.net with comcast id uKuQ1o0034yXVJQ01KuaVy; Mon, 22 Sep 2014 19:54:34 +0000 Received: from crud.chemoelectric.org ([66.41.30.59]) by resomta-po-06v.sys.comcast.net with comcast id uKuE1o00J1GXozm01KuQ5V; Mon, 22 Sep 2014 19:54:33 +0000 Received: by crud.chemoelectric.org (Postfix, from userid 1501) id 3BED3146021E; Mon, 22 Sep 2014 14:54:14 -0500 (CDT) Date: Mon, 22 Sep 2014 14:54:14 -0500 From: Barry Schwartz To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Boycott Systemd Message-ID: <20140922195414.GA30185@crud> References: <20140921143059.c3c16dfdeab6f65280b7caa6@comcast.net> <20140921192043.GA9652@crud> <20140921171301.5f008b3bd12c21c2f8fdd67e@comcast.net> <20140921202600.08d082d88014228172007477@comcast.net> <20140922175846.GA22399@crud> <20140922153022.b0f67e1f35974448d986205b@comcast.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140922153022.b0f67e1f35974448d986205b@comcast.net> User-Agent: Mutt/1.5.22 (2013-10-16) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1411415674; bh=k9F+7QYP3FaeUAuUBw4j6/zJE6CA8A4PIKWUh5Ta/qQ=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=W/AxUWSOhyKhW8tWX5x8wrCe3QnME/CEisetENaVeAptP1PDuoMga2dJciQX+rVrc eUhQrXX+yxbsCCviKYdeuKLm1HQIa1x6HDTKurk9lAcAhIIK5PpfsGGpXq3m0ZFNX6 k7nPP83bVxJSCoBS9+phYRnru3NQW9UuwxYcTz4bSDSEN2esW2Sk7DSPFvc+Mf3azH Nwq63OGqSIFxN//Hq5ux2cPF7b9EfqgCS8JtSCqWC0HY2eO5wwyfJkhZJzanimhhKH mel+s2gvxKtbk3QZoKfuw43FkCX/gt62I6GyPHZof8fP3jfI9ymjexXTkn0OYtCi2X Ar1ZofZTOV6Iw== X-Archives-Salt: c57320c0-44f1-49d8-821d-436ae517e90f X-Archives-Hash: ec80c584687046ce8ca03b58a645980f Frank Peters skribis: > Regarding the booting and configuring of a Linux system, the job can be > either very complex or very simple. For the simple case, is there > technical merit in having to use systemd? I would claim that there > is not. For complex scenarios, by all means utilize systemd. > But let's keep the appropriate tools available for the appropriate job. Yeah, I think people may not be getting my point. For instance, my complaint is not that systemd exists, but, for instance, that someone thought it a good idea to integrate udev and systemd, rather than make the effort to keep them distinct.