From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1S9OYx-0001SN-AB for garchives@archives.gentoo.org; Sun, 18 Mar 2012 22:26:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3C211E0BB5; Sun, 18 Mar 2012 22:26:22 +0000 (UTC) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.183]) by pigeon.gentoo.org (Postfix) with ESMTP id B326CE0B8B for ; Sun, 18 Mar 2012 22:24:18 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AokGAKU/KE9FpY2y/2dsb2JhbACBX48mjVV5iHCeGYYZBJROhkuECQ X-IronPort-AV: E=Sophos;i="4.73,1,1325480400"; d="scan'208";a="168768378" Received: from 69-165-141-178.dsl.teksavvy.com (HELO waltdnes.org) ([69.165.141.178]) by ironport2-out.teksavvy.com with SMTP; 18 Mar 2012 18:24:17 -0400 Received: by waltdnes.org (sSMTP sendmail emulation); Sun, 18 Mar 2012 18:23:37 -0400 From: "Walter Dnes" Date: Sun, 18 Mar 2012 18:23:37 -0400 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: systemd? [ Was: The End Is Near ... ] Message-ID: <20120318222337.GA11848@waltdnes.org> References: <709768995.843751.1331957483491.JavaMail.open-xchange@email.1and1.com> <20120317115300.GB3615@acm.acm> <20120318151502.36891b0a@khamul.example.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120318151502.36891b0a@khamul.example.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 2407e8bd-bb19-4e95-8555-34f395c116c5 X-Archives-Hash: b348248a86fe35540ec47b4a4d93d79c On Sun, Mar 18, 2012 at 03:15:02PM +0200, Alan McKinnon wrote > Here's what I want: > > When the machine starts, I want services X, Y and Z to run. The > software figures out what order they must start in and how the deps > work. Clean, neat, easy. systemd is like Captain Picard of STTNG (Start Trek The Next Generation) always saying "make it so". *HOW DO YOU "MAKE IT SO"? That intelligence has to be somewhere. So what alternative do you propose? A bash or ash script is more guaranteed to run than a binary. Shoving all that "intelligence" into the service itself, means that the service has to start up in order to determine whether it's safe for the service to start up. What's wrong with this picture? And if systemd is so great, here's my supersystemd #!/bin/bash ... ... /etc/init.d/net.lo start /etc/init.d/net.eth0 start /etc/init.d/net.sshd start etc, etc, etc -- Walter Dnes