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 2D28113838B for ; Mon, 22 Sep 2014 05:27:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4589BE099F; Mon, 22 Sep 2014 05:27:38 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 80A1DE0978 for ; Mon, 22 Sep 2014 05:27:37 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XVw9v-0008Hv-5G for gentoo-amd64@lists.gentoo.org; Mon, 22 Sep 2014 07:27:35 +0200 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 22 Sep 2014 07:27:35 +0200 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 22 Sep 2014 07:27:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: Boycott Systemd Date: Mon, 22 Sep 2014 05:27:23 +0000 (UTC) Message-ID: References: <20140921132548.d4ad54724473a2aeee688daa@comcast.net> <20140921143059.c3c16dfdeab6f65280b7caa6@comcast.net> <20140921192043.GA9652@crud> <20140921171301.5f008b3bd12c21c2f8fdd67e@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=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT d447f7c /m/p/portage/src/egit-src/pan2) X-Archives-Salt: bb273d6a-25a0-42ac-b1f5-494c97e4c4e9 X-Archives-Hash: d4af448efad3fb0dd43b1c32b1ac33a8 Canek Peláez Valdés posted on Sun, 21 Sep 2014 17:28:48 -0500 as excerpted: > Or even simpler than that: If I wrote a daemon, with SysV I could not > reliable write an script to starting it and stopping it in *all* > distributions. With systemd that actually works. IMO this the the big reason why upstreams are supporting systemd; it's a small, often trivial, file, with a lot of bang for the buck. Ship any other initscript and you cover a single distro. Ship a systemd unit file or two and you cover a half-dozen rather major unrelated distros and growing, along with most of their derivatives. Sure it's an upstream reference file that individual distros can and reasonably often do modify, but it's a reference file virtually guaranteed to work as-is on nearly all those distributions, and you just can't get that elsewhere, full-stop. Meanwhile, for me as a gentoo user one of the biggest benefits of systemd is that once it's the general standard pretty much everywhere I won't have the problem of having to learn something different to maintain for instance my openwrt-based router, as it'll be the same general init- system on my main systems and on my router. My biggest problem with the router right now is that it's not using an init system I'm familiar with, and having once gone thru everything and understood how it worked well enough to be comfortable working with the configuration, and then having configured it, I promptly forgot all that stuff once I got it working and had no need to screw with it any longer. Now it's seriously outdated, but I don't want to deal with updating it and having to go thru all that stuff to learn its special-purpose init setup once again, just to get it working and be able to forget about it again. I'm *REALLY* looking forward to the day when it's all standardized on systemd and I can put the same systemd knowledge I use while maintaining my general systems to work when I update openrc as well, and other than the few unique unit-files, I'll "just understand it" and not have to worry about relearning all that every time I decide it's time to upgrade the router again. Of course the same thing applies if I decide to make a job out of my currently and long-term hobby of Linux. Gentoo's openrc is certainly rather niche knowledge and won't help me much with the statistically more likely chance that my potential employer has standardized on centos/sle[ds]/ubuntu-server/debian/whatever. But my gentoo systemd knowledge will "just transfer", being as useful on any of them once everybody's switched, as on gentoo. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman